FIR 2010 Functional Requirements v1.4 12032014

FINNISH INTERLOCKING REQUIREMENTS 2010 - FUNCTIONAL REQUIREMENTS v1.4 12.3.2014

Finnish Transport Agency Page 1 of 89

FINNISH INTERLOCKING REQUIREMENTS 2010

FUNCTIONAL REQUIREMENTS



Document title Document Date Name Pages 12.3.2014 FINNISH INTERLOCKING REQUIREMENTS 2010 - FUNCTIONAL REQUIREMENTS 89 Revision history Revision Date Revision description 1.4 12.03.2014 Changes made based on the update of RATO and the comments made regarding the requirements 1.3 16.5.2012 Combined signal and stopping device have been added in the requirements. Changes in several requirements based

on received comments and updated RATO 6 "Signalling systems" 1.2 23.5.2011 Changes in FIR-FR384-Req,FIR-FR645-Req, FIR-FR1109-Req, FIR-FR1191-Req, FIR-FR1217-Req, FIR-FR1254-

Req. FIR-FR1113-Req removed, FIR-FR1246-Req removed 1.1 15.11.2010 Minor changes to requirements after comments 1 1.11.2010 Final version Detailed list of changes in version 1.4: - Removed items with numbers: 227, 236, 252, 258 - Changed items with numbers: 190, 217, 221, 232, 235, 250, 402, 535, 612, 741, 763, 805, 869, 1083, 1187, 1202, 1455, 1475, 1611, 1731 - Added items with numbers: 1807, 1808–



CONTENTS

1 Interlocking System General .......................................................................................................................................................................................................... 8 2 Route General ................................................................................................................................................................................................................................ 8

2.1 Route Definition ..................................................................................................................................................................................................................... 8 2.1.1 Route Life Cycle ........................................................................................................................................................................................................... 10 2.1.2 Route Setting ................................................................................................................................................................................................................ 11

2.2 Approach Zone ..................................................................................................................................................................................................................... 11 2.3 Route Types .......................................................................................................................................................................................................................... 12 2.4 Route Requesting .................................................................................................................................................................................................................. 12

2.4.1 Main Routes .................................................................................................................................................................................................................. 13 2.4.2 Shunting Routes ............................................................................................................................................................................................................ 14 2.4.3 Automatic Route Setting Functions .............................................................................................................................................................................. 15

2.5 Engineering Configuration Requirements ............................................................................................................................................................................ 16 3 Route Initiation-Completion ........................................................................................................................................................................................................ 17

3.1 Main Route Definition .......................................................................................................................................................................................................... 17 3.2 Shunting Route Definition .................................................................................................................................................................................................... 18 3.3 Route Rejection - Checking Basic Conditions ..................................................................................................................................................................... 18

3.3.1 Main Route Rejection - Checking Basic Conditions .................................................................................................................................................... 18 3.3.2 Shunting Route Rejection - Checking Basic Conditions .............................................................................................................................................. 20

3.4 Route Initiation ..................................................................................................................................................................................................................... 21 4 Route Locking - Proving .............................................................................................................................................................................................................. 21

4.1 Route Locking ...................................................................................................................................................................................................................... 21 4.2 Route Proving ....................................................................................................................................................................................................................... 22

5 Route Releasing ........................................................................................................................................................................................................................... 22 5.1 General .................................................................................................................................................................................................................................. 22 5.2 Route Cancellation or Emergency Release ........................................................................................................................................................................... 23

5.2.1 General .......................................................................................................................................................................................................................... 23 5.2.2 Valid Approach to Route .............................................................................................................................................................................................. 23 5.2.3 Main Route Cancellation and Emergency Release ....................................................................................................................................................... 24 5.2.4 Emergency release of Residual Route .......................................................................................................................................................................... 26 5.2.5 Shunting Route Cancellation ........................................................................................................................................................................................ 26

5.3 Route Use ............................................................................................................................................................................................................................. 27 5.3.1 Occupancy Sequence .................................................................................................................................................................................................... 27 5.3.2 Signal Replacement ...................................................................................................................................................................................................... 27 5.3.3 Main Route - Signal Replacement ................................................................................................................................................................................ 27 5.3.4 Shunting Route - Signal Replacement .......................................................................................................................................................................... 28



5.4 Train Operated Route Release .............................................................................................................................................................................................. 28 5.4.1 Route Release ............................................................................................................................................................................................................... 28 5.4.2 Overlap Release ............................................................................................................................................................................................................ 29

5.5 Special Route Releases ......................................................................................................................................................................................................... 29 5.5.1 Release by Turnback Movement .................................................................................................................................................................................. 29 5.5.2 Destination Track Release ............................................................................................................................................................................................ 29

5.6 Engineering Configuration Requirements ............................................................................................................................................................................ 30 6 Monitoring ................................................................................................................................................................................................................................... 30

6.1 General .................................................................................................................................................................................................................................. 30 6.2 Main Route Monitoring ........................................................................................................................................................................................................ 30

6.2.1 Monitoring Conditions .................................................................................................................................................................................................. 30 6.2.2 Signal Replacement - Irrevocable ................................................................................................................................................................................. 31

6.3 Shunting Route Monitoring .................................................................................................................................................................................................. 32 6.3.1 Monitoring Conditions .................................................................................................................................................................................................. 32 6.3.2 Signal Replacement - Irrevocable ................................................................................................................................................................................. 32

7 Track Section ............................................................................................................................................................................................................................... 32 7.1 General .................................................................................................................................................................................................................................. 33 7.2 Track blocking ...................................................................................................................................................................................................................... 33 7.3 Free of fouling restrictions .................................................................................................................................................................................................... 34

7.3.1 Standard Diamond Crossing ......................................................................................................................................................................................... 34 7.4 Axle Counting Systems ........................................................................................................................................................................................................ 35 7.5 Engineering Configuration Requirements ............................................................................................................................................................................ 35

8 Signals .......................................................................................................................................................................................................................................... 35 8.1 General .................................................................................................................................................................................................................................. 35 8.2 Main Signals ......................................................................................................................................................................................................................... 36

8.2.1 Signalling Conditions ................................................................................................................................................................................................... 36 8.2.2 Main Signal Aspects ..................................................................................................................................................................................................... 36

8.3 Distant Signals ...................................................................................................................................................................................................................... 37 8.3.1 Distant Signal Aspects .................................................................................................................................................................................................. 37

8.4 Shunting Signals ................................................................................................................................................................................................................... 37 8.4.1 Signalling conditions .................................................................................................................................................................................................... 38 8.4.2 Shunting Route Signalling ............................................................................................................................................................................................ 38 8.4.3 Shunting Signal Aspects ............................................................................................................................................................................................... 38

8.5 Block Signals or Line Main Signals ..................................................................................................................................................................................... 39 8.5.1 Signalling Conditions ................................................................................................................................................................................................... 39 8.5.2 Block Signal Aspects .................................................................................................................................................................................................... 40

8.6 Locking Signals .................................................................................................................................................................................................................... 40



8.6.1 Locking Signal Aspects ................................................................................................................................................................................................ 40 8.7 Level Crossing Signals ......................................................................................................................................................................................................... 41

8.7.1 Level Crossing Signal Aspects ..................................................................................................................................................................................... 41 8.8 Radio Signal ......................................................................................................................................................................................................................... 41 8.9 Combined signal ................................................................................................................................................................................................................... 41

8.9.1 Conditions for drive permitting aspect ......................................................................................................................................................................... 42 8.10 Signal Blocking .................................................................................................................................................................................................................... 44 8.11 Signal Supervision ................................................................................................................................................................................................................ 44 8.12 Setting Signals to 'Stop' Aspect by Request ......................................................................................................................................................................... 47

9 Powered Moveable Element ........................................................................................................................................................................................................ 48 9.1 General .................................................................................................................................................................................................................................. 48 9.2 Movement Request ............................................................................................................................................................................................................... 49

9.2.1 Automatic Operation .................................................................................................................................................................................................... 49 9.2.2 Individual operation ...................................................................................................................................................................................................... 50

9.3 Trailed Status ........................................................................................................................................................................................................................ 52 9.3.1 Assigning Trailed Status ............................................................................................................................................................................................... 52 9.3.2 Removal of Trailed Status by the Signaller .................................................................................................................................................................. 52

9.4 Blocking Moveable Elements ............................................................................................................................................................................................... 52 9.4.1 Setting Blocking ........................................................................................................................................................................................................... 52 9.4.2 Removing Blocking ...................................................................................................................................................................................................... 52

9.5 Route Blocking ..................................................................................................................................................................................................................... 53 9.5.1 Route Blocking ............................................................................................................................................................................................................. 53 9.5.2 Driving of Powered Moveable Element ....................................................................................................................................................................... 53 9.5.3 Hand Operation ............................................................................................................................................................................................................. 53

9.6 Engineering Configuration Requirements ............................................................................................................................................................................ 53 10 Lockable Devices ......................................................................................................................................................................................................................... 54

10.1 General .................................................................................................................................................................................................................................. 54 10.2 Blocking Lockable Devices .................................................................................................................................................................................................. 54 10.3 Operation of Lockable Devices ............................................................................................................................................................................................ 55

10.3.1 Release .......................................................................................................................................................................................................................... 55 10.3.2 Release of Lockable Devices on the Line ..................................................................................................................................................................... 55 10.3.3 Release Withdrawal ...................................................................................................................................................................................................... 55

11 Key-Locked Devices .................................................................................................................................................................................................................... 56 11.1 General .................................................................................................................................................................................................................................. 56 11.2 Line point .............................................................................................................................................................................................................................. 57 11.3 Operation .............................................................................................................................................................................................................................. 57

11.3.1 Basic state ..................................................................................................................................................................................................................... 57



11.3.2 Release .......................................................................................................................................................................................................................... 58 11.4 Area key lock system of the loading area ............................................................................................................................................................................. 59 11.5 Engineering Configuration Requirements ............................................................................................................................................................................ 59

12 Local Point Operation Permission ............................................................................................................................................................................................... 60 12.1 Giving a Local point operation permission ........................................................................................................................................................................... 60 12.2 Giving Local operation permission to Adjacent/Overlapping Local point operation group ................................................................................................ 62 12.3 Local point operation permission Monitoring ...................................................................................................................................................................... 62 12.4 Withdrawing a Local point operation permission ................................................................................................................................................................. 63 12.5 Withdrawing a Local point operation permission from an Adjacent/Overlapping Local point operation group ................................................................. 64 12.6 Engineering Configuration Requirements ............................................................................................................................................................................ 65

13 Line block .................................................................................................................................................................................................................................... 65 13.1 General .................................................................................................................................................................................................................................. 65 13.2 Block Conditions .................................................................................................................................................................................................................. 66 13.3 Line block Reset ................................................................................................................................................................................................................... 67 13.4 Block Travel Direction ......................................................................................................................................................................................................... 67

13.4.1 Line block Initialisation ................................................................................................................................................................................................ 67 13.4.2 Changing the Block Travel Direction ........................................................................................................................................................................... 67 13.4.3 Blocking the Block Travel Direction ............................................................................................................................................................................ 68

13.5 Route Setting into the Line Block ........................................................................................................................................................................................ 69 13.6 Engineering Configuration Requirements ............................................................................................................................................................................ 69

14 Level Crossing System Dependent on Interlocking ..................................................................................................................................................................... 69 14.1 General .................................................................................................................................................................................................................................. 69 14.2 States of the level crossing system ....................................................................................................................................................................................... 71

14.2.1 Basic state ..................................................................................................................................................................................................................... 71 14.2.2 Activation ..................................................................................................................................................................................................................... 71 14.2.3 Automatic operation ..................................................................................................................................................................................................... 73 14.2.4 Manual operation .......................................................................................................................................................................................................... 73 14.2.5 Elimination function ..................................................................................................................................................................................................... 74 14.2.6 Failures ......................................................................................................................................................................................................................... 75

14.3 Level Crossing System Activation ....................................................................................................................................................................................... 76 14.3.1 Alarm Section Occupation ............................................................................................................................................................................................ 77 14.3.2 Activation by Unit Detection ........................................................................................................................................................................................ 77 14.3.3 Activation by Manual Request ..................................................................................................................................................................................... 78

14.4 Level Crossing System Deactivation .................................................................................................................................................................................... 79 14.4.1 Deactivation by Unit Detection .................................................................................................................................................................................... 79 14.4.2 Deactivation by Manual Request .................................................................................................................................................................................. 80 14.4.3 Deactivation by Loss of Activation Conditions ............................................................................................................................................................ 80



14.5 Special Functions .................................................................................................................................................................................................................. 81 14.5.1 Disabling Level Crossing System Activation ............................................................................................................................................................... 81 14.5.2 Disabling an Activation Request for an Individual Track ............................................................................................................................................ 81 14.5.3 Overriding Failed Critical State .................................................................................................................................................................................... 81 14.5.4 Level Crossing System Out of Use ............................................................................................................................................................................... 82

14.6 Engineering Configuration Requirements ............................................................................................................................................................................ 82 15 Statuses ........................................................................................................................................................................................................................................ 83

15.1 General .................................................................................................................................................................................................................................. 83 15.2 Statuses ................................................................................................................................................................................................................................. 83

15.2.1 Route ............................................................................................................................................................................................................................. 83 15.2.2 Local point operation group .......................................................................................................................................................................................... 83 15.2.3 Powered Moveable elements ........................................................................................................................................................................................ 83 15.2.4 Key-locked Moveable Elements ................................................................................................................................................................................... 84

15.3 Signal .................................................................................................................................................................................................................................... 85 15.3.1 Main signal ................................................................................................................................................................................................................... 85 15.3.2 Combined signal ........................................................................................................................................................................................................... 85 15.3.3 Shunting signal ............................................................................................................................................................................................................. 85 15.3.4 Block Signal.................................................................................................................................................................................................................. 86 15.3.5 Locking Signal .............................................................................................................................................................................................................. 86 15.3.6 Level Crossing Signal ................................................................................................................................................................................................... 86

15.4 Track section ......................................................................................................................................................................................................................... 86 15.4.1 Occupation .................................................................................................................................................................................................................... 86 15.4.2 Locking ......................................................................................................................................................................................................................... 86 15.4.3 Axle counter reset ......................................................................................................................................................................................................... 87

15.5 Line block ............................................................................................................................................................................................................................. 87 15.6 Level crossing system ........................................................................................................................................................................................................... 87

15.6.1 Barriers ......................................................................................................................................................................................................................... 87 15.6.2 Road signal ................................................................................................................................................................................................................... 88

15.7 Lockable and Detection Devices .......................................................................................................................................................................................... 88 15.7.1 Detection Device .......................................................................................................................................................................................................... 88 15.7.2 Lockable Device ........................................................................................................................................................................................................... 88

15.8 Other Statuses ....................................................................................................................................................................................................................... 88 15.8.1 Power supply control .................................................................................................................................................................................................... 88 15.8.2 Operational mode transitions ........................................................................................................................................................................................ 89 15.8.3 Point heating control ..................................................................................................................................................................................................... 89 15.8.4 Signal intensity control ................................................................................................................................................................................................. 89



Requirement Finland - Priority FIR-FR001-Com

1 Interlocking System General FIR-FR002-Req Interlocking system shall be able to control and monitor signalling elements. Mandatory FIR-FR003-Req Interlocking shall ensure safety by interdependencies between signalling elements. Mandatory FIR-FR004-Req Interlocking shall be designed so that one failure shall not cause uncontrolled hazardous situation. Mandatory FIR-FR005-Req Interlocking shall fulfil the requirement for safety integrity level (SIL). Mandatory FIR-FR006-Com 2 Route General FIR-FR007-Com 2.1 Route Definition FIR-FR008-DK A route includes or associates the following: FIR-FR009-DK the route FIR-FR010-DK flank protection for the route FIR-FR011-DK the overlap FIR-FR012-DK The following diagram displays the terminology for the route and its possible elements. FIR-FR013-Diag

FIR-FR014-Req Main route may end to any of the following: Mandatory FIR-FR015-Req main signal in the traffic direction Mandatory FIR-FR1723-Req combined signal displaying aspects in the direction of the route, determined as the main route exit signal Mandatory



Requirement Finland - Priority FIR-FR016-Req block signal in the traffic direction Mandatory FIR-FR017-Req shunting signal equipped with main route exit sign in the traffic direction Mandatory FIR-FR018-Req track equipped with block system on line Mandatory FIR-FR019-Req track section of a track equipped with rail buffer Mandatory FIR-FR020-Req track section that is the last track section equipped with track vacancy proving on a track leading away

from railway operating location or its part Mandatory

FIR-FR021-Req Shunting route may end to any of the following: Mandatory FIR-FR022-Req main signal in the traffic direction Mandatory FIR-FR1724-Req combined signal displaying aspects in the direction of the route, determined as the shunting route exit

signal Mandatory

FIR-FR023-Req block signal in the traffic direction Mandatory FIR-FR024-Req shunting signal in the traffic direction Mandatory FIR-FR025-Req track equipped with block system on line Mandatory FIR-FR026-Req track section of a track equipped with rail buffer Mandatory FIR-FR027-Req track section that is the last track section equipped with track vacancy proving Mandatory FIR-FR028-Req on shunting routes a track section which has a sign limiting shunting positioned on the boundary Mandatory FIR-FR029-DK The elements that are not considered as part of the route, but are steered and/or monitored by the route, are: FIR-FR030-DK signals providing flank protection FIR-FR031-DK overlap FIR-FR032-DK track sections in the flank zone FIR-FR033-DK track sections in the overlap FIR-FR034-DK lockable devices FIR-FR035-DK level crossings FIR-FR036-DK line block FIR-FR037-DK The following diagram displays the monitored signals that are not part of the route.



Requirement Finland - Priority FIR-FR038-Diag

FIR-FR039-DK The following diagram displays the use of track sections by a route. FIR-FR040-Diag

FIR-FR041-DK The following diagram displays the use of the destination track and its track sections. FIR-FR042-Diag

FIR-FR043-Com 2.1.1 Route Life Cycle



Requirement Finland - Priority FIR-FR044-DK A route is considered as: FIR-FR045-DK requested if a request for a route is received (a requested route is either accepted or rejected)

FIR-FR046-DK initiated if the route request was accepted, until the route becomes locked

FIR-FR047-DK locked if all the route elements required to be locked are locked

FIR-FR048-DK An individual route element is considered as:

FIR-FR049-DK requested if the route request requires the use of that element

FIR-FR050-DK locked if the route requires the element to be locked and the element is locked

FIR-FR051-DK released if the element is released from its route

FIR-FR052-DK 2.1.2 Route Setting

FIR-FR053-DK Different route requests with separate conditions may be combined when setting a single route. For example, a shunting route to non-electrified track may be requested by the use of a combined request 'Set shunting route to non-electrified track'.

FIR-FR054-Com 2.2 Approach Zone

FIR-FR055-DK The approach zone is used to detect a vehicle on a valid approach in rear of the route entry signal. It provides the conditions if a time delay is required for releasing a route after a cancellation request.

FIR-FR056-DK The following diagram displays the possible approaches to a route.



Requirement Finland - Priority FIR-FR057-Diag

FIR-FR058-Com 2.3 Route Types

FIR-FR059-Req The interlocking system shall be able to set the following route types: Mandatory FIR-FR060-Req main routes Mandatory FIR-FR061-Req shunting routes Mandatory FIR-FR062-Req The sub-type of main route is main route to an occupied track. Mandatory FIR-FR063-Req Routes shall be set by one of the following: Mandatory FIR-FR064-Req the signaller via the interlocking local control or remote control Mandatory FIR-FR065-Req the automatic route setting system (ARS) Optional FIR-FR066-Req the automatic route setting functions for main routes incorporated into the interlocking system Mandatory FIR-FR067-Req the automatic route setting functions for shunting incorporated into the interlocking system Mandatory FIR-FR068-Com

2.4 Route Requesting

FIR-FR069-Req The following features for the route to be set must be defined: Mandatory FIR-FR070-Req route type Mandatory FIR-FR071-Req route entry signal Mandatory FIR-FR072-Req route exit point Mandatory FIR-FR073-Req required intermediate points for determining the alternative route Mandatory FIR-FR074-Req overlap Mandatory FIR-FR075-Req The route exit point can be determined by one of the following: Mandatory FIR-FR076-Req signal Mandatory FIR-FR077-Req track section Mandatory



Requirement Finland - Priority FIR-FR078-Req virtual route exit element Mandatory FIR-FR079-Req The overlap must be one of the following: Mandatory FIR-FR080-Req primary overlap (overlap 1) Mandatory FIR-FR081-Req secondary overlap (overlap 2 or 3) Mandatory FIR-FR082-Req overlap 0 Mandatory FIR-FR083-Req Different features of route shall be possible to be combined in a request for one route (e.g. overlap type, route to non-

electrified track). Mandatory

FIR-FR084-Com 2.4.1 Main Routes

FIR-FR085-Req Main route shall only be permitted to start from one of the following elements: Mandatory FIR-FR086-Req main signal Mandatory FIR-FR1725-Req combined signal which has been determined as the main route entry signal Mandatory FIR-FR087-Req block signal Mandatory FIR-FR088-Req Main route shall only be permitted to end to one of the following elements: Mandatory FIR-FR089-Req main signal in the same direction of travel Mandatory FIR-FR1726-Req combined signal in the same direction of travel, determined as the main route exit signal Mandatory FIR-FR090-Req shunting signal acting as main route exit signal Mandatory FIR-FR091-Req block signal in the same direction of travel Mandatory FIR-FR092-Req track equipped with block system on line Mandatory FIR-FR093-Req virtual route exit element, if route ends to line block Mandatory FIR-FR094-Req the last track section of a track included in the route equipped with track vacancy proving, also if the route

leads to rail buffer or track not equipped with track vacancy proving Mandatory

FIR-FR095-Req A main route shall be requested if any of the following conditions is satisfied: Mandatory FIR-FR096-Req a request 'Set main route' is received Mandatory FIR-FR097-Req a request 'Set main route, overlap 0' is received Mandatory FIR-FR098-Req a request 'Set main route to non-electrified tracks' is received Mandatory FIR-FR099-Req a request 'Set main route to to line point' is received Mandatory FIR-FR100-Req a request 'Set main route to dark territory' is received Mandatory FIR-FR101-Req A main route to an occupied track shall be requested, if a request 'Set main route to an occupied track' is received from

the signaller. Mandatory

FIR-FR102-Req A main route to an occupied track shall be requested without an overlap. Mandatory FIR-FR103-Req The main route to an occupied track is informed to the ATP, but it has no visible signal aspect. Mandatory FIR-FR104-Req The main route entry signal to an occupied track must display 'proceed 35, expect stop' aspect. Mandatory




2.4.1.1 Composite Main Routes

FIR-FR106-Req A composite main route shall be requested, if a request 'Set composite main route' is received from the signaller. Mandatory FIR-FR107-Req The request for a composite main route shall be decomposed to single main route requests between each main signal

within the composite route. Mandatory

FIR-FR108-Req The individual main routes in a composite main route shall be set in sequence from the first route entry signal towards the last route exit signal.

Optional

FIR-FR109-Com 2.4.2 Shunting Routes

FIR-FR110-Req Shunting route shall be permitted to start only from the following elements. Mandatory FIR-FR1727-Req shunting signal Mandattory FIR-FR1728-Req combined signal, which has been determined as the shunting route entry signal Mandatory FIR-FR111-Req Shunting route shall only be permitted to end to one of the following elements: Mandatory FIR-FR112-Req main signal in the same direction of travel Mandatory FIR-FR1729-Req combined signal in the same direction of travel, determined as the shunting route exit signal Mandatory FIR-FR113-Req shunting signal in the same direction of travel Mandatory FIR-FR114-Req block signal in the same direction of travel Mandatory FIR-FR115-Req track equipped with block system on line Mandatory FIR-FR116-Req the last track section included in the route equipped with track vacancy proving, also if the route leads to

rail buffer or track not equipped with track vacancy proving Mandatory

FIR-FR117-Req the last track section before a sign limiting shunting positioned on the track section boundary viewed from the direction of route entry signal

Mandatory

FIR-FR118-Req A shunting route shall be requested if any of the following conditions is satisfied: Mandatory FIR-FR119-Req a request 'Set shunting route' is received from the signaller Mandatory FIR-FR120-Req a request 'Set shunting route with permission to override track blocking' is received from the signaller Mandatory FIR-FR121-Req a request 'Set shunting route to non-electrified tracks' is received from the signaller Mandatory FIR-FR122-Com

2.4.2.1 Composite Shunting Routes

FIR-FR123-Req A composite shunting route shall be requested, if a request 'Set composite shunting route' is received from the signaller. Mandatory FIR-FR124-Req The request for a composite shunting route shall be decomposed to single shunting route requests between the route

entry and exit signals within the composite shunting route. Mandatory



Requirement Finland - Priority FIR-FR125-Req The individual shunting routes in a composite shunting route shall be set in a sequence from the last route exit signal

towards the first route entry signal. Mandatory

FIR-FR126-Com 2.4.3 Automatic Route Setting Functions

FIR-FR127-Req It shall be possible to set routes automatically by automatic route setting functions in the interlocking. Mandatory FIR-FR128-Req Automatic route setting command must be prevented, if the command is one of the following: Mandatory FIR-FR129-Req critical command Mandatory FIR-FR130-Req sets a route that includes a point, which hasn't been used in a route after a command to move a trailed

point, when the point has been trailed Mandatory

FIR-FR131-Req sets a main route that includes an occupied track section Mandatory FIR-FR132-Req sets a main route on the overlap which has an occupied track section Mandatory FIR-FR133-Req sets a main route that includes a track section with elimination function of a level crossing system applied Mandatory FIR-FR134-Req Automatic route setting shall be controlled by trigger section becoming occupied. Mandatory FIR-FR135-Req Trigger section is the furthest track section from the route entry signal on the approach zone for automatic route setting

for main routes, unless other track section is specified in engineering configuration requirements. Mandatory

FIR-FR136-Req Trigger section is the track section in rear of the shunting route entry signal for automatic route setting for shunting, unless other track section is specified in engineering configuration requirements.

Mandatory

FIR-FR137-Req Route setting may start after time delay determined in engineering configuration requirements started from the occupation of the track section.

Mandatory

FIR-FR138-Req The same route shall be requested again by automatic route setting, if the route is rejected. Mandatory FIR-FR139-Req The same route must not be set again by automatic route setting, if one of the following actions has been executed for

the route requested by automatics: Mandatory

FIR-FR140-Req cancellation Mandatory FIR-FR141-Req release Mandatory FIR-FR142-Req train operated route release Mandatory FIR-FR143-Req Automatic route setting must be set off, if the interlocking is in remote control and data transfer between interlocking

and remote control has a failure for over 1 minute. Mandatory

FIR-FR144-Req Automatic route setting can be set on or off by one of the following commands: Mandatory FIR-FR145-Req automatic route setting command for the interlocking Mandatory FIR-FR146-Req automatic route setting command for a signal, if the interlocking has automatic route setting on Mandatory FIR-FR147-Req Automatic route setting must not be set on automatically, when the interlocking is started. Mandatory FIR-FR148-Req Configuration change in automatic route setting shall not affect other functions of interlocking system. Mandatory




2.4.3.1 Automatic Pass-Through System

FIR-FR150-Req Automatic pass-through system sets the main routes through the railway operating location using determined through track for a train approaching the railway operating location.

Mandatory

FIR-FR151-Req 2.4.3.2 Automatic Encounter and Overtake

FIR-FR152-Req Automatic encounter sets the main routes for the trains approaching the railway operating location from different directions in single-track sections.

Mandatory

FIR-FR153-Req Automatic overtake sets the main routes for the trains approaching the railway operating location from the same direction in single-track sections.

Mandatory

FIR-FR154-Req Automatic encounter and overtake sets the routes in the following order: Mandatory FIR-FR155-Req The route from station entry signal to a track of railway operating location other than the through track for

the first train to arrive Mandatory

FIR-FR156-Req The routes from station entry signal through the railway operating location using a through track for the train to arrive from the opposite direction or for the second train to arrive from the same direction depending on trigger section

Mandatory

FIR-FR157-Req The route from the railway operating location to line for the first train Mandatory FIR-FR158-Req It shall be possible to define the first train arriving to the railway operating location by setting the route to the first train

before setting on the automatic encounter and overtake. Mandatory

FIR-FR159-Req Automatic encounter and overtake shall be set off automatically after one encounter or overtake. Mandatory FIR-FR160-Com

2.5 Engineering Configuration Requirements

FIR-FR161-Req One default route shall be assigned between a route entry signal and a route exit signal, if there is more than one possibility for the route between the signals.

Mandatory

FIR-FR162-Req All the permitted routes shall be defined. Mandatory FIR-FR163-Req All the permitted combined routes shall be defined. Mandatory FIR-FR164-Req All the permitted overlaps for each main route shall be defined. Mandatory FIR-FR165-Req Route setting configuration data for each route shall contain: Mandatory FIR-FR166-Req the applicable shunting or main route elements and their required positions Mandatory FIR-FR167-Req elements for flank protection to the main route and their required monitored statuses Mandatory FIR-FR168-Req the track sections between the flank protection element and the main route required to be not occupied Mandatory FIR-FR169-Req the track sections that may be occupied when setting main route to an occupied track Mandatory FIR-FR170-Req the track sections that are not permitted to be occupied when setting the shunting route Mandatory



Requirement Finland - Priority FIR-FR171-Req the lockable devices required by the shunting or main route Mandatory FIR-FR172-Req the level crossings activated by the shunting or main route Mandatory FIR-FR173-Req the conditions for the route based on level crossing alarm Mandatory FIR-FR174-Req the line block required by the shunting or main route Mandatory FIR-FR175-Req trigger section that starts the automatic route setting for each shunting or main route and type of automatic

route setting required Mandatory

FIR-FR176-Req required time delay for starting the automatic route setting for each shunting or main route and type of automatic route setting required

Mandatory

FIR-FR177-Req track sections that include a key-locked point or point included in local point operation group and that are in advance of route exit signal of a route with 0 overlap.

Mandatory

FIR-FR178-Req track section in advance of main route exit signal required to be not occupied in monitoring conditions, if the route has no overlap.

Mandatory

FIR-FR179-Req Route releasing configuration data for each route shall contain: Mandatory FIR-FR180-Req the destination track Mandatory FIR-FR181-Req the last track section of the approach zone viewed from the direction of route entry signal to be released Mandatory FIR-FR182-Req Automatic route setting configuration data for each automatic function shall contain: Mandatory FIR-FR183-Req trigger sections of automatic route setting for main routes, if other than the default track sections. Mandatory FIR-FR184-Req shunting routes and the setting order for automatic route setting for shunting Mandatory FIR-FR185-Com

3 Route Initiation-Completion

FIR-FR186-Com 3.1 Main Route Definition

FIR-FR187-Req The main route shall include the following route elements: Mandatory FIR-FR188-Req the main route entry signal Mandatory FIR-FR189-Req the main route exit signal Mandatory FIR-FR190-Req the sub-route signals parallel to the main route Mandatory FIR-FR191-Req the track sections in the route Mandatory FIR-FR192-Req the moveable elements in the route Mandatory FIR-FR193-Req The following elements are associated with the main route: Mandatory FIR-FR194-Req the elements for flank protection of the route Mandatory FIR-FR195-Req the track sections in the overlap Mandatory FIR-FR196-Req the moveable elements in the overlap Mandatory




3.2 Shunting Route Definition

FIR-FR198-Req The shunting route shall consist only of the following route elements: Mandatory FIR-FR199-Req the shunting route entry signal Mandatory FIR-FR200-Req the shunting route exit signal Mandatory FIR-FR201-Req the track sections in the route Mandatory FIR-FR202-Req the moveable elements of the route Mandatory FIR-FR203-Com

3.3 Route Rejection - Checking Basic Conditions

FIR-FR204-Req A route request shall be rejected if any of the following conditions exist at the time of request: Mandatory FIR-FR205-Req the route request contains insufficient information concerning the elements included or associated with the

route Mandatory

FIR-FR206-Req the requested route entry signal is located at the same track section boundary as a route entry signal for the route set in the opposite direction

Mandatory

FIR-FR207-Req a conflicting branch of a requested standard diamond crossing is assigned as occupied Mandatory FIR-FR208-Req If the route request is rejected, all elements of the route shall become available for use by other requests. Mandatory

FIR-FR209-Req The route request shall be rejected, if the checking phase of the basic conditions cannot be implemented in 5 s. Mandatory

FIR-FR210-Com 3.3.1 Main Route Rejection - Checking Basic Conditions

FIR-FR211-Req A main route request shall be rejected if any of the following conditions exist at the time of request: Mandatory FIR-FR212-Req an element included or associated with the requested route is being used in another route, unless the

element is a track section that is allowed to be used simultaneously for multiple requests not endangering the safety (e.g. route and overlap of subsequent routes)

Mandatory

FIR-FR213-Req a requested route overlap element is being used in another route unless the element is in the overlap of the route

Mandatory

FIR-FR214-Req an element included in the requested route is being used in a previous residual route with the identical route as the requested route

Mandatory

FIR-FR215-Req an element included in the requested route is being used in a shunting route with the identical route as the requested route

Mandatory

FIR-FR216-Req an element included in the requested route is being used as a route element of an opposing route Mandatory



Requirement Finland - Priority FIR-FR217-Req an element included in or associated with the requested route is included in a local point operation group,

which has been initiated or given a local operation permission Mandatory

FIR-FR218-Req a powered point included in the track section in advance of the main route exit signal for a main route, which is to be set with overlap 0, is included in a local point operation group that has local point operation permission given

Mandatory

FIR-FR219-Req a requested moveable element included with the route is 'locked' in an incorrect position for the requested route

Mandatory

FIR-FR220-Req a requested moveable element is 'locked' in an incorrect position for the requested overlap Mandatory FIR-FR221-Req a point included in or associated with the main route cannot be blocked for the use of the main route in the

position the route requires (for example ‘trailed’ point).a requested point is 'trailed' Mandatory

FIR-FR222-Req a signal included in or associated with the requested route is displaying 'no aspects' aspect Mandatory FIR-FR226-Req there are no occupied track sections on track in rear of the main route exit signal if the route is to an

occupied track Mandatory

FIR-FR228-Req a track section in the requested route is ‘track blocked’ Mandatory FIR-FR229-Req a track section in the overlap of the requested route is ‘track blocked’ Mandatory FIR-FR230-Req a track section in advance of the main route exit signal of the requested route with 0 overlap is ‘track

blocked’ Mandatory

FIR-FR231-Req a requested route point or derailer has 'route blocking' applied Mandatory FIR-FR232-Req a requested lockable device or monitoring device is not monitored 'in position for traffic' Mandatory FIR-FR233-Req a requested lockable device is 'released' Mandatory FIR-FR234-Req key box permission for the key box associated with the track section in advance of the route exit signal of a

main route, which is to be set with overlap 0, is given Mandatory

FIR-FR235-Req the requested line block is not or cannot be turned in the requested block travel direction, unless the line block conditions are disabled manually with a specific plug (see the item FIR-FR1187-Req regarding the manual disabling of the line block conditions)

Mandatory

FIR-FR237-Req the requested route leads from an electrified track to a non-electrified track or a dead power track, unless the request 'Set main route to non-electrified tracks' has been used

Mandatory

FIR-FR238-Req the requested route exit signal is being used as a shunting route entry signal Mandatory FIR-FR239-Req the requested main route exit signal is located at the same track section boundary as a route exit signal in

opposite direction Mandatory

FIR-FR240-Req the requested route entry signal is being used as a main route exit signal of a main route to an occupied track

Mandatory



Requirement Finland - Priority FIR-FR241-Req the requested route exit signal is being used as a main route entry signal and the request is for a main route

to an occupied track Mandatory

FIR-FR242-Req All individual route requests of a composite main route shall be rejected if one of the individual route requests is rejected.

Optional

FIR-FR243-Com 3.3.2 Shunting Route Rejection - Checking Basic Conditions

FIR-FR244-Req A shunting route request shall be rejected if any of the following conditions exist at the time of request: Mandatory FIR-FR245-Req an element included in the requested route is being used in another conflicting route, unless the element is

used by opposing route with the same destination track Mandatory

FIR-FR246-Req an element included in the requested route is being used in a previous residual route with the identical route as the requested route

Mandatory

FIR-FR247-Req an element included in the requested route is being used as a route element of an opposing route, unless the element is used by opposing route with the same destination track

Mandatory

FIR-FR248-Req an element included in the requested route is included in a local point operation group, for which has been initiated or given a local point operation permission

Mandatory

FIR-FR249-Req a requested moveable element is 'locked' in the incorrect position for the requested route Mandatory FIR-FR250-Req a point included in or associated with the main route cannot be locked for the use of the main route in the

position the route requires (for example ‘trailed’ point). Mandatory

FIR-FR251-Req a requested signal is displaying ‘no aspects’ aspect Mandatory FIR-FR253-Req a track section in the requested route has 'track blocking' applied unless the request 'Set shunting route with

permission to override track blocking' has been used Mandatory

FIR-FR254-Req a requested moveable element included in the route has 'track blocking' applied Mandatory FIR-FR255-Req a requested lockable device is not monitored 'in position for traffic' Mandatory FIR-FR256-Req a requested lockable device is 'released' Mandatory FIR-FR257-Req the requested line block cannot be turned in the requested block travel direction, unless the line block

conditions are disabled manually with a specific plug Mandatory

FIR-FR259-Req the requested route leads from an electrified track to a non-electrified track or a dead power track, unless the request 'Set main route to non-electrified tracks' has been used

Mandatory

FIR-FR260-Req the requested shunting route entry signal is being used as a main route exit signal Mandatory FIR-FR261-Req the requested shunting route exit signal is located at the same track section boundary as a main route exit

signal in opposite direction Mandatory

FIR-FR262-Req a requested track section is 'occupied', if required not 'occupied' in configuration requirements Mandatory



Requirement Finland - Priority FIR-FR263-Req a requested track section on destination track is not occupied, if route is set on the same destination track

with opposing route Mandatory

FIR-FR264-Req The track sections included in the shunting route must not be monitored as not 'occupied' in route basic conditions, unless required for specified track sections in configuration requirements.

Mandatory

FIR-FR265-Com 3.4 Route Initiation

FIR-FR266-Req If the route request is not rejected, the route shall become initiated. Mandatory FIR-FR267-Req All route elements in an initiated route shall be protected during the entire route life cycle from: Mandatory FIR-FR268-Req use by other route requests Mandatory FIR-FR269-Req use by local point operation permission Mandatory FIR-FR270-Req The initiation of a route shall consist of requesting the movement of powered moveable route elements to the required

position for the route, if the elements are not already in the required position, unless the point is a short trailing point on a track section of the overlap

Mandatory

FIR-FR271-Req The initiation of a main route shall consist of: Mandatory FIR-FR272-Req requesting the change of the block travel direction to the required direction for the route to be set into the

line, if the block travel direction is not already in the required position Mandatory

FIR-FR273-Req enabling the release of the line point upon the occupation of its associated track section, if the request 'Set main route to to line point' has been used

Mandatory

FIR-FR274-Req The initiation of a shunting route shall consist of requesting the change of the block travel direction to the required direction for the route to be set into the line, if the direction is not already in the required position.

Mandatory

FIR-FR275-Com 4 Route Locking - Proving

FIR-FR276-Com 4.1 Route Locking

FIR-FR277-Req The following route elements of an initiated route shall be locked: Mandatory FIR-FR278-Req all track sections included in the route and the overlap Mandatory FIR-FR279-Req all moveable elements included in or associated with the route, unless the point is a short trailing point on a

track section of the overlap that is not on the position required by the route Mandatory

FIR-FR281-Req A moveable element shall become locked, if any of the following conditions exist: Mandatory FIR-FR282-Req The element is monitored in the required position for the route. Mandatory FIR-FR283-Req The element provides flank protection to a route element that becomes locked for the route. Mandatory FIR-FR284-Req The locking of a route element shall be particular to its route. Mandatory



Requirement Finland - Priority FIR-FR285-Req A route element shall not be permitted to be locked simultaneously by multiple routes except in any of the following

cases: Mandatory

FIR-FR286-Req the element is locked in an overlap and in the next route in advance Mandatory FIR-FR287-Req the element is both locked for flank protection to a route and also locked in the route, flank protection or

overlap of another route Mandatory

FIR-FR288-Req the element is locked in the overlaps of converging routes Optional FIR-FR289-Req the element is locked in the overlaps of opposing routes Mandatory FIR-FR290-Req If a route element is locked simultaneously by multiple routes, the locking applied by each route shall be independent. Mandatory FIR-FR291-Req If a route is set into the line block, changing the block travel direction shall be prevented when the direction is in the

required position for the route. Mandatory

FIR-FR292-Req If a moveable element in the initiated route is not 'detected' in the required position following a movement request, the route shall remain initiated.

Mandatory

FIR-FR1807-Req The route elements locked in route locking shall not be released automatically if all of the route locking conditions are not satisfied and the proving of the route will not be completed.

FIR-FR295-Com 4.2 Route Proving

FIR-FR296-Req The entire route shall be assigned as 'locked', if all the following conditions exist: Mandatory FIR-FR297-Req all elements included or associated with route are protected from the use by other requests Mandatory FIR-FR298-Req all route elements required to be locked are locked for that route Mandatory FIR-FR299-Req The signalling of a route shall be enabled only when the entire route is 'locked'. Mandatory FIR-FR300-Req If the route is set into the 'route-initiated line block system', the associated block signals shall become enabled to

function automatically only after the entire route is 'locked'. Mandatory

FIR-FR301-Com 5 Route Releasing

FIR-FR302-Com 5.1 General

FIR-FR303-Req Route releasing includes following types of releasing: Mandatory FIR-FR304-Req Route cancellation by command Mandatory FIR-FR305-Req Route emergency release by command, for main routes only Mandatory FIR-FR306-Req Train operated route release Mandatory FIR-FR307-Req Releasing of a route or part of a route shall not affect any other routes. Mandatory



Requirement Finland - Priority FIR-FR308-Req If a route element included or associated with the route is released from its route, the following actions must be

executed: Mandatory

FIR-FR309-Req Route element shall be unlocked by its route. Mandatory FIR-FR310-Req Route element shall be available for use by other requests. Mandatory FIR-FR311-Com

5.2 Route Cancellation or Emergency Release

FIR-FR312-Com 5.2.1 General

FIR-FR313-Req Route cancellation shall be requested by 'Cancel route' from the signaller. Mandatory FIR-FR314-Req Route emergency release shall be requested by any of the following requests: Mandatory FIR-FR315-Req 'Entire route emergency release' from the signaller. Mandatory FIR-FR316-Req 'Residual route emergency release' from the signaller. Mandatory FIR-FR317-Req Route release shall release all route elements from route locking caused by the route in question. Mandatory FIR-FR318-Req Release of route elements can be done only after the route entry signal and the other signals between the route entry

and exit signals, which can display 'stop' aspect, display 'stop' aspect. Mandatory

FIR-FR319-Req Each route shall have an individual release delay timer for entire route emergency release. Mandatory FIR-FR320-Req A main route to an occupied track shall have the same release delay timer as the corresponding main route Mandatory FIR-FR321-Req Each route shall have an individual residual release delay timer for residual route emergency release. Mandatory FIR-FR322-Req Release of each individual route in a composite route shall be requested individually with a command. Mandatory FIR-FR323-Com

5.2.2 Valid Approach to Route

FIR-FR324-Req Approach zone may contain one or more approach options to the route considered. Mandatory FIR-FR325-Req Approach zone is defined in rear of the route entry signal in the following order: Mandatory FIR-FR326-Req 1. Track section, whose boundary is at least 300 m from a main or block signal or from a combined signal

connected with the ATP, from which there is at least the ATP data transfer distance to the signal considered. Mandatory

FIR-FR327-Req 2. The track section located by the distant signal, from which there is at least the ATP data transfer distance to the signal considered, if the track section boundary is at least 300 m from the distant signal

Mandatory

FIR-FR328-Req 3. The track section in rear of the main signal or a combined signal, which can act as the main route entry signal, from which the only route to the signal considered goes through a short point leading to the diverging track.

Mandatory

FIR-FR329-Req 4. The track section where the track vacancy proving ends. Mandatory



Requirement Finland - Priority FIR-FR330-Req

Mandatory

FIR-FR331-Req Approach zone shall be assigned as 'occupied', if a track section or track sections on the approach zone are detected as occupied.

Mandatory

FIR-FR332-Req The occupancy of a track section or consecutive track sections on a track in rear of the route entry signal of the route to be cancelled must be checked for valid approach, if no main route is set to route entry signal of the route to be released.

Mandatory

FIR-FR333-Req Track sections to be checked for valid approach in rear of route entry signal are the consecutive track sections starting from the track section in rear of route entry signal and ending to first of the following track sections:

Mandatory

FIR-FR334-Req The furthest track section from the route entry signal that does not include route point or points. Mandatory FIR-FR335-Req The track section that reaches the distance of 1200 m from route entry signal of the route to be released. Mandatory FIR-FR336-Req The furthest track section from the route entry signal equipped with track vacancy proving. Mandatory FIR-FR337-Req Route shall have a 'valid approach', if any of the following conditions exist: Mandatory FIR-FR338-Req Approach zone is occupied and a main route or routes are set from occupied track section to the route entry

signal of the route to be cancelled. Mandatory

FIR-FR339-Req Any track section that needs to be checked for valid approach is occupied and no main route is set to the route entry signal of the route to be released.

Mandatory

FIR-FR340-Com 5.2.3 Main Route Cancellation and Emergency Release

FIR-FR341-Com 5.2.3.1 Main Route Cancellation - Only 'Stop' Aspect Displayed



Requirement Finland - Priority FIR-FR342-Req Main route cancellation shall be accepted, if all the following conditions are satisfied: Mandatory FIR-FR343-Req Request 'Cancel route' is received from the signaller. Mandatory FIR-FR344-Req 'Signalling conditions' for the route entry signal have never been satisfied during entire route life cycle. Mandatory FIR-FR345-Req Route elements included or associated with the route shall be released immediately, when route cancellation is

accepted. Mandatory

FIR-FR346-Com 5.2.3.2 Route Cancellation / Emergency Release of Completed Main Route

FIR-FR347-Com 5.2.3.2.1 Valid Approach Not Detected for Route

FIR-FR348-Req Main route cancellation shall be accepted if all the following conditions are satisfied: Mandatory FIR-FR349-Req Request 'Cancel route' is received from the signaller. Mandatory FIR-FR350-Req Valid approach for the route has not been detected after the signalling conditions for the route were

fulfilled. Mandatory

FIR-FR351-Req All track sections in the route not 'occupied' at the time of route setting have not been 'occupied' during entire route life cycle.

Mandatory

FIR-FR352-Req All track sections in the route 'occupied' at the time of route setting for a main route to an occupied track have been 'occupied' during entire life cycle.

Mandatory

FIR-FR353-Req All track sections included or associated with the route are locked for the route in question. Mandatory FIR-FR354-Req 'Signalling conditions' for the route entry signal were satisfied within the current route life cycle. Mandatory FIR-FR355-Req Route cancellation shall consist of the following actions: Mandatory FIR-FR356-Req setting the route entry signal to display a 'stop' aspect Mandatory FIR-FR357-Req setting all the other signals between the route entry and exit signals to display a 'stop' aspect Mandatory FIR-FR358-Req Route elements shall be released immediately, when route cancellation is accepted and route entry signal is displaying

a 'stop' aspect. Mandatory

FIR-FR359-Com 5.2.3.2.2 Valid Approach Detected for Route

FIR-FR360-Req Route release shall be accepted if all the following conditions are satisfied: Mandatory FIR-FR361-Req Request 'Emergency route release' is received from the signaller. Mandatory FIR-FR362-Req Valid approach for the route has been detected in case, where a defined approach zone exists for the route. Mandatory FIR-FR363-Req all track sections in the route not 'occupied' at the time of route setting are not 'occupied' Mandatory FIR-FR364-Req all track sections in the route are locked Mandatory FIR-FR365-Req the 'signalling conditions' for the route entry signal were satisfied within the current route life cycle Mandatory



Requirement Finland - Priority FIR-FR366-Req Route release shall consist of following actions: Mandatory FIR-FR367-Req setting the route entry signal to display a 'stop' aspect Mandatory FIR-FR368-Req setting all sub-route signals, which can display 'stop' aspect, to display a 'stop' aspect Mandatory FIR-FR369-Req starting the release delay timer when the route entry signal is displaying a 'stop' aspect Mandatory FIR-FR370-Req Route elements shall be released when the release delay timer expires. Mandatory FIR-FR371-Req If a track section included or associated with the route becomes 'occupied' while the release delay time is running, route

release shall be stopped. Mandatory

FIR-FR372-Req Release delay timer for route release shall be configurable between 1s - 180s, when valid approach is detected for the route to be released.

Mandatory

FIR-FR373-Req Default value of release delay timer for route release shall be 60s unless other value specified in engineering configuration requirements.

Mandatory

FIR-FR374-Com 5.2.4 Emergency release of Residual Route

FIR-FR375-Com 5.2.4.1 Emergency release of Residual Main Route

FIR-FR376-Req The cancellation of a residual main route shall be accepted, if a request 'Release residual route' is received from the signaller and one of the following conditions exists:

Mandatory

FIR-FR377-Req a track section included in or associated with the route not 'occupied' at the time of route setting is 'occupied'

Mandatory

FIR-FR378-Req a track section included in or associated with the route is not locked in the route Mandatory FIR-FR379-Req Residual route release shall consist of: Mandatory FIR-FR380-Req setting the route entry signal to display a 'stop' aspect, if the signal is not displaying a 'stop' aspect Mandatory FIR-FR381-Req setting all the other sub-route signals, which can display 'stop' aspect, to display a 'stop' aspect, if all signals

are not displaying a 'stop' aspect Mandatory

FIR-FR382-Req starting the residual release delay timer when the route entry signal is displaying a 'stop' aspect Mandatory FIR-FR383-Req All route elements shall be released when the residual release delay time expires. Mandatory FIR-FR384-Req If a track section included or associated with the route or overlap becomes 'occupied' while the release delay time is

running, residual route release shall be stopped. Mandatory

FIR-FR385-Req Release delay timer for residual route release shall be configurable between 1s - 180s. Mandatory FIR-FR386-Req Default value of release delay timer for residual route release shall be 60s unless other value specified in engineering

configuration requirements. Mandatory

FIR-FR387-Com 5.2.5 Shunting Route Cancellation



Requirement Finland - Priority FIR-FR388-Req Route cancellation shall always be accepted for shunting route, if a request 'Cancel route' is received from the signaller. Mandatory FIR-FR389-Req Route cancellation shall consist of setting the route entry signal to display a 'stop' aspect, if the route entry signal is

displaying an aspect permitting driving. Mandatory

FIR-FR390-Req Route elements shall be released immediately, when route entry signal is displaying 'stop' aspect. Mandatory FIR-FR391-Com

5.3 Route Use

FIR-FR392-Com 5.3.1 Occupancy Sequence FIR-FR393-DK The following diagram displays the elements used to determine the correct occupancy sequence.

FIR-FR394-Diag

TVP sections

VEHICLE MOVEMENT

TVP A TVP B TVP C

FIR-FR395-DK The correct occupancy sequence reflecting the path of a unit shall be the following sequence in order: FIR-FR396-DK 1. track section A becomes 'occupied' FIR-FR397-DK 2. track section B becomes 'occupied'

FIR-FR398-Req

3. track section C becomes 'occupied' and track section A becomes not 'occupied' OR track section A becomes not 'occupied' and track section C becomes 'occupied'

FIR-FR399-DK 4. track section B becomes not 'occupied' FIR-FR400-Req The correct occupancy sequence has to be detected for each track section included in the route. Mandatory

FIR-FR401-Com 5.3.2 Signal Replacement

FIR-FR402-Com Signals shall be set to a ‘stop’ aspect according to the chapters 5.3.3 and 5.3.4. Mandatory

FIR-FR403-Com 5.3.3 Main Route - Signal Replacement

FIR-FR404-Req A main route entry signal shall be set to a 'stop' aspect by vehicle movement, if a 2-3 s delay timer expires after the track section in advance of the route entry signal becomes 'occupied'.

Mandatory

FIR-FR405-Req Another sub-route signal, which can display 'stop' aspect, shall be set to display a 'stop' aspect by vehicle movement, if the track section in advance of the sub-route signal becomes 'occupied'.

Mandatory



Requirement Finland - Priority

FIR-FR406-Req A shunting signal associated with a main route entry signal shall be set to a 'stop' aspect when the main route entry signal is set to a 'stop' aspect.

Mandatory

FIR-FR407-Req The entry signal for a route to an occupied track shall be set to a 'stop' aspect by vehicle movement identically as the main route entry signal.

Mandatory

FIR-FR408-Com 5.3.4 Shunting Route - Signal Replacement

FIR-FR409-Req A shunting route entry signal shall immediately be set to a 'stop' aspect: Mandatory FIR-FR410-Req if any track section in the route becomes 'occupied' Mandatory FIR-FR411-Req if any track section in the route becomes not 'occupied' Mandatory

FIR-FR412-Req While the track section in advance of the route entry signal is 'occupied' during route setting, the route entry signal shall immediately be set to a 'stop' aspect, if the track section in rear of the route entry signal becomes not 'occupied'.

Mandatory

FIR-FR413-Com 5.4 Train Operated Route Release

FIR-FR414-Req Train operated route release shall release route elements by correct occupancy sequence over the route. Mandatory

FIR-FR415-Req Route elements shall be released only if the direction of occupancy sequence in the route corresponds to the direction of the route.

Mandatory

FIR-FR416-Req When a track section becomes released by train operated route release, the following route elements shall be released: Mandatory FIR-FR417-Req the signal that is included in the route protecting the track section Mandatory FIR-FR418-Req the moveable elements included in the track section Mandatory FIR-FR419-Req the elements for flank protection for the track section Mandatory FIR-FR420-Req Train operated route release shall be started if all the following conditions are satisfied: Mandatory

FIR-FR421-Req the track section in advance of the route entry signal becomes 'occupied' while the track section in rear is

'occupied' Mandatory

FIR-FR422-Req the route entry signal is displaying a 'stop' aspect Mandatory

FIR-FR423-Com 5.4.1 Route Release

FIR-FR424-Req A route element shall not become released under or ahead of a train. Mandatory FIR-FR425-Req A track section shall become released by train operated route release if all the following conditions are satisfied: Mandatory FIR-FR426-Req the correct occupancy sequence is detected from the track section in rear to the track section in advance Mandatory FIR-FR427-Req the track section is not 'occupied' Mandatory FIR-FR428-Req the track section in rear has been released from the route, if it was locked in the same route Mandatory

FIR-FR429-Req If the track section in rear of the route entry signal is 'occupied', the track section in advance of the route entry signal shall become released without the track section in rear of the route entry signal becoming not 'occupied'.

Mandatory




FIR-FR430-Req If the route ends in dark territory, the last track section in the route shall become released without the occupancy of the track section in advance, if all other conditions for releasing are satisfied.

Mandatory

FIR-FR431-Com 5.4.2 Overlap Release

FIR-FR432-Req Each route shall have an individual overlap release timer. Mandatory FIR-FR433-Req The overlap release timer shall be started, if the entire train is within the destination track. Mandatory FIR-FR434-Req When the overlap release timer expires, all track sections in the overlap shall be released. Mandatory

FIR-FR435-Req The overlap release timer shall be stopped if a track section in the overlap becomes 'occupied' while the route exit signal is displaying a 'stop' aspect.

Mandatory

FIR-FR436-Req Release delay timer for overlap release shall be configurable between 1s - 180s. Mandatory

FIR-FR437-Req Default value of release delay timer for overlap release shall be 60s unless other value specified in engineering configuration requirements.

Mandatory

FIR-FR438-Req A track section in the overlap shall become released from its route by train operated route release, if all the following conditions are satisfied:

Mandatory

FIR-FR439-Req the conditions applicable for releasing a track section in the route are satisfied for the track section in the

overlap Mandatory

FIR-FR440-Req the same track section becomes released from the route of the route in advance Mandatory

FIR-FR441-Com 5.5 Special Route Releases

FIR-FR442-Com 5.5.1 Release by Turnback Movement

FIR-FR443-Req Release by turnback movement shall enable the release of track sections only for shunting route. Mandatory

FIR-FR444-Req All track sections of the original route behind a turnback movement shall become released immediately if all the following conditions are satisfied:

Mandatory

FIR-FR445-Req a reversing main or shunting route has been set for the turnback movement Mandatory

FIR-FR446-Req all track sections of the original route are not occupied Mandatory

FIR-FR447-Req the first track section of the reversing main or shunting route is occupied Mandatory

FIR-FR448-Req If the turnback movement uses the route in advance of the original route (long train), the release by turnback movement shall be applied to both routes in question separately.

Mandatory

FIR-FR449-Com 5.5.2 Destination Track Release

FIR-FR450-Req The destination track shall contain the track section or track sections of the track in rear of the route exit signal. Mandatory




FIR-FR451-Req While the track section in rear of the route exit signal is not 'occupied', train operated route release shall be applied to the other track sections in the destination track.

Mandatory

FIR-FR452-Req While the track section in rear of the route exit signal is 'occupied', all track sections in the destination track shall become released by the destination track release, if all the following conditions are satisfied:

Mandatory

FIR-FR453-Req the entire train is within the destination track Mandatory FIR-FR454-Req the destination track contains no moveable elements Mandatory FIR-FR455-Req all track sections behind the train have been released by train operated route release Mandatory FIR-FR456-Req The destination track release shall not release any track sections in the overlap. Mandatory

FIR-FR457-Com 5.6 Engineering Configuration Requirements

FIR-FR458-Req The furthest track section of all possible approach zones for each route shall be defined viewed from the direction of the route entry signal of the route to be cancelled or released.

Mandatory

FIR-FR459-Req The release time delay for overlap release shall be defined, if other than the default value. Mandatory

FIR-FR460-Req The release time delay for route release while valid approach is detected shall be defined, if other than the defaut value.

Mandatory

FIR-FR461-Req The release time delay for residual route release shall be defined, if other than the default value. Mandatory FIR-FR462-Req The destination track for each main route shall be defined. Mandatory

FIR-FR463-Com 6 Monitoring


FIR-FR465-Req The interlocking system shall continuously monitor the conditions in a route. Mandatory

FIR-FR466-Req If a main signal with an associated shunting signal is in position to provide flank protection or opposing route protection, the monitoring conditions shall be supervised for:

Mandatory

FIR-FR467-Req the main signal's 'stop' aspect Mandatory FIR-FR468-Req the shunting signal's 'stop' aspect Mandatory

FIR-FR469-Com 6.2 Main Route Monitoring

FIR-FR470-Com 6.2.1 Monitoring Conditions

FIR-FR471-Req Main route monitoring conditions are: Mandatory FIR-FR472-Req all moveable elements required as 'locked' included in or associated with the route remain 'locked' Mandatory




FIR-FR473-Req all moveable elements required as 'locked' included in or associated with the route or remain 'monitored' in

the required position Mandatory

FIR-FR474-Req all track sections included in or associated with the route remain 'locked' in the route, except the track

sections required to be not 'occupied' for flank protection Mandatory

FIR-FR475-Req all track sections included in or associated with the route remain not 'occupied' Mandatory

FIR-FR476-Req track section in advance of route exit signal required as not occupied in engineering configuration

requirements is not occupied, if route has no overlap Mandatory

FIR-FR477-Req all route elements remain not 'fouled' Mandatory FIR-FR1730-Req the route entry signal is displaying a monitored drive permitting aspect Mandatory FIR-FR478-Req the sub-route shunting signal is displaying a 'proceed with caution' aspect Mandatory

FIR-FR1731-Req the sub-route combined signal between the route entry and exit signals is displaying 'proceed with caution'

aspect Mandatory

FIR-FR479-Req all signals providing flank protection display a monitored 'stop' aspect Mandatory FIR-FR480-Req the route exit signal is not 'dark' Mandatory FIR-FR481-Req the route exit signal is able to display a 'stop' aspect Mandatory FIR-FR482-Req the route exit signal is displaying a monitored aspect Mandatory FIR-FR483-Req the shunting signal as a route exit signal is displaying a 'stop' aspect Mandatory FIR-FR484-Req level crossing system conditions are satisfied Mandatory FIR-FR485-Req all lockable devices included in or associated with the route remain not 'released' Mandatory FIR-FR486-Req all lockable devices included in or associated with the route are 'monitored' in 'position for traffic' Mandatory FIR-FR487-Req the 'signalling conditions' for a block entry signal are satisfied, if the main route ends to a line block Mandatory FIR-FR488-Req the conditions for block are fulfilled, if the main route ends to a line block Mandatory

FIR-FR489-Req Monitoring conditions for a main route to an occupied track include in addition to the normal route conditions that all track sections in the route 'occupied' at the time of route setting remain 'occupied'.

Mandatory

FIR-FR490-Req If the monitoring conditions of the route entry signal's aspect become disturbed: Mandatory FIR-FR491-Req the route entry signal shall immediately be set to a 'stop' aspect Mandatory

FIR-FR492-Req all other sub-route signals, which can display 'stop' aspect, shall immediately be set to displaya 'stop'

aspect Mandatory

FIR-FR493-Com 6.2.2 Signal Replacement - Irrevocable

FIR-FR494-Req The route entry signal shall be set to a 'stop' aspect for the remainder of the route life cycle, if route monitoring conditions are disturbed.

Mandatory




FIR-FR495-Com 6.3 Shunting Route Monitoring

FIR-FR496-Com 6.3.1 Monitoring Conditions

FIR-FR497-Req Shunting route monitoring conditions are: Mandatory FIR-FR498-Req all moveable elements required as 'locked' included in the route remain 'locked' Mandatory

FIR-FR499-Req all moveable elements required as 'locked' included in the route or remain 'monitored' in the required

position Mandatory

FIR-FR500-Req all track sections included in the route remain 'locked' in the route Mandatory FIR-FR501-Req all track sections included in the route 'occupied' at the time of route setting remain 'occupied' Mandatory FIR-FR502-Req all track sections included in the route not 'occupied' at the time of route setting remain not 'occupied' Mandatory FIR-FR503-Req all route elements remain not 'fouled' Mandatory FIR-FR505-Req the route exit signal is not 'dark' Mandatory FIR-FR506-Req the route exit signal is able to display a 'stop' aspect Mandatory FIR-FR507-Req the route exit signal is displaying a monitored 'stop' or 'proceed with caution' aspect Mandatory FIR-FR508-Req level crossing system conditions are satisfied Mandatory FIR-FR509-Req all lockable devices included in the route remain not 'released' Mandatory FIR-FR510-Req all lockable devices included in the route are 'monitored' in 'position for traffic' Mandatory FIR-FR511-Req the 'signalling conditions' for a block entry signal are satisfied, if the shunting route ends to a line block Mandatory FIR-FR512-Req the conditions for block are fulfilled, if the shunting route ends to a line block Mandatory FIR-FR513-Req The overlap shall not be monitored for the shunting route. Mandatory FIR-FR514-Req The flank protection shall not be monitored for the shunting route. Mandatory

FIR-FR515-Req If the shunting route monitoring conditions become disturbed, the route entry signal shall immediately be set to a 'stop' aspect.

Mandatory

FIR-FR516-Com 6.3.2 Signal Replacement - Irrevocable

FIR-FR517-Req The route entry signal shall be set to a 'stop' aspect for the remainder of the route life cycle, if route monitoring conditions are disturbed.

Mandatory

FIR-FR518-Com 7 Track Section





FIR-FR520-Req The interlocking system shall be able to monitor the occupancy of track sections. Mandatory FIR-FR521-Req A route shall be able to logically lock track sections. Mandatory FIR-FR522-Req A track section shall be monitored as: Mandatory FIR-FR523-Req not 'occupied' if there is no physical occupancy on the track section Mandatory FIR-FR524-Req 'occupied' if there is a physical occupancy on the track section Mandatory FIR-FR525-Req A track section shall be logically assigned as 'occupied' if any of the following conditions are satisfied: Mandatory FIR-FR526-Req the track section is 'failed' Mandatory FIR-FR527-Req the track section is occupied because it's not clear of fouling and the fouling conditions are satisfied Mandatory FIR-FR528-Req A track section shall be assigned as 'failed' if a failure state is detected from the track section. Mandatory FIR-FR529-Req A track section shall not become released by train operated route release if it is 'failed'. Mandatory

FIR-FR530-Req Train operated route release shall not accept the change of occupancy status caused by a 'failed' track section as valid for the releasing sequence.

Mandatory

FIR-FR531-Com 7.2 Track blocking

FIR-FR532-Req The interlocking system shall be able to block route setting, if the route includes a track section with track blocking applied.

Mandatory

FIR-FR533-Req 'Track blocking' shall be applied to a track section if a request 'Set route blocking on a track section' is received from the signaller.

Mandatory

FIR-FR534-Req It shall not be possible to set more than one track blocking to a track section simultaneously. Mandatory FIR-FR535-Req 'Track blocking' shall be applicable to: Mandatory FIR-FR536-Req a track Mandatory FIR-FR537-Req a moveable element Mandatory FIR-FR538-Req a diamond crossing Mandatory FIR-FR539-Req Route setting shall be prevented while 'track blocking' is applied to a track section in: Mandatory FIR-FR540-Req the requested route, unless shunting route is set with a command overriding 'track blocking' Mandatory FIR-FR541-Req the overlap of the requested main route Mandatory FIR-FR542-Req advance of the main route exit signal of a route with 0 overlap Mandatory

FIR-FR543-Req

Giving a local point operation permission shall be prevented to a local point operation group, if a track section with 'track blocking' applied is included in the local point operation group in question, unless the local point operation permission is given with an emergency command.

Mandatory

FIR-FR544-Req If 'track blocking' is applied to a point track section, route setting shall be prevented across both branches of the point. Mandatory




FIR-FR545-Req If 'track blocking' is applied to a track section including a standard diamond crossing, route setting shall be prevented across both branches of the standard diamond crossing.

Mandatory

FIR-FR546-Req 'Track blocking' shall be removed from a track section if a request 'Remove track blocking from a track section' is received from the signaller.

Mandatory

FIR-FR547-Com 7.3 Free of fouling restrictions

FIR-FR548-Req The branch is free of fouling restrictions when the element's associated track section boundary is at least 5m distance from the fouling point in the branch in question, when viewed from the direction of the element

Mandatory

FIR-FR549-Req The following elements may have one or more branches that are not free of fouling restrictions: Mandatory FIR-FR550-Req points Mandatory FIR-FR551-Req diamond crossings with slips Mandatory FIR-FR552-Req standard diamond crossings Mandatory FIR-FR553-Req Each branch that is not free of fouling restrictions shall be configured in engineering configuration requirements. Mandatory FIR-FR554-Req Element is free of fouling restrictions, if all element's branches are free of fouling restrictions. Mandatory

FIR-FR555-Req Track section including an element not free of fouling restrictions shall be assigned as occupied, if any of the following conditions exists:

Mandatory

FIR-FR556-Req the track section in question is detected as occupied Mandatory

FIR-FR557-Req

the track section associated with the element's branch not free of fouling restrictions of the track section in question is detected as occupied and the element on the associated track section is in the position leading to the branch not free of fouling restrictions

Mandatory

FIR-FR558-Req

the track section associated with the element's branch not free of fouling restrictions of the track section in question is detected as occupied and the element included in the associated track section has been moved when the track section was occupied independent of the original position

Mandatory

FIR-FR559-Req Conditions of free of fouling restrictions for each branch not free of fouling restrictions has to be considered independent of each other.

Mandatory

FIR-FR560-Req Track section assigned as occupied because of conditions of free of fouling restrictions shall be assigned as not occupied only, if all the following conditions exists:

Mandatory

FIR-FR561-Req the track section in question is detected as not occupied Mandatory

FIR-FR562-Req the track section (or track sections) associated with the branch not free of fouling restrictions is detected as

not occupied Mandatory

FIR-FR563-Com 7.3.1 Standard Diamond Crossing




FIR-FR564-Req If a track section associated with a standard diamond crossing is used in a route, only the applicable path of the standard diamond crossing shall be used by the route.

Mandatory

FIR-FR565-Req While a path of the standard diamond crossing is used in an initiated route, all requests for use of the other path shall be rejected.

Mandatory

FIR-FR566-Req If a track section associated with a standard diamond crossing is locked by a route, the locking shall be applied only to the path used by the route.

Mandatory

FIR-FR567-Req While a path of the standard diamond crossing is locked in a route, all requests for use of the other path shall be rejected.

Mandatory

FIR-FR568-Com 7.4 Axle Counting Systems

FIR-FR569-Req Momentary loss of 'occupied' status shall not cause the track section to become not 'occupied'. Mandatory

FIR-FR570-Req The interlocking system shall be able to indicate the axle count value for a track section if the track section is equipped with an axle counting system.

Optional

FIR-FR571-Req The reset of axle count value of a track section shall be possible if one of the following conditions are satisfied: Mandatory FIR-FR572-Req the track section is detected 'occupied' Mandatory FIR-FR573-Req the track section is 'failed' Mandatory FIR-FR574-Req The reset of the axle count value shall be possible to execute with emergency reset procedure: Mandatory

FIR-FR581-Req Emergency reset procedure shall reset the axle count value of the track section, if the following conditions are satisfied:

Mandatory

FIR-FR582-Req request for emergency reset of the axle count value is received from the signaller Mandatory FIR-FR583-Req the last axle was counted out from the track section Mandatory


FIR-FR585-Req Configuration data for each track section shall contain: Mandatory FIR-FR586-Req element's branches that are not free of fouling restrictions Mandatory FIR-FR587-Req information about the type of the track vacancy proving system Mandatory

FIR-FR588-Com 8 Signals


FIR-FR590-Req The interlocking system shall display correct signal aspects on signals. Mandatory FIR-FR591-Req The interlocking system shall apply correct ATP aspects in combination with signal aspects. Mandatory



Requirement Finland - Priority FIR-FR592-Req The interlocking system shall transmit additional route information to the ATP system to supplement signal aspects. Mandatory

FIR-FR593-Req If a signal aspect on a signal is changed, the signalling of the signals in rear shall be adjusted to maintain correct signal sequences.

Mandatory

FIR-FR594-Req If a signal aspect on a signal is changed, the ATP aspects shall be adjusted to maintain correct signal sequences and ATP sequences.

Mandatory

FIR-FR595-Com 8.2 Main Signals

FIR-FR596-Com 8.2.1 Signalling Conditions

FIR-FR597-Com 8.2.1.1 Route Signalling

FIR-FR598-Req The 'signalling conditions' for a main route entry signal are satisfied if all the following conditions are satisfied: Mandatory FIR-FR599-Req the route is set as a main route Mandatory FIR-FR600-Req the monitoring conditions of the route started by the main signal are satisfied Mandatory FIR-FR601-Req the signal has not a fault preventing the display of a drive permitting aspect Mandatory FIR-FR602-Req the signal was not set to a 'stop' aspect by the signaller by giving a Stop command Mandatory FIR-FR603-Req Signaller shall be able to cancel the Stop command by giving a Proceed command Mandatory

FIR-FR604-Com 8.2.2 Main Signal Aspects

FIR-FR605-Com 8.2.2.1 Main Signal Aspect - Stop

FIR-FR606-Req A main signal shall display a 'stop' aspect unless the 'signalling conditions' for the main route entry signal are satisfied. Mandatory

FIR-FR607-Com 8.2.2.2 Main Signal Aspect - Proceed

FIR-FR608-Req A main signal shall display a 'proceed' aspect if all the following conditions are satisfied: Mandatory FIR-FR609-Req the 'signalling conditions' for the main route entry signal are satisfied Mandatory

FIR-FR610-Req the 'signalling conditions' for a signal protecting a block section are satisfied, if the main signal also

protects the first block section on the line Mandatory

FIR-FR611-Com 8.2.2.3 Main Signal Aspect - Proceed 35

FIR-FR612-Req A main signal shall display a 'proceed 35' aspect if any the following conditions are satisfied: Mandatory



Requirement Finland - Priority FIR-FR613-Req the 'signalling conditions' for the route entry signal in a 'proceed 35' route are satisfied Mandatory FIR-FR614-Req the route is a main route to an occupied track Mandatory

FIR-FR615-Req A main signal displaying a 'proceed 35' aspect shall not change to a 'proceed' aspect if the 'signalling conditions' for a 'proceed' aspect become satisfied.

Mandatory

FIR-FR616-Com 8.3 Distant Signals

FIR-FR617-Com 8.3.1 Distant Signal Aspects

FIR-FR618-Req A distant signal shall indicate the appropriate aspect of the designated main signal. Mandatory FIR-FR619-Req A distant signal on the same mast as a main signal displaying a 'stop' aspect shall be set to dark. Mandatory

FIR-FR620-Com 8.3.1.1 Distant Signal Aspect - Expect stop

FIR-FR621-Req A distant signal shall display an 'expect stop' aspect if any of the following conditions exist: Mandatory FIR-FR622-Req the designated main signal is displaying a 'stop' aspect Mandatory FIR-FR623-Req the designated block signal is displaying a 'stop' aspect Mandatory FIR-FR624-Req the designated main signal is a route exit without physical signal displaying aspects Mandatory FIR-FR625-Req main route exit signal is shunting signal Mandatory FIR-FR626-Req there is no information available from the main route exit signal to the distant signal Mandatory

FIR-FR627-Req the distance signal is in the same mast with a main signal which displays a drive permitting aspect and

starts a main route to an occupied track Mandatory

FIR-FR628-Com 8.3.1.2 Distant Signal Aspect - Expect proceed

FIR-FR629-Req A distant signal shall display an 'expect proceed' aspect if one of the following conditions exist: Mandatory FIR-FR630-Req the designated main signal is displaying a 'proceed' aspect Mandatory FIR-FR631-Req the designated block signal is displaying a 'proceed' or 'proceed, expect stop' aspect Mandatory

FIR-FR632-Com 8.3.1.3 Distant Signal Aspect - Expect proceed 35

FIR-FR633-Req A distant signal shall display an 'expect proceed 35' aspect if the designated main signal is displaying a 'proceed 35' aspect.

Mandatory

FIR-FR634-Com 8.4 Shunting Signals




FIR-FR635-Com 8.4.1 Signalling conditions

FIR-FR636-Com 8.4.2 Shunting Route Signalling

FIR-FR637-Req The 'signalling conditions' for a shunting route entry signal are satisfied if all the following conditions are satisfied: Mandatory FIR-FR638-Req the route is set as a shunting route Mandatory FIR-FR639-Req the monitoring conditions for the route started by the signal are satisfied Mandatory FIR-FR640-Req the signal has not a fault preventing to display a drive permitting aspect Mandatory FIR-FR641-Req signaller has not set the signal to display 'stop' aspect by giving a Stop command Mandatory FIR-FR642-Req Signaller shall be able to cancel the Stop command by giving a Proceed command Mandatory

FIR-FR643-Req The 'signalling conditions' for a sub-route shunting signal in a main route are satisfied if all the following conditions are satisfied:

Mandatory

FIR-FR644-Req the route is set as a main route Mandatory FIR-FR645-Req the 'proceed' aspect's monitoring conditions for the corresponding route are satisfied Mandatory FIR-FR646-Req the signal has not been set to a 'stop' aspect Mandatory

FIR-FR647-Com 8.4.3 Shunting Signal Aspects

FIR-FR648-Com 8.4.3.1 Shunting Signal Aspect - Stop

FIR-FR649-Req A shunting signal shall display a 'stop' aspect unless one of the following conditions is satisfied: Mandatory FIR-FR650-Req the 'signalling conditions' for the shunting route entry signal are satisfied Mandatory FIR-FR651-Req the 'signalling conditions' for the sub-route shunting signal in a main route are satisfied Mandatory FIR-FR652-Req the shunting signal is set to 'no aspects' within an formed local permission area Mandatory

FIR-FR653-Com 8.4.3.2 Shunting Signal Aspect - Proceed with caution

FIR-FR654-Req A shunting signal shall display a 'proceed with caution' aspect if one of the following conditions is satisfied: Mandatory FIR-FR655-Req the 'signalling conditions' for the shunting route entry signal are satisfied Mandatory FIR-FR656-Req the 'signalling conditions' for the sub-route signal in a main route are satisfied Mandatory

FIR-FR657-Com 8.4.3.3 Shunting Signal Aspect - No aspects

FIR-FR658-Req A shunting signal shall display 'no aspects' if all the following conditions are satisfied: Mandatory



Requirement Finland - Priority FIR-FR659-Req the shunting signal is within an formed local point operation group Mandatory FIR-FR660-Req the monitoring conditions of the formed local point operation group are not disturbed Mandatory

FIR-FR661-Com 8.5 Block Signals or Line Main Signals

FIR-FR662-Com 8.5.1 Signalling Conditions

FIR-FR663-Req A line block section shall be protected by one of the following signals: Mandatory FIR-FR664-Req a block signal Mandatory FIR-FR665-Req line main signal Mandatory FIR-FR666-Req a main route entry signal also protecting the first block section on the line Mandatory

FIR-FR667-Req The 'signalling conditions' for a signal protecting a block section are satisfied if all the following conditions are satisfied:

Mandatory

FIR-FR668-Req the correct occupation sequence occurred for previously set block section from the block section to the

block section or to the line point side track, while the line point was not in the position for the line Mandatory

FIR-FR669-Req the block signal, line main signal or line block entry signal ending the block section displayed an aspect

permitting driving while the block section was occupied by the previous train Mandatory

FIR-FR670-Req the track sections within the block section were 'occupied' in a correct sequence, if there are multiple track

sections within the block section Mandatory

FIR-FR671-Req the track sections in the block section are not 'occupied' Mandatory FIR-FR672-Req the signal is not 'blocked' Mandatory FIR-FR673-Req the block or main signal in advance is not 'dark' Mandatory FIR-FR674-Req line points in the block section are monitored in the required position Mandatory FIR-FR675-Req lockable devices in the block section are monitored 'in position for traffic' Mandatory FIR-FR676-Req monitoring devices in the block section are monitored 'in position for traffic' Mandatory FIR-FR677-Req level crossing system conditions for a level crossing system in the block section are satisfied Mandatory

FIR-FR678-Req the track sections in the overlap of the block section in the direction of signalling are not 'occupied' (if an

overlap is configured) Mandatory

FIR-FR679-Req the block travel direction is in the direction of signalling Mandatory

FIR-FR680-Req A signal shall be set to a 'stop' aspect immediately if the 'signalling conditions' for the block signal become not satisfied.

Mandatory

FIR-FR681-Req Block signals or line main signals protecting a block section in an 'automatic block system' shall function automatically according to the 'signalling conditions'.

Mandatory

FIR-FR682-Req Block signals or line main signals protecting a block section in a 'route-initiated line block system' shall: Mandatory




FIR-FR683-Req function automatically according to the 'signalling conditions' while enabled by a route toward the line

block Mandatory

FIR-FR684-Req function automatically according to the 'signalling conditions' while enabled by a route from the line point

on the line Mandatory

FIR-FR685-Req be maintained at a 'stop' aspect while not enabled by a route Mandatory

FIR-FR686-Req Block signals or line main signals in a 'route-initiated line block system' shall be maintained at a 'stop' aspect following the passage of a train until the signals are enabled to function automatically by the next route.

Mandatory

FIR-FR687-Req

Cancellation of a route set into the line block shall set the block signals or line main signals in a 'route-initiated line block system' between the railway operating location and the rear of the previous train to a 'stop' aspect, when the route entry signal displays the 'stop' aspect.

Mandatory

FIR-FR688-Com 8.5.2 Block Signal Aspects

FIR-FR689-Req Block signal aspects shall contain main signal and distant signal information. Mandatory

FIR-FR690-Com 8.5.2.1 Aspect - Stop

FIR-FR691-Req A block signal shall display a 'stop' aspect unless the 'signalling conditions' for the block signal are satisfied. Mandatory

FIR-FR692-Com 8.5.2.2 Aspect - Proceed, expect proceed

FIR-FR693-Req A block signal shall display a 'proceed, expect proceed' aspect if the 'signalling conditions' for the block signal are satisfied and the next main or block signal is displaying an aspect permitting driving.

Mandatory

FIR-FR694-Com 8.5.2.3 Aspect - Proceed, expect stop

FIR-FR695-Req A block signal shall display a 'proceed, expect stop' aspect if the 'signalling conditions' for the block signal are satisfied and the next main or block signal is displaying a 'stop' aspect.

Mandatory

FIR-FR696-Com 8.6 Locking Signals

FIR-FR697-Com 8.6.1 Locking Signal Aspects

FIR-FR698-Req A locking signal aspect shall be controlled only by the state of the lockable device. Mandatory

FIR-FR699-Com 8.6.1.1 Aspect - Stop




FIR-FR700-Req A locking signal shall display a 'stop' aspect unless the conditions for 'no aspects' aspect for a locking signal are satisfied.

Mandatory

FIR-FR701-Com 8.6.1.2 Aspect - No aspects

FIR-FR702-Req Locking signal has to display 'No aspects' aspect, if one of the following conditions is satisfied: Mandatory FIR-FR703-Req a swing bridge is locked for railway traffic Mandatory

FIR-FR704-Req a device equipped with a locking signal is controllably in a position where it does not prevent the traffic

movements on the track. Mandatory

FIR-FR705-Com 8.7 Level Crossing Signals

FIR-FR706-Com 8.7.1 Level Crossing Signal Aspects

FIR-FR707-Req A level crossing signal aspect shall be controlled only by the state of the level crossing. Mandatory

FIR-FR708-Com 8.7.1.1 Aspect - Approach with caution

FIR-FR709-Req A level crossing signal shall display an 'Approach with caution' aspect unless the conditions for a 'no aspects' aspect for a level crossing signal are satisfied.

Mandatory

FIR-FR710-Com 8.7.1.2 Aspect - No aspects

FIR-FR711-Req The level crossing signal must display a 'no aspects' aspect, if all the following conditions are satisfied: Mandatory FIR-FR712-Req a level crossing system has given an alarm for a required time period Mandatory FIR-FR713-Req level crossing system has no critical faults Mandatory

FIR-FR714-Com 8.8 Radio Signal

FIR-FR715-Req From the radio signal state information, the corresponding information about the main signal ’Stop’ aspect and the necessary aspects permitting driving shall be transmitted to the radio signal balises

Mandatory

FIR-FR716-Req The state information of the radio signal transmitted to the balises shall meet the requirements of a main signal aspect. Mandatory

FIR-FR717-Req A radio signal can provide flank protection when the information corresponding to the main signal ‘Stop’ aspect is transmitted to the balises of the radio signal.

Mandatory

FIR-FR1732-Com 8.9 Combined signal




FIR-FR1733-DK

A combined signal can act as main route entry signal, shunting route entry signal, signal associated with a local point operation group, distant signal, signal providing only flank protection and/or a combination of the previous.

FIR-FR1734-DK

The combined signal acting as main route entry signal must display 'Proceed 35' aspect, when the signal is the entry signal of a set main route, the aspect of the route entry signal in question is determined to be 'Proceed 35' and the route monitoring conditions are fulfilled.

Mandatory

FIR-FR1735-Req

The combined signal acting as main route entry signal must display 'Proceed' aspect, when the signal is the entry signal of a set main route, the aspect of the route entry signal in question is determined to be 'Proceed' and the route monitoring conditions are fulfilled.

Mandatory

FIR-FR1736-Req

The combined signal acting as shunting route entry signal must display 'Proceed with caution', when the signal is the entry signal of a set shunting route and the route monitoring conditions are fulfilled, or when the signal is situated between the main route entry and exit signals of a set main route and the route monitoring conditions are fulfilled.

Mandatory

FIR-FR1737-Req The combined signal acting as distant signal must display 'Expect stop', 'Expect proceed 35' or 'Expect proceed' aspect, when the signal is acting only as a distant signal.

Mandatory

FIR-FR1738-Req The combined signal acting as distant signal must display 'Expect stop', 'Expect proceed 35' or 'Expert proceed' aspect, when the signal is also a main route entry signal and the signal displays 'Proceed 35' or 'Proceed' aspect.

Mandatory

FIR-FR1739-Req The distant signal aspect must be the same as the aspect of the next main route entry signal. Mandatory

FIR-FR1740-Req The combined signal must display 'No aspects', when the track sections in rear and in advance of the signal are associated with a local point operation group, which has the local point operation permission given.

Mandatory

FIR-FR1741-Req The combined signal must display 'Stop' aspect , when the requirements given above for displaying a drive permitting aspect or 'No aspects' aspect are not fulfilled and when the signal is not giving only distant signal information.

Mandatory

FIR-FR1742-Com 8.9.1 Conditions for drive permitting aspect

FIR_FR1743-Com 8.9.1.1 Conditions for drive permitting aspect of a main route

FIR-FR1744-Req The conditions for the drive permitting aspect of the main route entry signal are fulfilled, if all the following conditions are fuilfilled:

Mandatory

FIR-FR1745-Req the route is set according to the main route conditions Mandatory FIR-FR1746-Req the monitoring conditions of the route started by the signal are fulfilled Mandatory FIR-FR1747-Req the signal is not set to display 'stop' aspect Mandatory

FIR-FR1748- Req the traffic controller has not the signal to display 'stop' aspect by giving Stop-command and the Proceed-

command has not been given after that.. Mandatory

FIR-FR1749-Req The traffic controller must be able to cancel the Stop-command by giving the Proceed-command. Mandatory




FIR-FR1750-Com 8.9.1.2 Conditions for drive permitting aspect of a shunting route

FIR-FR1751-Req The conditions for the drive permitting aspect of the shunting route entry signal are fulfilled, if all the following conditions are fuilfilled:

Mandatory

FIR-FR1752-Req the route is set according to the shunting route conditions Mandatory FIR-FR1753-Req the monitoring conditions of the 'proceed with caution' aspect are fulfilled Mandatory FIR-FR1754-Req the signal is not set to display 'stop' aspect Mandatory

FIR-FR1755-Req the traffic controller has not the signal to display 'stop' aspect by giving Stop-command and the Proceed-

command has not been given after that Mandatory

FIR-FR1756-Req The traffic controller must be able to cancel the Stop-command by giving the Proceed-command. Mandatory

FIR-FR1757-Com

8.9.1.3 Conditions for drive permitting aspect of a signal protecting a block section on the line

FIR-FR1758-Req Conditions for drive permitting aspect of a signal protecting a block section are fulfilled, if all the following conditions are fulfilled:

Mandatory

FIR-FR1759-Req

the track sections became occupied and vacant in the correct sequence to a block section set earlier, from a block section to the next one or to the side track of the line point, if the point was in the position leading away from the line

Mandatory

FIR-FR1760-Req the block section exit signal displayed 'proceed' aspect, when the previous train was on the block section Mandatory

FIR-FR1761-Req the track sections of a block section became occupied in the correct sequence according to the block travel

direction, if there are several track sections in the block section Mandatory

FIR-FR1762-Req the track sections in the block section are vacant Mandatory FIR-FR1763-Req the signal is not blocked Mandatory FIR-FR1764-Req the block section exit signal is not 'dark' Mandatory FIR-FR1765-Req the line points in the block section are monitored in the positions required by the route Mandatory FIR-FR1766-Req the lockable devices in the block section are monitored in the position enabling the traffic Mandatory FIR-FR1767-Req the monitoring equipments in the block section are monitored in the state enabling the traffic Mandatory FIR-FR1768-Req the monitoring conditions of the level crossing systems in the block section are fulfilled Mandatory

FIR-FR1769-Req the track sections belonging to the overlap according to the block travel direction are vacant (if the overlap is

determined) Mandatory

FIR-FR1770-Req the line traffic direction is the same as the block travel direction of the set block section Mandatory




FIR-FR1771-Req The line signal must set immediately to display 'stop' aspect, if the conditions of the drive permitting aspect of the signal are not fulfilled

Mandatory

FIR-FR1772-Req The line signals belonging to the automatic block system, which protect the line section, must function automatically according to the conditions of the drive permitting aspect.

Mandatory

FIR-FR1773-Req The line signals belonging the route initiated block system must: Mandatory

FIR-FR1774-Req function automatically according th the conditions of the drive permitting aspect, when the route is set to the

line Mandatory

FIR-FR1775-Req function automatically according th the conditions of the drive permitting aspect, when a route is set from the

line point to the line Mandatory

FIR-FR1776-Req display 'stop' aspect, when the route is not set Mandatory

FIR-FR1777-Req The line signals belonging to the route initiated block system must display 'stop' aspect after a unit, until setting of a new route enables the functioning of the signals.

Mandatory

FIR-FR1778-Req In the route initiated block system the cancelling of the route set to the line must set the line signals, which are between the railway operating locations and behind of the previous unit, to display 'stop' aspect.

Mandatory

FIR-FR718-Com 8.10 Signal Blocking

FIR-FR719-Req The interlocking system shall be able to block the block section entry signals in a block system controlled by interlocking system.

Mandatory

FIR-FR720-Req A block section entry signal in a block system shall be 'blocked' if a request 'Block signal' is received from the signaller

Mandatory

FIR-FR721-Req If a signal is 'blocked', it shall: Mandatory FIR-FR722-Req be set to a 'stop' aspect Mandatory FIR-FR723-Req maintain displaying a 'stop' aspect regardless of its 'signalling conditions' Mandatory FIR-FR724-Req A signal shall become not 'blocked' if a request 'Unblock signal' is received from the signaller. Mandatory

FIR-FR725-Req If a signal becomes not 'blocked', it shall maintain displaying a 'stop' aspect unless the 'signalling conditions' for the signal are satisfied.

Mandatory

FIR-FR726-Com 8.11 Signal Supervision

FIR-FR727-Req The interlocking system shall supervise the signal lamps and LED units on: Mandatory FIR-FR728-Req main signals Mandatory FIR-FR1779-Req combined signals Mandatory FIR-FR729-Req shunting signals Mandatory FIR-FR730-Req block signals Mandatory



Requirement Finland - Priority FIR-FR731-Req distant signals Mandatory

FIR-FR732-Req The interlocking system shall detect signal failure (e.g., short circuits, broken wires, earth leakage, external voltage present).

Mandatory

FIR-FR733-Req A signal shall be assigned as 'failed' if one of the conditions is satisfied: Mandatory FIR-FR734-Req a signal lamp or a LED-unit of the signal is defective Mandatory FIR-FR735-Req signal failure information is detected (short circuits, broken wires, earth leakage, external voltage present) Mandatory FIR-FR736-Req A 'failed' signal shall be indicated to the signaller with the following information: Mandatory FIR-FR737-Req the signal number information Mandatory FIR-FR738-Req the lamp or LED unit information, if the signal is 'failed' due to defective signal lamp Mandatory

FIR-FR739-Req If the signal lamp is lit with an auxiliary filament while the main filament is defective, an indication 'Filament failure' shall be indicated to the signaller.

Mandatory

FIR-FR740-Req A signal shall be assigned as 'dark' if a signal lamp or a LED-unit of the 'stop' aspect is defective while the signal is set to display a 'stop' aspect.

Mandatory

FIR-FR741-Req If a signal is 'dark': Mandatory FIR-FR742-Req the signal is not able to provide flank protection to a route Mandatory FIR-FR743-Req the signal is not able to provide flank protection to a local point operation group Mandatory FIR-FR744-Req the signal is not able to function as a route exit signal Mandatory FIR-FR1808-Req the signal is not able to function as a route entry signal

FIR-FR745-Req If a signal lamp or a LED-unit of an aspect permitting driving becomes defective on a main signal while the signal is displaying an aspect permitting driving, all the following actions shall be done:

Mandatory

FIR-FR746-Req the signal shall be set to a 'stop' aspect Mandatory FIR-FR747-Req the shunting signal associated with the main signal shall be set to a 'stop' aspect Mandatory

FIR-FR748-Req If a signal lamp or a LED-unit of an aspect permitting driving becomes defective on a block signal while the signal is displaying an aspect permitting driving, the signal shall be set to a 'stop' aspect.

Mandatory

FIR-FR749-Req If a signal lamp of the 'expect proceed' or 'expect proceed 35' aspect becomes defective on a distant signal while the signal is displaying an 'expect proceed' or 'expect proceed 35' aspect, the signal shall be set to an 'expect stop' aspect.

Mandatory

FIR-FR750-Req If a signal lamp or a LED-unit of the 'expect stop' aspect becomes defective on a distant signal in a separate mast while the signal is displaying an 'expect stop' aspect, the main signal in rear shall be set to a 'stop' aspect.

Mandatory

FIR-FR751-Req

If a signal lamp or a LED-unit of the 'expect stop' aspect becomes defective on a distant signal in the same mast with a main signal while the signal is displaying an 'expect stop' aspect, the main signal in the same mast shall be set to a 'stop' aspect.

Mandatory

FIR-FR752-Req If a signal lamp or a LED-unit of a 'proceed with caution' aspect becomes defective on a shunting signal while the signal is displaying a 'proceed with caution' aspect, all the following actions shall be done:

Mandatory

FIR-FR753-Req the signal shall be set to a 'stop' aspect Mandatory



Requirement Finland - Priority FIR-FR754-Req the main signal associated with the shunting signal shall be set to a 'stop' aspect Mandatory

FIR-FR755-Req If a shunting signal lamp or a LED-unit of the 'no aspects' aspect becomes defective while the signal is displaying a 'no aspects' aspect, the shunting signal shall be set to a 'stop' aspect.

Mandatory

FIR-FR756-Req

If a defective shunting signal lamp or a LED-unit of the 'no aspects' aspect becomes corrected while the monitoring conditions of the formed local permission area are not disturbed, the signal shall automatically display a 'no aspects' aspect

Optional

FIR-FR757-Req If a defective shunting signal lamp or a LED-unit of a 'proceed with caution' aspect becomes corrected while the 'signalling conditions' for the shunting signal are satisfied, all the following actions shall be done:

Mandatory

FIR-FR758-Req the signal shall be upgraded if a request 'Reclear signal' is received from the signaller Mandatory

FIR-FR759-Req the signal shall automatically display a 'proceed with caution' aspect Optional to FIR-FR758-

Req

FIR-FR760-Req the shunting signal associated with the main signal shall display a 'proceed with caution' aspect when the

main signal displays the 'proceed' aspect Mandatory

FIR-FR761-Req the main signal associated with the shunting signal shall display a 'proceed' aspect when the shunting

signal displays the 'proceed with caution' aspect Mandatory

FIR-FR1780-Req

If the LED-unit of a combined signal, needed to display 'proceed' or 'proceed 35' aspects, breaks down when the combined signal is displaying 'proceed'or 'proceed 35' aspect, the signal must be set to display 'stop' aspect.

Mandatory

FIR-FR1781-Req

If the LED-unit of a combined signal, needed to display 'expect proceed' or expect proceed 35' aspects, breaks down when the combined signal is displaying 'expect proceed 'or 'expect proceed 35' aspect, the signal must be set to display 'expect stop' aspect

Mandatory

FIR-FR1782-Req

If the LED-unit of a combined signal acting only as distant signal, needed to display 'expect stop' aspect, breaks down when the combined signal is displaying 'expect stop' aspect, the signal in rear must be set to display 'stop' aspect

Mandatory

FIR-FR1783-Req

If the LED-unit of a combined signal acting as main route entry signal, needed to display 'expect stop' aspect, breaks down when the combined signal is displaying 'expect stop' aspect, the signal must be set to display 'stop' aspect

Mandatory

FIR-FR1784-Req

If the LED-unit of a combined signal, needed to display 'proceed with caution' aspect, breaks down when the combined signal is displaying 'proceed with caution' aspect, the signal must be set to display 'stop' aspect.

Mandatory

FIR-FR1785-Req

If the LED-unit of a combined signal, needed to display 'no aspects' aspect, breaks down when the combined signal is displaying 'no aspects' aspect, the signal must be set to display 'stop' aspect.

Mandatory

FIR-FR1786-Req

If the LED-unit of a combined signal, needed to display 'no aspects' aspect, which has been in faulty state recovers and it belongs to a local point operation permission group with the permission given and the local point operation conditions in force, the combined signal must automatically return to display 'no aspects' aspect.

Mandatory

FIR-FR1787-Req

If the LED-unit of a combined signal, needed to display 'proceed with caution' aspect, which has been in faulty state recovers and the conditions for drive permitting aspect are in force, all the following actions must be done:

Mandatory



Requirement Finland - Priority FIR-FR1788-Req

it must be possible to set the signal to display drive permitting aspect, if the traffic control has given a command to set the aspect

Mandatory

FIR-FR1789-Req

the signal must autotically set to display 'proceed with caution' aspect Optional with requirement FIR-FR1788-Req

FIR-FR762-Com 8.12 Setting Signals to 'Stop' Aspect by Request

FIR-FR763-Req The interlocking system shall be able to set to a 'stop' aspect upon request: Mandatory FIR-FR764-Req main signals Mandatory FIR-FR1790-Req combined signals, which can display 'stop' aspect Mandatory FIR-FR765-Req shunting signals Mandatory FIR-FR766-Req A signal shall be set to a 'stop' aspect immediately if a request 'Set signal to stop' is received from the signaller. Mandatory

FIR-FR767-Req If the route entry signal of a main route is set to a 'stop' aspect by the signaller, all sub-route signals, able to display 'stop' aspect and belonging to the route, shall be set to a 'stop' aspect.

Mandatory

FIR-FR768-Req If a sub-route signal in a main route is set to a 'stop' aspect by the signaller, all sub-route signals able to display 'stop' aspect and the route entry signal of that route shall be set to a 'stop' aspect.

Mandatory

FIR-FR769-Req If the route entry signal of a main route is set to a 'stop' aspect by the signaller, the signal shall be maintained at a 'stop' aspect for the remainder of the route life cycle, unless all the following conditions are satisfied:

Mandatory

FIR-FR770-Req a request 'Reclear signal' is received from the signaller Mandatory FIR-FR771-Req the 'signalling conditions' for the signal are satisfied Mandatory

FIR-FR772-Req

If a signal included in a main route, able to display 'stop' aspect, is set to a 'stop' aspect by the signaller, the signal shall be maintained at a 'stop' aspect for the remainder of the route life cycle, unless all the following conditions are satisfied:

Mandatory

FIR-FR773-Req a request 'Reclear signal' is received from the signaller for the route entry signal Mandatory FIR-FR774-Req the 'signalling conditions' for the signal are satisfied Mandatory

FIR-FR775-Req If the route entry signal of a shunting route is set to a 'stop' aspect by the signaller, the signal shall be maintained at a 'stop' aspect for the remainder of the route life cycle, unless all the following conditions are satisfied:

Mandatory

FIR-FR776-Req a request 'Reclear signal' is received from the signaller Mandatory FIR-FR777-Req the 'signalling conditions' for the signal are satisfied Mandatory

FIR-FR778-Req If a signal displaying a 'no aspects' aspect is set to a 'stop' aspect by the signaller, the signal shall be maintained at a 'stop' aspect unless all the following conditions are satisfied:

Mandatory

FIR-FR779-Req a request 'Set signal to 'no aspects' is received from the signaller Mandatory




FIR-FR780-Req the signal is included in local point operation permission group that has local point operation permission

given Mandatory

FIR-FR781-Req the monitoring conditions of the local permission are not disturbed Mandatory

FIR-FR782-Com 9 Powered Moveable Element


FIR-FR784-Req The interlocking system shall be able to control the following powered moveable elements: Mandatory FIR-FR785-Req points Mandatory FIR-FR786-Req derailers Mandatory FIR-FR1791-Req stopping device Mandatory FIR-FR787-Req The end positions of a powered point are: Mandatory FIR-FR788-Req 'left' position when the traffic can move over the left branch of the point Mandatory FIR-FR789-Req 'right' position when the traffic can move over the right branch of the point Mandatory FIR-FR790-Req The end positions of a powered derailer and stopping device are: Mandatory FIR-FR791-Req 'on rail' position when the derailer or stopping device prevents the movement of traffic Mandatory FIR-FR792-Req 'off rail' position when the derailer or stopping device permits the movement of traffic Mandatory FIR-FR793-Req Each powered moveable element shall have an individual operation timer. Mandatory FIR-FR794-Req The position monitoring of powered moveable elements shall be continuously supervised. Mandatory FIR-FR795-Req A powered moveable element shall be assigned as 'monitored' if all the following conditions are satisfied: Mandatory FIR-FR796-Req the end position of the element is monitored Mandatory FIR-FR797-Req the end position corresponds with the requested position Mandatory FIR-FR798-Req A powered moveable element shall be assigned as 'failed' if one of the conditions exists: Mandatory

FIR-FR799-Req the element was requested to move and it did not reach its monitored end position before the operation

timer of 10 seconds expired Mandatory

FIR-FR800-Req the element is monitored in an end position not corresponding with the requested position Mandatory FIR-FR801-Req the element is not monitored in an end position while the element was not requested to move Mandatory FIR-FR802-Req An alarm shall be indicated to the signaller if the operation timer expired without monitored end position. Mandatory

FIR-FR803-Req If the track section the element is included in, becomes 'occupied' while the element is moving, the element shall continue its movement.

Mandatory

FIR-FR804-Req A powered moveable element shall be reversed if the element is requested to move while the element is moving. Mandatory




FIR-FR805-Req Simultaneous requests for movement of powered moveable elements shall be handled with a minimum delay of 50 msec and a maximum delay of 100 msec between the movements of each element.

Mandatory

FIR-FR806-Com 9.2 Movement Request

FIR-FR807-Com 9.2.1 Automatic Operation

FIR-FR808-Req A powered moveable element shall be requested to move by 'automatic operation' if all the following conditions are satisfied:

Mandatory

FIR-FR809-Req the setting of a route requires the movement of the element to the requested position Mandatory

FIR-FR810-Req the setting of a local point operation permission requires the movement of the element to the requested

position Mandatory

FIR-FR811-Req A powered moveable element shall be moved by 'automatic operation' if all the following conditions are satisfied: Mandatory FIR-FR812-Req 'automatic operation' is not disabled Mandatory FIR-FR813-Req the element's associated track section is not 'occupied' Mandatory FIR-FR814-Req the element is not being used in a route Mandatory FIR-FR815-Req the element is not locked by a local point operation permission Mandatory FIR-FR816-Req the element is not locked for flank protection Mandatory FIR-FR817-Req the element is not 'blocked' Mandatory FIR-FR818-Req the element is not 'trailed' Mandatory

FIR-FR819-Com 9.2.1.1 Disabling Automatic Operation

FIR-FR820-Req 'Automatic operation' shall be disabled if a request 'Disable automatic operation of moveable elements' is received from the signaller.

Mandatory

FIR-FR821-Req The movement of a powered moveable element by 'automatic operation' shall be prevented while 'automatic operation' is disabled.

Mandatory

FIR-FR822-Req The movement of a powered moveable element by 'individual operation' shall be permitted while 'automatic operation' is disabled.

Mandatory

FIR-FR823-Req 'Automatic operation' shall be restored if a request 'Enable automatic operation of moveable elements' is received from the signaller.

Mandatory

FIR-FR824-Com 9.2.1.2 Selective Protection Point




FIR-FR825-Req The interlocking system shall be able to automatically reassign flank protection provided by a selective protection point.

Mandatory

FIR-FR826-Req Reassignment of flank protection shall not disturb the monitoring conditions. Mandatory

FIR-FR827-Req If the flank protection request for a selective protection point would require its movement while it is 'blocked', that flank protection request shall be transferred to the next alternative flank protection element.

Mandatory

FIR-FR828-Req A second request for flank protection for a point configured as selective protection point shall not be rejected if one of the following condtions is satisfied:

Mandatory

FIR-FR829-Req the point is already locked for flank protection to a route Mandatory

FIR-FR830-Req the point is already locked for flank protection to a local point operation group that has local operation

permission given Mandatory

FIR-FR831-Req If the second request for flank protection for a point configured as selective protection point is accepted: Mandatory FIR-FR832-Req the second request shall be transferred to an alternative flank protection element Mandatory FIR-FR833-Req the selective protection point shall remain locked for the original flank protection request Mandatory

FIR-FR834-Req If the selective protection point becomes available for flank protection while its alternative element is providing flank protection, the flank protection shall be transferred to the selective protection point.

Mandatory

FIR-FR835-Req The flank protection shall be transferred from the alternative element to the selective protection point only when the selective protection point starts providing the protection.

Mandatory

FIR-FR836-Com 9.2.2 Individual operation

FIR-FR837-Req Powered moveable element shall be requested to move by 'individual operation' if any of the following requests are received:

Mandatory

FIR-FR838-Req 'Move' request from the signaller Mandatory FIR-FR839-Req 'Move occupied' request from the signaller Mandatory FIR-FR840-Req 'Move trailed' request from the signaller Mandatory FIR-FR841-Req 'Move' request by a local operation button Mandatory

FIR-FR842-Com 9.2.2.1 Individual operation from the Signaller

FIR-FR843-Com 9.2.2.1.1 Move Normal

FIR-FR844-Req A powered moveable element shall be moved by 'individual operation' if all the following conditions are satisfied: Mandatory FIR-FR845-Req a 'Move' request is received from the signaller Mandatory FIR-FR846-Req the element is not locked in a route Mandatory




FIR-FR847-Req the element is not included in a local point operation permission group that has local point operation


FIR-FR848-Req the element is not 'blocked' Mandatory FIR-FR849-Req the element is not 'trailed' Mandatory FIR-FR850-Req the element's track section is not 'occupied' Mandatory

FIR-FR851-Com 9.2.2.1.2 Move Occupied

FIR-FR852-Req A powered moveable element with its associated track section 'occupied' shall be moved by 'individual operation' if all the following conditions are satisfied:

Mandatory

FIR-FR853-Req a 'Move occupied' request is received from the signaller Mandatory FIR-FR854-Req the element is not locked in a route Mandatory



FIR-FR856-Req the element is not 'blocked' Mandatory FIR-FR857-Req the element is not 'trailed' Mandatory FIR-FR858-Req the element's track section is 'occupied' Mandatory

FIR-FR859-Com 9.2.2.1.3 Move Trailed

FIR-FR860-Req A powered moveable element with a 'trailed' status shall be moved by 'individual operation' if all the following conditions are satisfied:

Mandatory

FIR-FR861-Req a 'Move trailed' request is received from the signaller Mandatory FIR-FR862-Req the element is 'trailed' Mandatory FIR-FR863-Req the element is not locked in a route Mandatory



FIR-FR865-Req the element is not 'blocked' Mandatory

FIR-FR866-Com 9.2.2.2 Local Operation by a local operation button

FIR-FR867-Req A powered moveable element shall be moved by 'local operation' by a local operation button if all the following conditions are satisfied:

Mandatory

FIR-FR868-Req the element is released within a local point operation permission Mandatory FIR-FR869-Req a 'Move' request is received by local point operation button continuously for at least for 1 second Mandatory



Requirement Finland - Priority FIR-FR870-Req the element is not 'blocked' Mandatory FIR-FR871-Req the element is not 'trailed' Mandatory

FIR-FR872-Com 9.3 Trailed Status

FIR-FR873-Com 9.3.1 Assigning Trailed Status

FIR-FR874-Req A powered moveable element shall be assigned as 'trailed', if the trailed status is detected from the interface with field elements.

Mandatory

FIR-FR875-Com 9.3.2 Removal of Trailed Status by the Signaller

FIR-FR876-Req A powered moveable element shall become not 'trailed' if all the following conditions are satisfied: Mandatory FIR-FR877-Req the element is moved by 'Turning of a trailed point' request Mandatory FIR-FR878-Req the element is 'monitored' Mandatory FIR-FR879-Req trailed status is not detected from the interface with field elements Mandatory

FIR-FR880-Com 9.4 Blocking Moveable Elements

FIR-FR881-Com 9.4.1 Setting Blocking

FIR-FR882-Req The interlocking system shall be able to block the movement of powered moveable elements by blocking. Mandatory FIR-FR883-Req A powered moveable element shall be 'blocked' if all the following conditions are satisfied: Mandatory FIR-FR884-Req a request 'Set blocking' is received from the signaller Mandatory FIR-FR885-Req the element is not included in a local point operation group that has local point operation permission given Mandatory FIR-FR886-Req Movement of an element shall be prevented while the moveable element is 'blocked'. Mandatory

FIR-FR887-Req A powered moveable element shall continue its movement if the element becomes 'blocked' while the element is moving.

Mandatory

FIR-FR888-Com 9.4.2 Removing Blocking

FIR-FR889-Req A powered moveable element shall become not 'blocked' if all the following conditions are satisfied: Mandatory FIR-FR890-Req a request 'Remove blocking' is received from the signaller Mandatory FIR-FR891-Req the element is not included in a local point operation group that has local point operation permission given Mandatory




FIR-FR892-Com 9.5 Route Blocking

FIR-FR893-Com 9.5.1 Route Blocking

FIR-FR894-Req The interlocking system shall be able to block route setting on a powered point. Mandatory FIR-FR895-Req Route blocking shall be applied to a point if a request 'Route blocking' is received from the signaller. Mandatory FIR-FR896-Req Route setting shall be prevented over both positions while the route blocking is applied on a point in the route. Mandatory FIR-FR897-Req Route blocking shall be removed from a point if a request 'Disabling of route blocking' is received from the signaller. Mandatory

FIR-FR898-Com 9.5.2 Driving of Powered Moveable Element

FIR-FR899-Req The interlocking system shall enable point machine movement until one of the conditions is satisfied: Mandatory FIR-FR900-Req the moveable element becomes 'detected' in the requested position Mandatory FIR-FR901-Req the operation timer has expired Mandatory

FIR-FR902-Req The individual operation timer shall be started when a request for element movement is generated to the interface with field elements.

Mandatory

FIR-FR903-Req If the operation timer expires before the point is locked to its end position, an indication must be provided to the signaller.

Mandatory

FIR-FR904-Req The operation timer shall be restarted if the element is requested to move while the operation time from the previous request is running.

Mandatory

FIR-FR905-Req The interlocking system shall be able to operate a point powered with multiple point machines. Mandatory FIR-FR906-Req The interlocking system shall be able to handle simultaneous requests for movement of powered moveable elements. Mandatory FIR-FR907-Req The interlocking system shall move only one point at a time while the system is running on emergency power. Mandatory

FIR-FR908-Com 9.5.3 Hand Operation

FIR-FR909-Req Powered moveable elements shall be moveable by 'hand operation' with a point handle. Mandatory


FIR-FR911-Req Configuration data for each powered moveable element shall contain: Mandatory FIR-FR912-Req the time of the operation timer Mandatory FIR-FR913-Req the element's track section Mandatory FIR-FR914-Req the point branches that are not free of fouling restrictions Mandatory FIR-FR915-Req the information if the point functions as a selective protection point Mandatory



Requirement Finland - Priority FIR-FR916-Req alternative protection elements for each point position if the point is a selective protection point Mandatory

FIR-FR917-Com 10 Lockable Devices


FIR-FR919-Req The interlocking system shall be able to release and monitor lockable devices. Mandatory FIR-FR920-Req The following devices shall be used as lockable devices: Mandatory FIR-FR921-Req moveable bridge Mandatory FIR-FR922-Req barrier, gate or door that can prevent traffic movements on track Mandatory FIR-FR923-Req loading or unloading device that can prevent traffic movements on track Mandatory FIR-FR924-Req turntable Mandatory FIR-FR925-Req The monitored position of the lockable device shall be monitored. Mandatory FIR-FR926-Req Moveable bridge shall be protected by one of the following: Mandatory FIR-FR927-Req point Mandatory FIR-FR928-Req line main signal Mandatory FIR-FR929-Req block signal Mandatory FIR-FR1792-Req combined signal Mandatory FIR-FR930-Req Lockable device shall be assigned as: Mandatory

FIR-FR931-Req 'in position for traffic' if the supervised position or status in position for traffic movements on track is

detected Mandatory

FIR-FR932-Req not 'in position for traffic' if the supervised position or status in position for traffic movements on track is

not detected Mandatory

FIR-FR933-Req A lockable device shall be assigned as 'failed' if all the following conditions are satisfied: Mandatory FIR-FR934-Req the lockable device is not 'released' Mandatory FIR-FR935-Req the lockable device is not 'in position for traffic' Mandatory FIR-FR936-Req The following states of moveable bridge shall be indicated to signaller: Mandatory FIR-FR937-Req locked in position for traffic Mandatory FIR-FR938-Req released for use Mandatory

FIR-FR939-Com 10.2 Blocking Lockable Devices

FIR-FR940-Req The interlocking system shall be able to block lockable devices. Mandatory FIR-FR941-Req A lockable device shall be 'blocked' if a request 'Set blocking' is received from the signaller. Mandatory



Requirement Finland - Priority FIR-FR942-Req The release of the lockable device shall be prevented while the lockable device is 'blocked'. Mandatory FIR-FR943-Req A lockable device shall become not 'blocked' if a request 'Remove blocking' is received from the signaller. Mandatory

FIR-FR944-Com 10.3 Operation of Lockable Devices

FIR-FR945-Req 10.3.1 Release

FIR-FR946-Req A lockable device shall be 'released' if all of the following conditions are satisfied: Mandatory FIR-FR947-Req a request 'Release lockable device' is received from the signaller Mandatory FIR-FR948-Req the lockable device is not being used by a route Mandatory FIR-FR949-Req the lockable device is not 'blocked' Mandatory

FIR-FR950-Com 10.3.2 Release of Lockable Devices on the Line

FIR-FR951-Req The release of a lockable device located on the line shall be permitted if all the following conditions are satisfied: Mandatory FIR-FR952-Req a request 'Release lockable device' is received from the signaller Mandatory FIR-FR953-Req route is not set to the line so that the block section of the lockable device is set Mandatory FIR-FR954-Req the corresponding line block is not 'failed' Mandatory FIR-FR955-Req the lockable device is not 'blocked' Mandatory

FIR-FR956-Req The emergency release of a lockable device located on the line shall be permitted, if a request 'Emergency release lockable device' is received from the signaller.

Mandatory

FIR-FR957-Req If release of lockable device is permitted, all the following actions shall be done: Mandatory FIR-FR958-Req time delay of 60 s for releasing the lockable device shall be started Mandatory FIR-FR959-Req the protecting signals of the lockable device shall controlled to display a 'stop' aspect Mandatory FIR-FR960-Req protecting point of the lockable device shall be locked to the required position Mandatory FIR-FR961-Req A lockable device located in a block section shall be 'released' if all the following conditions are satisfied: Mandatory FIR-FR962-Req the release of the lockable device is permitted Mandatory FIR-FR963-Req the protecting signals of the lockable device are displaying a 'stop' aspect Mandatory FIR-FR964-Req track sections between the protecting signals of the lockable device are not occupied Mandatory FIR-FR965-Req protecting point of the lockable device is locked to the required position Mandatory FIR-FR966-Req time delay for releasing the lockable device has expired Mandatory

FIR-FR971-Com 10.3.3 Release Withdrawal

FIR-FR972-Req A 'released' lockable device shall become not 'released' in its basic state if any of the following conditions are satisfied: Mandatory



Requirement Finland - Priority FIR-FR973-Req a request 'Cancel lockable device release' is received from the signaller Mandatory FIR-FR974-Req a request 'Cancel lockable device release' is received from the lockable device return button Mandatory FIR-FR975-Req the lockable device becomes detected 'in position for traffic' after use Mandatory

FIR-FR976-Com 11 Key-Locked Devices


FIR-FR978-Req The interlocking system shall be able to release and supervise the following key-locked moveable elements: Mandatory FIR-FR979-Req points Mandatory FIR-FR980-Req derailers Mandatory FIR-FR1793-Req stopping devices Mandatory FIR-FR981-Req The position of a key-locked point on a route track shall be monitored with point detector. Mandatory

FIR-FR982-DK An end position status of a key-locked element from an end position detector can be integrated in the status of the key as 'in place'.

Optional

FIR-FR983-Req The operation key of a key lock shall be locked in its basic state to one of the following: Mandatory FIR-FR984-Req another key lock Mandatory FIR-FR985-Req double key lock Mandatory FIR-FR986-Req key box Mandatory

FIR-FR987-Req The operation keys of key-locked elements shall be linked so that the state of all derailers or stopping devices can be monitored, if more than one derailer or stopping device is protecting route track.

Mandatory

FIR-FR988-Req Operation key of a point on a route track shall be locked in its basic state to one of the following: Mandatory FIR-FR989-Req double key lock of the point protecting route track Mandatory FIR-FR990-Req one key lock of the derailer or stopping device protecting route track Mandatory FIR-FR991-Req Operation key of a point that is not on a route track shall be locked in its basic state to a key box. Mandatory

FIR-FR992-Req Operation key of a derailer or stopping device that is not on a route track shall be locked in its basic state to one of the following:

Mandatory

FIR-FR993-Req key box Mandatory FIR-FR994-Req key lock of a linked derailer Mandatory FIR-FR995-Req The removal of the key from the key box shall be enabled only while key-locked moveable element is 'released'. Mandatory FIR-FR996-Req The status of the operation key of a key-locked moveable element shall be continuously monitored. Mandatory FIR-FR997-Req The operation key of a key-locked moveable element shall be monitored as: Mandatory FIR-FR998-Req ‘in place’ if the key is detected in its key box Mandatory



Requirement Finland - Priority FIR-FR999-Req not ‘in place’ if the key is not detected in its key box Mandatory FIR-FR1000-Req The position of a key-locked moveable element shall be continuously monitored, if a point detector is used. Mandatory

FIR-FR1001-Req A key-locked moveable element shall be assigned as 'monitored' in basic state if all the following conditions are satisfied:

Mandatory

FIR-FR1002-Req the element is not 'released' Mandatory FIR-FR1003-Req the element is not included in a local point operation group that has local point operation permission given Mandatory FIR-FR1004-Req the corresponding operation key is monitored 'in place' Mandatory FIR-FR1005-Req the end position of basic state of the element is monitored, if a point detector is used Mandatory

FIR-FR1006-Req A key-locked moveable derailer or stopping device shall be equipped with two key locks, one for locking the derailer or stopping device 'on rail' and the other for locking the derailer or stopping device 'off rail'.

Mandatory

FIR-FR1007-Req A key-locked moveable element shall be assigned as 'failed' while the element is not released and one of the conditions is satisfied:

Mandatory

FIR-FR1008-Req the end position of the element is not detected, if point detector is used Mandatory FIR-FR1009-Req the operation key corresponding to the end position is detected not 'in place' Mandatory FIR-FR1010-Req Key box shall be placed: Mandatory FIR-FR1011-Req as close to the element the operation key of which is monitored by the key box Mandatory FIR-FR1012-Req to a place from where the distance to the monitored element is maximum 100m Mandatory

FIR-FR1013-Req to a place from where the distance to the return button of the associated local point operation group is

maximum 100m Mandatory

FIR-FR1014-Req to a lockable box Mandatory

FIR-FR1015-Com 11.2 Line point

FIR-FR1016-Req The release delay timer for releasing key of the line point with an individual request shall be 60 seconds. Mandatory FIR-FR1017-Req The release delay timer for releasing key of the line point with a route request shall be 60 seconds. Mandatory

FIR-FR1018-Req Route set to a line point shall include the conditions and actions required to release the line point in addition to normal route conditions.

Mandatory

FIR-FR1019-Com 11.3 Operation

FIR-FR1020-Com 11.3.1 Basic state

FIR-FR1021-Req A key-locked moveable element shall be in basic state, when the element is 'monitored' in an end position. Mandatory FIR-FR1022-Req A key-locked deraileror stopping device shall be in basic state, when the derailer is locked on rail. Mandatory




FIR-FR1023-Com 11.3.2 Release

FIR-FR1024-Req A key-locked moveable element except line point shall be 'released' if all the following conditions are satisfied: Mandatory

FIR-FR1025-Req a request for giving key box permission is received from the signaller or local point operation permission

is given to the local point operation group the element is included in Mandatory

FIR-FR1026-Req the element is not being used in a route or overlap Mandatory

FIR-FR1027-Req the element is included in a track section that is not in advance of route exit signal of a route set with 0

overlap Mandatory

FIR-FR1028-Com 11.3.2.1 Release of Line Point

FIR-FR1029-Req The release of line point shall be initiated, if the request to release line point is given by signaller. Mandatory FIR-FR1030-Req The initiation of releasing a line point includes the following actions: Mandatory FIR-FR1031-Req line point protecting signals are set to 'stop' aspect Mandatory FIR-FR1032-Req the reversing of the block travel direction shall be prevented Mandatory FIR-FR1033-Req the release delay timer (60s) shall be started Mandatory

FIR-FR1034-Req The delay time for the key box permission shall be started after the key box permission command has been given, if all the following conditions are satisfied:

Mandatory

FIR-FR1035-Req the line is not in a faulty state Mandatory

FIR-FR1036-Req there is no set route from the station exit signal to the line, when the line point is located on the first block

section with respect to the block travel direction Mandatory

FIR-FR1037-Req

the track sections of the line between the signal protecting the line point and the line point are not occupied when viewed according to the block travel direction when the track section of the line point is not occupied

Mandatory

FIR-FR1038-Com 11.3.2.2 Interruption of Key Box Permission for Line Point

FIR-FR1039-Req The giving of key box permission to line point must be interrupted if one of the following conditions is fulfilled during the delay time:

Mandatory

FIR-FR1040-Req the line in a faulty state Mandatory

FIR-FR1041-Req a route is set from the station exit signal to the line, when the line point is located on the first block section

with respect to the block travel direction Mandatory

FIR-FR1042-Req

a not occupied track section between the line point and the line point protecting signal becomes occupied, viewed from the block travel direction when the line point track section was not occupied as the delay time started

Mandatory



Requirement Finland - Priority FIR-FR1043-Req Inerruption of giving key box permission to line point shall include the following actions: Mandatory FIR-FR1044-Req line point protecting signals are set to the aspects depending on the fulfilment of the signalling conditions Mandatory FIR-FR1045-Req the reversing of the block travel direction shall be possible, if other conditions are fulfilled Mandatory

FIR-FR1046-Com 11.3.2.3 Key Box Permission for Line Point

FIR-FR1047-Req The key box permission shall be given, if one of the following conditions is satisfied: Mandatory

FIR-FR1048-Req immediately, if the conditions for the key box permission of the line point are fulfilled for the length of the

60s delay time and the key box permission was given by a command Mandatory

FIR-FR1049-Req automatically after the 60s delay time, when the track section of the line point becomes occupied, if the

route has been set by a special command to the line point Mandatory

FIR-FR1050-Com 11.3.2.4 Emergency Key Box Permission for Line Point

FIR-FR1051-Req It must be possible to give key box permission for line point by an emergency command. Mandatory FIR-FR1052-Req The command must bypass the conditions for the key box permission of the line point. Mandatory FIR-FR1053-Req The emergency key box permission of the line point must be given after the 60s delay time. Mandatory

FIR-FR1054-Req 11.4 Area key lock system of the loading area

FIR-FR1055-DK A loading area can be protected by two key-locked derailers located at least 20m distance from each other, preventing traffic movements to and from the loading area, when on the rail.

Mandatory

FIR-FR1056-Req Derailers protecting loading area shall be linked with each other and the loading equipment. Mandatory

FIR-FR1057-Req The key box monitoring the operation key of a derailer of area key lock system of the loading area shall be supervised by interlocking system, if the derailer is protecting route track.

Mandatory


FIR-FR1059-Req Configuration data for each key-locked moveable element shall contain: Mandatory FIR-FR1060-Req end positions applicable for the element Mandatory FIR-FR1061-Req point detectors used Mandatory FIR-FR1062-Req basic state Mandatory FIR-FR1063-Req type of the key lock for the element (key lock, two single key locks or double key lock) Mandatory FIR-FR1064-Req type of the operation key Mandatory FIR-FR1065-Req key lock or key box supervising the operation key Mandatory FIR-FR1066-Req location of the spare key Mandatory



Requirement Finland - Priority FIR-FR1067-Req Configuration data for each line point shall contain: Mandatory

FIR-FR1068-Req the need for setting the routes simultaneously from opposite directions to the line because of the line point

and the respective route exit signals Mandatory

FIR-FR1069-Req track section associated with the line point Mandatory FIR-FR1070-Req Configuration data for each key box shall contain: Mandatory FIR-FR1071-Req location on the railway operating location Mandatory FIR-FR1072-Req type of the operation key the key box is supervising Mandatory

FIR-FR1073-Com 12 Local Point Operation Permission

FIR-FR1074-Com 12.1 Giving a Local point operation permission

FIR-FR1075-Req The interlocking system shall be able to give local point operation permission to a local point operation group. Mandatory FIR-FR1076-Req A local point operation permission shall be initiated if one of the following conditions is satisfied: Mandatory FIR-FR1077-Req a request 'Set local operation permission' is received from the signaller Mandatory FIR-FR1078-Req a request 'Override command for local operation' is received from the signaller Mandatory

FIR-FR1079-Req An attempt to initiate a local point operation permission shall be rejected if any of the following conditions exist at the time of the request:

Mandatory

FIR-FR1080-Req a moveable element included in the proposed local point operation group is being used in a route Mandatory FIR-FR1081-Req a signal associated with the proposed local point operation group is being used in a route Mandatory FIR-FR1082-Req a track section associated with the proposed local point operation group is being used in a route Mandatory

FIR-FR1083-Req the ‘no aspects’ aspect of a signal configured to display 'no aspects' aspect associated with the proposed

local point operation group is defective Mandatory

FIR-FR1084-Req

a moveable element included in the proposed local point operation group is ‘blocked’, unless the request 'Emergency set local point operation permission' has been used to give the local point operation permission

Mandatory

FIR-FR1085-Req a point included in the proposed local point operation group is 'trailed' Mandatory

FIR-FR1086-Req

a track section associated with the proposed local point operation group is 'track blocked', unless the request 'Emergency set local point operation permission' has been used to give the local point operation permission

Mandatory

FIR-FR1087-Req

a moveable element included in the proposed local point operation group has route blocking applied, unless the request 'Emergency set local point operation permission' has been used to give the local point operation permission

Mandatory

FIR-FR1088-Req a local point operation button associated with the proposed local point operation group is 'failed' Mandatory




FIR-FR1089-Req a point included in the local point operation group is included in track section that is in advance of route

exit signal of a route set with 0 overlap Mandatory

FIR-FR1090-Req

If a signal required to provide flank protection to the proposed local point operation group is being used as a route exit signal, the initiation of the local point operation permission shall be permitted, unless the route is set with 0 overlap and the track section in advance of the route exit signal includes a point included in local point operation group.

Mandatory

FIR-FR1091-Req The initiation of a local point operation permission shall consist of: Mandatory FIR-FR1092-Req requesting the movement of required powered moveable elements to the requested positions Mandatory FIR-FR1093-Req locking the required moveable elements in the requested positions Mandatory FIR-FR1094-Req maintaining the required signals for flank protection at a 'stop' aspect Mandatory

FIR-FR1095-Req preventing route requests or local point operation permission requests for use of the elements of the

initiated local point operation group Mandatory

FIR-FR1096-Req If a main signal with an associated shunting signal is in position to provide flank protection, the protection shall be provided by:

Mandatory

FIR-FR1097-Req the main signal displays 'stop' aspect Mandatory FIR-FR1098-Req the shunting signal displays 'stop' aspect Mandatory

FIR-FR1099-Req An initiated local point operation permission shall be given to local point operation group when all the following conditions become satisfied:

Mandatory

FIR-FR1100-Req the moveable elements required to be locked by the local point operation permission are 'locked' in the

requested position Mandatory

FIR-FR1101-Req the moveable elements required to be locked by the local point operation permission are 'detected' in the

requested position Mandatory

FIR-FR1102-Req the signals required to provide flank protection to the local point operation group are displaying a 'stop'

aspect Mandatory

FIR-FR1103-Req Giving a local point operation permission to a local point operation group shall consist of: Mandatory

FIR-FR1104-Req releasing all powered moveable elements within the local point operation group for individual operation

by a local operation button Mandatory

FIR-FR1105-Req disabling the individual operation of all powered moveable elements within the local point operation

group by the signaller Mandatory

FIR-FR1106-Req releasing all key-locked moveable elements within the local point operation group Mandatory

FIR-FR1107-Req disabling the cancellation of the release for all key-locked moveable elements within the local point

operation group by the signaller Mandatory

FIR-FR1108-Req displaying 'no aspects' aspects on all signals associated with the local point operation group Mandatory

FIR-FR1109-Req maintaining all main signals, whether stand-alone or associated with a shunting signal, associated with the

local point operation group at monitored 'stop' aspect Mandatory




FIR-FR1110-Req The release of a powered moveable element for individual operation by a local operation button shall be prevented if the element is 'blocked'.

Mandatory

FIR-FR1111-Req The release of a key-locked moveable element shall be prevented if the element is 'blocked'. Mandatory

FIR-FR1112-Req Giving a local point operation permission to a local point operation group shall not change the 'blocked' status of the moveable elements within the local point operation group.

Mandatory

FIR-FR1114-Req When a 'blocked' key-locked moveable element within a local point operation group with local point operation permission becomes not 'blocked', the element shall be released.

Mandatory

FIR-FR1115-Req A local point operation permission shall not be withdrawn if 'track blocking' is applied to a track section while a local point operation permission is initiated or given.

Mandatory

FIR-FR1116-Req The status of each powered moveable element shall be indicated in the local operation button while the element is released for individual operation by a local operation button.

Mandatory

FIR-FR1117-Com

12.2 Giving Local operation permission to Adjacent/Overlapping Local point operation group

FIR-FR1118-Req The interlocking system shall be able to give local point operation permission to an adjacent or overlapping local point operation group to local point operation group to which has already been given the local point operation permission.

Mandatory

FIR-FR1119-Req Flank protection shall be provided to the entire local point operation group formed by the adjacent or overlapping local point operation groups.

Mandatory

FIR-FR1120-Req Flank protection shall be changed automatically. Mandatory

FIR-FR1121-Req

A point previously locked as flank protection by one local point operation group shall be released as a part of an adjacent or overlapping local point operation group when the flank protection for the entire local point operation group has been provided.

Mandatory

FIR-FR1122-Req

If two or more adjacent or overlapping local point operation groups are simultaneously given local point operation permission, the entire local point operation group formed may include elements, which are not part of any of the individual local point operation groups.

Mandatory

FIR-FR1123-Req Giving a local point operation permission to an adjacent or overlapping local point operation group shall not disturb the monitoring conditions of the local point operation group with local point operation permission given.

Mandatory

FIR-FR1124-Com 12.3 Local point operation permission Monitoring

FIR-FR1125-Req The monitoring conditions for a local point operation group with local point operation permission given are: Mandatory FIR-FR1126-Req the local operation button associated with the local point operation group is not 'failed' Mandatory FIR-FR1127-Req all moveable elements required to be locked by the local point operation group remain 'locked' Mandatory




FIR-FR1128-Req all moveable elements required to be locked by the local point operation group remain 'monitored' in the

required positions Mandatory

FIR-FR1129-Req all signals required to provide flank protection to the local point operation group display monitored 'stop'

aspects Mandatory

FIR-FR1130-Req all moveable elements within an formed local point operation group remain not 'trailed' Mandatory FIR-FR1131-Req all signals associated with the local point operation group display 'no aspects' or 'stop' aspects Mandatory FIR-FR1132-Req If the monitoring conditions of a local point operation permission become disturbed: Mandatory

FIR-FR1133-Req all signals displaying 'no aspects' aspects associated with the local point operation group shall display

'stop' aspects Mandatory

FIR-FR1134-Req individual operation by a local operation button shall be disabled for all powered moveable elements

within the local point operation group Mandatory

FIR-FR1135-Req all key-locked elements within the local point operation group shall become not released Mandatory FIR-FR1136-Req the local point operation permission shall be maintained for the local point operation group Mandatory FIR-FR1137-Req When all the disturbed monitoring conditions of a local point operation permission become reinstated: Mandatory FIR-FR1138-Req all signals associated with the local point operation group shall display 'no aspects' aspects Mandatory

FIR-FR1139-Req individual operation by a local operation button shall be enabled for all powered moveable elements

within the local point operation group Mandatory

FIR-FR1140-Req all key-locked elements within the local point operation group shall be released Mandatory FIR-FR1141-Req Adjacent or overlapping local point operation groups shall be monitored as one local point operation group. Mandatory

FIR-FR1142-Com 12.4 Withdrawing a Local point operation permission

FIR-FR1143-Req An initiation of a local point operation permission to a local point operation group shall be withdrawn if all the following conditions are satisfied:

Mandatory

FIR-FR1144-Req a request 'Withdraw local point operation permission' is received from the signaller Mandatory FIR-FR1145-Req the local point operation permission has not been given Mandatory FIR-FR1146-Req Withdrawn of local point operation permission shall be initiated by any of the following requests: Mandatory FIR-FR1147-Req a request 'Return local point operation permission' is received by a return button Mandatory FIR-FR1148-Req a request 'Withdraw local point operation permission' is received from the signaller Mandatory FIR-FR1149-Req a request 'Emergency withdraw local point operation permission' is received from the signaller Mandatory

FIR-FR1150-Req Request to withdraw local point operation permission by a return button shall be accepted, if the monitoring conditions of the local point operation permission are not disturbed

Mandatory

FIR-FR1151-Req Request to withdraw local point operation permission by a request 'Withdraw local point operation permission' received from the signaller shall be accepted, if all the following conditions are satisfied:

Mandatory




FIR-FR1152-Req individual operation by local operation buttons has not been used after the local point operation

permission has been given Mandatory

FIR-FR1153-Req key-locked elements have not been used after the local point operation permission has been given Mandatory FIR-FR1154-Req the monitoring conditions of the local point operation permission are not disturbed Mandatory

FIR-FR1155-Req Request to withdraw local point operation permission by a request 'Emergency withdrawal of local point operation permission' received from the signaller shall be accepted always.

Mandatory

FIR-FR1156-Req Withdrawing a local point operation permission to the initiated state shall consist of: Mandatory FIR-FR1157-Req displaying 'stop' aspects on all signals associated with the local point operation group Mandatory FIR-FR1158-Req withdrawing the release from all key-locked moveable elements within the local point operation group Mandatory

FIR-FR1159-Req removing the release for individual operation by a local operation button for all powered moveable

elements within the local point operation group Mandatory

FIR-FR1160-Req enabling the individual operation of all powered moveable elements within the local point operation group

by the signaller Mandatory

FIR-FR1161-Req enabling the cancellation of the release by the signaller for all key-locked moveable elements within the

local point operation group Mandatory

FIR-FR1162-Req A local point operation permission returned from formed to initiated state shall be completely withdrawn immediately. Mandatory FIR-FR1163-Req The complete withdrawal of an initiated local point operation permission shall consist of: Mandatory

FIR-FR1164-Req unlocking all elements required to be locked by the local point operation group that has local point

operation permission withdrawn Mandatory

FIR-FR1165-Req enabling route requests or local point operation group requests for use of the local point operation group

that has local point operation permission withdrawn Mandatory

FIR-FR1166-Req maintaining any 'blocked' status of the moveable elements in the local point operation group that has local

point operation permission withdrawn Mandatory

FIR-FR1167-Req maintaining any 'track blocking' status of the track sections in the local point operation group that has

local point operation permission withdrawn Mandatory

FIR-FR1168-Com

12.5 Withdrawing a Local point operation permission from an Adjacent/Overlapping Local point operation group

FIR-FR1169-Req Withdrawal of a local point operation permission from an adjacent or overlapping local point operation group shall be permitted regardless of the order in which it was given.

Mandatory

FIR-FR1170-Req Flank protection shall be provided to the remaining local point operation group formed after the withdrawal of a local point operation permission from an adjacent or overlapping local point operation group.

Mandatory

FIR-FR1171-Req Flank protection shall be changed automatically. Mandatory



Requirement Finland - Priority FIR-FR1172-Req The local point operation permission for the remaining local point operation group shall remain given. Mandatory

FIR-FR1173-Req The monitoring of the local point operation permission for the remaining local point operation group shall remain undisturbed while the flank protection is being changed.

Mandatory

FIR-FR1174-Req

The elements that are not part of any individual local point operation groups and were part of a formed combined local point operation group shall be withdrawn if one of the local point operation groups from the combination has been withdrawn.

Mandatory


FIR-FR1176-Req Engineering configuration requirements for each individual and adjacent or overlapping local point operation group shall contain:

Mandatory

FIR-FR1177-Req the local point operation group identification Mandatory FIR-FR1178-Req the moveable elements within a local point operation group Mandatory FIR-FR1179-Req the signals associated with a local point operation group Mandatory FIR-FR1180-Req the track sections associated with a local point operation group Mandatory FIR-FR1181-Req the moveable elements required to be locked by a local point operation group and their positions Mandatory FIR-FR1182-Req the signals that provide flank protection to a local point operation group Mandatory

FIR-FR1183-Com 13 Line block


FIR-FR1185-DK A line block with multiple block sections shall be able to operate multiple consecutive trains in the block travel direction.

Mandatory

FIR-FR1186-Req The line block shall protect each associated line independently. Mandatory

FIR-FR1187-Req It must be possible to disable the line block conditions manually from the route conditions. Manual disabling can be implemented for example by a specific plug or by the interlocking system.

Mandatory

FIR-FR1189-Req The interlocking system shall be able to operate the following functional line block types: Mandatory FIR-FR1190-Req automatic line block Mandatory

FIR-FR1191-Req route-initiated line block Optional to FIR-FR1190-

Req FIR-FR1192-Req The line block shall have the following directions, relative to an adjacent railway operating location: Mandatory FIR-FR1193-Req outbound Mandatory FIR-FR1194-Req inbound Mandatory



Requirement Finland - Priority FIR-FR1195-Req The line is in a basic state, when: Mandatory FIR-FR1196-Req the track sections of the line are vacant Mandatory FIR-FR1197-Req the direction of the line has not been locked Mandatory FIR-FR1198-Req the line has no set routes Mandatory FIR-FR1199-Req the line is not in a faulty state. Mandatory FIR-FR1200-Req A line shall be assigned as 'failed' if any of the following conditions is satisfied: Mandatory FIR-FR1201-Req the block travel direction is not in correspondence on both adjacent railway operating locations Mandatory

FIR-FR1202-Req any signal in the line is not displaying a monitored aspect (see requirement FIR-FR1251-Req regarding

changing the block travel direction)

FIR-FR1203-Req a line point on the line is 'failed' Mandatory FIR-FR1204-Req a track section in the line block is 'failed' Mandatory FIR-FR1205-Req a track section in the line block is 'out of sequence' Mandatory FIR-FR1206-Req A track section in the line block shall be designated as 'out of sequence' if: Mandatory FIR-FR1207-Req an incorrect occupation of track sections is detected in the line block Mandatory FIR-FR1208-Req a block section exit signal in advance of the track section was passed while displaying a 'stop' aspect Mandatory

FIR-FR1209-Com 13.2 Block Conditions

FIR-FR1210-Req The block conditions are: Mandatory FIR-FR1211-Req The block section must be vacant. Mandatory FIR-FR1212-Req The block travel direction of the line is the same as the direction of the block section. Mandatory

FIR-FR1213-Req The block section and the following block section must become occupied in the sequence according to the

block travel direction. Mandatory

FIR-FR1214-Req The line point on the block section and the key box associated with the block section must be monitored. Mandatory

FIR-FR1215-Req The block section exit signal has been displaying an aspect permitting driving as the track section in advance

of the signal in question has become occupied. Mandatory

FIR-FR1216-Req The signal starting a set block section must be instructed to display a 'Stop' aspect after a 3s delay, when: Mandatory FIR-FR1217-Req the first track section of the block section in advance of the signal becomes occupied Mandatory

FIR-FR1218-Req a fault preventing the display of a ‘Stop' aspect is detected in the signal in advance of the signal starting a

block section Mandatory

FIR-FR1219-Req a fault preventing the display of a ‘Expect stop' aspect is detected in the distant signal or in the combined

signal acting only as distant signal, in advance of the signal starting a block section Mandatory

FIR-FR1220-Req the overlap in advance of the station entry signal, which ends a block section becomes occupied. Mandatory




FIR-FR1221-Req It must be possible to add the vacancy of the track section in advance of the signal ending the block section to the conditions for the aspect permitting driving of the line signal starting a block section or the station exit signal.

Mandatory

FIR-FR1222-Com 13.3 Line block Reset

FIR-FR1223-Req A track section designated as 'out of sequence' shall be set to not 'out of sequence' if a request 'Reset track section sequence' is received from the signaller.

Mandatory

FIR-FR1224-Req A line block shall be reset if all the following conditions are satisfied: Mandatory FIR-FR1225-Req a request 'Reset line block' is received from the signaller Mandatory FIR-FR1226-Req all track sections in the line block are not 'out of sequence' Mandatory FIR-FR1227-Req the line block is 'failed' Mandatory FIR-FR1228-Req The reset of the line block shall consist of: Mandatory FIR-FR1229-Req resetting the line block sequence Mandatory FIR-FR1230-Req maintaining the block travel direction Mandatory

FIR-FR1231-Req permitting the block or line main signals or combined signals in the direction of travel to function

automatically according to the 'signalling conditions', if the line block type is automatic block system Mandatory

FIR-FR1232-Req maintaining all block or line main signals or combined signals at a 'stop' aspect, if the line block type is

route-initiated block system Mandatory

FIR-FR1233-Req It must be possible to return the line to the basic state for the part of the conditions for displaying an aspect permitting driving by an emergency command.

Mandatory

FIR-FR1234-Com 13.4 Block Travel Direction

FIR-FR1235-Req The block travel direction shall be indicated to the signaller. Mandatory

FIR-FR1236-Com 13.4.1 Line block Initialisation

FIR-FR1237-Req If the block travel direction becomes not defined, the block travel direction shall be set to an undefined direction (not inbound and not outbound).

Mandatory

FIR-FR1238-Com 13.4.2 Changing the Block Travel Direction

FIR-FR1239-Req The line block travel direction shall be changed by one of the following conditions: Mandatory FIR-FR1240-Req the setting of a route which requires the use of the line block Mandatory FIR-FR1241-Req a request 'Reverse block travel direction' received from the signaller Mandatory FIR-FR1242-Req The line block travel direction shall be changed if all of the following conditions are satisfied: Mandatory



Requirement Finland - Priority FIR-FR1243-Req all track sections in the line block are not 'occupied' Mandatory FIR-FR1244-Req the block travel direction is not outbound of the station requesting the change Optional

FIR-FR1245-Req an opposing main route has not been locked or is not in the process of being set for the line, if the design

criteria do not require opposing routes to be implemented on the line Mandatory

FIR-FR1247-Req no route is set into the line block Mandatory FIR-FR1248-Req all line points in the line block are 'monitored' in the required position Mandatory FIR-FR1249-Req all lockable devices in the line block are monitored 'in position for traffic' Mandatory FIR-FR1250-Req all monitoring devices in the line block are monitored 'in position for traffic' Mandatory

FIR-FR1251-Req the line is not in a faulty state, unless the line’s faulty state is only caused by the line signal displaying an

unmonitored aspect. Mandatory

FIR-FR1252-Req the line block conditions are not disabled manually with a specific plug from the route conditions Mandatory FIR-FR1253-Req changing of the block travel direction is not 'blocked' Mandatory

FIR-FR1254-Req

the last track section in the railway operating location with outbound direction before the change of the block travel direction is not 'occupied', unless the track section is set as a shunting route and the shunting limit prohibits movement into the line block or the track section is within a local point operation group that has local point operation permission given

Mandatory

FIR-FR1255-Req If a route that requested the change of block travel direction is cancelled, any uncompleted requests for changing the block travel direction shall be removed.

Mandatory

FIR-FR1256-Req The change of the line block travel direction shall consist of: Mandatory

FIR-FR1257-Req setting the block or line main signals or combined signals opposing the requested block travel direction to

a 'stop' aspect Mandatory

FIR-FR1258-Req changing the block travel direction Mandatory

FIR-FR1259-Req permitting the block or line main signalsor combined signals in the new block travel direction to function

automatically according to the 'signalling conditions', if the line block type is automatic block system Mandatory

FIR-FR1260-Req maintaining all block or line main signals or combined signals in the new block travel direction at a 'stop'

aspect, if the line block type is route initiated block system Mandatory

FIR-FR1261-Com 13.4.3 Blocking the Block Travel Direction

FIR-FR1262-Req The interlocking system shall be able to block the changing of the block travel direction. Mandatory FIR-FR1263-Req The block travel direction shall be 'blocked' if all of the following conditions are satisfied: Mandatory FIR-FR1264-Req a request 'Block travel direction blocking' is received from the signaller Mandatory FIR-FR1265-Req the block travel direction is outbound of the railway operating location requesting the blocking Mandatory




FIR-FR1266-Req It must be possible to block the block travel direction outbound from a railway operating location, which has the possibility to disable the line block conditions manually with a specific plug from the route conditions.

Mandatory

FIR-FR1267-Req Changing of the block travel direction shall be prevented while the block travel direction is 'blocked'. Mandatory

FIR-FR1268-Req The block travel direction shall become not 'blocked' if a request 'Travel direction unblocking' is received from the signaller.

Mandatory

FIR-FR1269-Com 13.5 Route Setting into the Line Block

FIR-FR1270-Req If a route set into the line block becomes cancelled, the changing of the line block travel direction shall be permitted when the route is released.

Mandatory

FIR-FR1271-Req The block travel direction shall remain unchanged following the passage of a train. Mandatory

FIR-FR1272-Req Lockable device on line shall prevent the use of the associated block section for the route to the line, if the lockable device is not 'in position for traffic'.

Mandatory


FIR-FR1274-Req Configuration data for each line block shall contain: Mandatory FIR-FR1275-Req the applicable functional line block type Mandatory FIR-FR1276-Req the block sections in the line block Mandatory FIR-FR1277-Req the track sections in each block section Mandatory FIR-FR1278-Req the line points in the line block with the associated track sections Mandatory FIR-FR1279-Req the lockable devices in the line block with the associated track sections Mandatory FIR-FR1280-Req the monitoring devices in the line block with the associated track sections Mandatory

FIR-FR1281-Req line point that requires routes to the line block from opposite directions and the respective block section

exit signals opposing each other Mandatory

FIR-FR1282-Com 14 Level Crossing System Dependent on Interlocking


FIR-FR1284-DK The following diagram displays the use of multiple alarm sections per track, direction and route type.




FIR-FR1285-Diag

level crossing

main

shunting

main

shuntingshunting

main

main

mainRoute to an occupied track

FIR-FR1286-DK The following diagram displays the elements used to determine if occupancy in the alarm section is considered as 'valid for activation'.

FIR-FR1287-Diag

FIR-FR1288-Req The interlocking system shall be able to control and monitor level crossing systems. Mandatory

FIR-FR1289-Req The interlocking system shall have an interface to level crossing system, if a main, line main, combined or shunting signal is on the alarm section protecting level crossing.

Mandatory

FIR-FR1290-Req Type of the level crossing system shall be one of the following: Mandatory FIR-FR1291-Req level crossing barrier system equipped with road signals, alarm bells and full, half or double barriers Mandatory FIR-FR1292-Req level crossing light and audible system equipped with road signals and alarm bells Mandatory FIR-FR1293-Req level crossing light system equipped with road signals Mandatory



Requirement Finland - Priority FIR-FR1294-Req station crossing system equipped with road signals and alarm bells Mandatory FIR-FR1295-Req A level crossing may contain multiple tracks. Mandatory FIR-FR1296-Req A level crossing system may contain multiple alarm sections. Mandatory FIR-FR1297-Req The interlocking system shall monitor and indicate to the signaller: Mandatory FIR-FR1298-Req 'activated' when the level crossing system is activated Mandatory FIR-FR1299-Req action causing the activation Mandatory FIR-FR1300-Req 'secured' when the level crossing system is secured for the road traffic Mandatory FIR-FR1301-Req road signals of the level crossing activated Mandatory FIR-FR1302-Req barriers of the level crossing monitored open Mandatory FIR-FR1303-Req barriers of the level crossing monitored closed Mandatory FIR-FR1304-Req level crossing system operating on backup power Mandatory FIR-FR1305-Req a communication failure between the level crossing system and the interlocking system Mandatory FIR-FR1306-Req a request 'Request activation-all tracks' is given from the level crossing system Mandatory FIR-FR1307-Req level crossing system activated by local switch Mandatory FIR-FR1308-Req 'failed non-critical' when a non-critical failure is present that would not endanger the road traffic Mandatory FIR-FR1309-Req 'failed critical' when a critical failure is present that could endanger the road traffic Mandatory FIR-FR1310-Req track-specific use of the elimination function Mandatory FIR-FR1311-Req blocking for automatic operation Mandatory FIR-FR1312-Req use of the operation switch Mandatory FIR-FR1313-Req use of the substitution switch Mandatory

FIR-FR1314-Com 14.2 States of the level crossing system

FIR-FR1315-Com 14.2.1 Basic state

FIR-FR1316-Req The level crossing system shall not be activated, when the level crossing system is in its basic state. Mandatory FIR-FR1317-Req Other level crossing system than station crossing system shall fulfil all the following conditions in basic state: Mandatory FIR-FR1318-Req barriers shall be in vertical position Mandatory FIR-FR1319-Req road signals shall display a slowly flashing white light Mandatory FIR-FR1320-Req alarm bells shall not ring Mandatory FIR-FR1321-Req Road signals of station crossing system shall not display any lights, when the station crossing system is in basic state. Mandatory

FIR-FR1322-Com 14.2.2 Activation




FIR-FR1323-Req The level crossing system shall be activated so that the required alarm time is satisfied before unit arrives to level crossing.

Mandatory

FIR-FR1324-Req Level crossing system shall be activated, if one or more activation requests for one or more tracks of the level crossing exist.

Mandatory

FIR-FR1325-Req Activations shall be independent, if more than one activation requests exist. Mandatory FIR-FR1326-Req Activation shall be started after time delay, if time delay is configured for the applicable activation request. Mandatory FIR-FR1327-Req The activation phases shall be done in the following order: Mandatory FIR-FR1328-Req Pre-alarm time Mandatory FIR-FR1329-Req Time reserved for barriers to lower to horizontal position in level crossing barrier system Mandatory

FIR-FR1330-Req Time reserved for the barrier, which closes the lane leading away from the level crossing, to lower to a

horizontal position in level crossing barrier system equipped with double barriers Mandatory

FIR-FR1331-Req Safety time Mandatory FIR-FR1332-Req Level crossing system activation shall consist of all the following actions: Mandatory FIR-FR1333-Req road signals shall be controlled to display a fastly flashing red light Mandatory FIR-FR1334-Req alarm bells shall be controlled to ring Mandatory FIR-FR1335-Req pre-alarm time shall be started Mandatory FIR-FR1336-Req All the following actions shall be done after pre-alarm time: Mandatory

FIR-FR1337-Req All barriers shall be controlled to lower to a horizontal position in other level crossing system than level

crossing barrier system equipped with double barriers Mandatory

FIR-FR1338-Req Barriers of the lanes leading to the level crossing shall be controlled to lower to a horizontal position in

level crossing barrier system equipped with double barriers Mandatory

FIR-FR1339-Req The lights in the barriers shall display a slowly flashing light Mandatory

FIR-FR1340-Req

Barriers closing the lane leading away from the level crossing shall be controlled to lower to a horizontal position 10 s after the barriers of the lanes leading to the level crossing have begun to lower in level crossing barrier system equipped with double barriers.

Mandatory

FIR-FR1341-Req Ringing of the alarm bells shall be ended, if the road section becomes occupied. Mandatory

FIR-FR1342-Req Activation shall be ended, if the deactivation conditions of all activation requests for all tracks of the level crossing system are satisfied.

Mandatory

FIR-FR1343-Req Ending activation consists of all the following actions: Mandatory FIR-FR1344-Req barriers shall be controlled to rise to vertical position Mandatory FIR-FR1345-Req ringing of the alarm bells shall be ended, if not ended earlier Mandatory

FIR-FR1346-Req road signals shall be controlled to display a slowly flashing white light in other level crossing system than

level crossing barrier system and station crossing system Mandatory

FIR-FR1347-Req road signals in the station crossing system shall not display any lights Mandatory




FIR-FR1348-Req All the following actions shall be done in level crossing barrier system, when barriers have risen at least to 60˚ angle with respect to the horizontal plane after ending activation:

Mandatory

FIR-FR1349-Req road signals shall be controlled to display a slowly flashing white light Mandatory FIR-FR1350-Req lights in the barriers shall not display any lights Mandatory

FIR-FR1351-Com 14.2.2.1 Activation configuration data

FIR-FR1352-Req Time delay for starting the activation shall be configured, if the required alarm time is exceeded more than 10 s before unit using the highest permitted speed on the alarm section is arriving to level crossing.

Mandatory

FIR-FR1353-Req Pre-alarm time shall be determined by the following conditions: Mandatory FIR-FR1354-Req Minimum pre-alarm time is 10s Mandatory

FIR-FR1355-Req 1s shall be added to pre-alarm time for each metre that the mutual distance of the barriers on opposite

sides of the track in the direction of the road exceeds 14m Mandatory

FIR-FR1356-Req Time reserved for barriers to lower horizontal position shall be 10s. Mandatory

FIR-FR1357-Req

Barriers closing the lane leading away from the level crossing shall be controlled to lower to a horizontal position 10 s after the barriers of the lanes leading to the level crossing have begun to lower in level crossing barrier system equipped with double barriers.

Mandatory

FIR-FR1358-Req Time reserved for the barrier, which closes the lane leading away from the level crossing, to lower to a horizontal position shall be 8s in level crossing barrier system equipped with double barriers.

Mandatory

FIR-FR1359-Req Safety time shall be 10s, unless other safety time is configured. Mandatory FIR-FR1360-Req Time for reactivating the level crossing system shall be 5 min Mandatory

FIR-FR1361-Com 14.2.3 Automatic operation

FIR-FR1362-Req The level crossing system shall be in automatic operation, if all the following conditions are satisfied: Mandatory FIR-FR1363-Req track sections on the alarm sections and the road section control the alarm Mandatory FIR-FR1364-Req level crossing system has not been manually activated Mandatory FIR-FR1365-Req level crossing system has not been deactivated for one or more tracks Mandatory FIR-FR1366-Req level crossing system is not in a failure state preventing the automatic operation Mandatory FIR-FR1367-Req The level crossing system shall be activated in automatic operation, if activation conditions are satisfied. Mandatory FIR-FR1368-Req The level crossing system shall not be deactivated in automatic operation, if deactivation conditions are not satisfied. Mandatory

FIR-FR1369-Com 14.2.4 Manual operation

FIR-FR1370-Req Level crossing system shall be activated manually if any of the following conditions is satisfied: Mandatory FIR-FR1371-Req alarm switch (TK) is used Mandatory



Requirement Finland - Priority FIR-FR1372-Req track-wise alarm button (TR ON) is used Mandatory

FIR-FR1373-Req operation switch (KK) is used again and one or more activation requests are satisfied, if the level crossing

system was deactivated by using the operation switch Mandatory

FIR-FR1374-Req Activation of the level crossing system shall be ended, if any of the following conditions is satisfied: Mandatory

FIR-FR1375-Req alarm switch (TK) in the equipment room or on the outside wall of the equipment room is used again, if

the activation was caused by using the alarm switch in question Mandatory

FIR-FR1376-Req

any other alarm switch (TK) than in the equipment room or on the outside wall of the equipment room is used again, if the activation was caused by using other alarm switch than in the equipment room or on the outside wall of the equipment room

Mandatory

FIR-FR1377-Req track-wise button for ending the alarm (TR EI) caused by using the alarm button is used, if the activation

was caused by using the alarm button of the track in question Mandatory

FIR-FR1378-Req deactivation conditions of automatic operation principles are satisfied for the track, if the activation was

caused by using the alarm button of the track in question Mandatory

FIR-FR1379-Req operation switch (KK) is used Mandatory FIR-FR1380-Req return button (PAL) is used, if the activation was caused by long alarm failure Mandatory

FIR-FR1381-Req Use of the operation switch (KK) shall prevent activation of the level crossing system unless operation switch is used again.

Mandatory

FIR-FR1382-Com 14.2.5 Elimination function

FIR-FR1383-Req Configurable track sections shall have the elimination function. Mandatory

FIR-FR1384-Req Activation shall be ended or prevented, if elimination button (PP) is used and the activation is caused by occupied track section on the alarm section.

Mandatory

FIR-FR1385-Req Elimination function shall be ended, if any of the following conditions is satisfied: Mandatory FIR-FR1386-Req button for ending the elimination function (PP EI) is used Mandatory FIR-FR1387-Req a route is set through the level crossing and the track section, which has the elimination function on Mandatory FIR-FR1388-Req occupied track section that has elimination function on, becomes not occupied Mandatory

FIR-FR1389-Req track section that has the elimination function on and was not occupied when the elimination function

starts, becomes not occupied within 5 min of the start of the elimination function Mandatory

FIR-FR1390-Req Level crossing system shall be possible to be equipped with track-wise elimination switch or switches, if level crossing has more than one track.

Mandatory

FIR-FR1391-Req Track-wise elimination switch shall eliminate the effect of alarm sections and road section of the track in question on level crossing system functionality.

Mandatory




FIR-FR1392-Com 14.2.6 Failures

FIR-FR1393-Req Level crossing system failure shall be one of the following: Mandatory FIR-FR1394-Req critical failure Mandatory FIR-FR1395-Req non-critical failure Mandatory FIR-FR1396-Req Critical failure in level crossing system shall cause all the following actions: Mandatory FIR-FR1397-Req level crossing protecting signal shall display 'stop' aspect Mandatory FIR-FR1398-Req required alarm time shall not be realised Mandatory FIR-FR1399-Req indication of the failure shall be displayed to signaller Mandatory FIR-FR1400-Req Alarm time for realising required alarm time shall be started again, if critical failure disappears. Mandatory FIR-FR1401-Req Indication of a non-critical failure shall be displayed to signaller. Mandatory FIR-FR1402-Req Long alarm failure in level crossing system shall: Mandatory

FIR-FR1403-Req

control the barriers to rise to a position that corresponds with the position of the non-voltage state of the barrier motor in other level crossing barrier system than level crossing barrier system equipped with double barriers

Mandatory

FIR-FR1404-Req control the barriers to remain in the horizontal position in level crossing barrier system equipped with

double barriers Mandatory

FIR-FR1405-Req

Barriers of a level crossing system for several tracks, which is in the state of the long alarm failure, must lower to horizontal position, if the alarm conditions are satisfied on a track other than the track, which caused the long alarm failure.

Mandatory

FIR-FR1406-Req

Level crossing system for several tracks shall return to the state of the long alarm failure, if the long alarm failure conditions are satisfied, when the alarm caused by the other track than the track, which caused the long alarm fault, ends.

Mandatory

FIR-FR1407-Req Critical failure of the level crossing system shall be one of the following failures: Mandatory FIR-FR1408-Req reliability failure Mandatory FIR-FR1409-Req system failure Mandatory FIR-FR1410-Req barrier failure Mandatory FIR-FR1411-Req barrier position monitoring failure Mandatory FIR-FR1412-Req road signal failure Mandatory FIR-FR1794-Req long alarm failure Mandatory FIR-FR1795-Req earth failure Mandatory FIR-FR1413-Req Non-critical failure of the level crossing system shall be one of the following failures: Mandatory FIR-FR1414-Req low-voltage alarm Mandatory



Requirement Finland - Priority FIR-FR1415-Req lamp failure Mandatory FIR-FR1417-Req operation failure Mandatory FIR-FR1418-Req Reliability failure is in the level crossing system, if one of the following conditions is satisfied: Mandatory FIR-FR1419-Req level crossing system is not activated and the activation conditions are satisfied Mandatory FIR-FR1420-Req barriers do not lower to horizontal position and the conditions for lowering the barriers are satisfied Mandatory

FIR-FR1421-Req System failure is in the level crossing system, if a failure in the control system of the level crossing system prevents the function of level crossing system.

Mandatory

FIR-FR1422-Req Barrier failure is in the level crossing system, if monitoring of the barrier on place is not satisfied because of a failure in barrier monitoring circuit.

Mandatory

FIR-FR1423-Req Barrier position monitoring failure is in the level crossing system, if a barrier does not reach the horizontal position in the required time from when the barriers were controlled to lower to horizontal position.

Mandatory

FIR-FR1424-Req Road signal failure is in the level crossing system, if a road signal is unable to display red light. Mandatory FIR-FR1425-Req Low-voltage alarm is in the level crossing system, if the voltage of the level crossing system accumulators is low. Mandatory FIR-FR1426-Req Lamp failure is in the level crossing system, if any of the following conditions is satisfied: Mandatory FIR-FR1427-Req main or auxiliary filament failure is detected in road signal Mandatory FIR-FR1428-Req failure preventing the display of a white light is detected in the road signal Mandatory

FIR-FR1429-Req failure preventing the display of a red light with one red light is detected in the road signal, but the red

light can be displayed by the other red light of the road signal Mandatory

FIR-FR1430-Req Long alarm failure is in the level crossing system, if all the following conditions are satisfied: Mandatory FIR-FR1431-Req level crossing system is activated in the automatic operation state for over 10 min Mandatory

FIR-FR1432-Req road section has not become occupied after starting the activation or the road section is occupied while the

alarm sections are not occupied Mandatory

FIR-FR1433-Req activation is not caused by manual operation Mandatory FIR-FR1796-Req The long alarm failure is not monitored for the track section or sections in rear of the level crossing protecting signal.

FIR-FR1434-Req Time for long alarm failure shall be started again, if another unit arriving in the alarm section causes the alarm, which was previously started by another train, to continue.

Mandatory

FIR-FR1435-Req Operation failure is in the level crossing system, if level crossing system is activated while none of the activation conditions is satisfied.

Mandatory

FIR-FR1436-Com 14.3 Level Crossing System Activation

FIR-FR1437-Req A level crossing system shall be activated, if any of the following conditions is satisfied: Mandatory FIR-FR1438-Req unit detection on the alarm section or road section Mandatory FIR-FR1439-Req a manual request Mandatory



Requirement Finland - Priority FIR-FR1440-Req absence of the control information in a level crossing system operated by interlocking system Mandatory FIR-FR1441-Req A level crossing system may be activated by a different request from each alarm section. Mandatory FIR-FR1442-Req Multiple activation requests may be present at the same time for one level crossing system. Mandatory FIR-FR1443-Req Activation requests shall be independent of each other. Mandatory

FIR-FR1444-Com 14.3.1 Alarm Section Occupation FIR-FR1445-Req Alarm section shall be configured separately for each main route and shunting route through the level crossing, Mandatory FIR-FR1446-Req Alarm section shall be assigned as 'occupied' if a track section in the alarm section becomes 'occupied'. Mandatory FIR-FR1447-Req If an alarm section is monitored as failed, it shall be assigned as 'occupied'. Mandatory

FIR-FR1448-Req A unit shall be detected as leaving the alarm section if all track sections in the alarm section become not 'occupied' in correct sequence.

Mandatory

FIR-FR1449-Com 14.3.2 Activation by Unit Detection

FIR-FR1450-Com 14.3.2.1 Activation

FIR-FR1451-Req A level crossing system shall be activated by unit detection if all the following conditions are satisfied: Mandatory FIR-FR1452-Req occupied track section that is considered 'valid for activation' is detected Mandatory FIR-FR1453-Req level crossing system is in an automatic function mode Mandatory FIR-FR1454-Req An occupied track section on the road section shall always be considered as 'valid for activation'. Mandatory

FIR-FR1455-Req An occupied track section on the alarm section shall not be considered as 'valid for activation' if any of the following conditions are satisfied:

Mandatory

FIR-FR1456-Req there is a protecting signal displaying 'stop' aspect between the track section in question and road section

and no route is set to the level crossing Mandatory

FIR-FR1457-Req the track section in question is included in local point operation permission group that has local point

operation permission given Mandatory

FIR-FR1458-Req a point between the track section in question and the road section is in a position leading away from the

level crossing Mandatory

FIR-FR1459-Req the configured time delay for activating the alarm after the track section became occupied has not expired Mandatory FIR-FR1460-Req the elimination function of the track section in question is in use Mandatory FIR-FR1461-Req the timer for reactivation by occupied track section for unit leaving the level crossing has not expired Mandatory

FIR-FR1462-Com 14.3.2.2 Time Delay for Aspect Permitting Driving




FIR-FR1463-Req The control of a level crossing protecting signal displaying 'stop' aspect to display an aspect permitting driving shall be delayed, if all the following conditions are satisfied:

Mandatory

FIR-FR1464-Req the preceding track section in rear of the signal is occupied Mandatory

FIR-FR1465-Req there is no other level crossing protecting signal displaying 'Stop' aspect between the level crossing

protecting signal and the level crossing Mandatory

FIR-FR1466-Req

the result of the following equation is positive

astt hälhid , where

thid = delay time [s] thäl = The time required, according to specifications given in the document "Trackside equipment and interfaces", for which the level crossing system alarm must be activated before the train driving the maximum speed of the track arrives at the level crossing [s] s = signal distance from the level crossing [m] a = the maximum acceleration of the train, for which the value 1.0 m/s2 must be used [m/s2]

Mandatory

FIR-FR1467-Req Signal delay timers for all alarm sections shall be started when the level crossing system becomes activated by the first activation request.

Mandatory

FIR-FR1468-Req A signal shall be maintained at a 'stop' aspect until its signal delay timer expires. Mandatory FIR-FR1469-Req A delay time of less than 5 seconds must always be carried out as a 5 seconds delay time. Mandatory

FIR-FR1470-Com 14.3.2.3 Monitoring Conditions

FIR-FR1471-Req The activated level crossing system shall satisfy the monitoring conditions for its protecting signal if one of the following conditions configured in engineering configuration requirements for each signal is satisfied:

Mandatory

FIR-FR1472-Req the level crossing system is monitored as 'activated' Mandatory FIR-FR1473-Req the barriers of the level crossing system are detected not open Optional

FIR-FR1474-Req the level crossing is detected as 'secured' and critical failure has not been detected in the level crossing

system Mandatory

FIR-FR1475-Req

The horizontal position of the barriers must be monitored in the conditions of the aspect permitting driving of the level crossing's protecting signal, starting 12 seconds after the pre-alarm time ends in the level crossing half-barrier system and 20 seconds after the pre-alarm time ends in the level crossing full barrier system.

Mandatory

FIR-FR1476-Com 14.3.3 Activation by Manual Request




FIR-FR1477-Com 14.3.3.1 Manual Request for an Individual Track from the Signaller

FIR-FR1478-Req A level crossing system shall be activated for an individual track if a request 'Request activation-individual track' is received from the signaller.

Mandatory

FIR-FR1479-Com 14.3.3.2 Manual Request for All Tracks from the Signaller

FIR-FR1480-Req A level crossing shall be activated for all tracks if a request 'Request activation-all tracks' is received from the signaller.

Mandatory

FIR-FR1481-Com

14.3.3.3 Manual Request for All Tracks from the Local Level Crossing System Operator

FIR-FR1482-Req A level crossing shall be activated for all tracks if a request 'Request activation-all tracks' is received from the local level crossing operator.

Mandatory

FIR-FR1483-Com 14.4 Level Crossing System Deactivation

FIR-FR1484-Req An activated level crossing shall be deactivated if all of the activation requests for the level crossing have been removed.

Mandatory

FIR-FR1485-Com 14.4.1 Deactivation by Unit Detection

FIR-FR1486-Req The following activation requests are permitted to be removed by unit detection: Mandatory FIR-FR1487-Req an activation request by unit detection Mandatory FIR-FR1488-Req a manual activation request for an individual track Mandatory FIR-FR1489-Req An activation shall be ended by unit detection if all the following conditions are satisfied: Mandatory

FIR-FR1490-Req the track sections of the road and alarm section on the applicable track become occupied and not occupied

in the correct sequence Mandatory

FIR-FR1491-Req the route locking of the track section on the alarm section becomes released, if the the route in question is

set through level crossing Mandatory

FIR-FR1492-Req A timer for reactivation shall be started when the activation is ended by the unit leaving the level crossing. Mandatory

FIR-FR1493-Req While a unit that is leaving the level crossing is in an alarm section, the level crossing system shall not become activated by the occupied track section in question unless one of the following conditions is satisfied:

Mandatory

FIR-FR1494-Req track section on the alarm section between the occupied track section in question and the road section

becomes occupied Mandatory



Requirement Finland - Priority FIR-FR1495-Req track section on the alarm section of the opposite side of the level crossing becomes occupied Mandatory FIR-FR1496-Req a timer for reactivation has expired Mandatory

FIR-FR1497-Req a route that results in activation by unit detection is initiated while an occupancy is detected through that

alarm section Mandatory

FIR-FR1498-Req The timer for reactivation shall be reset when the alarm section occupied with the vehicle leaving the level crossing becomes not occupied.

Mandatory

FIR-FR1499-Com 14.4.2 Deactivation by Manual Request

FIR-FR1500-Com 14.4.2.1 Manual Request for an Individual Track from the Signaller

FIR-FR1501-Req The activation request is permitted to be removed by manual request for an individual track if the activation request has been given by any of the following:

Mandatory

FIR-FR1502-Req a manual activation request for an individual track Mandatory FIR-FR1503-Req an activation request by unit detection Mandatory

FIR-FR1504-Req An activation request shall be removed if a request 'Request deactivation-individual track' is received from the signaller for the applicable track

Mandatory

FIR-FR1505-Com 14.4.2.2 Manual Request for All Tracks from the Signaller

FIR-FR1506-Req The following activation requests are permitted to be removed by a manual request for all tracks: Mandatory FIR-FR1507-Req a manual activation request for all tracks from the signaller Mandatory FIR-FR1508-Req a manual activation request for all tracks from the level crossing system Mandatory FIR-FR1509-Req An activation request shall be removed if a request 'Request deactivation-all tracks' is received from the signaller. Mandatory

FIR-FR1510-Com 14.4.2.3 Manual Request for All Tracks from the Local Level Crossing Operator

FIR-FR1511-Req Activation shall be possible to be ended by manual request for all tracks, if the level crossing system was activated manually for all tracks from the level crossing system.

Mandatory

FIR-FR1512-Req Activation shall be ended if a request 'Request deactivation-all tracks' is received from the level crossing system. Mandatory

FIR-FR1513-Com 14.4.3 Deactivation by Loss of Activation Conditions

FIR-FR1514-Req An activation request for the level crossing shall be removed if its conditions for activation become not satisfied. Mandatory

FIR-FR1515-Req If a route that caused an activation request becomes cancelled, its activation request shall be removed, when the route becomes released.

Mandatory



Requirement Finland - Priority FIR-FR1516-Req Timer for removing activation request shall be started, if all the following conditions are satisfied: Mandatory FIR-FR1517-Req the occupied track section causing the activation becomes not occupied Mandatory FIR-FR1518-Req track sections on the alarm section and the road section are not occupied in the correct sequence Mandatory FIR-FR1519-Req none of the other activation conditions is satisfied Mandatory

FIR-FR1520-Req The activation request shall be removed after 40 s time delay, if any activation condition becomes satisfied during the time delay.

Mandatory

FIR-FR1521-Com 14.5 Special Functions

FIR-FR1522-Com 14.5.1 Disabling Level Crossing System Activation

FIR-FR1523-Req The activation of a level crossing system shall be disabled if all the following conditions are satisfied: Mandatory FIR-FR1524-Req a request 'Disable level crossing' is received from the signaller Mandatory FIR-FR1525-Req the level crossing is not activated Mandatory FIR-FR1526-Req If a level crossing system is 'disabled', all the following actions shall be done: Mandatory FIR-FR1527-Req an activation request by unit detection shall not activate the level crossing Mandatory FIR-FR1528-Req the level crossing shall not satisfy the monitoring conditions for its protecting signal Mandatory

FIR-FR1529-Req The activation of a level crossing system shall be enabled if a request 'Enable level crossing system' is received from the signaller

Mandatory

FIR-FR1530-Com 14.5.2 Disabling an Activation Request for an Individual Track

FIR-FR1531-Req An activation request by unit detection for an individual track shall be disabled if a request 'Deactivation-individual track' is received from the signaller.

Mandatory

FIR-FR1532-Req An activation request by vehicle detection for an individual track shall become enabled if any of the following conditions is satisfied:

Mandatory

FIR-FR1533-Req a request ‘Request activation-individual track' is received from the signaller Mandatory FIR-FR1534-Req a configured timer expired Mandatory FIR-FR1535-Req all alarm sections for that individual track become not occupied Mandatory

FIR-FR1536-Com 14.5.3 Overriding Failed Critical State

FIR-FR1537-Req A level crossing system with the state 'failed critical' shall satisfy the monitoring conditions for its protecting signal if a request 'Override failed critical state' is received from the signaller.

Mandatory

FIR-FR1538-Req The override of the 'failed critical' state shall satisfy the monitoring conditions only for one route life cycle. Mandatory




FIR-FR1539-Com 14.5.4 Level Crossing System Out of Use

FIR-FR1540-Req While a level crossing system is monitored out of use, the level crossing shall satisfy the monitoring conditions for its protecting signal.

Mandatory


FIR-FR1542-Req Level crossing system configuration data for interlocking system shall contain the following information: Mandatory FIR-FR1543-Req type of the level crossing system Mandatory FIR-FR1544-Req required alarm time Mandatory FIR-FR1545-Req safety time, if other than the default safety time Mandatory FIR-FR1546-Req road section or sections of the level crossing system Mandatory FIR-FR1547-Req alarm sections of the level crossing system and route dependencies Mandatory FIR-FR1548-Req applicable activation requests Mandatory FIR-FR1549-Req applicable deactivation requests Mandatory FIR-FR1550-Req barriers and raod signals of the level crossing system Mandatory FIR-FR1551-Req routes that have level crossing system conditions monitored in route monitoring conditions Mandatory

FIR-FR1552-Req track sections on the alarm section that are included in local operation permission group and the local

point operation permission of which shall eliminate the effect of occupied track section to activation Mandatory

FIR-FR1553-Req track sections on the alarm section that have elimination function Mandatory

FIR-FR1554-Req point position that shall eliminate the effect of occupied track section to activation and the track sections

in question Mandatory

FIR-FR1555-Req Level crossing system configuration data for each route shall contain the following information: Mandatory FIR-FR1556-Req alarm sections Mandatory FIR-FR1557-Req time delay for setting signal to an aspect permitting driving without other conditions Mandatory

FIR-FR1558-Req time delay for setting signal to an aspect permitting driving, if a route was set to the level crossing and the

track section in rear of the route entry signal is occupied Mandatory

FIR-FR1559-Req time delay for activating the level crossing system, if a route was set to the level crossing and the track

section in rear of the route entry signal is not occupied Mandatory

FIR-FR1560-Req barrier position monitoring condition in route conditions Mandatory

FIR-FR1561-Req The timer for level crossing system reactivation following a unit leaving the level crossing but staying on the alarm section in advance of the level crossing shall be 5 minutes.

Mandatory

FIR-FR1562-Req Maximum time of level crossing system activation without a warning to the signaller shall be 10 minutes. Mandatory FIR-FR1563-Req The timer for deactivation by loss of activation conditions shall be 40 seconds. Mandatory




FIR-FR1564-Com 15 Statuses


FIR-FR1566-Req The interlocking system shall generate the statuses described in the following chapters. Mandatory FIR-FR1567-Req The interlocking system shall record the statuses designated for recording. Mandatory

FIR-FR1568-Com 15.2 Statuses

FIR-FR1569-Com 15.2.1 Route

FIR-FR1570-Req Route release timing Mandatory FIR-FR1571-Req Residual route release timing Mandatory FIR-FR1572-Req Approach zone occupied Mandatory FIR-FR1573-Req Overlap release timing Mandatory FIR-FR1574-Req Route monitoring conditions failed Mandatory

FIR-FR1575-Com 15.2.2 Local point operation group

FIR-FR1576-Com 15.2.2.1 Local point operation permission giving and cancellation

FIR-FR1577-Req Local point operation permission not given to local point operation group Mandatory FIR-FR1578-Req Local point operation permission given to local point operation group Mandatory FIR-FR1579-Req Local point operation permission monitoring failed Mandatory

FIR-FR1580-Com 15.2.3 Powered Moveable elements

FIR-FR1581-Com 15.2.3.1 General

FIR-FR1582-Req Not detected Mandatory FIR-FR1583-Req Trailed Mandatory FIR-FR1584-Req Blocked Mandatory FIR-FR1585-Req Failed Mandatory




FIR-FR1586-Com 15.2.3.2 Powered points

FIR-FR1587-Req Detected right Mandatory FIR-FR1588-Req Detected left Mandatory

FIR-FR1589-Com 15.2.3.3 Powered derailers and stopping devices

FIR-FR1590-Req Detected on rail Mandatory FIR-FR1591-Req Detected off rail Mandatory

FIR-FR1592-Com 15.2.3.4 Locking

FIR-FR1593-Req Locked as part of a main route Mandatory FIR-FR1594-Req Locked as part of a shunting route Mandatory FIR-FR1595-Req Locked as part of an overlap Mandatory FIR-FR1596-Req Locked as flank protection Mandatory

FIR-FR1597-Com 15.2.3.5 Route blocking

FIR-FR1598-Req Route blocked Mandatory

FIR-FR1599-Com 15.2.4 Key-locked Moveable Elements

FIR-FR1600-Req Released Mandatory FIR-FR1601-Req Not released Mandatory FIR-FR1602-Req Key in place Mandatory FIR-FR1603-Req Key not in place Mandatory FIR-FR1604-Req Detected right Mandatory FIR-FR1605-Req Detected left Mandatory FIR-FR1606-Req Blocked Mandatory FIR-FR1607-Req Failed Mandatory

FIR-FR1608-Com 15.2.4.1 Locking

FIR-FR1609-Req Locked




FIR-FR1610-Com 15.3 Signal

FIR-FR1611-Req Failed, whose display must be different in the fault states regarding the failures of ‘Stop’ aspect and aspects permitting driving

Mandatory

FIR-FR1612-Req Dark Mandatory FIR-FR1613-Req Main filament failure Mandatory FIR-FR1614-Req Auxiliary filament failure Mandatory FIR-FR1615-Req Lamp failure Mandatory

FIR-FR1616-Com 15.3.1 Main signal

FIR-FR1617-Req Proceed aspect Mandatory FIR-FR1618-Req Proceed 35 aspect Mandatory FIR-FR1619-Req Stop aspect Mandatory FIR-FR1620-Req Blocked Mandatory

FIR-FR1621-Com 15.3.1.1 Automatic Route Setting Mode

FIR-FR1622-Req Automatic route setting enabled Mandatory FIR-FR1623-Req Automatic route setting disabled Mandatory

FIR-FR1797-Com 15.3.2 Combined signal

FIR-FR1798-Req 'Proceed' aspect Mandatory FIR-FR1799-Req 'Proceed 35 ' aspect Mandatory FIR-FR1800-Req 'Stop' aspect Mandatory FIR-FR1801-Req 'Proceed with caution' aspect Mandatory FIR-FR1802-Req 'No aspects' aspect Mandatory FIR-FR1803-Req Individually blocked Mandatory

FIR-FR1804-Com 15.3.2.1 Automatic route setting

FIR-FR1805-Req Automatic route setting is on. Mandatory FIR-FR1806-Req Automatic route setting is off. Mandatory

FIR-FR1624-Com 15.3.3 Shunting signal



Requirement Finland - Priority FIR-FR1625-Req Proceed with caution aspect Mandatory FIR-FR1626-Req Stop aspect Mandatory FIR-FR1627-Req No aspects aspect Mandatory FIR-FR1628-Req Blocked Mandatory

FIR-FR1629-Com 15.3.4 Block Signal

FIR-FR1630-Req Aspect permitting driving Mandatory FIR-FR1631-Req Proceed, expect proceed aspect Mandatory FIR-FR1632-Req Proceed, expect stop aspect Mandatory FIR-FR1633-Req Stop aspect Mandatory FIR-FR1634-Req Blocked Mandatory

FIR-FR1635-Com 15.3.5 Locking Signal Mandatory

FIR-FR1636-Req No aspects aspect Mandatory FIR-FR1637-Req Stop aspect Mandatory

FIR-FR1638-Com 15.3.6 Level Crossing Signal

FIR-FR1639-Req Approach with caution Mandatory FIR-FR1640-Req No aspects aspect Mandatory

FIR-FR1641-Com 15.4 Track section

FIR-FR1642-Req No electrification on track section Mandatory

FIR-FR1643-Com 15.4.1 Occupation

FIR-FR1644-Req Not occupied Mandatory FIR-FR1645-Req Occupied Mandatory FIR-FR1646-Req Failed Mandatory FIR-FR1647-Req Blocked Mandatory

FIR-FR1648-Com 15.4.2 Locking

FIR-FR1649-Req Locked as part of main route Mandatory FIR-FR1650-Req Locked as part of shunting route Mandatory



Requirement Finland - Priority FIR-FR1651-Req Locked as part of overlap Mandatory

FIR-FR1652-Com 15.4.3 Axle counter reset

FIR-FR1653-Req Axle counter unconditional reset activated Mandatory FIR-FR1654-Req Axle counter conditional reset activated Mandatory FIR-FR1655-Req Axle counter occupied after reset Mandatory FIR-FR1656-Req Axle counter clear before reset acknowledgement Mandatory

FIR-FR1657-Com 15.5 Line block

FIR-FR1658-Req Direction inbound Mandatory FIR-FR1659-Req Direction outbound Mandatory FIR-FR1660-Req Direction change not permitted Mandatory FIR-FR1661-Req Line block out of sequence Mandatory FIR-FR1662-Req Signalled block section out of sequence Mandatory FIR-FR1663-Req Failed Mandatory

FIR-FR1664-Com 15.6 Level crossing system

FIR-FR1665-Req Level crossing not activated Mandatory FIR-FR1666-Req Level crossing activated Mandatory FIR-FR1667-Req Activation request present from an alarm section Mandatory FIR-FR1668-Req Manual request present for all tracks Mandatory FIR-FR1669-Req Manual request present for all tracks from level crossing operator Mandatory FIR-FR1670-Req Manual request present for an individual track Mandatory FIR-FR1671-Req Failed non-critical Mandatory FIR-FR1672-Req Failed critical Mandatory FIR-FR1673-Req Level crossing secured Mandatory FIR-FR1674-Req Level crossing activated by local switch Mandatory FIR-FR1675-Req Level crossing out of use Mandatory FIR-FR1676-Req Running on backup power Mandatory FIR-FR1677-Req Communication failure Mandatory FIR-FR1678-Req Long alarm failure Mandatory

FIR-FR1679-Com 15.6.1 Barriers



Requirement Finland - Priority FIR-FR1680-Req Barriers open Mandatory FIR-FR1681-Req Barriers in 60 degree's angle compared to horizontal position Mandatory FIR-FR1682-Req Barriers closed Mandatory FIR-FR1683-Req Barriers failed Mandatory

FIR-FR1684-Com 15.6.2 Road signal

FIR-FR1685-Req Road signal on Mandatory FIR-FR1686-Req Road signal off Mandatory FIR-FR1687-Req Road signal disturbed Mandatory FIR-FR1688-Req Road signal failed Mandatory

FIR-FR1689-Com 15.7 Lockable and Detection Devices

FIR-FR1690-Com 15.7.1 Detection Device

FIR-FR1691-Req Device detected in position Mandatory FIR-FR1692-Req Device not detected in position Mandatory

FIR-FR1693-Com 15.7.2 Lockable Device

FIR-FR1694-Req Device detected in position Mandatory FIR-FR1695-Req Device not detected in position Mandatory FIR-FR1696-Req Device released Mandatory FIR-FR1697-Req Device not released Mandatory FIR-FR1698-Req Device blocked Mandatory

FIR-FR1699-Com 15.8 Other Statuses

FIR-FR1700-Com 15.8.1 Power supply control

FIR-FR1701-Req Emergency power on Mandatory FIR-FR1702-Req Batteries discharging Mandatory FIR-FR1703-Req Batteries low Mandatory FIR-FR1704-Req Boosted charging on Mandatory FIR-FR1705-Req Diesel generator operating Mandatory



Requirement Finland - Priority FIR-FR1706-Req Diesel generator low fuel Mandatory FIR-FR1707-Req Power supply failed Mandatory FIR-FR1708-Req Earth leakage Mandatory FIR-FR1709-Req Earth leakage detector failed Mandatory

FIR-FR1710-Com 15.8.2 Operational mode transitions

FIR-FR1711-Req Interlocking system remote controlled Mandatory FIR-FR1712-Req Interlocking system local controlled Mandatory

FIR-FR1713-Com 15.8.3 Point heating control

FIR-FR1714-Req Off Mandatory FIR-FR1715-Req Auto control with thermostat heating on Mandatory FIR-FR1716-Req Auto control with thermostat heating off Mandatory FIR-FR1717-Req Full power Mandatory FIR-FR1718-Req Non-critical failure Mandatory FIR-FR1719-Req Critical failure Mandatory

FIR-FR1720-Com 15.8.4 Signal intensity control

FIR-FR1721-Req Signal intensity-day Mandatory FIR-FR1722-Req Signal intensity-night Mandatory

Documents

FIR 2010 Functional Requirements v1.4 12032014