/CENELEC Phase 4/EIR/HL/Interface/Interlocking-TCS Interface
Project Interface
Interlocking-TCS Interface (part of Functional Interface Specification)
Version: 6.0
Printed by: Hansen
Printed on: 27 May 2002
Copyright UIC 2002
Contents
1 1Glossary
2 2Abbreviations
3 3General3.1 3Scope of this document
3.2 4Introduction
4 5System architecture
5 8Functional Interface description5.1 8Infrastructure Related Functions - Physical Objects
5.1.1 8Signals
5.1.1.1 8Signal status
5.1.1.2 9Signal reservation request5.1.1.3 9Signal reservation removal
5.1.1.4 10Signal Automatic Operation request
5.1.1.5 10Signal Automatic Operation removal5.1.1.6 10Proceed aspect request
5.1.1.7 10Stop aspect request
5.1.1.8 11Multiple stop aspect request
5.1.1.9 11Stop all signals request5.1.1.10 11Stop aspect cancellation
5.1.2 11Points
5.1.2.1 11Points status
5.1.2.2 12Points move request5.1.2.3 12Points lock request
5.1.2.4 12Points lock removal
5.1.2.5 13Points reserved request
5.1.2.6 13Points reserved removal5.1.2.7 13Points move (in occupied section) request
5.1.2.8 14First points move following trailing request
5.1.3 14Track vacancy proving
5.1.3.1 14Track vacancy proving device status5.1.3.2 15Track vacancy proving device initialise/restore request
5.1.3.3 15Track vacancy proving device reservation request
5.1.3.4 15Track vacancy proving device reservation removal5.1.4 16Level Crossings.
5.1.4.1 16Level crossing status
5.1.4.2 16Request closure of level crossing
5.1.4.3 17Request cancellation of level crossing closure5.1.4.4 17Request emergency opening of level crossing
5.1.4.5 17Request cancellation of level crossing emergency opening
5.1.4.6 17Enable level crossing request
5.1.4.7 18Disable level crossing request5.1.4.8 18Request emergency cleaning of level crossing
5.1.5 18Train ready to start indicator
5.1.5.1 18Train ready to start indicator status5.1.6 18Ground frames/local control posts and lockout devices
5.1.6.1 19Local control post status
5.1.6.2 19Handover of operation to local control post
5.1.6.3 19Takeover of operation from local control post5.1.6.4 19Request horn sound on local control post
5.1.6.5 20Emergency takeover of operation from local control post
5.1.7 20Trackside power supply
5.1.7.1 20Signalling power supply status 5.1.7.2 20Switch signals to daytime voltage request
5.1.7.3 21Switch signals to night voltage request
5.1.7.4 21Enable position check circuits of pointsContents i
5.1.7.5 21Disable position check circuits of points
5.1.7.6 22Switch off signalling power supply to a specified area5.1.7.7 22Switch on signalling power supply to a specified area
5.2 22Infrastructure Related Functions - Virtual Objects
5.2.1 22Routes
5.2.1.1 22Route status5.2.1.2 22Route lock request
5.2.1.3 23Route cancel request
5.2.1.4 23Routes stored status 5.2.1.5 23Route request storage enable request
5.2.1.6 23Route request storage disable request
5.2.1.7 24Delete stored route request
5.2.1.8 24Delete all stored route requests5.2.2 24ARS sub-areas
5.2.2.1 24ARS sub-area status
5.2.2.2 24ARS sub-area enable request
5.2.2.3 24ARS sub-area disable request5.2.3 25Alarms
5.2.3.1 25Alarm status
5.2.4 25Line block5.2.4.1 25Line block status
5.2.4.2 26Change line traffic direction request
5.2.4.3 26Cancellation of change line traffic direction request
5.2.4.4 26Granting of line traffic direction request5.2.4.5 27Switch all signals in a line section to stop aspect request
5.2.4.6 27Switch all signals in a line section to stop aspectcancellation
5.2.4.7 27Arrival of complete train report5.2.4.8 27Establish full block condition request
5.2.4.9 28Remove full block condition
5.2.4.10 28Enable departure without line block request
5.2.4.11 28Disable granting of line traffic direction request
5.2.4.12 28Enable granting of line traffic direction request5.2.4.13 28Disable departure request
5.2.4.14 29Enable departure request
5.2.5 29Station interlocking mode transitions
5.2.5.1 29Station interlocking control mode5.2.5.2 29Switch station Interlocking to remote control request
5.2.5.3 29Switch station interlocking to local control request
5.2.5.4 30Switch station interlocking to commanded local controlrequest
5.2.5.5 30Switch station interlocking to regime of automatic blockpost request
5.2.5.6 30Cancel regime of automatic block post
5.2.5.7 30Request stop of signalman service5.2.5.8 31Cancel stop of signalman service
5.2.5.9 31Request traffic sleeping
5.2.5.10 31Cancel traffic sleeping5.3 31Train Related Functions
6 33Variables6.1 33Name of Variable: Signal set ID
6.2 33Name of variable: Points trailed status6.3 33Name of variable: Track vacancy proving device artificially
set to not occupied status
6.4 34Name of variable: Track vacancy proving device artificiallyset to occupied status
6.5 34Name of variable: Level crossing anulling status
6.6 34Name of variable: Stored route list
6.7 34Route storage enabled status
6.8 35Name of variable: Entry signal identity6.9 35Name of variable: Exit signal identity
6.10 35Name of variable: Via informationContents ii
6.11 35Name of variable: Line block functional status
6.12 35Name of variable: Line block current traffic directionstatus
6.13 36Name of variable: Line block requested traffic directionstatus
6.14 36Name of variable: Line block approaching train status6.15 36Name of variable: Line block first section occupation status
7 45Input messages (to EURO-INTERLOCKING)
8 65Output messages (from EURO-INTERLOCKING)
9 81Reference to Functions in FRS
10 82Physical Interface
11 83Safety Requirements 11.1 83Originating System Identification
11.2 83Confirmation of Safety Related Requests
12 84Rail Authority Relevance Matrix
Contents iii
Interlocking-TCS Interface Page 1 of 86 Printed 29 May 2002
Identifier
FIS209-Com
FIS210-Com
Functional Interface Specification
1 Glossary
Where possible terms used in this document are those already defined in theEURO-INTERLOCKING Glossary of Terms. However there are some additional termswhich will need to be added to the project glossary or listed in this section in future issuesof the document.
Status
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 2 of 86 Printed 29 May 2002
Identifier
FIS188-Req
Functional Interface Specification
2 Abbreviations
ARS Automatic Route Setting system
FFFIS Form Fit Function Interface Specification
FIS Functional Interface Specification
HMI Human Machine Interface (for signaller)
TBD To be determined
TCS Traffic Control System
Status
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
Interlocking-TCS Interface Page 3 of 86 Printed 29 May 2002
Identifier
FIS211-Req
FIS212-Req
FIS213-Req
FIS214-Req
FIS215-Req
FIS216-Req
Functional Interface Specification
3 General
3.1 Scope of this document
This document describes the functional interface between the EURO-INTERLOCKINGsystem and the Traffic Control System(TCS). The Traffic Control System is defined as including all Human-Machine interfaces(HMI) used by signalling staff, either local or remote from the interlocking, and ancillarysystems such as automatic route setting (ARS) and information systems.
Functions relating to information from EURO-INTERLOCKING which may be requiredfor the specification and determination of fixed data in the TCS are not described in thisdocument. They shall be defined in the EURO-INTERLOCKING data preparationinterface functional interface specification.
Issue 0.1 of this document incorporates only the current interface requirements of therailways of the Czech Republic and United Kingdom. No attempt has yet been made tocapture functional requirements not currently needed by these rail authorities. It isintended that by making this version of the FIS available for review, the otherparticipating railways will be able to identify the additional functions which they require.
As far as possible, the terminology used is that implemented in theEURO-INTERLOCKINGfunctional specification and glossary of terms, but some functions have been identified inthe railway’s interface requirements which are additional to those already defined withinthe EURO-INTERLOCKING project.This document has not yet been reviewed by the EURO-INTERLOCKING Core ProjectTeam so there mayare likely to be discrepancies between it and other project documents.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 4 of 86 Printed 29 May 2002
Identifier
FIS217-Req
FIS218-Req
FIS219-Req
Functional Interface Specification
3.2 Introduction
This document follows the format adopted for FIS in the ERTMS project. All necessaryfunctions are described in section 5. Section 6 identifies a set of data variables. The logicalcontent of the required input and output messages are defined in sections 7 and 8respectively. Sections 9,10 deal with cross references to the FRSand physical interface details which are not completed in this version of the document.Section 11 specifies additional safety requirements. Section 12 (additional to ERTMSformat) was intended to be a table listing the usage of the specified functions by therailways participating in the EURO-INTERLOCKING project, but it has now been decidedto remove this to a separate document.
The functions at the interface relating to train objects have not been specified in this issueof the document. They will only be applicable to interlockings which implement someERTMS functionality.
Status
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 5 of 86 Printed 29 May 2002
Identifier
FIS220-Req
FIS221-Req
FIS222-Req
FIS223-Req
Functional Interface Specification
4 System architecture
In figure 1 the context in which EURO-INTERLOCKING interfaces with the TCS isshown. The interface described in this specification is that between the red box marked“Traffic Control System” and the light blue box “Control”.
Dummy1
Dummy2
Locking
R BC
LockingPower Supply
Movementauthority
Track vacancyproving ATP/ ATOPointsLevel
crossings R adio SignalsUser specific objects
Train
ERTMS/ ETCSTrackside
Line block
INTER -LO CKINGX
Data. Prep. system
Installation rules andtrack layout
Maintenance
Environment Human National rulesPower source
Traffic control system
Diagnostics system
Boundary 1:Interlocking Kernel
Control
Non-Vitalcommunicatio
Vitali ti
Figure 1 – EURO-INTERLOCKING Context Diagram
Status
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 6 of 86 Printed 29 May 2002
Identifier
FIS224-Req
FIS225-Req
FIS226-Req
Functional Interface Specification
In this Functional Interface Specification (FIS) the interface is described on a functionallevel. Detailsof communication protocols and physical interfaces will be specified at a later date in aForm Fit Function Interface Specification (FFFIS). There are potentially many alternativeways in which these lower levelinterface details could be specified, depending on the type of the Traffic Control System,the physical locations of the components of the Traffic Control System and the Interlocking, and theavailable communications systems.
For the purposes of the EURO-INTERLOCKING development, it is proposed to define theinterface sothat the interface is independent of the nature of the Traffic Control System. This isillustrated by the communication architecture shown in figure 2. This requires the TrafficControl System to provide a dedicated interface to each EURO-INTERLOCKING, with asecure and high bandwidth point-to-point communication link. This does not preclude theimplementation of Traffic Control Systems which are spread over a wide geographical areausing limited bandwith communications, provided a suitable interface is provided tocarry out the necessary protocol conversion at a location local to theEURO-INTERLOCKING.
Status
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 7 of 86 Printed 29 May 2002
Identifier
FIS227-Req
Functional Interface Specification
LocalHMI
RemoteHMI
Othersystem
Interface Interface
Traffic ControlSystem
EURO-INTERLOCKING
EURO-INTERLOCKING
TCS –EUR O-INTER LOCKING
Interface
Figure 2 – Proposed TCS - EURO-INTERLOCKING communication architecture
Status
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
Interlocking-TCS Interface Page 8 of 86 Printed 29 May 2002
Identifier
FIS228-Req
FIS229-Req
FIS230-Req
FIS231-Req
FIS232-Req
FIS233-Req
FIS234-Req
FIS235-Req
FIS236-Req
Functional Interface Specification
5 Functional Interface description
In the following section the functions are described which exchange information betweenthe TrafficControl System and the EURO-INTERLOCKING. The terms output and input have themeanings defined below:
Input means that the date flows from the Traffic Control System to theEURO-INTERLOCKING
Output means that the data flows from the EURO-INTERLOCKING to the Traffic ControlSystem.
A summarising table of all described functions indicating with which rail authorities theyare associated will be provided in a separate document.
5.1 Infrastructure Related Functions - Physical Objects
5.1.1 Signals
5.1.1.1 Signal status
The EURO-INTERLOCKING can report the status of a specified signal. The status reportshall include:
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 9 of 86 Printed 29 May 2002
Identifier
FIS237-Req
FIS238-Req
FIS239-Req
FIS240-Req
FIS241-Req
FIS242-Req
FIS243-Req
FIS244-Req
FIS245-Req
Functional Interface Specification
the aspect currently demanded. The aspect demanded may be different from that currentlydisplayed due to delay or lamp failure.
the aspect currently displayed;
the automatic status;
the reserved status
the locked status; and
the functional status (including lamp proved status) of a specified signal.
5.1.1.2 Signal reservation request
The TCS can request that a specified signal be reserved. The EURO-INTERLOCKING canreport that a signal reservation request has been rejected or accepted.
5.1.1.3 Signal reservation removal
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 10 of 86 Printed 29 May 2002
Identifier
FIS246-Req
FIS247-Req
FIS248-Req
FIS249-Req
FIS250-Req
FIS251-Req
FIS252-Req
FIS253-Req
FIS254-Req
Functional Interface Specification
The TCS can request that a specified signal be not-reserved. The EURO-INTERLOCKINGcan report that a signal reservation removal request has been rejected or accepted. Somerail authorities require seperate confirmation of this function.
5.1.1.4 Signal Automatic Operation request
The TCS can request that a specified signal be operated in automatic mode. TheEURO-INTERLOCKING can report that an automatic operation signal request has beenrejected or accepted.
5.1.1.5 Signal Automatic Operation removal
The TCS can request that a specified signal be operated in controlled (not-automatic)mode. The EURO-INTERLOCKING can report that an automatic operation removalrequest has been rejected or accepted.
5.1.1.6 Proceed aspect request
The TCS can request that a specified signal display a proceed aspect. TheEURO-INTERLOCKING canreport that a proceed aspect request for a specified signal has been rejected or accepted.
5.1.1.7 Stop aspect request
The TCS can request that a specified signal display a stop aspect. TheEURO-INTERLOCKING can report that a request for a specified signal to display a stop aspect has been rejected (ifimplementation is not posible) or accepted.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 11 of 86 Printed 29 May 2002
Identifier
FIS4072-Req
FIS4073-Req
FIS4074-Req
FIS255-Req
FIS256-Req
FIS257-Req
FIS258-Req
Functional Interface Specification
5.1.1.8 Multiple stop aspect request
The TCS can request that a specified (predefined) set of signals show a stop aspect. TheEURO-INTERLOCKING can report that a multiple stop aspect request for a (predefined)set of signals has been rejected (if implementation is not possible) or accepted.
5.1.1.9 Stop all signals request
The TCS can request that all signals (controlled by the interlocking) show a stop aspect.The EURO-INTERLOCKING can report that a stop all signals request has been rejected(if implementation is not possible) or accepted
5.1.1.10 Stop aspect cancellation
The TCS can request that the requirement for a specified signal to display a stop aspect becancelled. The EURO-INTERLOCKING can report that a stop aspect cancellation hasbeen rejected or accepted. Some rail authorities require separate confirmation of thisfunction.
5.1.2 Points
5.1.2.1 Points status
The EURO-INTERLOCKING can report the status of a specified set of points. The statusreport shall include:
the position currently demanded ;
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 12 of 86 Printed 29 May 2002
Identifier
FIS259-Req
FIS4036-Req
FIS260-Req
FIS261-Req
FIS262-Req
FIS263-Req
FIS264-Req
FIS265-Req
FIS266-Req
Functional Interface Specification
the position currently achieved;
the trailed status;
the locked status; and
the reserved status of a specified set of points.
5.1.2.2 Points move request
The TCS can request that a specific set of points be moved to either the left or rightposition.The EURO-INTERLOCKING can report that a points movement request has been rejectedor accepted.
5.1.2.3 Points lock request
The TCS can request that a specific set of points be locked. The EURO-INTERLOCKINGcan report that a points lock request has been rejected or accepted.
5.1.2.4 Points lock removal
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 13 of 86 Printed 29 May 2002
Identifier
FIS267-Req
FIS268-Req
FIS269-Req
FIS270-Req
FIS271-Req
FIS272-Req
FIS273-Req
Functional Interface Specification
The TCS can request that a specified set of points be not-locked. TheEURO-INTERLOCKING can report that a points lock removal request has been rejectedor accepted. The request and report relate to signaller initiated points locking. Some railauthorities require separate confirmation of this function in some cases.
5.1.2.5 Points reserved request
The TCS can request that a specific set of points be reserved. The EURO-INTERLOCKINGcan report that a pointsreserved request has been rejected or accepted.
5.1.2.6 Points reserved removal
The TCS can request that a specified set of points be not-reserved. TheEURO-INTERLOCKING can report that a points lock reserved request has been rejected or accepted. Some railauthorities requireseparate confirmation of this function.
5.1.2.7 Points move (in occupied section) request
The TCS can request that a specific set of points in an occupied section be moved to eitherthe left or right position. The EURO-INTERLOCKING can report that a points movement (in anoccupied section)request has been rejected or accepted. Some rail authorities require separate confirmationof this function.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 14 of 86 Printed 29 May 2002
Identifier
FIS4038-Req
FIS274-Req
FIS275-Req
FIS276-Req
FIS277-Req
FIS278-Req
FIS279-Req
FIS280-Req
Functional Interface Specification
5.1.2.8 First points move following trailing request
The TCS can request that a specific set of points be moved for the first time followingtrailing to either the left or right position. The EURO-INTERLOCKING can report that afirst points movement following trailing request has been rejected or accepted. Some railauthorities require separate confirmation of this function.
5.1.3 Track vacancy proving
5.1.3.1 Track vacancy proving device status
The EURO-INTERLOCKING can report the status of a specified track vacancy provingdevice. The status report shall include:
the occupied status ;
the functional status (including identification of the condition where initialisation /restoration is required);
the locked status (distinguishing between locked-odd and locked-even) ; and
the reserved status of a specified track vacancy proving device.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 15 of 86 Printed 29 May 2002
Identifier
FIS4039-Req
FIS4040-Req
FIS281-Req
FIS282-Req
FIS283-Req
FIS284-Req
FIS285-Req
FIS286-Req
Functional Interface Specification
artificially set to not occupied
artificially set to occupied
5.1.3.2 Track vacancy proving device initialise/restore request
The TCS can request that a specific track vacancy proving device be initialised / restoredInitialisation may be required by axle counter systems or by track circuit combinationsprotecting branch lines, etc.. The EURO-INTERLOCKING can report that a track vacancyproving device initialise / restore request has been rejected or accepted. Some railauthorities require separate confirmation of this function.
5.1.3.3 Track vacancy proving device reservation request
The TCS can request that a specified track vacancy proving device be reserved. TheEURO-INTERLOCKING can report that a Track vacancy proving device reservationrequest has been rejected or accepted. Some rail authorities require separate confirmationof this function.
5.1.3.4 Track vacancy proving device reservation removal
The TCS can request that a specified track vacancy proving device be not-reserved. Thenature of the reservation removal requested (block all trains or block electric traction only)shall be specified. The EURO-INTERLOCKING can report that a track vacancy provingdevice reservation removal request has been rejected or accepted. Some rail authoritiesrequire separate confirmation of this function.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 16 of 86 Printed 29 May 2002
Identifier
FIS287-Req
FIS288-Req
FIS289-Req
FIS290-Req
FIS291-Req
FIS4042-Req
FIS292-Req
FIS293-Req
FIS294-Req
Functional Interface Specification
5.1.4 Level Crossings.
5.1.4.1 Level crossing status
The EURO-INTERLOCKING can report the status of a specified level crossing. The statusreport shall include:
the open status ;
the functional status; and
the annulling status
the enabled status of a specified level crossing.
5.1.4.2 Request closure of level crossing
The TCS can request that a specified level crossing be closed. TheEURO-INTERLOCKING can report that a close level crossing request has been acceptedor rejected.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 17 of 86 Printed 29 May 2002
Identifier
FIS295-Req
FIS296-Req
FIS297-Req
FIS298-Req
FIS299-Req
FIS300-Req
FIS301-Req
FIS302-Req
Functional Interface Specification
5.1.4.3 Request cancellation of level crossing closure
The TCS can request that the closure of a specified level crossing be cancelled. TheEURO-INTERLOCKING can report that a cancellation of close level crossing request hasbeen accepted or rejected (if implementation is not possible). Some rail authorities requireseparate confirmation of this function.
5.1.4.4 Request emergency opening of level crossing
The TCS can request that a specified level crossing be (emergency) opened. TheEURO-INTERLOCKING can report that an emergency open level crossing request hasbeen accepted or rejected. Some rail authorities require separate confirmation of thisfunction.
5.1.4.5 Request cancellation of level crossing emergency opening
The TCS can request that the emergency opening of a specified level crossing be cancelled.The EURO-INTERLOCKING can report that a cancellation of emergency open levelcrossing request has been accepted or rejected (if implementation is not possible).
5.1.4.6 Enable level crossing request
The TCS can request that a specified level crossing be enabled. TheEURO-INTERLOCKING can report that a request to enable a specified level crossing has been rejected or accepted. Some railauthoritiesrequire separate confirmation of this function.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 18 of 86 Printed 29 May 2002
Identifier
FIS303-Req
FIS304-Req
FIS4041-Req
FIS305-Req
FIS306-Req
FIS307-Req
FIS308-Req
Functional Interface Specification
5.1.4.7 Disable level crossing request
The TCS can request that a specified level crossing be disabled. TheEURO-INTERLOCKING can reportthat a request to disable a specified level crossing has been rejected or accepted. Some railauthoritiesrequire separate confirmation of this function.
5.1.4.8 Request emergency cleaning of level crossing
The TCS can request that a specified level crossing using intermittent devices beemergency cleaned. The EURO-INTERLOCKING can report that an emergency cleaningof level crossing request has been rejected or accepted. Some rail auhtoriities requireseparate confirmation of this function.
5.1.5 Train ready to start indicator
5.1.5.1 Train ready to start indicator status
The EURO-INTERLOCKING can report the status of a specified train ready to startindicator
5.1.6 Ground frames/local control posts and lockout devices
These devices are referred to collectively as local control posts in the requirements thatfollow.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 19 of 86 Printed 29 May 2002
Identifier
FIS309-Req
FIS310-Req
FIS311-Req
FIS312-Req
FIS313-Req
FIS314-Req
FIS315-Req
FIS316-Req
Functional Interface Specification
5.1.6.1 Local control post status
The TCS can request the status of a specified local control post. TheEURO-INTERLOCKING canreport the status of a local control post.
5.1.6.2 Handover of operation to local control post
The TCS can yield operation to a local control post. (It is assumed that each local controlpost will have a pre-defined area of infrastructure associated with it.) TheEURO-INTERLOCKING can report that the handover of operation to a local control posthas been accepted or rejected.
5.1.6.3 Takeover of operation from local control post
The TCS can request takeover of operation from a local control post. (It is assumed thateach local control post will have a pre-defined area of infrastructure associated with it.) TheEURO-INTERLOCKING can report that the request for takeover of operation from a localcontrol post has been accepted or rejected.
5.1.6.4 Request horn sound on local control post
The TCS can request that the horn on a local control post be sounded. TheEURO-INTERLOCKING can report that the request has been accepted or rejected.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 20 of 86 Printed 29 May 2002
Identifier
FIS317-Req
FIS318-Req
FIS319-Req
FIS320-Req
FIS321-Req
FIS322-Req
FIS323-Req
FIS324-Req
FIS325-Req
Functional Interface Specification
5.1.6.5 Emergency takeover of operation from local control post
The TCS can request emergency takeover of operation from a local control post. TheEURO-INTERLOCKING can report that the request has been accepted or rejected. Somerail authorities require separate confirmation of this function.
5.1.7 Trackside power supply
5.1.7.1 Signalling power supply status
The EURO-INTERLOCKING can report the status of the signalling power supply of aspecified power supply area. That status report shall include:
the signal voltage status (night or daytime);
the (secondary) points position checking circuits status (enabled or disabled); and
the supply source status (normal, reserve or failed) of the specified power supply area.
5.1.7.2 Switch signals to daytime voltage request
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 21 of 86 Printed 29 May 2002
Identifier
FIS326-Req
FIS327-Req
FIS328-Req
FIS329-Req
FIS330-Req
FIS331-Req
FIS332-Req
Functional Interface Specification
The TCS can request that all signals be switched to daytime voltage. TheEURO-INTERLOCKING can report that the request to switch the signals to daytime voltage has been rejected oraccepted.
5.1.7.3 Switch signals to night voltage request
The TCS can request that all signals be switched to night voltage. TheEURO-INTERLOCKING can report that the request to switch the signals to night voltage has been rejected or accepted.
5.1.7.4 Enable position check circuits of points
The TCS can request that the reserve power supply to the position check circuits of thecontrolled setsof points be enabled. The EURO-INTERLOCKING can report that the request to enablethe power supplyto position check circuits of the controlled sets of has been rejected or accepted.
5.1.7.5 Disable position check circuits of points
The TCS can request that the reserve power supply to the position check circuits of thecontrolled setsof points be disabled. The EURO-INTERLOCKING can report that the request to disablethe position check circuits of the controlled sets of has been rejected or accepted.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 22 of 86 Printed 29 May 2002
Identifier
FIS4043-Req
FIS4044-Req
FIS333-Req
FIS334-Req
FIS335-Req
FIS336-Req
FIS337-Req
FIS338-Req
Functional Interface Specification
5.1.7.6 Switch off signalling power supply to a specified area
The TCS can request that signalling power supply to a specified area be switched off. TheEURO-INTERLOCKING can report that the request to switch off signalling power to aspecified area has been rejected or accepted.
5.1.7.7 Switch on signalling power supply to a specified area
The TCS can request that signalling power supply to a specified area be switched on. TheEURO-INTERLOCKING can report that the request to switch on signalling power to aspecified area has been rejected or accepted.
5.2 Infrastructure Related Functions - Virtual Objects
5.2.1 Routes
5.2.1.1 Route status
The EURO-INTERLOCKING can report the route locked status of a specified route.
5.2.1.2 Route lock request
The TCS can request that a specific route be locked. The request shall identify the categoryof route request and shall distinguish between a route requested by the signaller, a routeselected by ARS and a route selected (by the signaller) that ignores the reserved status ofthe entry and exit signals. The EURO-INTERLOCKING can report that a route lock
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 23 of 86 Printed 29 May 2002
Identifier
FIS339-Req
FIS340-Req
FIS4045-Req
FIS4047-Req
FIS4046-Req
Functional Interface Specification
request has been rejected or accepted.The route can be identified either by reference to a route identity or by specification of :- entry signal- exit signalTo this request it shall be possible to add via information:- Information about having points in a certain position for the route- Information about having a certain signal or track as via point for the route- Information about which overlap is used.
5.2.1.3 Route cancel request
The TCS can request that a specific route be unlocked. The EURO-INTERLOCKING canreport that a route cancel request has been rejected or accepted.
5.2.1.4 Routes stored status
The TCS can request a route request storage status report. The EURO-INTERLOCKINGcan report the enabled status of route request storage, and a list of route requestscurrently stored (if any).
5.2.1.5 Route request storage enable request
The TCS can request that route request storage be enabled. The EURO-INTERLOCKINGcan report that a route request storage enable request has been rejected or accepted.
5.2.1.6 Route request storage disable request
The TCS can request that route request storage be disabled. The EURO-INTERLOCKINGcan report that a route request storage disable request has been rejected or accepted.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 24 of 86 Printed 29 May 2002
Identifier
FIS4048-Req
FIS4049-Req
FIS341-Req
FIS342-Req
FIS343-Req
FIS344-Req
FIS345-Req
FIS346-Req
Functional Interface Specification
5.2.1.7 Delete stored route request
The TCS can request that a specified stored route request be deleted from ths listmaintained by the EURO-INTERLOCKING. The EURO-INTERLOCKING can reportthat a delete stored route request has been rejected or accepted.
5.2.1.8 Delete all stored route requests
The TCS can request that all stored route requests are deleted from the list maintained bythe EURO-INTERLOCKING. The EURO-INTERLOCKING can report that a delete allstored routes request has been rejected or accepted.
5.2.2 ARS sub-areas
5.2.2.1 ARS sub-area status
The EURO-INTERLOCKING can report the status of a specific ARS sub-area.
5.2.2.2 ARS sub-area enable request
The TCS can request that a specific ARS sub-area be enabled. TheEURO-INTERLOCKING can report that a specificARS sub-area enable request has been rejected or accepted.
5.2.2.3 ARS sub-area disable request
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 25 of 86 Printed 29 May 2002
Identifier
FIS347-Req
FIS348-Req
FIS349-Req
FIS350-Req
FIS351-Req
FIS352-Req
FIS353-Req
Functional Interface Specification
The TCS can request that a specific ARS sub-area be disabled. TheEURO-INTERLOCKING can reportthat a specific ARS sub-area disable request has been rejected or accepted.
5.2.3 Alarms
5.2.3.1 Alarm status
The EURO-INTERLOCKING can report the status of a specific alarm.
5.2.4 Line block
5.2.4.1 Line block status
The TCS can request the status of a specified line block. The EURO-INTERLOCKING canreport the status of a specific line block. The status report will contain a copy of theinformation reported from the line block system to the EURO-INTERLOCKING. Thisreport may include:
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 26 of 86 Printed 29 May 2002
Identifier
FIS355-Req
FIS356-Req
FIS357-Req
FIS358-Req
FIS359-Req
FIS360-Req
FIS361-Req
Functional Interface Specification
- line block functional status- current traffic direction status- requested traffic direction status- approaching train status- first section occupation status- full block condition status
5.2.4.2 Change line traffic direction request
The TCS can request that the line traffic direction of a specific line block be reversed (withrespect to its normal direction). The EURO-INTERLOCKING can report that a specificchange line traffic direction request has been rejected or accepted.
5.2.4.3 Cancellation of change line traffic direction request
The TCS can request that the reverse in line traffic direction of a specific line block (withrespect to itsnormal direction) be cancelled (returned to its normal direction). TheEURO-INTERLOCKING can reportthat a specific cancellation of change line traffic direction request has been rejected oraccepted.
5.2.4.4 Granting of line traffic direction request
The TCS can grant a line traffic direction request.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 27 of 86 Printed 29 May 2002
Identifier
FIS362-Req
FIS363-Req
FIS4051-Req
FIS364-Req
FIS365-Req
FIS366-Req
FIS367-Req
Functional Interface Specification
5.2.4.5 Switch all signals in a line section to stop aspect request
The TCS can request that all signals in a specified line block (in actual traffic direction) beswitched to show a stop aspect. The EURO-INTERLOCKING can report that a specificswitch all signals in a line section to stop aspect request has been rejected (ifimplementation is not possible)or accepted.
5.2.4.6 Switch all signals in a line section to stop aspect cancellation
The TCS can request that the requirement for all signals in a specified line block (in actualtraffic direction) be switched to show a stop aspect be cancelled. TheEURO-INTERLOCKING can report that a Switch all signals in a line section to stopaspect cancellation has been rejected or accepted. Some rail authoriities require seperateconfirmation of this function.
5.2.4.7 Arrival of complete train report
The TCS can issue an arrival of complete train report associated with a specific line block.Some rail authorities require separate confirmation of this function.
5.2.4.8 Establish full block condition request
The TCS can request that a full block condition be established for a specified line block.The EURO-INTERLOCKING can report that an establish full block condition request hasbeen rejected or accepted. Some rail authorities require separate confirmation of thisfunction.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 28 of 86 Printed 29 May 2002
Identifier
FIS368-Req
FIS369-Req
FIS4052-Req
FIS4053-Req
FIS4054-Req
FIS4055-Req
Functional Interface Specification
5.2.4.9 Remove full block condition
The TCS can request that a full block condition be removed for a specified line block. TheEURO-INTERLOCKING can report that a remove full block condition request has beenrejected or accepted. Some rail authorities require separate confirmation of this function.
5.2.4.10 Enable departure without line block request
The TCS can request that departure of a train be authorised by the interlocking withoutacceptance by the line block system (e.g. when line block system is not installed or hasfailed). The EURO-INTERLOCKING can report that the Enable departure without lineblock request has been rejected or accepted. Some rail authorities require separateconfirmation of this function.
5.2.4.11 Disable granting of line traffic direction request
The TCS can request that the ability of the line block system to grant a change in linetraffic direction be disabled. The EURO-INTERLOCKING can report that a Disablegranting of line traffic direction requiest has been rejected or accepted.
5.2.4.12 Enable granting of line traffic direction request
The TCS can request that the ability of the line block system to grant a change in linetraffic direction be enabled. The EURO-INTERLOCKING can report that a Enablegranting of line traffic direction request has been rejected or accepted. Some railauthorities require separate confirmation of this function.
5.2.4.13 Disable departure request
The TCS can request that departures into the line block section can be disabled. TheEURO-INTERLOCKING can report that an Disable departure request has been rejectedor accepted.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 29 of 86 Printed 29 May 2002
Identifier
FIS4056-Req
FIS370-Req
FIS371-Req
FIS372-Req
FIS373-Req
FIS374-Req
FIS375-Req
Functional Interface Specification
5.2.4.14 Enable departure request
The TCS can request that departures into the line block section shall be enabled. TheEURO-INTERLOCKING can report that an Enable departure request has been rejectedor accepted. Some rail authorities require separate confirmation of this function.
5.2.5 Station interlocking mode transitions
5.2.5.1 Station interlocking control mode
The EURO-INTERLOCKING can report the control mode of a specified stationinterlocking.
5.2.5.2 Switch station Interlocking to remote control request
The TCS can request that a specified station interlocking be switched to remote controlmode.The EURO-INTERLOCKING can report that a request to switch a specified stationinterlocking toremote control mode has been accepted or rejected.
5.2.5.3 Switch station interlocking to local control request
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 30 of 86 Printed 29 May 2002
Identifier
FIS376-Req
FIS377-Req
FIS378-Req
FIS379-Req
FIS380-Req
FIS381-Req
FIS382-Req
FIS383-Req
Functional Interface Specification
The TCS can request that a specified station interlocking be switched to local control mode.
The EURO-INTERLOCKING can report that a request to switch a specified stationinterlocking to local control mode has been accepted or rejected.
5.2.5.4 Switch station interlocking to commanded local control request
The TCS can request that a specified station interlocking be switched to commanded localcontrol mode. The EURO-INTERLOCKING can report that a request to switch a specifiedstation interlocking to commanded local control mode has been accepted or rejected.
5.2.5.5 Switch station interlocking to regime of automatic block post request
The TCS can request that a specified station interlocking be switched to automatic blockpost mode. The EURO-INTERLOCKING can report that a request to switch a specifiedstation interlocking to automatic block post mode has been accepted or rejected. Some railauthorities require separate confirmation of this function.
5.2.5.6 Cancel regime of automatic block post
The TCS can request that a specified station interlocking be switched from automatic blockpost mode. The EURO-INTERLOCKING can report that a request to switch a specifiedstation interlocking from automatic block post mode has been accepted or rejected. Somerail authorities require separate confirmation of this function.
5.2.5.7 Request stop of signalman service
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 31 of 86 Printed 29 May 2002
Identifier
FIS384-Req
FIS385-Req
FIS386-Req
FIS387-Req
FIS388-Req
FIS389-Req
FIS390-Req
FIS391-Req
Functional Interface Specification
The TCS can request that a specified station interlocking be switched to no-signalmanmode. The EURO-INTERLOCKING can report that a request to switch a specified stationinterlocking to no-signalman mode has been accepted or rejected. Some rail authoritiesrequire separate confirmation of this function.
5.2.5.8 Cancel stop of signalman service
The TCS can request that a specified station interlocking be switched from no-signalmanmode. The EURO-INTERLOCKING can report that a request to switch a specified stationinterlocking from no-signalman mode has been accepted or rejected. Some rail authoritiesrequire separate confirmation of this function.
5.2.5.9 Request traffic sleeping
The TCS can request that a specified station interlocking be switched to traffic sleepingmode. The EURO-INTERLOCKING can report that a request to switch a specified stationinterlocking to traffic mode has been accepted or rejected. Some rail authorities requireseparate confirmation of this function.
5.2.5.10 Cancel traffic sleeping
The TCS can request that a specified station interlocking be switched from traffic sleepingmode. The EURO-INTERLOCKING can report that a request to switch a specified stationinterlocking from traffic mode has been accepted or rejected. Some rail authorities requireseparate confirmation of this function.
5.3 Train Related Functions
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 32 of 86 Printed 29 May 2002
Identifier
FIS392-Req
Functional Interface Specification
<To be determined>
Status
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
Interlocking-TCS Interface Page 33 of 86 Printed 29 May 2002
Identifier
FIS393-Req
FIS4057-Req
FIS4058-Req
FIS4059-Req
Functional Interface Specification
6 VariablesThe variable definitions were originally produced as a series of Word tables, which weresubsequently imported into DOORS. Using the DOORSnet editing facility, it is notpossible to add new tables or add additional rows to existing tables. For this reason, newvariables added as a result of changes after Baseline 4 are listed in plain text at the startof section 6, with the original variables defined in baseline 4 following in the original tableformat.
6.1 Name of Variable: Signal set ID
Description:A unique identifier for a predefined set of signals.Values:TBD
6.2 Name of variable: Points trailed status
Description:The trailed status of a set of pointsValues:TrueFalse
6.3 Name of variable: Track vacancy proving device artificially set to notoccupied status
Description:The logical state of the track vacancy proving device which allows the section of track to beartificially set to not occupied within the interlocking.Values:TrueFalse
Status
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 34 of 86 Printed 29 May 2002
Identifier
FIS4060-Req
FIS4061-Req
FIS4062-Req
FIS4063-Req
Functional Interface Specification
6.4 Name of variable: Track vacancy proving device artificially set tooccupied status
Description:The logical state of the track vacancy proving device which allows the section of track to beartificially set to occupied within the interlocking.Values:TrueFalse
6.5 Name of variable: Level crossing anulling status
Description:TBDValues:TBD
6.6 Name of variable: Stored route list
Description:List of all routes stored by the interlockingValue:nullroute identitylist of route identities
6.7 Route storage enabled status
Description:The status of the route storage function in the interlocking.Values:route storage enabledroute storage disabled
Status
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 35 of 86 Printed 29 May 2002
Identifier
FIS4064-Req
FIS4065-Req
FIS4066-Req
FIS4067-Req
FIS4068-Req
Functional Interface Specification
6.8 Name of variable: Entry signal identity
Description:The unique identify of a signal associated with the entry to a routeValues:Signal identity
6.9 Name of variable: Exit signal identity
Description:The unique identify of a signal associated with the exit from a routeValues:Signal identity
6.10 Name of variable: Via information
Description:Sufficient information to allow an unambiguous route to be defined between specifiedentry and exit signals.Values:TBD (to include points position and/or overlap length)
6.11 Name of variable: Line block functional status
Description:The functional status of a line block systemValues:WorkingFailed
6.12 Name of variable: Line block current traffic direction status
Description:The current direction of traffic in a line block sectionValues:Normal
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 36 of 86 Printed 29 May 2002
Identifier
FIS4069-Req
FIS4070-Req
FIS4071-Req
Functional Interface Specification
Reverse
6.13 Name of variable: Line block requested traffic direction status
Description:The requested direction of traffic in a line block sectionValues:NormalReverse
6.14 Name of variable: Line block approaching train status
Decsription:Status of approaching trains on the line block sectionValues:TBD
6.15 Name of variable: Line block first section occupation status
Description:The occupation status of the section of track up to the first intermediate signal in a lineblockValues:OccupiedNot occupied
Name of Variable Signal Identity
Description An unique identifier
Values TBD
Name of Variable Signal aspect
Description Signal aspect
Status
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 37 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Values No aspectRedYellowFlashing YellowDouble YellowFlashing Double YellowGreenFlashing GreenWhiteShuntCall-onSpeed limit at this signal 30,60 etcSpeed limit at next signal 0,30, 60, etc
Others TBD
Name of Variable Signal locked status
Description The locked status of a signal
Values LockedLocking timing outNot locked
Name of Variable Signal functional status
Description The functional status of asignal
Values Lamp provedLamp not provedOthers TBD
Name of Variable Request response
Description The response to a request toimplement a status change
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 38 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Values Request is acceptedRequest is rejected
Name of Variable Reservation type
Description The type of signal
Values ReservedNot reserved
Name of Variable Signal automatic status
Description The automatic status of asignal
Values AutomaticControlled (non-automatic)
Name of Variable Points Identity
Description An unique identifier
Values TBD
Name of Variable Points position
Description The position of a set of points
Values LeftRight
Name of Variable Points locked status
Description The locked status of a set ofpoints
Values Not lockedLocked by the signallerLocked by route lockingLocked by the signaller andby route locking
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 39 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Name of Variable Points reserved status
Description The reserved status of a setof points
Values ReservedNot reserved
Name of Variable Track vacancy proving deviceIdentity
Description An unique identifier
Values TBD
Name of Variable Track vacancy proving deviceoccupied status
Description The occupied status of atrack vacancy proving device
Values OccupiedNot occupied
Name of Variable Track vacancy proving devicefunctional status
Description The functional status of atrack vacancy proving device
Values Initialisation / restoration isrequiredWorkingFailed
Name of Variable Track vacancy proving devicelocked status
Description The locked status of a trackvacancy proving device
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 40 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Values Locked oddLocked evenNot locked
Name of Variable Track vacancy proving devicereserved status
Description The reserved status of atrack vacancy proving device
Values ReservedNot reserved
Name of Variable Level crossing identity
Description An unique identifier
Values TBD
Name of Variable Level crossing open status
Description The open status of a levelcrossing
Values Closed (to road traffic, i.e.open to rail traffic)Not closed (to road traffic, i.e.closed to rail traffic)
Name of Variable Level crossing functionalstatus
Description The functional status of alevel crossing
Values FunctionalFunctional using reservepower supplyNot functional
Name of Variable Level crossing enabled status
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 41 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description The enabled status of a levelcrossing
Values EnabledDisabled
Name of Variable Train Ready To Startindicator identity
Description An unique identifier
Values TBD
Name of Variable Train Ready to Startindicator status
Description The status of a train ready tostart indicator
Values ReadyNot ready
Name of Variable Route identity
Description An unique identity
Values TBD
Name of Variable Route locked status
Description The locked status of a route
Values Route lockedRoute not locked
Name of Variable Route lock request category
Description The category of route lockrequest
Values Route lock requested by ARSRoute lock requested by asignaller
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 42 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Route lock requested by asignaller (ignoring thereserved status of entranceand exit signals)Others TBD
Name of Variable ARS sub-area identity
Description An unique identity
Values TBD
Name of Variable ARS sub-area status
Description The status of an ARSsub-area
Values EnabledNot enabled
Name of Variable Alarm identity
Description An unique identity
Values TBD
Name of Variable Alarm status
Description The status of an Alarm
Values ActiveInactive
Name of Variable Confirmation data
Description Data required to provideconfirmation of a command
Values TBD
Name of Variable Line block identity
Description An unique identity
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 43 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Values TBD
Name of Variable Line traffic direction
Description The line traffic direction of aline block
Values NormalReverse
Name of Variable Full block condition status
Description The full block conditionstatus of a line block
Values EnabledDisabled
Name of Variable Local control Post Identity
Description An unique identity
Values TBD
Name of Variable Control status
Description The location of control
Values LocalRemote
Name of Variable Station interlocking identity
Description An unique identity
Values TBD
Name of Variable Station interlocking controlmode
Description The location of control
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 44 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Values Remote controlLocal controlCommanded local controlAutomatic block postNo-signalmanTraffic sleepingOthers TBD
Name of Variable Controlled area sub-setidentity
Description An unique identity
Values TBD
Name of Variable Signal voltage status
Description The voltage status of a signalpower supply
Values DaytimeNight
Name of Variable Signal supply status
Description The supply status of a signalpower supply
Values NormalReserveFailed
Name of Variable Points position check circuitstatus
Description The position check circuitstatus of a set of points
Values EnabledDisabled
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 45 of 86 Printed 29 May 2002
Identifier
FIS804-Req
FIS4075-Req
FIS805-Req
Functional Interface Specification
7 Input messages (to EURO-INTERLOCKING)
This section has not been updated for Baseline 5 and is now out-of-date compared tosections 5 & 6. This is due to the difficulty in updating information in tables followingimport from Word into DOORS.
Each of the messages defined in this section of the document consists of a componentwhich identifies the nature of the message (shown in italics) and all other requiredcomponents. No structure nor implementation is implied nor mandated. Messagesrequesting status information have not been included to avoid implying a specificimplementation. It is noted that status reports may be generated periodically, by requestor on status-change and may relate to all or a subset of controlled objects.
Description Signal reservation request(3.1.1.2)
Content Functional data flows Type
Signal reservation request mandatory
Signal Identity mandatory
Reservation type mandatory
SRS ref.
Description Signal reservation removal(3.1.1.3)
Content Functional data flows Type
Signal reservation removal mandatory
Signal Identity mandatory
Reservation type mandatory
SRS ref.
Status
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 46 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Signal automatic operationrequest (3.1.1.4)
Content Functional data flows Type
Auto signal request mandatory
Signal Identity mandatory
SRS ref.
Description Auto signal removal (3.1.1.5)
Content Functional data flows Type
Auto signal removal mandatory
Signal Identity mandatory
SRS ref.
Description Proceed aspect request (3.1.1.6)
Content Functional data flows Type
Proceed aspect request mandatory
Signal Identity mandatory
SRS ref.
Description Stop aspect request (3.1.1.7)
Content Functional data flows Type
Stop aspect request mandatory
Signal Identity mandatory
SRS ref.
Description Points move request (3.1.2.2)
Content Functional data flows Type
Points move request mandatory
Points Identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 47 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Points position mandatory
SRS ref.
Description Points lock request (3.1.2.3)
Content Functional data flows Type
Points lock request mandatory
Points Identity mandatory
SRS ref.
Description Points lock removal (3.1.2.4)
Content Functional data flows Type
Points lock removal mandatory
Points Identity mandatory
SRS ref.
Description Points lock removalconfirmation (3.1.2.4)
Content Functional data flows Type
Points lock removal mandatory
Points Identity mandatory
Confirmation data mandatory
SRS ref.
Description Points reserved request (3.1.2.5)
Content Functional data flows Type
Points reserved request mandatory
Points Identity mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 48 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Points reserved removal
Content Functional data flows Type
Points reserve removal mandatory
Points Identity mandatory
SRS ref.
Description Points reserve removalconfirmation (3.1.2.6)
Content Functional data flows Type
Points reserve removalconfirmation
mandatory
Points Identity mandatory
Confirmation data mandatory
SRS ref.
Description Points move (in occupiedsection) request (3.1.2.7)
Content Functional data flows Type
Points move (in occupied section)request
mandatory
Points Identity mandatory
Points position mandatory
SRS ref.
Description Points move (in occupiedsection) request confirmation
Content Functional data flows Type
Points move (in occupied section)request confirmation
mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 49 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Points Identity mandatory
Points position mandatory
Confirmation data mandatory
SRS ref.
Description Track vacancy proving deviceinitialise/restore request
Content Functional data flows Type
Track vacancy proving deviceinitialise/restore request
mandatory
Track vacancy proving deviceIdentity
mandatory
SRS ref.
Description Track vacancy proving deviceinitialise/restore requestconfirmation (3.1.3.2)
Content Functional data flows Type
Track vacancy proving deviceinitialise/restore requestconfirmation
mandatory
Track vacancy proving deviceIdentity
mandatory
Confirmation data mandatory
SRS ref.
Description Track vacancy proving devicereservation request (3.1.3.3)
Content Functional data flows Type
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 50 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Track vacancy proving devicereservation request
mandatory
Track vacancy proving deviceIdentity
mandatory
Reservation type mandatory
SRS ref.
Description Track vacancy proving devicereservation request confirmation(3.1.3.3)
Content Functional data flows Type
Track vacancy proving devicereservation request confirmation
mandatory
Track vacancy proving deviceIdentity
mandatory
Confirmation data mandatory
SRS ref.
Description Track vacancy proving devicereservation removal (3.1.3.4)
Content Functional data flows Type
Track vacancy proving devicereservation removal
mandatory
Track vacancy proving deviceIdentity
mandatory
Reservation type mandatory
SRS ref.
Description Track vacancy proving devicereservation removalconfirmation (3.1.3.4)
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 51 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Content Functional data flows Type
Track vacancy proving devicereservation removal
mandatory
Track vacancy proving deviceIdentity
mandatory
Confirmation data mandatory
SRS ref.
Description Level crossing closure request(3.1.4.2)
Content Functional data flows Type
Level crossing closure request mandatory
Level crossing Identity mandatory
SRS ref.
Description Cancellation of level crossingclosure request (3.1.4.3)
Content Functional data flows Type
Cancellation of level crossingclosure request
mandatory
Level crossing Identity mandatory
SRS ref.
Description Confirm cancellation of levelcrossing closure request (3.1.4.3)
Content Functional data flows Type
Confirm cancellation of levelcrossing closure request
mandatory
Level crossing Identity mandatory
Confirmation data mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 52 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Level crossing emergency openrequest (3.1.4.4)
Content Functional data flows Type
Level crossing emergency openrequest
mandatory
Level crossing Identity mandatory
SRS ref.
Description Confirm level crossingemergency open request (3.1.4.4)
Content Functional data flows Type
Confirm level crossingemergency open request
mandatory
Level crossing Identity mandatory
Confirmation data mandatory
SRS ref.
Description Cancellation of level crossingemergency open request (3.1.4.5)
Content Functional data flows Type
Cancellation of level crossingemergency open request
mandatory
Level crossing Identity mandatory
SRS ref.
Description Level crossing enable request(3.1.4.6)
Content Functional data flows Type
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 53 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Level crossing enable request mandatory
Level crossing Identity mandatory
SRS ref.
Description Confirm level crossing enablerequest (3.1.4.6)
Content Functional data flows Type
Confirm level crossing enablerequest
mandatory
Level crossing Identity mandatory
Confirmation data mandatory
SRS ref.
Description Level crossing disable request(3.1.4.7)
Content Functional data flows Type
Level crossing disable request mandatory
Level crossing Identity mandatory
SRS ref.
Description Confirm level crossing disablerequest (3.1.4.7)
Content Functional data flows Type
Confirm level crossing disablerequest
mandatory
Level crossing Identity mandatory
Confirmation data mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 54 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Handover of operation to localcontrol post request (3.1.6.2)
Content Functional data flows Type
Handover of operation to localcontrol post request
mandatory
Local control post identity mandatory
SRS ref.
Description Takeover of operation from localcontrol post request (3.1.6.3)
Content Functional data flows Type
Takeover of operation from localcontrol post request
mandatory
Local control post identity mandatory
SRS ref.
Description Horn sound on local control postrequest (3.1.6.4)
Content Functional data flows Type
Horn sound on local control postrequest
mandatory
Local control post identity mandatory
SRS ref.
Description Emergency takeover ofoperation from local control postrequest (3.1.6.5)
Content Functional data flows Type
Emergency takeover of operationfrom local control post request
mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 55 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Local control post identity mandatory
SRS ref.
Description Emergency takeover ofoperation from local control postrequest confirmation (3.1.6.5)
Content Functional data flows Type
Emergency takeover of operationfrom local control post requestconfirmation
mandatory
Local control post identity mandatory
Confirmation data mandatory
SRS ref.
Description Switch signals to daytimevoltage request (3.1.7.2)
Content Functional data flows Type
Switch signals to daytimevoltage request
mandatory
Control area sub-set mandatory
SRS ref.
Description Switch signals to night voltagerequest (3.1.7.3)
Content Functional data flows Type
Switch signals to night voltagerequest
mandatory
Control area sub-set identity mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 56 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Enable (secondary) positioncheck circuits of points request (3.1.7.4)
Content Functional data flows Type
Enable (secondary) positioncheck circuits of points request
mandatory
Control area sub-set identity mandatory
SRS ref.
Description Disable position check circuits ofpoints request (3.1.7.5)
Content Functional data flows Type
Disable position check circuits ofpoints request
mandatory
Control area sub-set identity mandatory
SRS ref.
Description Route lock request (3.2.1.2)
Content Functional data flows Type
Route lock request mandatory
Route Identity mandatory
Route lock request category mandatory
SRS ref.
Description Route cancel request (3.2.1.3)
Content Functional data flows Type
Route cancel request mandatory
Route Identity mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 57 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description ARS sub-area enable request(3.2.2.2)
Content Functional data flows Type
ARS sub-area enable request mandatory
ARS sub-area identity mandatory
SRS ref.
Description ARS sub-area disable request(3.2.2.3)
Content Functional data flows Type
ARS sub-area disable request mandatory
ARS sub-area identity mandatory
SRS ref.
Description Change line traffic directionrequest (3.2.4.2)
Content Functional data flows Type
Change line traffic directionrequest
mandatory
Line block identity mandatory
SRS ref.
Description Cancellation of a change linetraffic direction request (3.2.4.3)
Content Functional data flows Type
Cancellation of a change linetraffic direction request
mandatory
Line block identity mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 58 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Granting of a line trafficdirection request (3.2.4.4)
Content Functional data flows Type
Granting of a line trafficdirection request
mandatory
Line block identity mandatory
SRS ref.
Description Switch all signals in a linesection to stop aspect request(3.2.4.5)
Content Functional data flows Type
Switch all signals in a linesection to stop aspect request
mandatory
Line block identity mandatory
SRS ref.
Description Arrival of complete train report(3.2.4.6)
Content Functional data flows Type
Arrival of complete train report mandatory
Line block identity mandatory
SRS ref.
Description Arrival of complete train reportconfirmation (3.2.4.6)
Content Functional data flows Type
Arrival of complete train reportconfirmation
mandatory
Line block Identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 59 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Confirmation data mandatory
SRS ref.
Description Establish full block conditionrequest (3.2.4.7)
Content Functional data flows Type
Establish full block conditionrequest
mandatory
Line block identity mandatory
SRS ref.
Description Establish full block conditionrequest confirmation (3.2.4.7)
Content Functional data flows Type
Establish full block conditionrequest confirmation
mandatory
Line block Identity mandatory
Confirmation data mandatory
SRS ref.
Description Remove full block conditionrequest (3.2.4.8)
Content Functional data flows Type
Remove full block conditionrequest
mandatory
Line block identity mandatory
SRS ref.
Description Remove full block conditionrequest confirmation (3.2.4.8)
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 60 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Content Functional data flows Type
Remove full block conditionrequest confirmation
mandatory
Line block Identity mandatory
Confirmation data mandatory
SRS ref.
Description Switch station interlocking toremote control request (3.2.5.2)
Content Functional data flows Type
Switch station interlocking toremote control request
mandatory
Station interlocking Identity mandatory
SRS ref.
Description Switch station interlocking tolocal control request (3.2.5.3)
Content Functional data flows Type
Switch station interlocking tolocal control request
mandatory
Station interlocking Identity mandatory
SRS ref.
Description Switch station interlocking tocommanded local control request(3.2.5.4)
Content Functional data flows Type
Switch station interlocking tocommanded local control request
mandatory
Station interlocking Identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 61 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Switch station interlocking toautomatic block post moderequest (3.2.5.5)
Content Functional data flows Type
Switch station interlocking toautomatic block post moderequest
mandatory
Station interlocking Identity mandatory
SRS ref.
Description Confirm switch stationinterlocking to automatic blockpost mode request (3.2.5.5)
Content Functional data flows Type
Confirm switch stationinterlocking to automatic blockpost mode request
mandatory
Station interlocking Identity mandatory
Confirmation data mandatory
SRS ref.
Description Switch station interlocking fromautomatic block post moderequest (3.2.5.6)
Content Functional data flows Type
Switch station interlocking fromautomatic block post moderequest
mandatory
Station interlocking Identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 62 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Confirm switch stationinterlocking from automaticblock post mode request (3.2.5.6)
Content Functional data flows Type
Confirm switch stationinterlocking from automaticblock post mode request
mandatory
Station interlocking Identity mandatory
Confirmation data mandatory
SRS ref.
Description Switch station interlocking tono-signalman mode request(3.2.5.7)
Content Functional data flows Type
Switch station interlocking tono-signalman mode request
mandatory
Station interlocking Identity mandatory
SRS ref.
Description Confirm switch stationinterlocking to no-signalmanmode request (3.2.5.7)
Content Functional data flows Type
Confirm switch stationinterlocking to no-signalmanmode request
mandatory
Station interlocking Identity mandatory
Confirmation data mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 63 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Switch station interlocking fromno-signalman mode request(3.2.5.8)
Content Functional data flows Type
Switch station interlocking fromno-signalman mode request
mandatory
Station interlocking Identity mandatory
SRS ref.
Description Confirm switch stationinterlocking from no-signalmanmode request (3.2.5.8)
Content Functional data flows Type
Confirm switch stationinterlocking from no-signalmanmode request
mandatory
Station interlocking Identity mandatory
Confirmation data mandatory
SRS ref.
Description Switch station interlocking totraffic sleeping mode request(3.2.5.9)
Content Functional data flows Type
Switch station interlocking totraffic sleeping mode request
mandatory
Station interlocking Identity mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 64 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Confirm switch stationinterlocking to traffic sleepingmode request (3.2.5.9)
Content Functional data flows Type
Confirm switch stationinterlocking to traffic sleepingmode request
mandatory
Station interlocking Identity mandatory
Confirmation data mandatory
SRS ref.
Description Switch station interlocking fromtraffic sleeping mode request(3.2.5.10)
Content Functional data flows Type
Switch station interlocking fromtraffic sleeping mode request
mandatory
Station interlocking Identity mandatory
SRS ref.
Description Confirm switch stationinterlocking from trafficsleeping mode request (3.2.5.10)
Content Functional data flows Type
Confirm switch stationinterlocking from traffic sleepingmode request
mandatory
Station interlocking Identity mandatory
Confirmation data mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 65 of 86 Printed 29 May 2002
Identifier
FIS2229-Req
FIS4076-Req
FIS2230-Req
Functional Interface Specification
8 Output messages (from EURO-INTERLOCKING)
This section has not been updated for Baseline 5 and is now out-of-date compared tosections 5 & 6. This is due to the difficulty in updating information in tables followingimport from Word into DOORS.
Each of the messages defined in this section of the document consists of a componentwhich identifies the nature of the message and all other required components. Nostructure nor implementation is implied nor mandated.
Description Signal status report (3.1.1.1)
Content Functional data flows Type
Signal status report mandatory
Signal Identity mandatory
Signal aspect (currently demanded) mandatory
Signal aspect (currently displayed) mandatory
Automatic operation status mandatory
Signal locked status mandatory
Signal reserved status mandatory
Signal functional status mandatory
SRS ref.
Description Signal reservation request response (3.1.1.2)
Content Functional data flows Type
Signal reservation request response mandatory
Signal Identity mandatory
Reservation type mandatory
Request response mandatory
Status
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 66 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Signal reservation removal response (3.1.1.3)
Content Functional data flows Type
Signal reservation removal response mandatory
Signal Identity mandatory
Reservation type mandatory
Request response mandatory
SRS ref.
Description Signal automatic operation response (3.1.1.4)
Content Functional data flows Type
Signal automatic operation response mandatory
Signal Identity mandatory
Request response mandatory
SRS ref.
Description Signal automatic operation removal response (3.1.1.5)
Content Functional data flows Type
Signal automatic operation removal response mandatory
Signal Identity mandatory
Request response mandatory
SRS ref.
Description Proceed aspect request response (3.1.1.6)
Content Functional data flows Type
Proceed aspect request response mandatory
Signal Identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 67 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Request response mandatory
SRS ref.
Description Stop aspect request response (3.1.1.7)
Content Functional data flows Type
Stop aspect request response mandatory
Signal Identity mandatory
Request response mandatory
SRS ref.
Description Points status report (3.1.2.1)
Content Functional data flows Type
Points status report mandatory
Points Identity mandatory
Points Position (currently demanded) mandatory
Points Position (currently achieved) mandatory
Points locked status mandatory
Points reserved status mandatory
SRS ref.
Description Points move request response (3.1.2.2)
Content Functional data flows Type
Points move request response mandatory
Points Identity mandatory
Points position mandatory
Request response mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 68 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Points lock request response (3.1.2.3)
Content Functional data flows Type
Points lock request response mandatory
Points Identity mandatory
Request response mandatory
SRS ref.
Description Points lock removal response (3.1.2.4)
Content Functional data flows Type
Points lock removal response mandatory
Points Identity mandatory
Request response mandatory
SRS ref.
Description Points reserve request response (3.1.2.5)
Content Functional data flows Type
Points reserve request response mandatory
Points Identity mandatory
Request response mandatory
SRS ref.
Description Points reserve removal response (3.1.2.6)
Content Functional data flows Type
Points reserve removal response mandatory
Points Identity mandatory
Request response mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 69 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Description Points move request (in occupied section) response (3.1.2.7)
Content Functional data flows Type
Points move request (in occupied section) response mandatory
Points Identity mandatory
Points position mandatory
Request response mandatory
SRS ref.
Description Track vacancy proving device status report (3.1.3.1)
Content Functional data flows Type
Track vacancy proving device status report Mandatory
Track vacancy proving device Identity Mandatory
Track vacancy proving device occupied status Mandatory
Track vacancy proving device functional status mandatory
Track vacancy proving device locked status mandatory
Track vacancy proving device reserved status mandatory
SRS ref.
Description Track vacancy proving device initialise / restore request response (3.1.3.2)
Content Functional data flows Type
Track vacancy proving device initialise / restorerequest response
mandatory
Track vacancy proving device Identity mandatory
Request response mandatory
SRS ref.
Description Track vacancy proving device reservation request (3.1.3.3)
Content Functional data flows Type
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 70 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Track vacancy proving device l reservation request mandatory
Track vacancy proving device Identity mandatory
Reservation type mandatory
SRS ref.
Description Track vacancy proving device reservation removal (3.1.3.4)
Content Functional data flows Type
Track vacancy proving device reservation removal mandatory
Track vacancy proving device Identity mandatory
Reservation type mandatory
SRS ref.
Description Level crossing status report (3.1.4.1)
Content Functional data flows Type
Level crossing status report mandatory
Level crossing open status mandatory
Level crossing functional status mandatory
Level crossing enabled status mandatory
SRS ref.
Description Level crossing closure response (3.1.4.2)
Content Functional data flows Type
Level crossing closure response mandatory
Level crossing Identity mandatory
Request response mandatory
SRS ref.
Description Cancellation of level crossing closure response (3.1.4.3)
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 71 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Content Functional data flows Type
Cancellation of level crossing closure response mandatory
Level crossing Identity mandatory
Response request mandatory
SRS ref.
Description Level crossing emergency open response (3.1.4.4)
Content Functional data flows Type
Level crossing emergency open response mandatory
Level crossing Identity mandatory
Request response mandatory
SRS ref.
Description Cancellation of level crossing emergency open response (3.1.4.5)
Content Functional data flows Type
Cancellation of level crossing emergency openresponse
mandatory
Level crossing Identity mandatory
Request response mandatory
SRS ref.
Description Level crossing enable response (3.1.4.6)
Content Functional data flows Type
Level crossing enable response mandatory
Level crossing Identity mandatory
Request response mandatory
SRS ref.
Description Level crossing disable response (3.1.4.7)
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 72 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Content Functional data flows Type
Level crossing disable response mandatory
Level crossing Identity mandatory
Request response mandatory
SRS ref.
Description Train Ready To Start indicator status report (3.1.5.1)
Content Functional data flows Type
Train Ready To Start indicator status report mandatory
Train Ready To Start indicator Identity mandatory
Train Ready To Start indicator status mandatory
SRS ref.
Description Local control post status report (3.1.6.1)
Content Functional data flows Type
Local control post status report mandatory
Local control post identity mandatory
Control status mandatory
SRS ref.
Description Handover of operation to local control post response (3.1.6.2)
Content Functional data flows Type
Handover of operation to local control post response Mandatory
Local control post identity mandatory
Request response mandatory
SRS ref.
Description Takeover of operation from local control post response (3.1.6.3)
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 73 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Content Functional data flows Type
Takeover of operation from local control post response mandatory
Local control post identity mandatory
Request response mandatory
SRS ref.
Description Horn sound on local control post response (3.1.6.4)
Content Functional data flows Type
Horn sound on local control post response mandatory
Local control post identity mandatory
Request response mandatory
SRS ref.
Description Emergency takeover of operation from local control post response (3.1.6.5)
Content Functional data flows Type
Emergency takeover of operation from local controlpost response
mandatory
Local control post identity mandatory
Request response mandatory
SRS ref.
Description Signalling power supply status report (3.1.7.1)
Content Functional data flows Type
Signalling power supply status report mandatory
Controlled area sub-set identity mandatory
Signal voltage status mandatory
Points position check circuit status mandatory
Signal supply status mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 74 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Switch signals to daytime voltage response (3.1.7.2)
Content Functional data flows Type
Switch signals to daytime voltage response mandatory
Controlled area sub-set identity mandatory
Request response mandatory
SRS ref.
Description Switch signals to night voltage response (3.1.7.3)
Content Functional data flows Type
Switch signals to night voltage response mandatory
Controlled area sub-set identity mandatory
Request response mandatory
SRS ref.
Description Enable position check circuits of points response (3.1.7.4)
Content Functional data flows Type
Enable position check circuits of points response mandatory
Controlled area sub-set identity
Request response mandatory
SRS ref.
Description Disable position check circuits of points response (3.1.7.5)
Content Functional data flows Type
Disable position check circuits of points response mandatory
Controlled area sub-set identity mandatory
Request response mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 75 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description Route status report (3.2.1.1)
Content Functional data flows Type
Route status report mandatory
Route Identity mandatory
Route locked status mandatory
SRS ref.
Description Route lock request response (3.2.1.2)
Content Functional data flows Type
Route lock request response mandatory
Route Identity mandatory
Request response mandatory
SRS ref.
Description Route cancel response (3.2.1.3)
Content Functional data flows Type
Route cancel response mandatory
Route Identity mandatory
Request response mandatory
SRS ref.
Description ARS sub-area status response (3.2.2.1)
Content Functional data flows Type
ARS sub-area status response mandatory
ARS sub-area identity mandatory
ARS sub-area status mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 76 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
SRS ref.
Description ARS sub-area enable response (3.2.2.2)
Content Functional data flows Type
ARS sub-area enable response mandatory
ARS sub-area identity mandatory
Request response mandatory
SRS ref.
Description ARS sub-area disable response (3.2.2.3)
Content Functional data flows Type
ARS sub-area disable response mandatory
ARS sub-area identity mandatory
Request response mandatory
SRS ref.
Description Alarm status report (3.2.3.1)
Content Functional data flows Type
Alarm status response mandatory
Alarm identity mandatory
Alarm status mandatory
SRS ref.
Description Line block status report (3.2.4.1)
Content Functional data flows Type
Line block status report mandatory
Line block identity mandatory
Line traffic direction mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 77 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Full block condition status mandatory
SRS ref.
Description Change line traffic direction response (3.2.4.2)
Content Functional data flows Type
Change line traffic direction response mandatory
Line block identity mandatory
Request response mandatory
SRS ref.
Description Cancellation of change line traffic direction response (3.2.4.3)
Content Functional data flows Type
Cancellation of change line traffic direction response mandatory
Line block identity mandatory
Request response mandatory
SRS ref.
Description Switch all signals in a line section to stop aspect response (3.2.4.5)
Content Functional data flows Type
Switch all signals in a line section to stop aspectresponse
mandatory
Line block identity mandatory
Request response mandatory
SRS ref.
Description Establish full block condition response (3.2.4.7)
Content Functional data flows Type
Establish full block condition response mandatory
Line block identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 78 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Request response mandatory
SRS ref.
Description Remove full block condition response (3.2.4.8)
Content Functional data flows Type
Remove full block condition response mandatory
Line block identity mandatory
Request response mandatory
SRS ref.
Description Station interlocking control mode report (3.2.5.1)
Content Functional data flows Type
Station interlocking control mode request mandatory
Station interlocking Identity mandatory
Station interlocking control mode mandatory
SRS ref.
Switch station interlocking to remote control response (3.2.5.2)
Content Functional data flows Type
Switch station interlocking to remote control response Mandatory
Station interlocking Identity Mandatory
Request response mandatory
SRS ref.
Description Switch station interlocking to local control response (3.2.5.3)
Content Functional data flows Type
Switch station interlocking to local control response mandatory
Station interlocking Identity mandatory
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 79 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Response request mandatory
SRS ref.
Description Switch station interlocking to commanded local control response (3.2.5.4)
Content Functional data flows Type
Switch station interlocking to commanded localcontrol response
mandatory
Station interlocking Identity mandatory
Request response mandatory
SRS ref.
Description Switch station interlocking to automatic block post mode response (3.2.5.5
Content Functional data flows Type
Switch station interlocking to automatic block postmode response
mandatory
Station interlocking Identity mandatory
Request response mandatory
SRS ref.
Description Switch station interlocking from automatic block post mode response (3.2.
Content Functional data flows Type
Switch station interlocking from automatic block postmode response
mandatory
Station interlocking Identity mandatory
Request response mandatory
SRS ref.
Description Switch station interlocking to no-signalman mode response (3.2.5.7)
Content Functional data flows Type
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 80 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
Switch station interlocking to no-signalman moderesponse
mandatory
Station interlocking Identity mandatory
Request response mandatory
SRS ref.
Description Switch station interlocking from no-signalman mode response (3.2.5.8)
Content Functional data flows Type
Switch station interlocking from no-signalman moderesponse
mandatory
Station interlocking Identity mandatory
Request response mandatory
SRS ref.
Description Switch station interlocking to traffic sleeping mode response (3.2.5.9)
Content Functional data flows Type
Switch station interlocking to traffic sleeping moderesponse
mandatory
Station interlocking Identity mandatory
Response request mandatory
SRS ref.
Description Switch station interlocking from traffic sleeping mode response (3.2.5.10)
Content Functional data flows Type
Switch station interlocking from traffic sleeping moderesponse
mandatory
Station interlocking Identity mandatory
Response request mandatory
SRS ref.
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 81 of 86 Printed 29 May 2002
Identifier
FIS3664-Req
FIS3665-Req
Functional Interface Specification
9 Reference to Functions in FRS
Cross reference to functions in FRS is not specified in this issue of the document.
Status
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 82 of 86 Printed 29 May 2002
Identifier
FIS3666-Req
FIS3667-Req
Functional Interface Specification
10 Physical Interface
The physical interface is not specified in this issue of the document.
Status
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 83 of 86 Printed 29 May 2002
Identifier
FIS3668-Req
FIS3669-Req
FIS3670-Req
FIS3671-Req
FIS3672-Req
Functional Interface Specification
11 Safety Requirements
11.1 Originating System Identification
Each input message may carry a component that allows the identity of its source to beestablished. This shall allow the EURO-INTERLOCKING to determine whether the identified sourcehas the appropriate authority to make the request. This will allow discrimination betweenfor example, manual and automatedroute setting, and local and remote control points.
11.2 Confirmation of Safety Related Requests
Certain safety related input messages shall only be acted upon by the Interlocking after an
additional confirmation message has been received from the TCS. The purpose of this is toenforcethe correct operating procedures by the signaller and to ensure that a single software errorin the TCScannot cause the Interlocking to undertake a hazardous action.
Status
Forreview
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 84 of 86 Printed 29 May 2002
Identifier
FIS3673-Req
FIS4077-Req
FIS3674-Req
FIS3675-Req
Functional Interface Specification
12 Rail Authority Relevance Matrix
It is intended that this section will be removed from future versions of the TCS FIS. Aseparate document is being produced to define the mapping from TCS FIS functions toindividual railways.
Key to Rail Authority abbreviations:
RT United Kingdom (Railtrack) CD Czech Republic
RT CD
3.1.1.1
3.1.1.2 The term ‘blocking’is used in the Czech
republic.
3.1.1.3
3.1.1.4
3.1.1.5
3.1.1.6
3.1.1.7
3.1.2.1
3.1.2.2
3.1.2.3
3.1.2.4
3.1.2.5
Status
Forreview
Forreview
Forreview
Forreview
Comment Rationale,Guidelines, App to
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
APPLICABLE TO:All
Interlocking-TCS Interface Page 85 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
3.1.2.6
3.1.2.7
3.1.3.1
3.1.3.2
3.1.3.3
3.1.3.4
3.1.4.1 Note that theenabled status of alevel crossing is not
required forRailtrack.
3.1.4.2
3.1.4.3
3.1.4.4
3.1.4.5
3.1.4.6
3.1.4.7
3.1.5.1
3.1.6.1
3.1.6.2
3.1.6.3
3.1.6.4
3.1.6.5
3.1.7.1
3.1.7.2
3.1.7.3
3.1.7.4
Status Comment Rationale,Guidelines, App to
Interlocking-TCS Interface Page 86 of 86 Printed 29 May 2002
Identifier Functional Interface Specification
3.1.7.5
3.2.1.1
3.2.1.2
3.2.1.3
3.2.2.1
3.2.2.2
3.2.2.3
3.2.3.1
3.2.4.1
3.2.4.2
3.2.4.3
3.2.4.4
3.2.4.5
3.2.4.6
3.2.4.7
3.2.4.8
3.2.5.1
3.2.5.2
3.2.5.3
3.2.5.4
3.2.5.5
3.2.5.6
3.2.5.7
3.2.5.8
3.2.5.9
3.2.5.10
Status Comment Rationale,Guidelines, App to