3bu_51500_5301_dtapa.pdf

THALES GROUP INTERNAL

System/Segment Specification

System Subsystem Specification

OMC (BFZ)

TML (ZVL)

ÖBB

BFZ

Thales Austria GmbH

3BU 51500 5301 DTAPA / 03 / RL

www.thalesgroup.com

All rights reserved. Passing on and copying of this document, use and communication of its contents

not permitted without written authorization. © Thales Austria GmbH

www.thalesgroup.com


© Thales Austria GmbH / 105 3BU 51500 5301 DTAPA / 03 / RL

Template: 83530171-DOC-AUT-EN-002 THALES GROUP INTERNAL

COVER SHEET

Level of Sensitivity THALES GROUP INTERNAL

Document Type System/Segment Specification

Document Code 305

Title 1 System Subsystem Specification

Title 2 OMC (BFZ)

Title 3 TML (ZVL)

Class 1 ÖBB

Class 2 BFZ

Class 3 Thales Austria GmbH

Class 4

TRN / Version / Status

BI 1 / Edition / Status 3BU 51500 5301 DTAPA / 03 / RL

BI 2 / Edition / Status

Date 2013-10-09

Change Note

Special Tag

Local Identifier

Actors Name & Role

Written by

Thales Austria/TDE RD

M. Zirwes RM

R. Samsegger

Verified by Thales Austria/ES

QAM A. Haslinger

Approved by Thales Austria/TDE

PDA G. Grünsteidl


3BU 51500 5301 DTAPA / 03 / RL / 105

Template: 83530171-DOC-AUT-EN-002

© ThalesAustria GmbH


Versions and Change History Version Edition Date Written by Verified by Approved by Change Description

01 2012-05-15 Thales Austria/TDE RD

M. Zirwes

Thales Austria/ES QAM

A. Haslinger

Thales Austria/TDE PDA

G. Grünsteidl

First edition


M. Zirwes


A. Haslinger


G. Grünsteidl

See chapter 4.2


M. Zirwes RM

R. Samsegger


A. Haslinger


G. Grünsteidl

See chapter 4.3




Table of Contents 1 SCOPE ....................................................................................................................................................... 6

1.1. IDENTIFICATION ..................................................................................................................................... 6 1.2. SYSTEM OVERVIEW ............................................................................................................................... 6 1.3. DOCUMENT OVERVIEW .......................................................................................................................... 8 1.4. ABBREVIATIONS ..................................................................................................................................... 8

2 REFERENCED DOCUMENTS .................................................................................................................. 9

2.1. TECHNICAL LITERATURE ........................................................................................................................ 9 2.2. INFORMATION FOR DOCUMENT GENERATION .......................................................................................... 9

3 REQUIREMENTS ..................................................................................................................................... 10

3.1. HIGH LEVEL REQUIREMENTS ................................................................................................................ 10 3.1.1. System Capability Requirements ......................................................................................................... 10 3.1.2. System External Interface Requirements ........................................................................................... 13 3.1.3. System Internal Data Requirements ................................................................................................... 17 3.1.4. Adaptation Requirements ..................................................................................................................... 17 3.1.5. Safety Requirements ............................................................................................................................. 17

3.2. LOW LEVEL REQUIREMENTS ................................................................................................................. 18 3.2.1. System Capability Requirements ......................................................................................................... 18 3.2.2. System External Interface Requirements ........................................................................................... 87 3.2.3. System Internal Data Requirements ................................................................................................... 95 3.2.4. Adaptation Requirements ..................................................................................................................... 95 3.2.5. Safety Requirements ............................................................................................................................. 95

4 CHANGE HISTORY ................................................................................................................................. 96

4.1. EDITION 01 ......................................................................................................................................... 96 4.2. EDITION 02 ......................................................................................................................................... 96

4.2.1. New Requirements ................................................................................................................................ 96 4.2.2. Modified Requirements ......................................................................................................................... 96 4.2.3. Deleted Requirements ........................................................................................................................... 97

4.3. EDITION 03 ......................................................................................................................................... 97 4.3.1. New Requirements ................................................................................................................................ 97 4.3.2. Modified Requirements ......................................................................................................................... 98 4.3.3. Deleted Requirements ......................................................................................................................... 102

5 NOTES ................................................................................................................................................... 103

APPENDIX A INDEX OF REQUIREMENTS ........................................................................................... 104


3BU 51500 5301 DTAPA / 03 / RL / 105




1 Scope

1.1. Identification

1.2. System Overview Within the OMC the TML Service is responsible for the management of the train numbers and other related information. A train number can be set / deleted by various services (manually by the command set on the OMC’s own EBO, ARAMIS-RBP) but the TML service is the only service, which really decides, if the command will be accepted and performed. TML service shall also be capable of the automatic train number shift as a result of the current train movement. The TML Service provides other services with current train number data in order to support their function, e.g. inform the ATRS about current train position to allow this service the automatic train route setting according to the schedule. The TML Service receives commands either directly from the command source service (OMC’s own EBO) or via RBP and sends the corresponding command acknowledge on the same way. The TML Service receives also train number messages via RBP, if they are used similarly to commands as a method of train number setting / update. The TML Service receives element state messages only via ILCs. The only exception is additional train information (such as RBC registration status), which shall be provided directly by ARAMIS, not via ILCs. The TML Service distributes train number messages as notification about train number operation performed via ILC and RBP, there is no direct communication with destination service, which shall get informed. TML answers the RBC status request for particular train number received from ATRS by current registration status. Commands (train number commands) and messages (command acknowledge, train number message, element state messages) shall be capable to transmit at least the information contained in corresponding commands / messages according to X25-protocol. (“Message” used to point up the relation to X25-Protocol. Not to be understood as a message at a low level in the SIL-0 context, e.g. JMS message.) Further the TML Service employs general OMC Services Components (e.g. Administration and Diagnosis, Protocol, Infrastructure Service).




TML

ILC

Administration & Diagnosis

Infrastructure

Protocol

ARAMISTrain info

ILP

Periphery

OMC-EBO

RBP

Other System

Interlocking System

ARAMIS-TML Manager

CMD + ACK

CMD + ACKMSG

Element State

CMD + ACK

MSG

ETCS-Info + ACK

ETCS-Info + ACK

Element State

Element State

Element State

MSG

IF-06

Database

IF-08

IF-23

IF-19

IF-10

IF-24

IF-09

IF-30

IF-30

IF-11

IF-30

IF-04

IF-40

ATRS

RBC StatusRequest / Response

IF-30

MSG MSG

Figure 1 Position of the TML Service in the OMC system and the communication with other services

• It is possible, that there are multiple TML instances in an OMC at the same time, if configured so. Each TML instance is running redundantly.

• A TML instance can manage a group of stations, so it will communicate with multiple ILC instances. • To simplify the figure, there is always only a single instance shown (TML, ILC, ILP etc.). • As it is possible that not all stations managed by one TML instance are also managed by one RBP

instance, it is supposed, that the TML instance shall communicate with multiple RBP instances in the figured way.

• Train number commands referred in the figure as “CMD”, train number messages and element state messages as “MSG”.

• “Other System” may be Railbroker, other OMC, standalone interlocking system etc., which is (based on configuration) capable to force the TML Service to set / update train numbers.


3BU 51500 5301 DTAPA / 03 / RL / 105




1.3. Document Overview The purpose of this document is to list the capabilities of the system under development at a high common abstraction level and in a language understood by all project participants. This document shall list all necessary capabilities for the OMC TML application. For High Level Requirements see Chapter 3.1. For further details see Low Level Requirements in Chapter 3.2.

1.4. Abbreviations ARAMIS Advanced Railway Automation, Management and Information

System ATRS Automatic Train Routing System BFZ Betriebsführungszentrale (= OMC) BOS Betriebsoperationssystem EBO Einheitliche Bedienoberfläche ETCS-L2 European Train Control System Level 2 GUI Graphical User Interface ILC Interlocking Cache ILP Interlocking Proxy JMS Java Messaging Service LZB Linienzugsbeeinflussung NADA no actual data available OMC Operational Management Center (= BFZ) PH Pflichtenheft RBP Railbroker Proxy RZUE Rechnergestütze Zuglaufueberwachung SIL-4 Safety Integrity Level 4 TML Train Monitoring Logic ZVL Zugverfolgungslogik




2 Referenced Documents

2.1. Technical Literature [SSDD] System/Subsystem Design Description BFZ 2.0

3BU 51500 1036 DSAPC, Ed. 02 [PH ZNM] Pflichtenheft ESTW Zugnummernmeldung

3BU 20000 0007 DSAPC, Ed.03 [PH BOS ZN] Pflichtenheft Betriebsoperationssystem BOS

Zugnummereinwahlstelle 3BU 20000 0010 DSAPC, Ed. 02

[SS ETCS] Schnittstellenbeschreibung BFZ IF-06 ETCS Einfahrverhinderung Nummer 3BU 51500 1087 PBAPC, Ed. 01

[SRS] System Requirements Specification BFS 2.0 3BU 51500 1033 DTAPC, Ed. 04

[X25 PH] Pflichtenheft X25-Schnittstelle 3BU 20000 0011 DSAPC, Ed. 08

[IF-11-ICD] IF-11 Interface Control Description 3BU 51500 4002 PBAPA, Ed. 04

[GCD-SIL-0] General SIL-0 Communication Description TBD

[SSDD GMED] System/Subsystem Design Description Generic Message and Element Definitions 3BU 51500 1069 DSAPA, Ed. 04

[SSDD INFRA] System/Subsystem Design Description Infrastructure OMC 2.0 3BU 51500 3606 DSAPA, Ed. 01

[IF-08-LIF] Interface Design Description IF-08 Logging Interface 3BU 51500 3601 PBAPA, Ed. 02

[X25-IF] Spezifikation X25 Schnittstelle / Specification X25 Interface 3BU 15000 4167 DTAPQ, Ed. 21

[IF-09-ADM IF-10-STAT] Interface Control Description IF-09 Administration / IF-10 Status 3BU 51500 3602 PBAPA, Ed. 02

2.2. Information for Document Generation The present document was generated by using IBM™ Rational DOORS. Settings applied: DOORS/RMF Version: 9.3.0.7/v6.1.0.0a DOORS/RMF Module Name: TML-SSS DOORS/RMF Module Version (Baseline): 3.0 (Ed03) DOORS/RMF Module Path: /TML/Specification DOORS/RMF Export View: WEXP DEV_002 DOORS/RMF Current Filter: (TA Req Status != deleted) AND (Column 'Filter

Sub:noexport' contains 'false' (case sensitive)) DOORS/RMF Export Options 1: 2,false,2,0,false,false,0,true,false, DOORS/RMF Export Options 2: true,false,true,2,false,false,true,PostprocessAllStyles,, DOORS/RMF Export Options 3: ,true,true,true,false,false,true,false,true, DOORS/RMF Export Options 4: 0,###,===,false,false,false,false,false, DOORS Document Template Name: V:\PROJECTS\ReqMng\DOORS\Word Export\DOORS-

EXPORT-TEMPLATES\BFZ\SRS\3BU_60001_0524_DTAPC-Template.doc

Documentation-Vob Template Name: 3BU_60001_0524_DTAPC-Template.doc


3BU 51500 5301 DTAPA / 03 / RL / 105




3 Requirements

3.1. High Level Requirements

3.1.1. System Capability Requirements [OMC-TML:SSS:CAPA:0001] Handle train number commands

TML shall handle train number commands received from the command source service. TML shall decide, whether the command will be accepted or not, as a result of the analysis of command data (e.g. start and goal train number field, permissions of sender station, receiver station) and current states (e.g. content of concerned train number fields). It shall send corresponding command acknowledge to the command source. For train number messages, which shall be generated as a result of accepted train number command see requirement [OMC-TML:SSS:CAPA:0008].

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0002] Handle train number messages

TML shall handle train number messages sent by another system via RBP or by other TML-Instances. According to OMC-X25-definition train number command and train number message have the same functional bits. It depends on the assignment of the train number field to a station (station descriptor data), whether the train number shall be placed by a command or by a message. For train number messages, which shall be generated as a result of accepted train number message see requirement [OMC-TML:SSS:CAPA:0008]. [OMC-TML:SSS:CAPA:0006]

Status: approved

Comments: Train number message to be used also for automatic train number shift over the station border and the border of service areas of different TML instances.

[OMC-TML:SSS:CAPA:0003] Receive element / station connection states

TML shall receive element state messages e.g. occupation of track bound elements, switch position, current signal aspect from ILC and use this information for checking the conditions for the automatic train number shift. TML shall receive also station connection state messages (ILC Service Protocol) from ILC.

Status: approved

Comments:




[OMC-TML:SSS:CAPA:0004] Perform automatic train number shift

Automatic train number shift means, that a train number shall be shifted from the start train number field placed in front of a train route relevant signal to the goal train number field placed in front of the next train route relevant signal or on a line track in the traffic direction. TML shall perform the automatic train number shift if the defined conditions based on element states are fulfilled. There are some special conditions for automatic train number shift concerning pre announcement field. For train number messages, which shall be generated as a result of the automatic train number shift see requirement [OMC-TML:SSS:CAPA:0008].

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0005] Train number storage

If the conditions for the automatic train number shift are fulfilled, but there is no train number in the start train number field, then TML shall get the train number from the train number storage (if there is a number valid for desired shifting direction), put it on the start number field and perform the automatic train number shift as usual. It shall also be possible to perform various storage operations via EBO.

Status: approved

Comments: Not implemented in ELEKTRA ÖBB. To be descoped. Function intended to be fulfilled by the train number storage (a train divided into parts, each part provided with its own train number) could be performed by Railbroker by means of the train number break-in.

[OMC-TML:SSS:CAPA:0006] Ghost number

TML shall generate a ghost number and put it on the goal train number field, if the conditions for the automatic train number shift are fulfilled, but in the start train number field there is currently no train number.

Status: approved

Comments: The train number storage need not to be considered if the start train number field is empty, because the requirement regarding the train number storage ([OMC-TML:SSS:CAPA:0005]) is to be descoped.

[OMC-TML:SSS:CAPA:0007] Train number alarm

TML shall generate a train number alarm and send it via ILC to EBO, if the conditions for the automatic train number shift are fulfilled, but the goal train number field cannot be found.

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0008] Generate train number messages

TML shall generate train number messages and send it to ILC, if it identifies the need to change the current content of a train number field as a result of accepted train number command, message or the automatic train number shift.

Status: approved

Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:CAPA:0009] Monitor station connection

TML shall monitor the station connection state according to the information received from ILC. Train numbers shall not be deleted on connection breakdown. The automatic train number shift cannot be performed while the connection to this station is down (element state messages cannot be received). Under some certain conditions the automatic train number shift shall be performed immediately after the station connection has been restored. Command performance / message acceptance concerning the train number fields of the station actually not connected shall be allowed. If there is a need to change the train number or some information associated with it (e.g. RBC registration status) during connection breakdown, TML shall provide the ILC with the new information immediately (as usual). TML shall not perform any special activities after the station connection has been restored. (The train number update for restored station shall be done by ILC, which already has been provided with actual train number by the ILC. See also [OMC-TML:SSS:CAPA:0010]).

Status: approved

Comments: Concerns station connection while the ILC connection is working.

[OMC-TML:SSS:CAPA:0010] Monitor ILC connection

TML shall monitor the ILC connection state. After the ILC connection has been restored, TML shall receive current element / station connections states (see also [OMC-TML:SSS:CAPA:0003]) from ILC and provide ILC with current train numbers and the entire information associated with it (e.g. RBC registration status).

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0011] Logging and Diagnosis

TML shall log status-, event- and error-logs: • via the connection to the OMC Administration and Diagnosis Service (see also [OMC-TML:SSS:CAPA:0028]) • To the file system

For both logging methods the logging level shall be configurable independently online by the OMC Administration and Diagnosis Service (see also [OMC-TML:SSS:CAPA:0027]).

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0012] No TML Graphical User Interface

There is no need for special TML GUI. Train number commands and messages shall be handled only by EBO. Additional train number information (e.g. RBC registration status) shall only be displayed on ARAMIS-GUI or EBO (if needed).

Status: approved

Comments:




[OMC-TML:SSS:CAPA:0013] TML Service Instances

There shall be multiple TML-Instances, each of them responsible for a group of stations (service area). For station - instance assignment see also [OMC-TML:SSS:CAPA:0027].

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0014] TML Architecture

TML shall fit the general SIL-0-Architecture. See [SSDD GMED] and [Dokument-to-be-written]

Status: approved

Comments:

3.1.2. System External Interface Requirements Description of the fact, if TML uses or provides an Interface corresponds to SSDD (except [OMC-TML:SSS:CAPA:0027] and [OMC-TML:SSS:CAPA:0028]). Interface numbers IF-nn also. [OMC-TML:SSS:CAPA:0016] Use the TML command interface (IF-30) for train number

command transmission

TML (interface provider) shall receive train number commands from the command sender (OMC’s own EBO, other system via RBP) via the TML command interface and inform the command sender about the reception (command acknowledge). TML shall also send train number commands to RBP via this interface, if other system is responsible for the performance of the commanded train number operation. Each TML instance shall be able to receive train number commands concerning all stations of its instance service area via this interface.

Status: approved

Comments: For configuration of the service area see also [OMC-TML:SSS:CAPA:0027] and [OMC-TML:SSS:CAPA:0031].

[OMC-TML:SSS:CAPA:0017] Use the TML command interface (IF-30) for train number

messages transmission

TML (interface provider) shall receive train number messages from other system via RBP (interface user) or from another TML instance. TML shall also send train number messages to RBP or to another TML instance via this interface.

Status: approved

Comments: Train number message to be used as method for train number update (similar to train number command) depending on managing station. See also [OMC-TML:SSS:CAPA:0002].


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:CAPA:0035] Use the TML command interface (IF-30) for RBC status request transmission

TML (interface provider) shall receive RBC status request for particular train number from ATRS (interface user).

Status: approved

Comments: Train number message to be used as method for train number update (similar to train number command) depending on managing station. See also [OMC-TML:SSS:CAPA:0002].

[OMC-TML:SSS:CAPA:0018] Use the ILC Service Interface (IF-11) - general characteristics

TML (interface consumer) shall establish and manage a connection to multiple ILC instances (interface provider), one for each station, and communicate with them in both directions.

Status: approved

Comments: For Details concerning IF-11 see [IF-11 ICD].

[OMC-TML:SSS:CAPA:0019] Use the interface to the ILC (IF-11) - train number messages

from ILC to TML

TML (interface consumer) shall receive train number messages from ILC (interface provider).

Status: approved

Comments: Train number message to be used as method for train number update (similar to train number command) depending on managing station. See also [OMC-TML:SSS:CAPA:0002]. To be descoped. Replaced by [OMC-TML:SSS:CAPA:0017] because the train number message shall be received via IF-30.

[OMC-TML:SSS:CAPA:0020] Use the interface to the ILC (IF-11) - train number update from

TML to ILC

TML (interface consumer) shall provide ILC (interface provider) with current train number messages as a result of the command performance or automatic train number shift based on train movements. Train number messages will not be sent directly from TML to other components, which need them (EBO, ATRS).

Status: approved

Comments: Only train number messages addressed to the RBP will be sent directly to RBP (IF-30), not via ILC (IF-11).

[OMC-TML:SSS:CAPA:0021] Use the interface to the ILC (IF-11) - additional train information

TML (interface provider) shall provide ILC (interface consumer) with additional train information (e.g. RBC registration status).

Status: approved

Comments: Substitute of interface to ATRS (IF-16). Additional train information shall be a part of train number update. See also [OMC-TML:SSS:CAPA:0020]




[OMC-TML:SSS:CAPA:0022] Use the interface to the ILC (IF-11) - element / station connection states

TML (interface consumer) shall be provided by ILC (interface provider) with current element and station connection states to allow TML to perform the automatic train number shift. Each TML instance must be able to specify the elements and states needed (element / state observer).

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0023] Use the File Interface to the Infrastructure Service (IF-40)

TML (interface consumer) shall use the File Interface (IF-40) to the Infrastructure Service (interface provider) to read data from station descriptor, such as:

• topology data - for following the train routes in order to perform the automatic train number shift • train number data - track with/without train number field, station permissions on this field, performance of automatic train number shift wanted, recording configuration for the automatic train number shift

This data has to be managed by the File Service as a part of OMC Infrastructure Service.

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0024] Use the Interface to the ARAMIS train information (IF-06)

TML (interface consumer) shall be provided by ARAMIS train information (interface provider) with additional train information (e.g. RBC registration status).

Status: approved

Comments: The communication protocol has been defined by the customer, see [SS ETCS].

[OMC-TML:SSS:CAPA:0025] Use the OMC Recording Interface (IF-19)

TML (interface consumer) shall use the interface to the OMC Protocol Service (interface provider) to record the performance of

• The automatic train number shift (if configured so) • Performance of the train number command “break-in”, receiving of the train number message “break-in” • Performance of the train number command “outbreak”, receiving of the train number message “outbreak” • Performance of train number commands set via EBO

The recording text shall contain also service instance information additionally to usual train number command data.

Status: approved

Comments: In PH ZNM there has been defined, that the command “outbreak” is not to be recorded, but it will be useful to record it also (e.g. for efficient field analysis).


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:CAPA:0026] Use the ADM Logging Interface (IF-08)

TML (interface consumer) shall use the ADM Logging Interface to the OMC Administration and Diagnosis Service (interface provider) for remote logging of status-, event- and error-logs.

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0027] Use the ADM Administration Interface (IF-09)

There shall be multiple TML Instances started by cluster. Each TML Instance shall be responsible for a group of stations (service area). The Administration Service shall be responsible for the station - service instance assignment. The OMC Administration and Diagnosis Service (interface provider) shall use the ADM Administration Interface to the TML Service (interface user) to change this station - service instance assignment also during service operation. For the performance of the automatic train number shift it will be advantageous, if one TML-Instance would be responsible for a group of stations, which are gapless neighbors of each other. OMC Administration and Diagnosis Service shall get the current service state information on request via the ADM Status Interface (see also [OMC-TML:SSS:CAPA:0028]).

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0028] Use the ADM Status Interface (IF-10)

TML (interface consumer) shall use the ADM Status Interface to provide the OMC Administration and Diagnosis Service (interface provide) with status information (e.g. TML service instance, stations in its service area, current service state of each station, interface state) via the ADM Status Interface.

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0029] Use the Interface to the OMC Database Service (IF-23)

TML (interface consumer) shall use the interface to the OMC Database Service (interface provider) to store current train numbers in order to save this information during a short-term failure of the TML service and to use it afterwards. Maximum short-term failure time shall be a TML-configurable item. See also [OMC-TML:SSS:CAPA:0031].

Status: approved

Comments: According to PH ZNM the train number shall be stored during a short-term failure, but not during a long-term failure. The description of this requirement corresponds to this feature. TML is responsible for scheme definition and access permissions.




[OMC-TML:SSS:CAPA:0030] Use the interface to the OMC Infrastructure Service (IF-24)

TML (interface consumer) shall use the interface to the OMC infrastructure Service (interface provider), to be provided with:

• configuration data (via distributed file system)

Status: approved

Comments: See also [OMC-TML:SSS:CAPA:0023] for station descriptor data via the interface to the ILC. To be descoped, see changed requirement [OMC-TML:SSS:CAPA:0023], concerning now IF-40.

3.1.3. System Internal Data Requirements [OMC-TML:SSS:CAPA:0031] Configuration

It shall be possible to configure the number of TML-Instances to be started and to configure the stations to be managed by each TML-Instance (service area). There is no special configuration related to TML function scope. All stations have to be provided with full train number function, otherwise the station may not be included in the TML-service area (to be considered at instance start). Maximum short-term failure time as a limit for usage of the train number data stored by the OMC Database Service shall be a TML-configurable item (only one value per OMC). Other configuration items, such as system related configuration data shall be read from a file system provided by File Service as a part of the OMC Infrastructure Service.

Status: approved

Comments:

[OMC-TML:SSS:CAPA:0032] Train number field managing station

In a station managed by an OMC, this OMC shall be configured also as a train number field managing station for all existing train number fields.

Status: approved

Comments: Train number field managing station is a configurable ítem of a track section, already existing in ELEKTRA ÖBB.

3.1.4. Adaptation Requirements [OMC-TML:SSS:CAPA:0033] Station temporarily excluded

It shall be possible to exclude a station temporarily from the service area of a TML instance due to adaptation work (e.g. for version update, new database load) and rejoin it again, after this work is finished. During this retirement period there will be no train number service for this station. Train number function in all remaining stations of the same service area shall work unaffected, except of the automatic train number shift from a neighbor station to excluded station and vice versa.

Status: approved

Comments:

3.1.5. Safety Requirements


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:CAPA:0034] TML Safety Requirements

There are no safety requirements on TML-Service.

Status: approved

Comments:

3.2. Low Level Requirements

3.2.1. System Capability Requirements

3.2.1.1. Handle train number commands

Use Case

Identification [OMC-TML:SSS:UC:0012] Train number command concerning a train number field not managed by own OMC Command sent due to menu configuration error. Any other command action will be rejected also.

Preconditions Train number field not managed by own OMC, e.g. train number field of a line track section managed by Railbroker

Postconditions no changes in train number state

Trigger Train number command "Dial-in" via IF-30

Basic Flow 1. Train number command Dial-in has been received via IF-30 due to manual command performed via OMC's own EBO 2. TML rejects this command, because not OMC, but Railbroker is responsible for this train number field 3. TML answers the command by negative acknowledge 4. TML performs no change of train number field content

Requirements [OMC-TML:SSS:REQ:0001], [OMC-TML:SSS:REQ:0003], for configuration [OMC-TML:SSS:REQ:0114]

Use Case

Identification [OMC-TML:SSS:UC:0013] Train number command concerning a train number field managed by own OMC Command to be allowed.

Preconditions train number field managed by own OMC it is usual train number field, not a border one

Postconditions Train number set on the track section handled by the manual command.

Trigger Train number command "Dial-in" via IF-30




Use Case

Basic Flow 1. Train number command Dial-in has been received via IF-30 due to manual command performed via OMC's own EBO 2. TML accepts this command 3. TML answers the command by positive acknowledge 4. TML puts train number and all its additional attributes in the goal train number field according to command data 5. TML sends corresponding Dial-in message to ILC und RBP, in order to inform all components / stations, which are interested in it 6. TML records this command via IF-19

Specific Non-Functional Requirements

[OMC-TML:SSS:REQ:0001], [OMC-TML:SSS:REQ:0003], [OMC-TML:SSS:REQ:0012], [OMC-TML:SSS:REQ:0028], [OMC-TML:SSS:REQ:0134] for configuration [OMC-TML:SSS:REQ:0112], [OMC-TML:SSS:REQ:0113], [OMC-TML:SSS:REQ:0114], [OMC-TML:SSS:REQ:0115]

Issues no issues Use Case

Identification [OMC-TML:SSS:UC:0014] Manual train number shift command Manual train number shift command concerning both start and goal train number fields managed by own OMC

Preconditions both start and goal train number fields managed by own OMC in the start train number field there is a train number

Postconditions Train number moved from start train number field to goal train number field

Trigger Train number command "Manual train number shift" via IF-30

Basic Flow 1. Train number command Manual train number shift has been received via IF-30 2. Train number and steering character currently placed in the start train number field are equal to those from command data 3. TML accepts this command. 4. TML answers the command by positive acknowledge 5. TML puts the train number and all its additional attributes in the goal train number field and removes it from the start train number field 6. TML sends corresponding Manual train number shift message to ILC and RBP, in order to inform all components / stations, which are interested in it 7. TML records this command via IF-19.


3BU 51500 5301 DTAPA / 03 / RL / 105




Use Case

Alternative Flows 5a. goal train number field managed by Railbroker: 1. TML sends the command Dial-in to Railbroker via RBP (IF-30), for the train number to be shifted to the goal train number field 2. TML puts the train number in the goal train number field 3. TML removes the train number from the start train number field 4. TML sends Dial-in message to ILC, in order to inform all components, which are interested in it 5. TML sends Deletion message to ILC, in order to inform all components, which are interested in it 6. TML sends a message to the stations to get informed via RBP. Message Automatic train number shift to be sent if particular station is interested in both start and goal train number field. Message Dial-in / Deletion to be sent, if the station is interested only in goal / start train number filed. 7. TML receives Dial-in message from Railbroker, after successfull command performance. No change cause by this, because the train number has already been put in the goal train number filed (see step 2). 8. sequence terminates here Train number shift will be completed after the Railbroker executed the deletion. OMC will receive a corresponding "Deletion" message via RPB (IF-30) concerning the start train number field. Afterwards TML will remove the train number from the start train number field and generate corresponding message to ILC.

5b. start train number field managed by Railbroker: 1. TML sends the command Deletion to Railbroker via RBP (IF-30), for the train number to be removed from the start train number field 2. TML puts the train number in the goal train number field 3. TML removes the train number from the goal train number field 4. TML sends Dial-in message to ILC, in order to inform all components, which are interested in it 5. TML sends Deletion message to ILC, in order to inform all components, which are interested in it 6. TML sends a message to the stations to get informed via RBP. Message Automatic train number shift to be sent if particular station is interested in both start and goal train number field. Message Dial-in / Deletion to be sent, if the station is interested only in goal / start train number filed. 7. TML receives Deletion message from Railbroker, after successfull command performance. No change cause by this, because the train number has already been removed from the goal train number filed (see step 3). 8. sequence terminates here


[OMC-TML:SSS:REQ:0001], [OMC-TML:SSS:REQ:0003], [OMC-TML:SSS:REQ:0016], [OMC-TML:SSS:REQ:0017], [OMC-TML:SSS:REQ:0012], [OMC-TML:SSS:REQ:0034], [OMC-TML:SSS:REQ:0014], [OMC-TML:SSS:REQ:0134] for configuration [OMC-TML:SSS:REQ:0114], [OMC-TML:SSS:REQ:0115]

Issues no issues




[OMC-TML:SSS:REQ:0001] — FUR Train number command allowed

A train number operation performed by a train number command shall only be allowed, if the train number field concerned is managed by own OMC (configuration item, see also [OMC-TML:SSS:REQ:0114]). If both start and goal train number fields are concerned (e.g. command manual train number shift), then at least one of them shall comply.

Status: approved Stability: stable

Target Release: Rel. 01.00 Priority: mandatory

Originator: Product Management Origin:

Verification Method: Test Verification Step: subit test

Verification Notes: Source: [OMC-TML:SSS:CAPA:0001]

Comments: For message generation depending on managing station see also [OMC-TML:SSS:REQ:0017].

[OMC-TML:SSS:REQ:0002] — FUR Any other command except train number command

Train number command is the only one to be performed by TML. TML shall reject any other command.






Comments:

[OMC-TML:SSS:REQ:0003] — FUR Command acknowledge

If TML accepts the train number command received, it shall send positive command acknowledge to the command sender, otherwise negative command acknowledge (e.g. for not allowed train number command, any other command). No rejection text shall be sent proceeding the negative command acknowledge.






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0004] — FUR Allowed start / goal train number field in command data

As a start / goal train number field of a train number command following element types shall be allowed: not isolated track section, isolated station track section, isolated track section on the line (each of them with train number field), dummy (X25 number = 0). If the start / train number field shall not be required for particular command (as described in subsequent requirements), it may be dummy. If it is not dummy, the command shall not be rejected for this reason.






Comments: Definition of Dummy = 0 is based on X25 definition and current ELEKTRA implementation. In OMC (based on different technology) the corresponding attribute will just not be set.

[OMC-TML:SSS:REQ:0005] — FUR Command sender

A train number command shall be allowed only if the command sender is — OMC’s own EBO — Railbroker (via RBP) — other system (via RBP) - it may be a standalone interlocking system, a BOS center or another OMC (usually a neighbor, where the train number field concerned is also known / visible, but not being managed by this neighbor itself)

There shall be a unique sender identifier provided via IF-30 in order to enable TML to identify the real command source, e.g. Railbroker (not RBP). This will be necessary, because some operations /flags shall be allowed / not allowed (see [OMC-TML:SSS:REQ:0001]) or handled in different way (see e.g. [OMC-TML:SSS:REQ:0020]), depending on the command source. If train number address is concerned, command shall be allowed only if the other system is configured also as the station to get informed (see [OMC-TML:SSS:REQ:0115]). This check is applicable for start or goal train number field, if start or goal train number field is required. For Manual train number shift both of them shall be checked. If preannouncement field or fictive field is concerned, there shall be no sender restriction (each command sender allowed).





Verification Notes: Source: [OMC-TML:SSS:CAPA:0001] [OMC-TML:SSS:CAPA:0012]

Comments:




[OMC-TML:SSS:REQ:0006] — FUR Command receiver

There is no need to perform special checks of the command receiver in the TML, because IF-30 shall support only the commands really addressed to TML.




Verification Method: Test Verification Step: analysis


Comments:

[OMC-TML:SSS:REQ:0007] — FUR Train number - valid characters

Following characters shall be allowed for the train number (7 digits) of the train number command data: — numbers 0-9 — letters a-z / A-Z, without german umlaut — Blanc — comma — dot — question mark (not possible to enter it via EBO)

Invalid characters shall be replaced by “?”.






Comments:

[OMC-TML:SSS:REQ:0008] — FUR Steering character - valid characters

Following characters shall be allowed for the steering character (1 digit) of the train number command data: — numbers 0-9 — Blanc — question mark (not possible to enter it via EBO)







Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0009] — FUR Schedule difference - valid characters

Following characters shall be allowed for the schedule difference (2 digits) of the train number command data:

— numbers 0-9 — question mark







Comments:

[OMC-TML:SSS:REQ:0010] — FUR Exactly one command in one telegram

A train number command telegram shall contain exactly one command of the following set, otherwise it shall be rejected:

— Dial-in — Break-in — Deletion — Outbreak — Manual train number shift — Partial evaluation — State change






Comments: Corresponds to exactly one bit of control word 1 of X25-CMD 174 required in ELEKTRA train number function.




[OMC-TML:SSS:REQ:0011] — FUR Additional attributes of train number in train number command

There are following additional attributes connected to a train number: — steering character — schedule difference plus — schedule difference minus — no current schedule difference data — train lead by LZB — radio equipped train — to be displayed blue — to be displayed blinking

It shall be possible to set / reset one or more of these additional attributes by a flag set in the same command telegram, additionally to command to be performed (see also [OMC-TML:SSS:REQ:0010]). The only exception is the steering character, which shall be considered as a part of the train number, not needing a special flag.






Comments: Corresponding to control word 2 of X25-CMD 174.

[OMC-TML:SSS:REQ:0012] — FUR Command Dial-in

By the command Dial-in a train number and all its additional attributes (e.g. steering character, schedule difference plus /minus) shall be placed in the goal train number field. The command shall not be performed, if the command data contains only some additional attributes without a train number. Goal train number field shall be required. Start number field may be dummy.






Comments: Stw 1, Bit 1 = Taufe / Einwahl


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0013] — FUR Command Break-in

For the command Break-in the same conditions shall be applicable as for the command Dial-in. Additionally command Break-in shall be recorded if configured so (see also [OMC-TML:SSS:REQ:0116] and [OMC-TML:SSS:REQ:0134]).




Verification Method: Test Verification Step: subit test part system test


Comments: Stw 1, Bit 2 = Einbruch

[OMC-TML:SSS:REQ:0014] — FUR Command Deletion

By the command Deletion a train number and all its attributes (e.g. steering character, schedule difference plus /minus) shall be deleted from the start train number field (reset to default values). Start train number field shall be required. Goal train number may be dummy.TML shall ignore train number (and its attributes) possibly contained in the command. As result of command Deletion performance, TML shall generate a Deletion message to ILC, containing only the train number located on the start train number field, found by TML by interrogating the data base (no additional attributes, no flags).






Comments: Stw 1, Bit 3 = Löschen

[OMC-TML:SSS:REQ:0015] — FUR Command Outbreak

For the command Outbreak the same conditions shall be applicable as for the command Deletion (see also [OMC-TML:SSS:REQ:0014]). Additionally command Outbreak shall be recorded if configured so (see also [OMC-TML:SSS:REQ:0116] and [OMC-TML:SSS:REQ:0134]). As result of command Outbreak performance, TML shall generate an Outbreak message to ILC, containing only the train number located on the start train number field, found by TML by interrogating the data base (no additional attributes, no flags).






Comments: Stw 1, Bit 4 - Zugausbruch




[OMC-TML:SSS:REQ:0016] — FUR Command Manual train number shift

By the command Manual train number shift a train number (and all its additional attributes) shall be shifted from the start train number field to the goal train number field. Start train number field shall stay empty (reset to default values). Both start and goal train number fields shall be required. There shall be a train number in the start number field (no ghost number generation by manual train number shift). This train number and its steering character shall be equal to those from command data. If this condition is not fulfilled, then the negative command acknowledge shall be sent. No rejection text to be sent prior to the negative command acknowledge. Any other train number attributes (e.g. schedule difference plus / minus) shall not influence the command acceptance.






Comments: Manual train number shift is only possible, if both start and goal train number fields are configured as train number address, other train number field types cannot be handled by a manual command. (For automatic train number shift also fictive field and preannouncement field are applicable. See also [OMC-TML:SSS:REQ:0050].) Stw 1, Bit 5 = Handfortschaltung Stw 1, Bit 6 not used - It is not possible to perform the automatic train number shift by command (only by message). No rejection text to be sent due to previously intended simplified handling of the command acknowledge. Positive command acknowledge to be sent by ILC to EBO, if ILC is able to forward the command to the performing service. Rejection text sent afterwards would not reach the EBO.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0017] — FUR Generate train number message(s) / command(s) as result of performing manual train number shift

The content of the message(s) / command(s), which shall be generated as a result of manual train number shift, depends on start / goal train number field managing station. Message shall be sent to ILC (who is responsible for its further distribution to the components, which are interested in train number information) and via RBP to all stations to get informed (for configuration see [OMC-TML:SSS:REQ:0115].). Command shall be sent to the train number field managing station (for configuration see [OMC-TML:SSS:REQ:0114].).

1) both start and goal train number fields managed by own OMC -> manual train number shift message, no further commands 2) only start train number field managed by own OMC, goal train number field by some other station -> command Dial-in for the goal train number field, deletion message for the start train number field 3) only goal train number field managed by own OMC, start number field by some other station -> Dial-in message for the goal train number filed, command Deletion for the start train number field 4) both start and goal train number field managed by the same station (not own OMC) -> command Manual train number shift 5) start and goal train number field managed by different stations (none of them is the own OMC) -> command Dial-in for the goal train number field, command Deletion for the start train number field

Train number message concerning train number field not managed by the OMC (see alternatives 2 - 5) shall be generated immediately after sending the command to the managing station of the train number field. TML shall not wait for the train number message from the managing station as feedback of command performance (applicable for all command operations).






Comments: The alternatives 4 and 5 were in the current ELEKTRA train number function used in order to handle a manual command set by local operation in a remote station and to perform it in the central station. In the OMC the described relation of start and goal train number field will not be very common, but may be it will be used in the OMC build-up phase. TML will not check the current connection state to the station, which the train number command resulting from the automatic train number shift will be sent to. See also [OMC-TML:SSS:REQ:0108]. Not waiting for the train number message as feedback of command performance corresponds to the current ELEKTRA train number function. This feature will be kept in order to shorten the time slots, while particular train number is positioned at both start and goal train number fields.




[OMC-TML:SSS:REQ:0018] — FUR Command Partial evaluation

Command Partial evaluation shall only be allowed, if the train number from command data is equal to the current train number in the goal train number field. In that case all additional attributes of the train number (e.g. steering character, schedule difference plus / minus) shall be updated corresponding to the command data. Goal train number field shall be required. Start train number field may be dummy. If there is currently no train number in the goal train number field or other train number not corresponding to command data, then negative command acknowledge shall be sent.






Comments: Stw 1, Bit 7 = Kennung

[OMC-TML:SSS:REQ:0019] — FUR Command State change

By the command State change a train number and all its additional attributes (e.g. steering character, schedule difference plus /minus) shall be placed in the goal train number field. Goal train number field shall be required. Start number field may be dummy.




Verification Method: Test Verification Step: analysis subit test


Comments: Stw 1, Bit 8 = Zustandsänderung Similar use as Dial-in. No check of the current train number needed. TML will not enable raising the train number alarm by the command State change with both start and goal train number field dummy.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0020] — FUR Command flag LZB

TML shall accept the LZB flag and update the corresponding additional attribute of the train number concerned, if the command operation has been:

— Dial-in, if received from the Railbroker — Break-in — Partial evaluation — State change, if received from the Railbroker

If this condition is not fulfilled, TML shall ignore the LZB flag and perform the operation according to the command bits left. If TML accepts the LZB flag, then it shall be contained also in the train number message generated as result of the command performance (see also [OMC-TML:SSS:REQ:0028]).






Comments: Stw 2, Bit 1 = LZB Corresponding to current ELEKTRA train number function. Sender check just for Dial-in.

[OMC-TML:SSS:REQ:0021] — FUR Command flag Radio

For the Radio Flag the same conditions shall be applicable as for the LZB flag. See [OMC-TML:SSS:REQ:0020].






Comments: Stw 2, Bit 2 = Funk

[OMC-TML:SSS:REQ:0022] — FUR Command flag Schedule difference

For the Schedule difference flag (minus / plus / NADA) the same conditions shall be applicable as for the LZB flag. See [OMC-TML:SSS:REQ:0020]. For mutual dependencies of schedule difference flag and schedule difference value see [OMC-TML:SSS:REQ:0023].






Comments: Stw 2, Bit 7 = Planabweichung Minus, Bit 8 = Planabweichung Plus, Stw 3, Bit 1 = Zustandsdaten PA




[OMC-TML:SSS:REQ:0023] — FUR Mutual dependencies of Schedule difference command flag and value

TML shall consider following dependencies between the schedule difference command flag and schedule difference value:

— TML shall validate the schedule difference value only if the schedule difference flag is not set to NADA. — Valid characters shall be accepted. Invalid characters shall be replaced by '?'. — In case of invalid characters TML shall set the schedule difference flag to NADA. Additionally also the flags Blue and Train number alarm shall be set.






Comments:

[OMC-TML:SSS:REQ:0024] — FUR Command flag Blue

The Blue flag set in the command data received shall always be ignored. TML shall add the Blue flag (and also the Alarm flag) and update the corresponding additional attribute of the train number concerned, if TML encounters the condition for raising the train number alarm based on invalid characters contained in train number, steering character or schedule difference value. For exact conditions for raising the train number alarm see also [OMC-TML:SSS:REQ:0026].






Comments: Stw 3, Bit 2 = Blau

[OMC-TML:SSS:REQ:0025] — FUR Command flag Blinking

TML shall accept the Blinking flag and update the corresponding additional attribute of the train number concerned, if the command operation has been:

— Break-in — State change

If TML accepts / sets the Blinking flag, then it shall be added also to the train number message generated as result of the command performance (see also [OMC-TML:SSS:REQ:0028]).






Comments: Stw 3, Bit 3 = Blinken Corresponding to current ELEKTRA train number function.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0026] — FUR Command flag Train number alarm

TML shall accept the Train number alarm flag and update the corresponding additional attribute of the train number concerned, if the command operation has been:

• State change (it does not matter, if received from the Railbroker or from other sender) The Train number alarm flag shall be also added by TML to the command data due to negative result of the command consistency check if

— train number, steering character or schedule difference value contains an invalid character (validity to be checked according to [OMC-TML:SSS:REQ:0007], [OMC-TML:SSS:REQ:0008] and [OMC-TML:SSS:REQ:0009]).

Applicable for all command operations except Deletion and Outbreak. For the Blue flag to be added also see [OMC-TML:SSS:REQ:0024]. If TML accepts / sets the Train number alarm flag, then it shall be added also to the train number message generated as result of the command performance (see also [OMC-TML:SSS:REQ:0028]).






Comments: Stw 3, Bit 4 = ZN-Alarm; Stw 3, Bit 5 not used TML will not enable raising the train number alarm by the command State change with both start and goal train number field dummy.

[OMC-TML:SSS:REQ:0027] — FUR Additional attributes not implemented yet

Following additional attributes — GSM-R — shunting state 1-3

which have been defined in X25 protocol, but are not implemented yet in current ELEKTRA train number function, shall also be out off OMC scope. For operation ETCS, also not implemented yet in current ELEKTRA train number function, see [OMC-TML:SSS:REQ:0101].




Verification Method: Inspection/Review Verification Step: code reading


Comments: Stw 2, Bit 3 = ETCS, Stw 2, Bit 4 = GSM-R Stw 3, Bits 6-8 = shunting state 1-3




[OMC-TML:SSS:REQ:0028] — FUR Generate train number message(s) as result of train number command performance

If the train number or some attribute of it (steering character, schedule difference plus / minus) shall be changed as a result of the command performance, TML shall generate corresponding train number message (message content equal to performed command, e.g. message Break-in, if the command Break-in has been performed). This message shall be sent to ILC (who is responsible for its further distribution to the components, which are interested in train number information) and via RBP to all stations to get informed (for configuration see [OMC-TML:SSS:REQ:0115].) The only exception shall be the command Manual train number shift (see also [OMC-TML:SSS:REQ:0017]). If a border train number field is concerned, then message shall be sent also to the TML Instance managing the neighboring station / service area. See also [OMC-TML:SSS:REQ:0064].





Verification Notes: Source: [OMC-TML:SSS:CAPA:0001] [OMC-TML:SSS:CAPA:0012] [OMC-TML:SSS:CAPA:0020] [OMC-TML:SSS:CAPA:0025]

Comments: Current ELEKTRA train number function generates no train number messages, if a fictive train number field is concerned, because the fictive train number field is not visible on EBO. TML may generate train number messages also for a fictive field (unique mechanism). ILC will not forward them, if there is no observer registered for this field. Message via RBP to be sent to all stations to get informed also if the command has been received via RBP from a particular station in this list.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0134] — FUR Recording of train number command

All train number commands, which can be performed manually, shall be recorded and the Recording flag shall always be set to FALSE in the train number message generated as result of the command performance. It does not matter, whether they really have been set manually at OMC EBO or received via RBP. This concerns following command operations:

— Dial-in — Deletion — Manual train number shift - Always to be recorded as Manual train number shift, also if the operation is split to Dial-in and Deletion in case of start / goal train number field not being managed by the own OMC.

Following command operations shall be recorded, if configured so (for configuration see also [OMC-TML:SSS:REQ:0116]):

— Break-in — Outbreak

In case of recording of Break-in the Recording flag shall be set to TRUE in the train number message generated as result of the command performance. In case of Outbreak all Flags shall be set to FALSE (see also [OMC-TML:SSS:REQ:0015]), so there is no special handling of Recording flag. Train number command shall only be recorded, if TML accepts the command according to the requirements describing the general command checks.






Comments: Command operations Partial evaluation and State change will never be recorded.

3.2.1.2. Handle train number messages

Use Case

Identification [OMC-TML:SSS:UC:0016] Train number via preannouncement field Train number enters service area of a TML instance via preannouncement field

Preconditions preannouncement field managed by another system (e.g. Railbroker), not by the OMC

Postconditions Train number set on the preannoncement field concerned by the message.

Trigger Train number message Break-in via RBP (IF-30) from another system

Basic Flow 1. Train number message Break-in concerning this preannouncement has been received via RBP (IF-30) from another system 2. TML accepts this message 3. TML puts the train number and all its additional attributes in the preannouncement field 4. TML sends corresponding Break-in message to ILC and RBP, in order to inform all components / stations, which are interested in it 5. TML records this message via IF-19, if recording flag is set




Use Case


[OMC-TML:SSS:REQ:0029], [OMC-TML:SSS:REQ:0034], [OMC-TML:SSS:REQ:0013], [OMC-TML:SSS:REQ:0048], [OMC-TML:SSS:REQ:0135] for configuration [OMC-TML:SSS:REQ:0111], [OMC-TML:SSS:REQ:0114], [OMC-TML:SSS:REQ:0115]


Identification [OMC-TML:SSS:UC:0017] Train number shift from preannouncement field Train number shift from preannouncement field to line track section performed by another system

Preconditions preannouncement field managed by another system (e.g. Railbroker), not by the OMC train number field of line track section in front of arrival signal managed by another system (e.g. Railbroker), not by the OMC automatic train number shift from the preannouncement field, initiated by occupation of the line track section is not configured there is currently a train number in the preannouncement field

Postconditions train number moved from preannouncement field to the line track section

Trigger Train number message Break-in / Outbreak via RBP (IF-30)

Basic Flow 1. Train number message Break-in concerning the line track section has been received via RBP (IF-30) from another system 2. Message data contains the same train number, which is currently placed in the preannouncement field 3. TML accepts this message 4. TML puts train number and all its additional attributes in the train number field of the line track section 5. TML sends corresponding Break-in message to ILC and RBP, in order to inform all components / stations, which are interested in it 6. Train number message Outbreak concerning the preannouncement has been received via RBP (IF-30) from another system 7. TML accepts this message 8. TML removes the train number and all its additional attributes from the preannouncement field 9. TML sends corresponding Outbreak message to ILC and RBP, in order to inform all components / stations, which are interested in it 10. TML records both messages via IF-19, if recording flag is set


[OMC-TML:SSS:REQ:0029], [OMC-TML:SSS:REQ:0034], [OMC-TML:SSS:REQ:0013], [OMC-TML:SSS:REQ:0015], [OMC-TML:SSS:REQ:0048], [OMC-TML:SSS:REQ:0135] for configuration [OMC-TML:SSS:REQ:0111], [OMC-TML:SSS:REQ:0114], [OMC-TML:SSS:REQ:0115], [OMC-TML:SSS:REQ:0118]



3BU 51500 5301 DTAPA / 03 / RL / 105




Use Case

Identification [OMC-TML:SSS:UC:0015] invalid Train number message Train number message concerning an usual train number field managed by own OMC

Preconditions train number field managed by own OMC, it is a usual train number filed, not a border one

Postconditions no changes in train number state

Trigger Train number message Break-in via RBP (IF-30).

Basic Flow 1. Train number message Break-in has been received from Railbroker via RBP (IF-30). 2. TML ignores this message (without any answer), because OMC itself, not the Railbroker, is responsible for this train number field 3. TML performs no change of train number field content. (Message sent due to configuration error. Any other action will be rejected also.)


[OMC-TML:SSS:REQ:0029] for configuration [OMC-TML:SSS:REQ:0112], [OMC-TML:SSS:REQ:0113], [OMC-TML:SSS:REQ:0114]

Issues no issues [OMC-TML:SSS:REQ:0029] — FUR Train number message concerning usual train number field

allowed

A train number operation performed by a train number message shall only be allowed, if the train number field concerned is managed by sender of the message (configuration item, see also [OMC-TML:SSS:REQ:0114]), which is not the own OMC.If both start and goal train number fields are concerned (e.g. manual / automatic train number shift), then both of them shall comply. The only exception is a train number message concerning a border train number field. See also [OMC-TML:SSS:REQ:0030].






Comments: Message sender could be (corresponding to configuration) Railbroker, another OMC or standalone interlocking system, not included in any OMC.




[OMC-TML:SSS:REQ:0030] — FUR Train number message concerning border train number field allowed

A train number operation performed by a train number message shall be also allowed, if the train number field concerned is a border train number field managed by the own OMC and the message sender is also the own OMC (another TML instance).




Verification Method: Test Verification Step: part system test


Comments: A border train number field shall be visible in both neighboring stations / TML instances. If one of them performs a train number update in this train number field, it shall inform the other station / instance by means of a train number message.

[OMC-TML:SSS:REQ:0031] — FUR Message acknowledge

If TML accepts the train number message, it shall send positive acknowledge to the message sender, otherwise negative acknowledge (e.g. for train number message sent by the station, which is not the managing station of the train number field concerned).






Comments: This message acknowledge will be sent for internal purpose only, in order to use the same mechanism as for train number command. Message acknowledge will not be forwarded to external components via X25 communication.

[OMC-TML:SSS:REQ:0032] — FUR Train number, steering character, schedule difference - valid

characters

For the train number, the steering character and the schedule difference of the train number message data the same characters shall be considered as valid as for the train number command data. See [OMC-TML:SSS:REQ:0007], [OMC-TML:SSS:REQ:0008], [OMC-TML:SSS:REQ:0009].






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0033] — FUR Exactly one message in one telegram

A train number message telegram shall contain exactly one action of the following set, otherwise it shall be ignored:

— Dial-in — Break-in — Deletion — Outbreak — Manual train number shift — Automatic train number shift — Partial evaluation — State change






Comments: Corresponds to exactly one bit of control word 1 of X25-MSG 53 required in ELEKTRA train number function.

[OMC-TML:SSS:REQ:0034] — FUR Handle train number message equal to train number command

Following train number messages shall be handled equal to corresponding train number commands, if the message is allowed according to [OMC-TML:SSS:REQ:0029] and [OMC-TML:SSS:REQ:0030]:

— Dial-in — Break-in — Deletion — Outbreak

Equal handling concerns: — start / goal train number field checks — action to be performed — messages to be generated

It is not applicable, that message acceptance shall result in generating further train number command. For special handling of train number messages State change and Automatic train number shift (which have not corresponding train number command) see requirements [OMC-TML:SSS:REQ:0034] and [OMC-TML:SSS:REQ:0035]. For special handling of train number message Manual train number shift and Partial evaluation, which differs from handling of the corresponding train number command see [OMC-TML:SSS:REQ:0129] and [OMC-TML:SSS:REQ:0038].






Comments:




[OMC-TML:SSS:REQ:0129] — FUR Message Manual train number shift

Train number message Manual train number shift shall be handled equal to corresponding train number command, except of the check of train number currently placed in start train number field. The operation shall always be performed according to message data (even if there is currently no train number in the start train number field or train number / steering character in the start train number is not equal to those from message data).






Comments: Current ELEKTRA train number function do not check the train number / steering character from message data against the current train number / steering character of the start train number field while processing the message Manual train number shift.

[OMC-TML:SSS:REQ:0035] — FUR Message Automatic train number shift concerning usual train

number field

Train number message Automatic train number shift shall be allowed only if both start and goal train number fields concerned are not managed by own OMC. By the message Automatic train number shift a train number (and all its additional attributes) shall be shifted from the start train number field to the goal train number field. Start train number field shall stay empty (reset to default values). Both start and goal train number fields shall be required. It shall not be relevant, whether

— there is currently a train number in the start train number field (no ghost number generation, if there is no train number). — train number and steering character from message data are equal to the current data

The operation shall always be applied to the train number from message data - putting this train number to the goal train number field and always leaving the start train number field empty, not depending on its previous content. Any other train number attributes (e.g. schedule difference plus / minus) shall not influence the message acceptance.






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0036] — FUR Special usage of messages Break-in / Outbreak and Dial-in / Deletion concerning border train number field

Message Break-in / Outbreak shall be used to perform the automatic train number shift concerning a border train number field. Message Dial-in / Deletion shall be used to perform manual train number shift concerning a border train number field. It shall be applicable for both station border and instance border. Message Break-in / Dial-in shall be received, if neighboring station / instance is performing train number shift into “my” station / service area. Message Outbreak / Deletion shall be received, if neighboring station / instance is performing further train number shift in its station / instance area, so that the train number leaves definitely “my” station / service area.






Comments:

[OMC-TML:SSS:REQ:0037] — FUR Train number message concerning border train number field

Train number messages concerning border train number field (except Manual / Automatic train number shift, which shall not be received for a border train number field) shall be performed equal to message concerning usual train number fields.






Comments:

[OMC-TML:SSS:REQ:0038] — FUR Message Partial evaluation

Message Partial evaluation shall be handled equal to the message Break-in. It means, that it shall be not necessary to check the train number from message data against the current train number in the goal train number field. By this message not only the additional attributes shall be changed, but also the train number (in contrast to command Partial evaluation). For recording of the Partial evaluation see [OMC-TML:SSS:REQ:0135].






Comments:




[OMC-TML:SSS:REQ:0039] — FUR Message State change

If goal train number field is not dummy, then the message State change shall be handled equal to the command State change. TML will not enable raising the train number alarm by the message State change with both start and goal train number field dummy.






Comments:

[OMC-TML:SSS:REQ:0040] — FUR Additional attributes of train number in train number message

It shall be possible to set / reset one or more additional attributes connected to a train number by a flag set in the same message telegram, additionally to action to be performed (see also [OMC-TML:SSS:REQ:0033]). The only exception is the steering character, which shall be considered as a part of the train number, not needing a special flag. For full list of additional attributes see [OMC-TML:SSS:REQ:0011].






Comments:

[OMC-TML:SSS:REQ:0041] — FUR Message flag LZB

TML shall always accept the LZB flag set in the train number message and update the corresponding additional attribute of the train number concerned, not depending on the action to be performed (for list of actions see [OMC-TML:SSS:REQ:0033]). The LZB flag shall also be contained in the train number message generated as result of the message acceptance (see also [OMC-TML:SSS:REQ:0048]).






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0042] — FUR Message flag Radio

For the Radio Flag the same conditions shall be applicable as for the LZB flag. See [OMC-TML:SSS:REQ:0041].






Comments:

[OMC-TML:SSS:REQ:0043] — FUR Message flag Schedule difference

For all message operations except- Deletion and- OutbreakTML shall accept the Schedule difference flag (minus / plus / NADA) and update the corresponding additional attribute of the train number concerned. For mutual dependencies of schedule difference flag and schedule difference value see [OMC-TML:SSS:REQ:0044].






Comments: Stw 2, Bit 7 = Planabweichung Minus, Bit 8 = Planabweichung Plus

[OMC-TML:SSS:REQ:0044] — FUR Mutual dependencies of Schedule difference message flag and

value

TML shall consider following dependencies between the schedule difference message flag and schedule difference value: TML shall always validate the schedule difference value. Valid characters shall be accepted. Invalid characters shall be replaced by '?'. In case of invalid characters TML shall set the schedule difference flag to NADA. Additionally also the flags Blue and Train number alarm shall be set.






Comments: Stw 3, Bit 1 0 Zustandsdaten PA




[OMC-TML:SSS:REQ:0045] — FUR Message flag Blue

For the Blue flag the same conditions shall be applicable as for the LZB flag. See [OMC-TML:SSS:REQ:0041]. TML shall also add the Blue flag (and also the Alarm flag) and update the corresponding additional attribute of the train number concerned, if TML encounters the condition for raising the train number alarm based on invalid characters contained in train number, steering characters or schedule difference value. For conditions for raising the train number alarm see also [OMC-TML:SSS:REQ:0047].






Comments: Stw 3, Bit 2 = Blau

[OMC-TML:SSS:REQ:0046] — FUR Message flag Blinking

For the Blinking flag the same conditions shall be applicable as for the LZB flag. See [OMC-TML:SSS:REQ:0041].






Comments: Stw 3, Bit 3 = Blinken

[OMC-TML:SSS:REQ:0047] — FUR Message flag Train number alarm

The Train number alarm flag set in the message data received shall always be ignored. The Train number alarm flag shall be added by TML to the message data due to negative result of the message consistency check if - train number, steering character or schedule difference value contains an invalid character (validity to be checked according to [OMC-TML:SSS:REQ:0007], [OMC-TML:SSS:REQ:0008] and [OMC-TML:SSS:REQ:0009]). Applicable for all message operations except Deletion and Outbreak. For the Blue flag to be added also see [OMC-TML:SSS:REQ:0045].

Status: in work Stability: instable





Comments: Stw 3, Bit 4 = ZN-Alarm


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0048] — FUR Generate train number message(s) as result of train number message acceptance

If the train number or some additional attributes of it (e.g. steering character, schedule difference plus / minus) shall be changed as a result of the message acceptance, TML shall generate corresponding train number message to ILC and to RBP in order to inform other systems (message content equal to performed action, e.g. message Break-in, if action Break-in has been performed). If the message operation is Deletion or Oubreak, this generated message shall contain only the train number (no additional attributes, no flags).






Comments:

[OMC-TML:SSS:REQ:0135] — FUR Recording of train number message

All train number messages corresponding to train number commands, which can be performed manually, shall always be recorded, not depending on the Recording flag in the received message. Recording flag also not to be added in the message to ILC / RBP generated by TML. This concerns following message operations:

— Dial-in — Deletion — Manual train number shift

Following message operations shall be recorded, if the Recording flag is set in the same train number message (this means, that the managing station of the train number field concerned decided, that this operation has to be registered). Recording flag to be set also in the message to ILC / RBP generated by TML (except of Outbreak, because for this operation all flags will be removed):

— Break-in — Outbreak — Automatic train number shift — Partial evaluation (because the operation is functionally equal to Break-in)

Train number message shall only be recorded, if TML accepts the message according to the requirements describing the general message checks. Train number message shall only be recorded, if message sender is not another TML instance, in order to avoid double recording of operations on border train number field.






Comments: Message operation State change will never be recorded.

3.2.1.3. Automatic train number shift

Use Case




Use Case

Identification [OMC-TML:SSS:UC:0001] Automatic train number shift from preannouncement field Automatic train number shift from preannouncement field to train number field of a line track section

Preconditions preannouncement field not managed by own OMC (e.g. by Railbroker) train number field of the line track section managed by own OMC there is a train number in the preannouncement field line track section is configured for automatic train number shift from associated preannouncement field line track section is currently free

Postconditions train number moved from preannouncement field to the line track section

Trigger occupation message received from ILC

Basic Flow 1. Line track section gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML puts the train number in the train number field of the line track section and removes it from the preannouncement field associated with the line track section according to the configuration. TML performs no topological search. 3. TML generates Break-in message concerning the line track section to ILC / RBP 4. TML sends Break-in command concerning the line track section to the managing station of this train number field via RBP 5. TML generates Outbreak message concerning the preannouncement field to ILC / RBP 6. TML records the operation Break-in via IF-19, if configured.

Alternative Flows 2a. no train number in the preannouncement field: 1. TML generates the ghost number and puts it in the train number field of the line track section 2. sequence terminates here


[OMC-TML:SSS:REQ:0070], [OMC-TML:SSS:REQ:0071], [OMC-TML:SSS:REQ:0136] for configuration: [OMC-TML:SSS:REQ:0111], [OMC-TML:SSS:REQ:0114], [OMC-TML:SSS:REQ:0115], [OMC-TML:SSS:REQ:0116], [OMC-TML:SSS:REQ:0118]


Identification [OMC-TML:SSS:UC:0002] Automatic train number shift over an arrival signal From line track section to track section in the station.

Preconditions there is a train number in the train number field of the line track section in front of the arrival signal managed by own OMC goal train number field behind the arrival signal is also managed by the own OMC arrival signal shows a free speed aspect arrival signal is configured as train number shift point


3BU 51500 5301 DTAPA / 03 / RL / 105




Use Case

Postconditions train number moved correspondig to train movement train number set on the goal track section placed in the train route starting currently at the arrival signal


Basic Flow 1. Track bound element immediately after the arrival signal gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML performs successfully the topological search in order to find both goal and start train number fields. 3. TML puts the train number in the goal train number field and removes it from the start train number field. 4. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 5. TML records the operation Automatic train number shift via IF-19, if configured.


[OMC-TML:SSS:REQ:0059], [OMC-TML:SSS:REQ:0052], [OMC-TML:SSS:REQ:0053], [OMC-TML:SSS:REQ:0054], [OMC-TML:SSS:REQ:0055], [OMC-TML:SSS:REQ:0057], [OMC-TML:SSS:REQ:0060], [OMC-TML:SSS:REQ:0065], [OMC-TML:SSS:REQ:0074] for configuration [OMC-TML:SSS:REQ:0114], [OMC-TML:SSS:REQ:0119], [OMC-TML:SSS:REQ:0126], [OMC-TML:SSS:REQ:0120], [OMC-TML:SSS:REQ:0121]


Identification [OMC-TML:SSS:UC:0003] Enter neighbouring service instance Train number enters following instance service area by automatic train number shift

Preconditions there is a train number in the train number field in front of departure signal, managed by own OMC goal train number field (line track section) is configured as a border train number field; partner of this border train number field belongs to another station, managed by neighbor TML instance departure signal shows a free speed aspect departure signal is configured as train number shift point

Postconditions train number moved correspondig to train movement neighbor station received the train number information





Use Case

Basic Flow 1. Track bound element immediately after the departure signal gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML performs successfully the topological search in order to find both goal and start train number fields. 3. TML puts the train number in the goal train number field and removes it from the start train number field. 4. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 5. TML generates also Break-in message concerning the goal train number field and sends it to the neighbor TML instance managing the station, where the partner of the border train number field is visible, in order to inform it, that the train number enters its service area. The neighboring TML instance performs the Break-in operation in the same way, as in the case, if the message has been sent by the station managing this train number field (although managed by the own OMC). This Break-in operation will not be recorded. The neighboring instance sends no train number message back to the instance, which has initiated the automatic train number shift. 6. TML records the operation Automatic train number shift via IF-19, if configured.


[OMC-TML:SSS:REQ:0064], [OMC-TML:SSS:REQ:0066], [OMC-TML:SSS:REQ:0127] for configuration [OMC-TML:SSS:REQ:0112] additionally all requirements refered in the Use Case Automatic train number shift over an arrival signal ([OMC-TML:SSS:UC:0002])


Identification [OMC-TML:SSS:UC:0004] Leave proceeding service instance Train number leaves proceeding instance service area by automatic train number shift

Preconditions there is a train number field (line track section) in front of block signal / arrival signal, managed by own OMC this field is configured as a border train number field; partner of this border train number field belongs to another station, managed by neighbor TML instance block signal / arrival signal shows a free speed aspect block signal / arrival signal is configured as train number shift point




3BU 51500 5301 DTAPA / 03 / RL / 105




Use Case

Basic Flow 1. Track bound element immediately after the block signal / arrival signal gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML performs successfully the topological search in order to find both goal and start train number fields. 3. TML puts the train number in the goal train number field and removes it from the start train number field. 4. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 5. TML generates also Outbreak message concerning the start train number field and sends it to the neighbor TML instance managing the station, where the partner of the border train number field is visible, in order to inform it, that the train number leaves its service area. The neighboring TML instance performs the Outbreak operation in the same way, as in the case, if the message has been sent by the station managing this train number field (although managed by the own OMC).This Outbreak operation will not be recorded. The neighboring instance sends no train number message back to the instance, which has initiated the automatic train number shift. 6. TML records the operation Automatic train number shift via IF-19, if configured.


See Use Case Train number enters following instance service area by automatic train number shift


Identification [OMC-TML:SSS:UC:0005] enter following station Train number enters following station by automatic train number shift neighbor station received the train number information

Preconditions See the use case Train number enters following instance service area by automatic train number shift, except of goal train number field (line track section) is configured as a border train number field; partner of this border train number field belongs to another station, managed also by the same TML instance

Postconditions train number moved correspondig to train movement


Basic Flow See the use case Train number enters following instance service area by automatic train number shift. TML generates also the Break-in message concerning the goal train number field and sends it to the own TML instance. (Same mechanism to be implemented not depending on the fact, whether the same TML instance or another one is managing the partner of the border train number field.)


[OMC-TML:SSS:REQ:0064], [OMC-TML:SSS:REQ:0066], [OMC-TML:SSS:REQ:0127] for configuration [OMC-TML:SSS:REQ:0113] additionally all requirements refered in the Use Case Automatic train number shift over an arrival signal ([OMC-TML:SSS:UC:0002])

Issues no issues




Use Case

Identification [OMC-TML:SSS:UC:0006] leave proceeding station Train number leaves proceeding station by automatic train number shift

Preconditions See the use case Train number leaves proceeding instance service area by automatic train number shift, except of partner of the border train number field concerned belongs to another station, managed also by the same TML instance



Basic Flow See the use case Train number leaves proceeding instance service area by automatic train number shift. TML generates also the Outbreak message concerning the start train number field and sends it to the own TML instance. (Same mechanism to be implemented not depending on the fact, whether the same TML instance or another one is managing the partner of the border train number field.)


See Use Case Train number enters following station by automatic train number shift


Identification [OMC-TML:SSS:UC:0007] Automatic train number shift over an internal agree point Automatic train number shift over an internal agree point

Preconditions there is a train route starting at a main signal, ending at an internal agree point main signal shows currently a free speed aspect main signal (start element) is configured as train number shift point agree point (goal element) is not configured as train number shift point no fictive train number field associated with this agree point

Postconditions train number moved correspondig to train movement train number set on the goal track section placed behind the agree point


Basic Flow 1. Track bound element immediately after the main signal gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML performs successfully the topological search in order to find both goal and start train number fields. Goal train number field is placed behind the agree point, in front of the next main signal or protection signal in the train movement direction. 3. TML puts the train number in the goal train number field and removes it from the start train number field. 4. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 5. TML records the operation Automatic train number shift via IF-19, if configured.


3BU 51500 5301 DTAPA / 03 / RL / 105




Use Case


[OMC-TML:SSS:REQ:0137] additionally all requirements refered in the Use Case Automatic train number shift over an arrival signal ([OMC-TML:SSS:UC:0002])


Identification [OMC-TML:SSS:UC:0008] Automatic train number shift over an agree point at topology end Train leaves the station via train route ending at agree point

Preconditions there is a train route starting at a main signal, ending at an agree point main signal shows currently a free speed aspect (approval for train route received) main signal (start element) is configured as train number shift point agree point (goal element) is configured as train number shift point there is currently a train number in the train number field in front of main signal, this field is managed by own OMC

Postconditions train number moved correspondig to train movement train number set on the goal track section placed behind agree point (goal element)


Basic Flow 1. Track bound element immediately after the main signal gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML performs successfully the topological search in order to find both goal and start train number fields. Goal train number field is placed behind the agree point. 3. TML puts the train number in the goal train number field and removes it from the start train number field. 4. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 5. TML records the operation Automatic train number shift via IF-19, if configured.




Identification [OMC-TML:SSS:UC:0009] Automatic train number shift over an agree point at topology beginning Train enters the station via train route starting at agree point




Use Case

Preconditions there is a train route starting at agree point, ending at a main signal agree point in state approval granted (corresponding to free speed aspect of a main signal) agree point (start element) is configured as train number shift point main signal (goal element) is configured as train number shift point there is currently a train number in the train number field in front of agree point, this field is managed by own OMC

Postconditions train number moved correspondig to train movement train number set on the goal track section placed in front of main signal (goal element)


Basic Flow 1. Track bound element immediately after the agree point gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML performs successfully the topological search in order to find both goal and start train number fields. Goal train number field is placed behind the agree point, in front of the goal element. 3. TML puts the train number in the goal train number field and removes it from the start train number field. 4. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 5. TML records the operation Automatic train number shift via IF-19, if configured.




Identification [OMC-TML:SSS:UC:0010] Automatic train number shift over an protection signal Between two track sections in the station.

Preconditions there is a train number in the train number field of the track section in front of the protection signal managed by own OMC goal train number field behind the protection signal is also managed by the own OMC protection signal shows a free speed aspect protection signal is configured as train number shift point

Postconditions train number moved correspondig to train movement train number set on the goal track section placed in the train route starting currently at protection signal



3BU 51500 5301 DTAPA / 03 / RL / 105




Use Case

Basic Flow 1. Track bound element immediately after the protection signal gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. TML verifies that a start indication is present for the protection signal. This is the essential attribute to distinguish train routes from shunting routes, if the route is starting at protection signal. 3. TML performs successfully the topological search in order to find both goal and start train number fields. 4. TML puts the train number in the goal train number field and removes it from the start train number field. 5. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. (The same as described in the Use Case Automatic train number shift over an arrival signal.) 6. TML records the operation Automatic train number shift via IF-19, if configured.

Alternative Flows 2a. no start indication present: 1. TML starts a 5 second scrambling supervision timeout 2. The scrambling timeout expires 3. sequence terminates here

2a2a. start indication arives: 1. TML performs successfully the topological search in order to find both goal and start train number fields. 2. TML puts the train number in the goal train number field and removes it from the start train number field. 3. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. (The same as described in the Use Case Automatic train number shift over an arrival signal.) 4. TML records the operation Automatic train number shift via IF-19, if configured.




Identification [OMC-TML:SSS:UC:0011] random message order in a relay interlocking Automatic train number shift considering random message order in a relay interlocking system

Preconditions all elements concerned belong to a station of relay interlocking type there is a train number in the train number field of the train number shift point (element type of the train number shift point does not matter) both start and goal train number fields are managed by the own OMC train number shift point shows a free speed aspect, starting aspect is also available

Postconditions no postconditions





Use Case

Basic Flow 1. Track bound element immediately after the train number shift point gets occupied. This occupation message received from ILC initiates the automatic train number shift. 2. During the topological search for the goal train number field TML detects a switch from the peak (facing switch), which is currently moving, so it is not possible to determine further direction of the topological search. (It is caused by the random message order in the relay interlocking system. In the electronic interlocking system it would be not possible, to switch the free signal aspect at the start element without proper switch position.) 3. TML starts a 5 second scrambling supervision timeout 4. The switch reports a supervised end position (left or right) during the 5s timeout started by TML. 5. TML continues its topological search and finally finds the goal train number field. 6. TML puts the train number in the goal train number field and removes it from the start train number field. 7. TML generates Automatic train number shift message (one message) concerning both start and goal train number field. 8. TML records the operation Automatic train number shift via IF-19, if configured.

Alternative Flows 4a. scrambling timeout expires: 1. TML issues a train number alarm 2. sequence terminates here


[OMC-TML:SSS:REQ:0056], [OMC-TML:SSS:REQ:0058], [OMC-TML:SSS:REQ:0061], [OMC-TML:SSS:REQ:0130], [OMC-TML:SSS:REQ:0131], [OMC-TML:SSS:REQ:0132] additionally all requirements refered in the Use Case Automatic train number shift over an arrival signal ([OMC-TML:SSS:UC:0002])

Issues no issues [OMC-TML:SSS:REQ:0049] — FUR Train number shift points

All element types, which are in principle allowed as start element of a train route (main signal, protection signal, agree point) and the block signal (as a special type of the main signal) shall be considered as possible train number shift points. For configuration see [OMC-TML:SSS:REQ:0119].






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0050] — FUR Train number field employable as start / goal train number field

A train number field shall be employable as a start / goal number field of the automatic train number shift only if it is configured as

— train number address or — preannouncement field or — fictive train number field

A track section without train number field has no relevancy for the automatic train number shift and shall be skipped in course of the topological search.






Comments:

[OMC-TML:SSS:REQ:0051] — FUR Further direction of the topological search

If there is a switch in the topological search path, special conditions shall be applied for start / goal train number field search (see also [OMC-TML:SSS:REQ:0053] and [OMC-TML:SSS:REQ:0055]). If there is a track crossing / flat crossing (in a relay interlocking system) in the topological search path, then the search shall be continued crossways. (A flat crossing in ESTW, represented by two switches, shall be also by TML handled as two switches.)






Comments: The direction of further topological search at all other elements is unambiguous.

[OMC-TML:SSS:REQ:0052] — FUR Start train number field description

Start train number field shall be traced by TML by means of backward topological search beginning at a train number shift point (see also [OMC-TML:SSS:REQ:0049]). It shall be the first employable train number field found. It shall not matter, if there are other elements placed in between. For employable train number fields see also [OMC-TML:SSS:REQ:0050].






Comments:




[OMC-TML:SSS:REQ:0053] — FUR Start train number field search conditions

Start train number field search shall terminate at — start train number field found — switch met from a leg side, if the current position is not corresponding (left leg met - left position required, right leg met - right position required) *) — switch met from the peak, if the current position is not a supervised end position — previous main signal or protection signal in the train direction (=against the search direction), previous agree point; it does not matter, whether the element is configured as train number shift point — service area end






Comments: *) It is not required that there is currently a train route ending at the train number shift point, so the current switch position shall be checked although it is not necessary for determination of further search direction.

[OMC-TML:SSS:REQ:0054] — FUR Goal train number field description

Goal train number field shall be traced by TML by means of forward topological search beginning at a train number shift point (see also [OMC-TML:SSS:REQ:0049]). It shall be

— the last train number field in front of the next main signal or protection signal corresponding to the train movement direction or — the last train number field in front of the block start against the train movement direction — the last train number field in front of the service area end (e.g. line track section, track section behind an agree point or in front of the goal point) - service area end to be identified by an element having no further topological neighbor — fictive train number field associated with the agree point, if there is any in the search path

For employable train number fields see also [OMC-TML:SSS:REQ:0050]. It shall be allowed, that there is another train number field placed between the train number shift point and the goal train number field.






Comments: The goal train number field found at this way shall correspond to the start train number field of the following automatic train number shift. The orientation of a block start in relation to the train movement direction is the same as that of a main / protection signal - block start against the train movement direction will be met from 'back'.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0055] — FUR Goal train number field search conditions

Goal train number field search shall terminate at • switch met from the peak, if the current position is not a supervised end position *) • next main signal or protection signal (not applicable for an agree point) in the train direction (= the search direction also), if

— an employable train number field has been found in-between or — no employable train number field has been found in-between and the automatic train number shift over the following signal is configured; for configuration see also [OMC-TML:SSS:REQ:0119] (If no employable train number field have been found and the automatic train number shift over the signal shall not be performed, then the search shall be continued.)

• block start against the train direction (= against the search direction also), if an employable train number field has already been passed • service area end






Comments: *) The position of the switch met from the peak is necessary to determine the further search direction. There is no need to check the current position of the switch met from a leg side, because without defined position the speed aspect of the train route start element would be not free. It is not necessary to check, if the switch is actually locked by a train route.

[OMC-TML:SSS:REQ:0056] — FUR Start / goal train number field not found

If the start / goal train number field cannot be found due to the desired switch position missing (for conditions see also [OMC-TML:SSS:REQ:0053] and [OMC-TML:SSS:REQ:0055]) a train number timeout of 5s shall be started and TML shall wait for this switch position. If the desired switch position would be reached within train number timeout, TML shall continue the topological search. Train number timeout shall not be started more than once for a particular automatic train number shift operation (i.e. not for each missing switch position separately). If the start / goal train number field cannot be found due to some other cause, the topological search for this train number field shall terminate immediately (without starting a timeout).






Comments:




[OMC-TML:SSS:REQ:0057] — FUR Topological search order

TML shall perform the topological search for the goal train number field first. If the goal train number field has been found (immediately or within train number timeout), the topological search for the start train number field shall be performed subsequently. The topological search for the start train number field shall also be performed if the goal train number field cannot be found. (It will not be possible to perform the automatic train number shift, but it will help to precise the data of the train number message to be generated).






Comments: Corresponding to actual ELEKTRA train number function.

[OMC-TML:SSS:REQ:0058] — FUR Train number timeout expired

If the train number timeout expires, then the topological search for the start / goal train number field shall be considered as terminated without success. For special conditions depending on whether start / goal / both train number fields cannot be found and the current availability of the train number see [OMC-TML:SSS:REQ:0130], [OMC-TML:SSS:REQ:0131], [OMC-TML:SSS:REQ:0132], [OMC-TML:SSS:REQ:0133].






Comments:

[OMC-TML:SSS:REQ:0130] — FUR Both start and goal train number fields not found

If TML is not able to perform the automatic train number shift, because both start and goal train number fields cannot be found, then TML shall raise a general train number alarm with no relation to particular train number field. Train number message containing following data shall be sent to ILC of the station, which the train number shift point belongs to:

— operation Global alarm — additional attributes Blinking and Alarm set — both start and goal train number fields - Dummy — no train number (filled with Blancs)

This alarm will not be persisted.






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0131] — FUR Goal train number field not found, train number available

If TML is not able to perform the automatic train number shift, because the goal train number field cannot be found and there is currently a train number in the start train number field, then TML shall raise a train number alarm concerning the start train number field. Train number message containing following data shall be sent to ILC of the station, which the track section of the start train number field belongs to:

— operation State change — additional attributes Blinking and Alarm set — start train number field - Dummy — goal train number field - start train number field found by topological search — train number from the start train number field

This data shall be persisted. Train number message shall be applicable only if the start train number field is managed by the OMC, otherwise a train number command with same data shall be sent to the managing station of the start train number field.






Comments: Operation Global alarm is a new operation, not based on X25 definition. To be used only for train number messages from TML to ILC.

[OMC-TML:SSS:REQ:0132] — FUR Goal train number field not found, no train number

If TML is not able to perform the automatic train number shift, because the goal train number field cannot be found and there is currently no train number in the start train number field, then TML shall raise a general train number alarm. This train number message shall be sent to ILC of the station, which the track section of the start train number field belongs to. For message data definition see [OMC-TML:SSS:REQ:0130]. This alarm will not be persisted.






Comments:




[OMC-TML:SSS:REQ:0133] — FUR Start train number field not found

If TML is not able to perform the automatic train number shift, because the start train number field cannot be found, then TML shall perform Break-in of a ghost train number in the goal train number field. Train number message containing following data shall be sent to ILC of the station, which the track section of the goal train number field belongs to:

— operation Break-in — additional attributes Blinking and Schedule difference NADA set — start train number field - Dummy — goal train number field - goal train number field found by topological search — ghost train number generated by TML (for the ghost number see also [OMC-TML:SSS:REQ:0075] and [OMC-TML:SSS:REQ:0076]).

This data shall be persisted. Break-in operation shall be recorded if configured so (see also [OMC-TML:SSS:REQ:0116]). Train number message shall be applicable only if the goal train number field is managed by the OMC, otherwise a train number command with same data shall be sent to the managing station of the goal train number field.






Comments:

[OMC-TML:SSS:REQ:0059] — FUR Initiation of the automatic train number shift by occupation

The automatic train number shift shall be initiated by the occupation of a track bound element (track section, switch, track crossing, single key operated switch, derail) immediately behind a

— main signal with free signal aspect — protection signal with free signal aspect, if it has been switched on for a train route (in that case starting aspect also available) — subsidiary / caution signal / virtual caution signal currently switched on, placed at the mast of a main signal or a protection signal — agree point in the current state “agreement granted for train”

if the main signal, protection signal, agree point concerned or on the same mast of subsidiary / caution signal / virtual caution signal concerned is configured as train number shift point. If the considered track bound element is already occupied at the moment, when the signal message (see the list above) has been received, then the automatic train number shift shall be initiated at this moment.






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0060] — FUR Performance of the automatic train number shift

If the start train number field and the goal train number field (see also [OMC-TML:SSS:REQ:0053] and [OMC-TML:SSS:REQ:0055]) have been traced successfully and the initiation conditions (see also [OMC-TML:SSS:REQ:0059]) are fulfilled, then the automatic train number shift shall be performed - it means the train number (and all its additional attributes) from the start train number field shall be placed in the goal number field. If there already was a train number in the goal train number field, it shall be overwritten. Afterwards the start number field shall stay empty.






Comments:

[OMC-TML:SSS:REQ:0061] — FUR Special conditions in a relay interlocking system

In the relay interlocking system there is no guaranteed message order. TML shall expect, that the element state messages may be received in a random order and consider this fact while checking the initiation conditions for the automatic train number shift. This concerns especially following conditions:

1) free signal aspect of a protection signal as automatic train number shift point, no start information received yet for this signal - TML shall perform the automatic train number shift after receiving of the start information; no supervision timeout shall be started 2) change of signal aspect of an automatic train number shift point from free to stop / dark, no occupation behind the signal yet - TML shall perform the automatic train number shift after receiving of the occupation message; supervision timeout of 5s length shall be started 3) occupation behind an automatic train number shift point without free signal aspect - TML shall perform the automatic train number shift after receiving of the free signal aspect, if the element behind it is still occupied at that moment; no supervision timeout shall be started 4) desired switch position missing, although initiation condition of the automatic train number shift already fulfilled - for handling of this situation see [OMC-TML:SSS:REQ:0054], [OMC-TML:SSS:REQ:0055], [OMC-TML:SSS:REQ:0056].






Comments: In the relay interlocking system it is possible, that e.g. the free speed aspect of the start element will be received before the desired switch position or the starting aspect will be received at last. In the electronic interlocking system the messages concerning a particular train route will be received always in the same defined order.




[OMC-TML:SSS:REQ:0062] — FUR Agree point as automatic train number shift point

If an agree point is configured as automatic train number shift point, TML shall consider it in the same way, as main / protection signal, while performing the automatic train number shift: Neighbor directions of an agree point towards the train movement direction are the same.

1) TML shall search for the occupation initiating the automatic train number shift in the 'back' direction. 2) TML shall search in the 'back' direction for the goal train number field and in the 'front' direction for the start train number field.






Comments: In ELEKTRA train number function the orientation of an agree point in relation to the train movement direction has been reversed in comparison to main / protection signal.

[OMC-TML:SSS:REQ:0137] — FUR Agree point in topological search path

If TML encounters an agree point during the topological search performed for an automatic train number shift starting at an automatic train number shift point placed in front / behind the agree point, TML shall consider following special conditions:

1) If TML is searching for the goal train number field, then the topological search shall be continued over the agree point in the 'back' direction. It does not matter, whether the agree point itself is configured as automatic train number shift or not. (So the goal train number field will be found behind the agree point). 2) If TML is searching for the start train number field, then the topological search shall terminate at an agree point without success. (Probably a configuration error. There has to be a train number field between an agree point and next signal, if next signal is configured as train number shift point).






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0063] — FUR Automatic train number shift ends at a goal point

If a train / combined goal point in train movement direction is configured as the end point of automatic train number shift, than the goal number field search shall terminate at this goal point. In that case, goal number field shall be found in front of the goal point.






Comments: Not implemented in current ELEKTRA train number function. A need for this feature arose in real operation. For configuration item see also [OMC-TML:SSS:REQ:0124]. The orientation of an goal point in relation to the train movement direction is equal to that of a main / protection signal - to be considered, if met from 'front'.

[OMC-TML:SSS:REQ:0064] — FUR Operations over the station / instance border

Operations over the station / instance border shall be performed via border train number fields visible for both neighbor stations / instances (border element existing twice). If TML performs an operation, which results in change of the train number (or its additional attributes) in a border train number field, then the content of the partner element in the neighbor station / instance shall be changed correspondingly. The partner element shall be informed by means of the train number message sent directly to the TML instance managing the partner (not via ILC). If both partners are managed by the same TML instance, this train number message shall be sent to the own instance also, in order to use the same mechanism. Both partners shall be provided with equal rights (no master - slave method).






Comments: If the message will not reach the partner element in neighbor station(e.g. because the neighbor station is temporarily excluded due to maintenance activities), sending TML instance will receive no acknowledge. This information shall be logged (after timeout expiration).




[OMC-TML:SSS:REQ:0065] — FUR Generate Automatic train number shift message

If both start an goal train number fields are not configured as fictive, then at successful performance of the automatic train number shift TML shall generate a train number message containing following information: current train number and all its additional attributes start and goal train number field as detected by topological search action - Automatic train number shift Applicable for both usual and border train number fields. For train number messages Break-in / Outbreak concerning the partner of the border train number field see also [OMC-TML:SSS:REQ:0066].






Comments: Stw 1 / Bit 6 For messages concerning fictive train number fields see subsequent requirements.

[OMC-TML:SSS:REQ:0066] — FUR Generate Break-in / Outbreak message concerning station /

instance border train number fields

If either start train number field or goal train number field is configured as border train number field, then at successful performance of the automatic train number shift TML shall generate a train number message to the TML instance managing its partner element (additionally to usual messages to ILC and RBP, see also [OMC-TML:SSS:REQ:0065]) containing following information:

1) Goal train number field is configured as border one, i.e. train number shift into the neighboring station / service area- action Break-in 2) Start train number field is configured as border one, i.e. further train number shift, so that the train number leaves the neighboring station / service area- action Outbreak

For both of them: — current train number and all its additional attributes — train number field based on the configuration of partner elements (see also [OMC-TML:SSS:REQ:0112])






Comments: Stw 1 / Bit 2, Bit 4 Similar to train number messages concerning a fictive train number field, see [OMC-TML:SSS:REQ:0067] and [OMC-TML:SSS:REQ:0068].


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0067] — FUR Generate Break-in message

If the start train number field is configured as fictive and the goal train number field not, then at successful automatic train number shift TML shall generate a Break-in message concerning the goal train number field containing following information:

— current train number and all its additional attributes — start train number field = dummy — goal number field as detected by topological search — action - Break-in

No message shall be generated concerning start train number field.






Comments: This message to be sent instead of the Automatic train number shift message described in [OMC-TML:SSS:REQ:0065]. Fictive train number fields only applicable for train number shift over an agree point. Stw 1 / Bit 2

[OMC-TML:SSS:REQ:0068] — FUR Generate Outbreak message

If the goal train number field is configured as fictive and the start train number field not, then at successful automatic train number shift TML shall generate an Outbreak message concerning the start train number field containing following information:

— current train number and all its additional attributes — start train number field as detected by topological search — goal train number field = dummy — action - Outbreak

No message shall be generated concerning goal train number field.






Comments: This message to be sent instead of the Automatic train number shift message described in [OMC-TML:SSS:REQ:0065]. Fictive train number fields only applicable for train number shift over an agree point. Stw 1 / Bit 4




[OMC-TML:SSS:REQ:0069] — FUR Generate no message

If both start and goal train number fields are configured as fictive, then at successful automatic train number shift TML need to generate no message.






Comments: Is the automatic train number shift from fictive train number field to another fictive train number field really possible? Conditions? According to current code no message to EBO. Messages to other receivers (sent from another code parts)?

[OMC-TML:SSS:REQ:0070] — FUR Automatic train number shift from a preannouncement field

If a train number field has been configured for the automatic train number shift from an preannouncement field (applicable only for line track sections, see also [OMC-TML:SSS:REQ:0118]) the automatic train number shift shall be initiated by the occupation of this line track section. The train number shall be shifted from the associated preannouncement field ( = start train number field) in the train number field of the currently occupied track section ( = goal track number field).






Comments: No topological search needed to determine start / goal train number field.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0071] — FUR Generate Break-in / Outbreak message, if preannouncement field is concerned

At successful automatic train number shift from a preannouncement field TML shall generate two separate messages concerning the goal and the start number field instead of the train number shift message (as described [OMC-TML:SSS:REQ:0065]). The messages shall be sent in the given order and shall contain following information:

• Break-in message — current train number and all its additional attributes — start train number field = dummy — goal number field (occupied line track section) — action - Break-in

• Outbreak message — current train number and all its additional attributes — start train number field (preannouncement field) — goal train number field = dummy — action - Outbreak

For recording of this automatic operation see [OMC-TML:SSS:REQ:0136].






Comments: Stw 1 / Bit 2, Stw 1 / Bit 4 Message data equal to break-in / outbreak message at automatic train number shift to / from a fictive train number field (see also [OMC-TML:SSS:REQ:0067] and [OMC-TML:SSS:REQ:0068]).

[OMC-TML:SSS:REQ:0072] — FUR Automatic train number deleting by getting free

The train number shall be deleted automatically by getting free, if the track section is configured so (see also [OMC-TML:SSS:REQ:0117]).Applicable at state transition occupied -> free and also disturbed -> free.






Comments:




[OMC-TML:SSS:REQ:0073] — FUR Generate Outbreak message at automatic train number deleting

If the conditions for an automatic train number deleting are fulfilled (see also [OMC-TML:SSS:REQ:0072]), then TML shall generate an outbreak message concerning “freigemeldetes Gleis”

— current train number and all its additional attributes — start train number = “freigemeldetes Gleis” — goal train number field = dummy — action - Outbreak






Comments: Current ELEKTRA train number function sends dummy train number instead of the current train number, but current train number would correspond to Outbreak message sent due to the automatic train number shift from a preannouncement field. Stw 1 / Bit 4

[OMC-TML:SSS:REQ:0074] — FUR Recording of standard automatic train number shift

Considering both requirements [OMC-TML:SSS:REQ:0120] and [OMC-TML:SSS:REQ:0121], standard automatic train number shift shall only be recorded, if the attribute “Record the automatic train number shift over this element” (of the train number shift point concerned) is set to TRUE and the attribute “No recording of the automatic train number shift in front of this element” (of main signal / protection signal / agree point relevant for the goal train number field determination) is set to FALSE. Always to be recorded as Automatic train number shift, also if the operation is split to Break-in and Outbreak in case of start / goal train number field not being managed by the own OMC. In case of recording the Recording flag shall be added to the Automatic train number shift message.






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0136] — FUR Recording of automatic train number shift from a preannouncement field

Since the automatic train number shift from an preannouncement field will always be performed as two separate operations Break-in and Outbreak (see also [OMC-TML:SSS:REQ:0071]), the operations Break-in / Outbreak shall be recorded instead of the operation Automatic train number shift, if recording of Break-in / Outbreak is configured (for configuration see also [OMC-TML:SSS:REQ:0116]).In case of recording the Recording flag shall be added to the Break-in / Outbreak train number message.






Comments:

[OMC-TML:SSS:REQ:0075] — FUR Ghost number generation

TML shall generate a ghost number and put it in the goal train number field, if the conditions for the automatic train number shift are fulfilled (see also [OMC-TML:SSS:REQ:0059]), but in the start train number field (see also [OMC-TML:SSS:REQ:0052]) there is currently no train number. The ghost number shall be generated by TML as follows:

— train number = leading question mark, track section identifier of the start train number field (3 characters), point, ghost number counter (2 digits, for values 0-9 filled with leading 0) — steering character = Blanc — both schedule difference plus /minus = 0

If the track section identifier (as displayed on EBO) is longer than 3 characters, then the last 3 characters shall be used for the ghost number generation. If it is shorter than 3 characters, then it shall be completed with trailing blanks. Validity of the characters derived from the track section identifier shall be checked according to [OMC-TML:SSS:REQ:0007]. Example of ghost train numbers:?201.01, ?a12.02






Comments: It is a special case of the automatic train number shift. Applicable also if the start train number field is an preannouncement field. Train number storage needs not to be considered, because the Requirement [OMC-TML:SSS:CAPA:0005] has been discoped.




[OMC-TML:SSS:REQ:0076] — FUR Ghost number counter

Ghost number counter shall be a serial number between 0 and 99, starting at 0, which shall be increased after each ghost number generation. If the ghost number counter reaches the limit of 99, 0 shall be used next. The ghost number counter shall be maintained separately for each TML instance. The ghost number counter shall be stored as persistent data.






Comments:

3.2.1.4. Instance handling [OMC-TML:SSS:REQ:0078] — FUR Start TML instance

TML instance shall be started within a FUSE ESB-container, managed by OMC Infrastructure Service, as defined in [SSDD INFRA]. TML instance shall be provided with a list of stations to be managed by this instance.





Verification Notes: Source: [OMC-TML:SSS:CAPA:0013] [OMC-TML:SSS:CAPA:0014] [OMC-TML:SSS:CAPA:0031]

Comments: OMC Administration and Diagnosis Service is responsible for station - instance assignment and also for belonging of a station only to the service area of one particular TML instance.

[OMC-TML:SSS:REQ:0079] — FUR Start ARAMIS-TML manager instance

ARAMIS-TML manger instance shall be started within the global FUSE ESB-container, managed by OMC Infrastructure Service, as defined in [SSDD INFRA]. There will be only one instance of this process in the OMC.






Comments: Details concerning functional details of ARAMIS-TML manager see chapter 3.2.1.10 Additional train information.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0080] — FUR Stop TML / ARAMIS-TML manager instance

TML / ARAMIS-TML manager instance shall be able to be stopped by the OMC Infrastructure Service, as defined in [SSDD INFRA].






Comments:

3.2.1.5. Activities on instance start [OMC-TML:SSS:REQ:0081] — FUR Establish connections

Immediately after the start, each TML instance shall establish following connections (physical / logical): — ILC of each station included in its service area (logical connection via IF-11) — ARAMIS-TML manager (using a service-internal message format; further on TCP/IP based connection between ARAMIS-TML manager and ARAMIS train information via IF-06) — OMC Administration and Diagnosis Service (TCP/IP based connection via IF-08 - IF-10) — OMC Protocol Service (logical connection via IF-19) — OMC Database Service (logical connection via IF-23) — start TML command interface (IF-30)






Comments: Connection to OMC Infrastructure Service (IF-24) not really needed?




[OMC-TML:SSS:REQ:0082] — FUR Get station descriptor data

TML shall get all station descriptor data needed by means of file read via File Interface (IF-40). There shall be only one configuration file containing all configuration items provided especially for SIL-0 components, so TML shall pick out on its own the information really needed (e.g. in order to identify elements, which shall be observed further). TML shall get the train number configuration data of all

— main signals — protection signals — agree points — track sections — goal points

in its instance service area. For data details see Requirements from Chapter 3.2.2.2.1.




Verification Method: Test Verification Step: code reading part system test


Comments:

[OMC-TML:SSS:REQ:0083] — FUR General request performance between TML and ILC

Based on the data from station descriptor (see also [OMC-TML:SSS:REQ:0082]) TML shall identify the elements, which shall be concerned by the general request. The general request between TML and ILC in both directions shall be performed. There will not be a ready-made command general request (as known for X25-communication), so TML shall request / send element states really needed on its own. For details concerning states to be communicated see also [OMC-TML:SSS:REQ:0084] and [OMC-TML:SSS:REQ:0085].






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0084] — FUR General request - state update messages from ILC to TML, observing states

TML instance shall register itself at ILC of each station of its service area as observer for following element states:

• station connection state (if the connection is currently down, all following states will stay undefined) • Main signals, protection signals, agree points configured as train number shift points (based on data from station descriptor)

— speed aspect — starting aspect (only for protection signal) — on/off state of subsidiary / caution signal / virtual caution signal (if there is any on the same mast)

• track bound element immediately after train number shift points (see above), considered in train movement direction (it may be a switch, track section, track crossing, single key operated switch in the station or on the line or derailer)

— occupation state (free, occupied, undefined) — position, if this element is a switch

• line track section, if it is configured for automatic train number shift from associated preannouncement field or for automatic deletion by “Freimeldung”

— occupation state Immediately after observer registration ILC shall provide TML with all current states, which TML has been registered for (by means of ILC built-in function).






Comments: This state information is necessary in order to check the conditions for automatic train number shift performance. For data from the station descriptor see also [OMC-TML:SSS:REQ:0082]. There is no need for the removal of the observers, which may be left due to a failure of former managing instance, because the ILC will be able to identify and remove these observers on its own. Startmeldung = start indication




[OMC-TML:SSS:REQ:0085] — FUR General request - train number update from TML to ILC

ILC shall be provided by TML with following current train number states: • full train number information (train number, all additional attributes, additional information) for all configured train number fields corresponding to

— current data from database, if TML instance has been just started and data expiration timeout is not over yet — all data reset to default values (equal to currently no train number set), if TML instance has been just started and data expiration timeout is already expired

This information shall be provided by train number message Break-in, if there is currently a train number or Outbreak, if there is currently no train number. The track section concerned shall be referred in the message data as goal train number field. TML shall generate a message for each track section with train number field. TML shall perform this update without any request from ILC.






Comments: Data expiration timeout length is a configurable item.

3.2.1.6. Activities on instance termination [OMC-TML:SSS:REQ:0086] — FUR Activities on instance termination

Following activities shall be performed before a TML instance terminates (forced by cluster and also due to a failure, if possible):

— remove all observers registered by this instance




Verification Method: Test Verification Step: code reading part system test


Comments: Current train numbers and all information associated with it shall be kept (ILC, persistent data).

3.2.1.7. Administration commands


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0087] — FUR TML Administration commands

All administration commands directed to TML shall be generated by OMC Administration and Diagnosis Service and be delivered via Interface IF-09. Administration commands shall concern the station as the whole, not particular train number or train number field. They shall be performed by TML without any impact on other stations. TML shall notify administration commands by a notification message corresponding to IF-09 definition.






Comments:

[OMC-TML:SSS:REQ:0088] — FUR Set operation mode command

By the administration command setMode a station shall be set in one of the following modes: — NORMAL — RETROFIT_SAFETY_RELATED — RETROFIT_NON_SAFETY_RELATED

TML shall persist the current operation mode of a station. For details concering the mode definition see [IF-09-ADM IF-10-STAT].






Comments: Administration command setMode will be performed ahead / afterwards of maintenance operations. Both inactive mode and maintenance requested mode not to be set by the maintenance command. Applicable only for EBO.

[OMC-TML:SSS:REQ:0144] — FUR Set retrofit mode implicitly

TML shall set a station to the RETROFIT_NON_SAFETY_RELATED mode — after receiving loadStation command (as part of add station operation – see [OMC-TML:SSS:REQ:0090]) — after reading a configuration file update, containing added station (as part of move station operation – see [OMC-TML:SSS:REQ:0146] and [OMC-TML:SSS:REQ:0148])






Comments:




[OMC-TML:SSS:REQ:0089] — FUR Remove Station

Administration command removeStation shall induce, that station given as command parameter will be removed from instance service area. TML shall remove the station and all its elements from the database.






Comments: Handling of this station to be stopped at configuration file change prior to this command. See [OMC-TML:SSS:REQ:0145].

[OMC-TML:SSS:REQ:0090] — FUR Add Station

Administration command loadStation shall induce, that station given as command parameter and currently not included in the instance service area, will be added to the instance service area. After receiving this command TML shall load the station descriptor data of the station and take the operation mode RETROFIT_SAFETY_RELATED. After following update of the configuration file TML shall change the operation state to non-SIL-maintenance and start the handling of the station.






Comments:

[OMC-TML:SSS:REQ:0145] — FUR Station removed from configuration file

TML shall stop handling of a station, but keep the persisted data, if TML detects, that the station has been removed from the configuration file.






Comments: Configuration file to be updated by Administration and Diagnosis Service prior to administration command removeStation or as a part of move station operation.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0146] — FUR Station added to configuration file

TML shall start handling of a station, if TML detects, that the station has been added to the configuration file.






Comments: Configuration file to be updated by Administration and Diagnosis Service after administration command loadStation or as a part of move station operation. Persisted data already recorded (loadStation) or kept (move station operation).

[OMC-TML:SSS:REQ:0147] — FUR Update station descriptor data

Administration command loadStation shall induce, that station descriptor data of the station given as command parameter and handled currently by TML shall be updated. The command shall be allowed only in a retrofit mode.






Comments: Train numbers, which were located on tracks which were removed in the updated topology, shall be removed.

[OMC-TML:SSS:REQ:0148] — FUR Move station to another cell

If a station shall be moved from Cell 1 to Cell 2, the maintenance operation will be performed as follows: — If TML in Cell 1 reads a configuration file update, where a station has been removed, TML in Cell 1 shall stop the handling of the station. All persisted data concerning this station shall be kept. The operation mode of this station shall be changed to RETROFIT_SAFETY_RELATED. — If TML in Cell 2 reads a configuration file update, where a station has been added, TML in Cell 2 shall start the handling of the station. It shall load the station descriptor data of this station and use the data persisted previously by TML in Cell 1. The operation mode of this station shall be changed to non-SIL-maintenance.






Comments:




[OMC-TML:SSS:REQ:0091] — FUR ARAMIS-TML manager during maintenance

There shall be no special activities performed by ARAMIS-TML manager due to maintenance. If a TML instance is not able to handle an ETCS telegram sent by ARAMIS-TML manager while being in the retrofit mode, the telegram shall be answered by negative acknowledge. In this situation the information shall be stored by ARAMIS-TML Manager into a special database table (which shall hold only information about trains located in the OMC area which were announced by ARAMIS while the respective station was in RETROFIT_SAFETY_RELATED mode), and, when TML will start handling the station again, the stored ETCS information shall be merged into trains table of that station and removed from the special table.






Comments:

[OMC-TML:SSS:REQ:0149] — FUR Restrictions in NORMAL mode

If a station is in NORMAL mode the full functionality of TML shall be available. In this mode TML shall reject following maintenance operations:

— update station descriptor data of a station currently handled by TML by administration command loadStation — remove a station by administration command removeStation






Comments:

[OMC-TML:SSS:REQ:0150] — FUR Restrictions in RETROFIT_NON_SAFETY_RELATED mode -

TML station handling instance

In RETROFIT_NON_SAFETY_RELATED mode the full functionality of TML shall be available. Only while loadStation command is active, TML will not be able to perform any train number operation. Notifications received during this period shall be processed after loadStation completion. All currently available train numbers with all their additional attributes and flags shall be kept in RETROFIT_NON_SAFETY_RELATED mode.






Comments: Full functionality means equal to active mode.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0151] — FUR Restrictions in RETROFIT_SAFETY_RELATED - TML station handling instance

In RETROFIT_SAFETY_RELATED mode no TML functionality shall be available: — TML shall reject the train number commands by negative command notification. — TML shall ignore train number messages. — TML shall not perform any automatic train number shift.

All currently available train numbers with all their additional attributes and flags shall be kept in RETROFIT_SAFETY_RELATED mode.






Comments:

[OMC-TML:SSS:REQ:0152] — FUR Restrictions in both retrofit modes - TML-ARAMIS-Manager

In both RETROFIT_SAFETY_RELATED and RETROFIT_NON_SAFETY_RELATED modes the full functionality of TML-ARAMIS-Manager shall be available. Only while loadStation command is active, operations to be performed by TML-ARAMIS-Manager will be delayed and performed after completion of command performance.






Comments: Full functionality means equal to active mode.

3.2.1.8. Adaptation activities [OMC-TML:SSS:REQ:0092] — FUR Activities on add station

After a station has been added to the instance service area by means of loadStation (see [OMC-TML:SSS:REQ:0090]) command or as part of move station operation (see [OMC-TML:SSS:REQ:0148]) TML shall perform following operations:

— perform general request in both directions concerning all relevant elements of this station (for details see also [OMC-TML:SSS:REQ:0084] and [OMC-TML:SSS:REQ:0085])






Comments: Similar to activities at instance start.




[OMC-TML:SSS:REQ:0093] — FUR Activities on remove station

After a station has been removed from the instance service area by means of removeStation command or as part of move station operation TML shall perform following activities:

— remove all observers registered by current TML instance in the station to be removed






Comments:

3.2.1.9. ILC connection state [OMC-TML:SSS:REQ:0094] — FUR Monitor TML-ILC connection

TML shall monitor the connection to each ILC needed by monitoring of life cycle messages sent by ILCs.






Comments: For more details see [IF-11-ICD] and [GCD-SIL0].

[OMC-TML:SSS:REQ:0095] — FUR General request after TML-ILC connection re-establishment

TML shall monitor the ILC connection state. After the ILC connection has been restored, TML shall receive current element / station connections states from ILC and provide ILC with current train number states. States to be provided are the same, as provided by general request after instance start. For Details see [OMC-TML:SSS:REQ:0084] (from ILC to TML) and [OMC-TML:SSS:REQ:0085] (from TML to ILC).






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0153] — FUR Train number update from TML to ILC after short time connection loss

If the connection between ILC and TML is down and up again without TML noticing loss of ILC life cycle, TML will receive the information "connection ok" without previous "connection not ok". In this case TML shall provide ILC with current train number information: full train number information (train number, all additional attributes, additional information) for all configured train number fields corresponding to current data from database, if a train number is currently available (data expiration timeout not to be concidered) This information shall be provided by train number message Break-in.The track section concerned shall be referred in the message data as goal train number field.






Comments: Similar to [OMC-TML:SSS:REQ:0085], but Outbreak for empty train number fields not to be sent.

3.2.1.10. Additional train information Additional train information will be provided by another external component (e.g. ARAMIS). It concerns particular train numbers, but is not a part of train number data based on X25 protocol (in contrast to additional train number attributes, see also [OMC-TML:SSS:REQ:0011], which are the part of this data). A telegram received from ARAMIS train information concerns particular train number, but there is no information about track section, where the train number is currently placed. It is also possible, that one telegram contains information concerning multiple train numbers. In order to distribute the information properly to the TML instances currently responsible for the individual train number, it will be necessary to have single instance ARAMIS-TML manager process. [OMC-TML:SSS:REQ:0096] — FUR RBC registration status

Presently the only additional train information, which shall be supported by TML is: — the registration status of this train in particular RBC, multiple RBCs shall be possible

Only train numbers with up to 6 characters can be provided with this information.






Comments: Presently no need for any other additional information.




[OMC-TML:SSS:REQ:0097] — FUR Communication protocol for ETCS information

TML Service shall receive additional information concerning ETCS directly from ARAMIS train information via IF-06. Special therefore designed communication protocol shall be implemented as described in [SS ETCS]. In further text a telegram received from ARAMIS train information, containing additional information about ETCS equipment will be referred only as ETCS telegram.




Verification Method: Test Verification Step: system test part system test


Comments:

[OMC-TML:SSS:REQ:0098] — FUR ARAMIS-TML Manager

ARAMIS-TML-MNG shall be a single copy process with following responsibilities: — use an interface to ARAMIS train information (IF-06) — receive ETCS telegrams via IF-06 — distribute ETCS telegram parts concerning singular train numbers to the TML instances currently responsible for these train numbers over JMS, using a service internal message format (no service interface needed) — collect the acknowledge messages of partial ETCS telegrams concerning singular train numbers, build an overall acknowledge message and send it to ARAMIS train information via IF-06






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0099] — FUR ETCS Telegram distribution

In order to distribute the ETCS telegram parts properly to the TML instances currently responsible for singular train numbers, ARAMIS-TML manager process shall:

— find out based on database query, where the train number is currently placed — if an station / instance border train number field is concerned, then the train number will be found in both partner elements — partial ETCS telegram shall be sent to the station responsible for the next automatic train number shift; this information is also available in the database






Comments: For details concerning persistent data see [OMC-TML:SSS:REQ:0104] and [OMC-TML:SSS:REQ:0105]. For details concerning operations on border train number fields see [OMC-TML:SSS:REQ:0064].

[OMC-TML:SSS:REQ:0100] — FUR Partial ETCS telegram acknowledge

TML shall accept the partial ETCS telegram only if the train number concerned is currently placed in its service area and the instance itself is responsible for next automatic train number shift. In this case positive acknowledge message shall be sent to ARAMIS-TML manager process, otherwise a negative one.






Comments:




[OMC-TML:SSS:REQ:0101] — FUR ETCS telegram handling

If TML accepts a partial ETCS telegram (see also [OMC-TML:SSS:REQ:0100]), then TML shall update instance internal data / database according to telegram data (RBC identification, registration status). TML shall generate a train number message to ILC containing current train number, all current additional attributes and updated ETCS information. Start train number may be Dummy. Goal train number field shall be that one, where the train number is currently placed. Message operation shall be ETCS. If a border train number field is concerned, partner train number field visible in the neighbor station shall be informed by means described in [OMC-TML:SSS:REQ:0064] concerning operations on border train number fields in general. TML shall generate no train number message to RBP for stations to get informed, because those stations shall receive just the train number information corresponding to X25 definition.






Comments: Goal train number field used, similarly to Dial-in or Break-in. Stw 3, Bit 3

[OMC-TML:SSS:REQ:0138] — FUR ETCS information for unknown train number

ARAMIS-TML-MNG shall accept the ETCS information even if the train number concerned has not entered the OMC yet (e.g. by means of Break-in, Dial-in). ARAMIS-TML-MNG shall handle this part of the ETCS telegram as positively acknowledged, although it is not possible to forward it to responsible TML instance. ARAMIS-TML-MANAGER shall persist the ETCS information of this train number, without connection to particular train number field.






Comments: ATRS will send a request for this train number, if ATRS receives the train number by means of answer to train number back tracking, before this train number enters the OMC. ATRS will send this request to the TML instance responsible for the station, which the start element of back tracking belongs to.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0139] — FUR Join ETCS information with train number received afterwards

If a new train number enters the OMC (e.g. by means of Break-in / Dial-in from Railbroker / other station or by means of a manual command), the command /message data has to be joined with currently available ETCS information persisted by ARAMIS-TML-MNG, as described in [OMC-TML:SSS:REQ:0138]. The message to ILC, generated as result of Dial-in / Break-in operation performance shall contain the joined information.






Comments:

[OMC-TML:SSS:REQ:0140] — FUR Request for ETCS information

TML shall be able to answer a request for ETCS information of a particular train number. TML shall provide the requesting service with the information persisted by ARAMIS-TML-MNG as described in [OMC-TML:SSS:REQ:0138]. TML shall answer the request in the same way, also if the train number has entered the OMC in the mean time. Both request and answer shall be transmitted via IF-30.






Comments:

[OMC-TML:SSS:REQ:0102] — FUR Forwarding ETCS information

ILC shall be responsible for forwarding of ETCS information. All components interested in train number information will receive the full information - both usual train number information (corresponding to X25 definition) and additional information. Each component shall pick the information needed on its own.




Verification Method: Test Verification Step: analysis part system test


Comments: ATRS and EBO will need the full train number information. RBP will receive the train number information during general query between ILC and RBP and will need just the usual part.




[OMC-TML:SSS:REQ:0103] — FUR Default ETCS information

If no ETCS information have been received yet for particular train number, then the additional information shall be set to default values as follows:

— not ETCS equipped train — RBC = Dummy — not registered

Applicable for internal data, database, train number messages.






Comments:

3.2.1.11. Persistent data [OMC-TML:SSS:REQ:0104] — FUR Store train number data as persistent data

TML shall store current train numbers, all additional attributes and additional information concerning RBC registration status via Interface to OMC Database Service (IF-23) as persistent data. It does not matter, whether the train number data has been changed due to train number command, train number message, automatic train number shift or any other mechanism.






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0105] — FUR Station responsible for particular train number

It shall also be stored as persistent data, which station is responsible for particular train number. It shall be that station, which will perform next automatic train number shift of this train number. This information is very important for instance border train number fields in order to distribute additional train information correctly (see also [OMC-TML:SSS:REQ:0099]), but it shall be maintained also for usual train number fields to make the algorithm unique:

— station / instance border train number field, visible for both stations / instances: if automatic train number shift has been performed from station A to station B lately, then station B will be responsible for next automatic train number; if the train number has been placed by some other operation, then it shall be the station, which has performed this operation (e.g. command Dial-in) — train number field in the middle of a station: station itself






Comments:

3.2.1.12. Logging [OMC-TML:SSS:REQ:0141] — FUR Operational Log

TML operational log shall contain information about events of operational importance. Events to be logged, message types, parameters and message text shall comply with the definition in [IF-08-LIF].






Comments: To be used by customer's maintenance staff and first level support of Thales.

[OMC-TML:SSS:REQ:0142] — FUR Technical Log

TML technical log shall contain additional technical information for diagnosis purpose. The only restriction is the usage of English language. The decision about events and information to be logged is under TML's responsibility.






Comments: To be used by technical staff of Thales.




[OMC-TML:SSS:REQ:0143] — FUR Use the ADM Logging Interface (IF-08)

TML shall use the ADM Logging Interface (IF-08) provided by OMC Administration and Diagnosis Service for both operational and technical logging.






Comments:

3.2.2. System External Interface Requirements

3.2.2.1. Cooperation with RBP [OMC-TML:SSS:REQ:0106] — FUR Other systems providing / to be provided with train number

information

TML shall communicate with other systems providing / to be provided with train number information via RBP. RBP shall use therefore the TML Command Interface (IF-30). Other system may be:

— Railbroker — OMC’s neighbor, such as standalone interlocking system, BOS center, another OMC






Comments:


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0107] — FUR Communication between TML Service and RBP

TML Service shall communicate with RBP via TML Command Interface (IF-30) in these circumstances: 1) TML receives via RBP a train number command sent by another system, concerning a train number field managed by the own OMC 2) TML sends via RBP a train number message to another system, concerning a train number field managed by own OMC, in order to inform it about train number update performed by TML (as result of command performance, automatic train number shift or additional train information changed via ARAMIS Train Information) 3) TML sends via RBP a train number command, concerning a train number field managed by another system, to this system 4) TML receives via RPB a train number message sent by another system, concerning a train number field managed by another system






Comments: For configuration see also [OMC-TML:SSS:REQ:0114] (managing station) and [OMC-TML:SSS:REQ:0115] (station to be informed).

[OMC-TML:SSS:REQ:0108] — FUR Connection state to other system

TML shall not monitor the connection state to other system (only RBP will have this knowledge). If TML would send train number command to other system during connection breakdown, RBP will answer it by negative command acknowledge, which shall not result in the train number alarm generation Train number message during the connection breakdown will be ignored without answer.






Comments: Current ELEKTRA train number function sends the train number command / message to other system only if the connection is established, otherwise no action will be performed (especially no train number alarm generation).

3.2.2.2. Configuration Following requirements describe a variety of attributes, which shall be configured for the TML Service. If there is a similarity to the attributes usually configured for the former train number function of ELEKTRA, it will be indicated as comment.




[OMC-TML:SSS:REQ:0110] — FUR Perform configuration update of single station

It shall be possible to perform configuration update of single station separately, without the need for configuration update of any other station managed by the same TML instance or the same OMC. The only exception: If the configuration modification concerns a border train number field, it will be perhaps necessary (depending on the modifications done) to perform also configuration update of the neighbor station, where the partner of the border train number field is also visible.






Comments: It is also currently necessary to perform ELEKTRA configuration update, if elements visible in both neighboring stations (e.g. track section on the line) are concerned. Hint from OREST possible?

3.2.2.2.1. Data from the station descriptor

The following requirements describe all single train number configuration items. For the description how TML shall get this data see also [OMC-TML:SSS:REQ:0082]. [OMC-TML:SSS:REQ:0111] — FUR Train number field type

For each isolated track section in a station or on a line it shall be possible to configure the train number field type as one of the following values:

— no track number field existing — train number address - visible on EBO, manual commands possible — preannouncement field - visible on EBO, no manual command possible — fictive train number field - not visible on EBO, no manual commands possible

Default: no track number field existing




Verification Method: Test Verification Step: tool test part system test


Comments: In ELEKTRA: rlo_track_section - reo_znf_type (e_no_znf, e_znf_adresse, e_vorankuendigung, e_fiktives_znf) The train number field “text only” (e_nur_text) not applicable any more - former EBO1 feature.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0112] — FUR Instance border train number field

First / last train number field on the border of the service area of an TML instance shall be configured as border train number field, which shall be visible for both neighboring TML instances (although existing only once), in order to perform automatic / manual train number shift between these instances: Only applicable for train number address.






Comments: For special conditions concerning train number messages, if start / goal train number field is a border train number field see also [OMC-TML:SSS:REQ:0064].

[OMC-TML:SSS:REQ:0113] — FUR Station border train number field

In order to allow to exclude / include a station from instance service area with at least possible impact (e.g. on automatic train number shift), also first / last train number field on the station border shall be configured as border train number field, visible twice for the managing TML instance.






Comments: For special conditions concerning train number messages, if start / goal train number field is a border train number field see also [OMC-TML:SSS:REQ:0064].

[OMC-TML:SSS:REQ:0114] — FUR Train number management by own OMC

All train number fields known in the OMC, except preannouncement field and /or train number field of the line track section on the edge of OMC (not particular instance service area) shall be managed by own OMC.






Comments: In ELEKTRA: rlo_track_section - reo_zn_im_eigenen_fsb, reo_zn_verwaltende_bst.




[OMC-TML:SSS:REQ:0115] — FUR Stations / services to be provided with train number information

For a TML-Instance it shall be not necessary to have a knowledge about OMC services which shall be provided with current train number information. TML shall only inform the ILC-Instance of the track section owner station. Additionally TML shall send the current train number information via RBP also to the stations to be informed (outside of OMC).






Comments: In ELEKTRA: rlo_track_section - reo_zn_parallel_ausl_bst.

[OMC-TML:SSS:REQ:0116] — FUR Record train number break-in / outbreak

For each track section in shall be possible to configure, whether a train number break-in / outbreak in / from its train number field needs to be recorded. Default: TRUE






Comments: In ELEKTRA train number function only break-in can be recorded. In OMC outbreak will be recorded also, if configured so by mutual attribute. In ELEKTRA: rlo_track_section, reo_zn_prot_einbruch, default: FALSE.

[OMC-TML:SSS:REQ:0117] — FUR Automatic train number deleting

For each track section in shall be possible to configure, whether the train number contained in its train number field shall be deleted automatically by getting this track section free. Default: TRUE






Comments: In ELEKTRA: reo_track_section - reo_zn_autom_loeschen. To be used for first / last line track section with a train number field on the edge of OMC.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0118] — FUR Automatic train number shift from preannouncement field

For each track section it shall be possible to configure an associated preannouncement field. By the occupation of this track section the automatic train number shift from the associated preannouncement field to the train number field of this track section shall be performed.






Comments: In ELEKTRA: reo_track_section - reo_zn_fs_aus_vorankuend, reo_zn_zugeord_vorank_feld. Only one attribute in TML, covering functionally both of them.

[OMC-TML:SSS:REQ:0119] — FUR Perform the automatic train number shift over this element

For each main signal, protection signal, agree point (= train route relevant start element) it shall be possible to configure, whether the automatic train number shift over this element shall be performed. Default: TRUE






Comments: In ELEKTRA: rlo_main_signal, rlo_protection_signal, rlo_agree_point - reo_xxxx_zn_fs.

[OMC-TML:SSS:REQ:0120] — FUR Record the automatic train number shift over this element

For each main signal, protection signal, agree point (= train route relevant start element) it shall be possible to configure, whether the performance of the automatic train number shift over this element shall be recorded. Default: TRUE






Comments: In ELEKTRA: rlo_main_signal, rlo_protection_signal - reo_xxxx_zn_prot_fs, default: FALSE. Missing in rlo_agree_point, in the application always set to TRUE. May be it would be better to handle the agree point in the same way (see description). Also existing for goal point, not used in the application.




[OMC-TML:SSS:REQ:0121] — FUR No recording of the automatic train number shift in front of this element

For each main signal, protection signal, agree point, goal point (= train route relevant goal element) it shall be possible to configure, whether the automatic train number shift in the goal train number field placed in front of this element shall not be recorded. Default: FALSE






Comments: In ELEKTRA: rlo_main_signal, rlo_protection_signal - reo_xxxx_zn_no_prot. Missing in rlo_agree_point, in the application always set to FALSE. May be it would be better to handle the agree point in the same way (see description). Also existing for goal point, not used in the application currently, but it will be needed due to addition of the goal point attribute described in [OMC-TML:SSS:REQ:0124]. Another possibility would be to record the automatic train number shift always (no configurable ítem).

[OMC-TML:SSS:REQ:0124] — FUR Goal point as end point of automatic train number shift

For each train / combined goal point it shall be possible to configure it as end point of automatic train number shift. This configurable feature shall be used, if behind the goal point (considered in train movement direction) there is a topology part used only for shunting movements, while all train movements end at this goal point.






Comments: Not applicable for shunting goal points. See also [OMC-TML:SSS:REQ:0101]. Not implemented in current ELEKTRA train number function. The need for this feature arose in the real operation.


3BU 51500 5301 DTAPA / 03 / RL / 105




[OMC-TML:SSS:REQ:0125] — FUR Railbroker identifier

TML shall be provided with the Railbroker identifier, because some train number commands / messages shall be handled differently depending on their sender (Railbroker or a neighbor). Default: Dummy




Verification Method: Test Verification Step: subit test tool test


Comments: In ELEKTRA: rlo_processor_data - reo_rzue.

3.2.2.2.2. Topological data

[OMC-TML:SSS:REQ:0126] — FUR Neighbor element information on demand

Topological inquires will be necessary in order to perform forward / backward search along the train routes and line sections. See also [OMC-TML:SSS:REQ:0053] and [OMC-TML:SSS:REQ:0055]. ILC shall provide TML on demand with following information concerning given element and given search direction, in order to support the forward / backward topological search:

— neighbor element(s) — met from direction — current state






Comments: TML will not be provided with full topological information of the whole station.

[OMC-TML:SSS:REQ:0127] — FUR Topological connection to a neighbor station

TML shall be provided with information concerning topological connection to the neighbor station by means of configuration. For each border train number field (see also [OMC-TML:SSS:REQ:0112] ans [OMC-TML:SSS:REQ:0113]) it shall be possible to configure a partner train number field - this is the track section of the neighbor station, which follows / proceeds at the beginning / end of a station. This is indispensable for successful automatic / manual train number shift through the whole service area of a TML instance and adaptation activities (include / exclude station).






Comments: No corresponding attribute in ELEKTRA train number function. OREST shall make it possible to provide this information.




3.2.3. System Internal Data Requirements

3.2.4. Adaptation Requirements See chapter 3.2.1.7 Administration commands and 3.2.1.8 Adaptation activities.

3.2.5. Safety Requirements There are no special safety low level requirements.


3BU 51500 5301 DTAPA / 03 / RL / 105




4 Change History

4.1. Edition 01 First edition.

4.2. Edition 02

4.2.1. New Requirements • REQ:0129 • REQ:0130 • REQ:0131 • REQ:0132 • REQ:0133 • REQ:0134 • REQ:0135 • REQ:0136 • REQ:0137 • REQ:0138 • REQ:0139 • REQ:0140 • REQ:0141 • REQ:0142 • REQ:0143

4.2.2. Modified Requirements • REQ:0003 – no rejection text -> description, comments removed • REQ:0004 – comments extended – explanation of Dummy usage • REQ:0016 – No rejection text to be sent prior to NACK, if no train number in the start field -> description • REQ:0017 – not waiting for feedback from managing station • REQ:0019 – Global train number alarm by command not supported, explained in comments • REQ:0020 – command operation corrected– State change instead of Outbreak; this one from Railbroker (not Partial evaluation); condition for ignore flag; comments updated • REQ:0022, REQ:0023 – Information in these 2 requirements structured in a different way -> synopsis changed; description filled • REQ:0024 – description defined (was almost empty) • REQ:0026 – valid operation for alarm flag -> corrected; conditions for alarm added • REQ:0028 – recording removed, because new requirement REQ:0134 defined • REQ:0031 – acknowledge for msg to be sent –> synopsis, description, comments • REQ:0034 – Manual train number shift excluded from equal handling - described in new requirement REQ:0129; comments moved to REQ:0129 • REQ:0035 – check against the train number from start field removed (was a copy from CMD MAN_TNS, not correct); comments concerning this removed also; ghost number removed • REQ:0038 – reference to REQ:0135 instead of recording description here • REQ:0039 – description corrected – goal TNF needed • REQ:0043, REQ:0044 – see REQ:0022, REQ:0023 • REQ:0045 – see REQ:0024 • REQ:0046 – no additional conditions, incomplete sentence removed • REQ:0047 – see REQ:0026 • REQ:0054 – description precised, comments partly removed • REQ:0055 – format problems fixed




• REQ:0056 – TO start conditions precised, information from comments moved to description • REQ:0057 – description extended • REQ:0058 – requirement was „almost empty“; filled with references, because it’s too much for one requirement • REQ:0059 – comments deleted • REQ:0061 – precised; relevant examples of message order listed • REQ:0062 – synopsis changed (because of new requirement – REQ:0137 - concerning also this topic); description filled • REQ:0071 – recording removed, new requirement referred • REQ:0074 – Synopsis changed -> standard ATNS (in order to set it apart from shift from preannouncement field), description extended,; operation Recording -> flag Recording • REQ:0075 – description extended, part of the comments removed • REQ:0076 – comments removed • REQ:0078, REQ:0079, REQ:0080 – description precised FUSE ESB-container instead of cluster • REQ:0082 – comments deleted • REQ:0101 – no msg to RBP added • REQ:0102 – description and comments changed corresponding to current ILC design • REQ:0108 – NACK instead of CONNECTION_BREAKDOWN • REQ:0118 – comments updated • REQ:0127 – description changed – no ILC participation • REQ:0130 – description updated – new operation defined • REQ:0135 – description corrected – message instead of command

• CAPA:0025 – description updated, comments partly removed – commands via EBO to be recorded • CAPA:0027 – description updated – status on request, not periodically

4.2.3. Deleted Requirements • REQ:0077 • REQ:0109 • CAPA:0015

4.3. Edition 03 Chapter 1.2 – text updated – remote EBO, RBC request / response Figure 1 (communication) updated Chapter 2.1 Technical Literature Chapter 3.2.1.7, 3.2.1.10 - text about maintenance use case to be added removed

4.3.1. New Requirements • REQ:0144 • REQ:0145 • REQ:0146 • REQ:0147 • REQ:0148 • REQ:0149 • REQ:0150 • REQ:0151 • REQ:0152 • REQ:0153

Capabilities:

• CAPA:0035


3BU 51500 5301 DTAPA / 03 / RL / 105




4.3.2. Modified Requirements • REQ:0003 – previously intended simplified acknowledge handling • REQ:0005 – formatting problems fixed; local EBO in remote controlled station removed; check for other systems added • REQ:0014 – only train number in generated message, no flags • REQ:0015 – only train number in generated message, no flags • REQ:0016 – previously intended simplified acknowledge handling • REQ:0017 – applicable for all command operations • REQ:0025 – no blinking flag to be set to due to inconsistency (probably left after copying the text from other requirement) • REQ:0026 – no alarm by State change message without start and goal – text removed, comment added • REQ:0028 – description - message also to be sent via RBP to stations to get informed, comment added • REQ:0029 – sender described more precisely • REQ:0035 – handling of no / different train number in comparison to message data • REQ:0039 – no general alarm by message State change with start and goal dummy (equal to command) • REQ:0048 – only train number in generated message, no flags • REQ:0054 – Comment added - block start is oriented as signal. • REQ:0062 – In Ed.02 there has been defined, that agree point is to be handled differently in comparison to the signal, but now the condition is the same. Update done, describing, that it’s the same, giving currently correct hints to back and front. Comment added – different handling in ELEKTRA train number function (which explains the existence of the requirement). • REQ:0063 – Some information added, concerning the fact, that only a goal point in the train movement direction shall be considered. • REQ:0064 – Touched by an error instead of 0063, unchanged. • REQ:0066 - References corrected (old legacy numbers FR:OMC-TML:nn were referred) • REQ:0084 – INDICATION -> indication • REQ:0085 – Comment changed – data expiration timeout configurable; time stamp and border removed • REQ:0087 – description extended • REQ:0088 – synopsis, description, comment changed • REQ:0089 – synopsis, description, comment change • REQ:0090 - synopsis, description changed, comment removed • REQ:0091 – description changed, comment removed • REQ:0092 – synopsis, description, comment changed; • REQ:0093 – synopsis, description changed; comment removed • REQ:0096 – RBC registration status instead of ELCS-L2 equipped train • REQ:0101 – RBC registration status instead of ELCS-L2 equipped train • REQ:0104 – RBC registration status instead of ELCS-L2 equipped train • REQ:0106 – ATRS removed from description (not extern) • REQ:0115 – message also to be sent via RBP to stations to get informed • REQ:0134 – information about Recording flag added • REQ:0135 – Information added – concerning recording flag to be set or not in the generated message • REQ:0140 – comment moved to REQ:0138

Changed Verification Step: Added: part system test

• REQ:0013 • REQ:0015 • REQ:0016 • REQ:0033 • REQ:0034 • REQ:0036




• REQ:0097

Added: subit test • REQ:0019

Changed: subit test -> part system test

• REQ:0030 • REQ:0035 • REQ:0037 • REQ:0049 • REQ:0050 • REQ:0051 • REQ:0052 • REQ:0053 • REQ:0054 • REQ:0055 • REQ:0056 • REQ:0057 • REQ:0058 • REQ:0059 • REQ:0060 • REQ:0061 • REQ:0062 • REQ:0063 • REQ:0065 • REQ:0066 • REQ:0067 • REQ:0068 • REQ:0069 • REQ:0070 • REQ:0071 • REQ:0072 • REQ:0073 • REQ:0074 • REQ:0075 • REQ:0076 • REQ:0081 • REQ:0083 • REQ:0084 • REQ:0085 • REQ:0087 • REQ:0088 • REQ:0089 • REQ:0090 • REQ:0091 • REQ:0092 • REQ:0093 • REQ:0094 • REQ:0095 • REQ:0096 • REQ:0098 • REQ:0099 • REQ:0100 • REQ:0101 • REQ:0103 • REQ:0105 • REQ:0106


3BU 51500 5301 DTAPA / 03 / RL / 105




• REQ:0107 • REQ:0108 • REQ:0111 • REQ:0112 • REQ:0113 • REQ:0114 • REQ:0115 • REQ:0116 • REQ:0117 • REQ:0118 • REQ:0119 • REQ:0120 • REQ:0121 • REQ:0124 • REQ:0126 • REQ:0127 • REQ:0130 • REQ:0131 • REQ:0132 • REQ:0133 • REQ:0137

Changed: subit test -> code reading

• REQ:0082 • REQ:0086

Changed: system test -> part system test

• REQ:0110 Removed: subit test

• REQ:0102 • REQ:0136 • REQ:0138 • REQ:0139 • REQ:0140

Capabilities: • CAPA:0003 – comment removed – communication with ILC already defined • CAPA:0004 – comment removed – solution added to REQ:0064, References corrected (old legacy numbers FR:OMC-TML:nn were referred) • CAPA:0006 - References corrected (old legacy numbers FR:OMC-TML:nn were referred) • CAPA:0009 – RBC registration status instead of ELCS-L2 equipped train • CAPA:0010 – RBC registration status instead of ELCS-L2 equipped train • CAPA:0010 - References corrected (old legacy numbers FR:OMC-TML:nn were referred) • CAPA:0012 – RBC registration status instead of ELCS-L2 equipped train • CAPA:0017 - also another TML instance as message sender • CAPA:0019 - References corrected (old legacy numbers FR:OMC-TML:nn were referred) • CAPA:0021 – RBC registration status instead of ELCS-L2 equipped train • CAPA:0023 (synopsis), REQ:0082 (description) - interface number described as to be defined, although already done -> removed • CAPA:0024 – RBC registration status instead of ELCS-L2 equipped train • CAPA:0024 – information about ILC removed, not applicable • CAPA:0033 – comment removed (corresponding requirements already defined)

Use Cases:




Formal changes: Guidance texts (explanation of recommended usage) of identification, postconditions, triggers and other items has been removed from following use cases:

• UC:0001 • UC:0002 • UC:0003 • UC:0004 • UC:0004 • UC:0005 • UC:0006 • UC:0007 • UC:0010 • UC:0013 • UC:0014 • UC:0015 • UC:0016 • UC:0017

Identification hierarchy corrected:

• UC:0001 • UC:0003 • UC:0004 • UC:0005 • UC:0006 • UC:0007 • UC:0015 • UC:0016 • UC:0017

Content changes:

• UC:0001 – preconditions – typos fixed, postconditions filled, • UC:0001 – text added: Break-in command to managing station (Step 4); messages to ILC / RBP (step 3, 5), issue removed -> no issues • UC:0002 – requirement references moved from issues to proper place • UC:0002 - postconditions filled, • UC:0003 - postconditions filled, REQ. references – formatting • UC:0004 - postconditions filled • UC:0005 - trigger filled • UC:0005 – postconditions filled, Basic Flow – formatting • UC:0006 - postconditions filled, Basic Flow – formatting + empty steps removed • UC:0006 - trigger filled • UC:0007 - postconditions filled, REQ. references filled • UC:0008 - filled • UC:0009 – filled • UC:0010 - postconditions filled, basic flow, item 2 extended, req. references updated using reference to another UC, REQ. references updated • UC:0012 – Basic Flow – no rejection text to be sent (see REQ:0003) • UC:0013 – stations to get informed – added in step 5 • UC:0013 – alternative flow removed • UC:0014 – alternative flow corrected • UC:0014 – stations – added in basic flow step 6 • UC:0014 – postconditions filled, REQ. reference 0115 added • UC:0015 - postconditions filled, REQ. references added (the entire row was missing) • UC:0015 - identification corrected • UC:0016 - postconditions filled, REQ. reference 0115 added • UC:0016 – stations – added in step 4 • UC:0017 - postconditions filled, REQ. reference 0015 added • UC:0017 – stations – added in steps 5 and 9


3BU 51500 5301 DTAPA / 03 / RL / 105




• UC:0017 - trigger filled Recording added:

• UC:0001 (REQ:0136, REQ:0116) • UC:0002 (REQ:0074, REQ:0120, REQ:0121) • UC:0003 • UC:0004 • UC:0007 • UC:0010 • UC:0011 • UC:0013 (REQ:0134) • UC:0014 (REQ:0134) • UC:0016 (REQ:0135) • UC:0017 (REQ:0135)

4.3.3. Deleted Requirements • REQ:0122 • REQ:0123 • CAPA:0005




5 NOTES


3BU 51500 5301 DTAPA / 03 / RL / 105




APPENDIX A INDEX OF REQUIREMENTS OMC-TML:SSS:CAPA:0001 10 OMC-TML:SSS:CAPA:0002 10 OMC-TML:SSS:CAPA:0003 10 OMC-TML:SSS:CAPA:0004 11 OMC-TML:SSS:CAPA:0005 11 OMC-TML:SSS:CAPA:0006 11 OMC-TML:SSS:CAPA:0007 11 OMC-TML:SSS:CAPA:0008 11 OMC-TML:SSS:CAPA:0009 12 OMC-TML:SSS:CAPA:0010 12 OMC-TML:SSS:CAPA:0011 12 OMC-TML:SSS:CAPA:0012 12 OMC-TML:SSS:CAPA:0013 13 OMC-TML:SSS:CAPA:0014 13 OMC-TML:SSS:CAPA:0016 13 OMC-TML:SSS:CAPA:0017 13 OMC-TML:SSS:CAPA:0018 14 OMC-TML:SSS:CAPA:0019 14 OMC-TML:SSS:CAPA:0020 14 OMC-TML:SSS:CAPA:0021 14 OMC-TML:SSS:CAPA:0022 15 OMC-TML:SSS:CAPA:0023 15 OMC-TML:SSS:CAPA:0024 15 OMC-TML:SSS:CAPA:0025 15 OMC-TML:SSS:CAPA:0026 16 OMC-TML:SSS:CAPA:0027 16 OMC-TML:SSS:CAPA:0028 16 OMC-TML:SSS:CAPA:0029 16 OMC-TML:SSS:CAPA:0030 17 OMC-TML:SSS:CAPA:0031 17 OMC-TML:SSS:CAPA:0032 17 OMC-TML:SSS:CAPA:0033 17 OMC-TML:SSS:CAPA:0034 18 OMC-TML:SSS:CAPA:0035 14 OMC-TML:SSS:REQ:0001 . 21 OMC-TML:SSS:REQ:0002 . 21 OMC-TML:SSS:REQ:0003 . 21 OMC-TML:SSS:REQ:0004 . 22 OMC-TML:SSS:REQ:0005 . 22 OMC-TML:SSS:REQ:0006 . 23 OMC-TML:SSS:REQ:0007 . 23 OMC-TML:SSS:REQ:0008 . 23 OMC-TML:SSS:REQ:0009 . 24 OMC-TML:SSS:REQ:0010 . 24 OMC-TML:SSS:REQ:0011 . 25 OMC-TML:SSS:REQ:0012 . 25 OMC-TML:SSS:REQ:0013 . 26 OMC-TML:SSS:REQ:0014 . 26 OMC-TML:SSS:REQ:0015 . 26 OMC-TML:SSS:REQ:0016 . 27 OMC-TML:SSS:REQ:0017 . 28 OMC-TML:SSS:REQ:0018 . 29 OMC-TML:SSS:REQ:0019 . 29 OMC-TML:SSS:REQ:0020 . 30 OMC-TML:SSS:REQ:0021 . 30 OMC-TML:SSS:REQ:0022 . 30 OMC-TML:SSS:REQ:0023 . 31 OMC-TML:SSS:REQ:0024 . 31

OMC-TML:SSS:REQ:0025 . 31 OMC-TML:SSS:REQ:0026 . 32 OMC-TML:SSS:REQ:0027 . 32 OMC-TML:SSS:REQ:0028 . 33 OMC-TML:SSS:REQ:0029 . 36 OMC-TML:SSS:REQ:0030 . 37 OMC-TML:SSS:REQ:0031 . 37 OMC-TML:SSS:REQ:0032 . 37 OMC-TML:SSS:REQ:0033 . 38 OMC-TML:SSS:REQ:0034 . 38 OMC-TML:SSS:REQ:0035 . 39 OMC-TML:SSS:REQ:0036 . 40 OMC-TML:SSS:REQ:0037 . 40 OMC-TML:SSS:REQ:0038 . 40 OMC-TML:SSS:REQ:0039 . 41 OMC-TML:SSS:REQ:0040 . 41 OMC-TML:SSS:REQ:0041 . 41 OMC-TML:SSS:REQ:0042 . 42 OMC-TML:SSS:REQ:0043 . 42 OMC-TML:SSS:REQ:0044 . 42 OMC-TML:SSS:REQ:0045 . 43 OMC-TML:SSS:REQ:0046 . 43 OMC-TML:SSS:REQ:0047 . 43 OMC-TML:SSS:REQ:0048 . 44 OMC-TML:SSS:REQ:0049 . 53 OMC-TML:SSS:REQ:0050 . 54 OMC-TML:SSS:REQ:0051 . 54 OMC-TML:SSS:REQ:0052 . 54 OMC-TML:SSS:REQ:0053 . 55 OMC-TML:SSS:REQ:0054 . 55 OMC-TML:SSS:REQ:0055 . 56 OMC-TML:SSS:REQ:0056 . 56 OMC-TML:SSS:REQ:0057 . 57 OMC-TML:SSS:REQ:0058 . 57 OMC-TML:SSS:REQ:0059 . 59 OMC-TML:SSS:REQ:0060 . 60 OMC-TML:SSS:REQ:0061 . 60 OMC-TML:SSS:REQ:0062 . 61 OMC-TML:SSS:REQ:0063 . 62 OMC-TML:SSS:REQ:0064 . 62 OMC-TML:SSS:REQ:0065 . 63 OMC-TML:SSS:REQ:0066 . 63 OMC-TML:SSS:REQ:0067 . 64 OMC-TML:SSS:REQ:0068 . 64 OMC-TML:SSS:REQ:0069 . 65 OMC-TML:SSS:REQ:0070 . 65 OMC-TML:SSS:REQ:0071 . 66 OMC-TML:SSS:REQ:0072 . 66 OMC-TML:SSS:REQ:0073 . 67 OMC-TML:SSS:REQ:0074 . 67 OMC-TML:SSS:REQ:0075 . 68 OMC-TML:SSS:REQ:0076 . 69 OMC-TML:SSS:REQ:0078 . 69 OMC-TML:SSS:REQ:0079 . 69 OMC-TML:SSS:REQ:0080 . 70 OMC-TML:SSS:REQ:0081 . 70 OMC-TML:SSS:REQ:0082 . 71 OMC-TML:SSS:REQ:0083 . 71

OMC-TML:SSS:REQ:0084 . 72 OMC-TML:SSS:REQ:0085 . 73 OMC-TML:SSS:REQ:0086 . 73 OMC-TML:SSS:REQ:0087 . 74 OMC-TML:SSS:REQ:0088 . 74 OMC-TML:SSS:REQ:0089 . 75 OMC-TML:SSS:REQ:0090 . 75 OMC-TML:SSS:REQ:0091 . 77 OMC-TML:SSS:REQ:0092 . 78 OMC-TML:SSS:REQ:0093 . 79 OMC-TML:SSS:REQ:0094 . 79 OMC-TML:SSS:REQ:0095 . 79 OMC-TML:SSS:REQ:0096 . 80 OMC-TML:SSS:REQ:0097 . 81 OMC-TML:SSS:REQ:0098 . 81 OMC-TML:SSS:REQ:0099 . 82 OMC-TML:SSS:REQ:0100 . 82 OMC-TML:SSS:REQ:0101 . 83 OMC-TML:SSS:REQ:0102 . 84 OMC-TML:SSS:REQ:0103 . 85 OMC-TML:SSS:REQ:0104 . 85 OMC-TML:SSS:REQ:0105 . 86 OMC-TML:SSS:REQ:0106 . 87 OMC-TML:SSS:REQ:0107 . 88 OMC-TML:SSS:REQ:0108 . 88 OMC-TML:SSS:REQ:0110 . 89 OMC-TML:SSS:REQ:0111 . 89 OMC-TML:SSS:REQ:0112 . 90 OMC-TML:SSS:REQ:0113 . 90 OMC-TML:SSS:REQ:0114 . 90 OMC-TML:SSS:REQ:0115 . 91 OMC-TML:SSS:REQ:0116 . 91 OMC-TML:SSS:REQ:0117 . 91 OMC-TML:SSS:REQ:0118 . 92 OMC-TML:SSS:REQ:0119 . 92 OMC-TML:SSS:REQ:0120 . 92 OMC-TML:SSS:REQ:0121 . 93 OMC-TML:SSS:REQ:0124 . 93 OMC-TML:SSS:REQ:0125 . 94 OMC-TML:SSS:REQ:0126 . 94 OMC-TML:SSS:REQ:0127 . 94 OMC-TML:SSS:REQ:0129 . 39 OMC-TML:SSS:REQ:0130 . 57 OMC-TML:SSS:REQ:0131 . 58 OMC-TML:SSS:REQ:0132 . 58 OMC-TML:SSS:REQ:0133 . 59 OMC-TML:SSS:REQ:0134 . 34 OMC-TML:SSS:REQ:0135 . 44 OMC-TML:SSS:REQ:0136 . 68 OMC-TML:SSS:REQ:0137 . 61 OMC-TML:SSS:REQ:0138 . 83 OMC-TML:SSS:REQ:0139 . 84 OMC-TML:SSS:REQ:0140 . 84 OMC-TML:SSS:REQ:0141 . 86 OMC-TML:SSS:REQ:0142 . 86 OMC-TML:SSS:REQ:0143 . 87 OMC-TML:SSS:REQ:0144 . 74 OMC-TML:SSS:REQ:0145 . 75




OMC-TML:SSS:REQ:0146 . 76 OMC-TML:SSS:REQ:0147 . 76 OMC-TML:SSS:REQ:0148 . 76

OMC-TML:SSS:REQ:0149 . 77 OMC-TML:SSS:REQ:0150 . 77 OMC-TML:SSS:REQ:0151 . 78

OMC-TML:SSS:REQ:0152 . 78 OMC-TML:SSS:REQ:0153 . 80

END OF DOCUMENT

3bu_51500_5301_dtapa.pdf

Documents

thales austriatde rd

thales austria gmbh

zirwes thales austriaes

samsegger thales austriaes

bfz class

system overview

rl page

rl template