Railway (Best)

(1)

Software Requirement Specification

For Control Office Application

Project : Control Office Application (COA)

(2)

Project Code: COA_CRIS

Project Name: Control Office Application for CRIS

Account: CRIS

Vertical: E-Governance Solutions

Location: Delhi

Customer Name: Centre for Railway Information Systems(CRIS) Technical Manager/ Email ID: Jeyaseelan J

[email protected] Project Manager / Email ID: Praveen Kumar Rajuladevi

[email protected] Quality Co-ordinator / Email ID: Santosh Dharwadkar

[email protected] Customer Contact Information: Mr.Rajeev Gupta –GGM(IT)Centre for Railway Information Systems

Chanakya Puri New Delhi

Prepared by/Date

Praveen Kumar Rajuladevi

Reviewed by/Date

Mr.Rajeev Gupta/ 05-Jul-2005

Approved by/Date

(3)

Revision History Version

(x.yy) Date of Revision Description of Change Reason for Change Affected Sections Approved By

1.0 11-April-05

Draft Version for submission to CRIS

1.1 05-July-05 Included Browser based access to MIS reports

(4)

Table of Contents (Re-generate the TOC after modifications to the document)

1 Background and Introduction...6

2 Functional Requirements...7

USE-CASE Specification – User Login...7

2.1.1 Basic Flow – User Login ...7

USE-CASE Specification – Order a Train ...8

2.1.2 Basic Flow – Train Ordering...8

2.1.3 Alternate Flow ...10

USE-CASE Specification – Maintain Train Information...17

2.1.4 Basic Flow – Maintain Train Information. ...17

USE-CASE Specification – Train Movement...26

2.1.5 Basic Flow – Manage Train Movement. ...26

USE-CASE Specification – Report Unusual Occurances...39

2.1.6 Basic Flow ...39

2.1.7 Alternative Flow...56

USE-CASE Specification – Management of Maintenance Blocks...57

2.1.8 Basic Flow – Maintenance Blocks...58

USE-CASE Specification – Caution Orders...63

2.1.10 Basic Flow – Caution Order...63

USE-CASE Specification – Plot Graph ...67

2.1.12 Basic Flow – Plot Graph ...68

USE-CASE Specification – Advance Plotting...71

2.1.14 Basic Flow – Advance Plot ...72

USE-CASE Specification – Create/Maintain Referential Data...82

2.1.16 Basic Flow – Maintain Referential Data ...82

USE-CASE Specification – MIS Reports...83

2.1.17 Basic Flow – MIS Reports...83

USE-CASE Specification – Yard Management...93

2.1.18 Basic Flow – Manage Yard. ...93

USE-CASE Specification – Security & Administration...94

2.1.19 Basic Flow – Manage User ...95

USE-CASE Specification – Miscellaeneous Functions...97

2.1.20 Basic Flow – Reporting Miscellaneous Tasks ...97

2.1.21 Alternative Flows...97

USE-CASE Specification – ...98

2.1.22 Basic Flow – ...99

Integration with NTES...99

(5)

2.1.23 Basic Flow – ...102

USE-CASE Specification – Integration with Data Loggers...104

2.1.24 Automatic Train Ordering...105

3 Operational Concepts and Scenarios...106

Distributed Architecture:...106

Highly Available System:...108

Evolutionary MIS:...108

Security of the System...109

4 Interface Requirements...110

Hardware Interfaces...110

4.1.1 Dual Screen Capability...110

4.1.2 Chart Printing...110

Browser based access to MIS Queries/Reports...111

5 Non functional/Specific Requirements...113

Risks 114

6 Assumptions/Dependencies/Limitations...118

7 Acceptance Criteria...119

8 Allocation of System Requirements...120

9 Others...121

10 Acronyms and Glossary...121

(6)

1 Background and Introduction

Indian Railways comprises of about 70 divisions which are the operational arms and responsible for day-to-day operations . The divisional control office is the nerve centre for all activities related to train running. It has the following functionaries

- Chief Controller controlling overall train movement and related activities.

- Stock Controller for planning the demand and supply of wagons

- Dy Trains for planning and control of freight train movement

- Dy Punctuality for monitoring punctuality of passenger trains.

- Power controller for arranging locomotive and crew for trains.

- Section Controller for regulating the movement of all trains over a specified

jurisdiction.

The duties of the Section Controller are very strenuous in nature involving high level of documentation work in addition to his primary duty of planning and reporting the

movement of trains.The present system of operational practices also/ involves a lot of paper work by support staff to convert the operational related information from the Control Chart into various registers. Thus the core activity of advance plotting and timely reporting of movements is hampered . Thus, the management is forced to rely only on selective information about various events for decision making.

In view of the above scenario, Indian Railways has prioritised the need to automate these operations and identified the need for technology enabled services as part of its

automation strategy to achieve operational efficiency. The benefits of such an automated system would be

- Integration of various distributed systems in a cost effective manner

- Better operational efficiency and productivity by replacing manual processes with

automated processes.

- Establishment of faster and better interfaces with the consumers by streamlining of

processes and enhancement of information availability

- Greater cohesiveness among various divisions

Divisional Control Office Operations Application (COA) is as an application capable of collaborating with FOIS/ NTES and Charting front end and other planned sub modules on an All-India basis. This would facilitate prevention of duplication of efforts, maintain

uniformity of data and ensure that investments already made in these applications are fully utilized, thereby leading to a best value for money solution. The following considerations are being addressed while designing the architecture of COA.

(7)

2 Functional Requirements

USE-CASE Specification – User Login

The purpose of this use case is to allow user to login to the system. The authenticity of user shall be checked and access to various functions shall be given as per his assigned group. Actors 1. Primary Actors 1.1Section Controller 1.2Dy. Trains 1.3Dy. Coaching 1.4Power Controller 1.5Yard Manager 1.6MIS User 2. Secondary Actors Flow Of Events

2.1.1 Basic Flow – User Login

The use-case starts when user gets login screen on clicking COA icon or on selecting logout option.

• User shall give user-id, password and Shift details.

• On submitting, user details shall be validated.

• If validation fails

 Message shall be displayed. Use-Case ends.

• If valid,

 Menu screen shall be displayed with options enabled as per group

assigned at the time of user creation.

 Any information to be given on login shall be displayed through an

alert displayed on main menu screen.

 In case a user is assigned more than one section highest priority section shall be enabled at the time of login with facility of changing the section any time after logging into the system.

(8)

2.1.1.1 Pre-Conditions

• User database information should be available.

USE-CASE Specification – Order a Train

The purpose of this use case is to allow for entry of train details in to the system. Any changes in train details of existing trains shall also be facilitated through this use case.

3. Primary Actors 3.1Section Controller (SC) 3.2Dy. Coaching 3.3Dy. Trains(Stock) 3.4Data Logger 4. Secondary Actors 1.1 CAS System Flow Of Events

2.1.2 Basic Flow – Train Ordering.

This use case starts when Section Controller selects “Order a Train” from the menu. The screen displays the available options. The options available are

(9)

(i) Add New Train (ii) Modify Train (iii) Cancel Train (iv) Link Trains

2.1.2.1 Add New Train

User selects Add New Train only in cases where train does not exist in the system. Adding of Train shall be allowed within some pre-defined time interval before the departure of the train(To avoid overlap with train information coming from CAS).

• The screen is displayed to enter train details.

• List of trains available through CAS system but not linked to trains in this

system shall be displayed (To avoid double entry of trains)

• User can either select train or enter new train details.

• If user selects train, available train details such as Train number/name, Train

Type, Train Sub-Type, Originating Station, Destination Station, Day(s) of service (only for new passenger services), Expected Departure Time (ETD) shall be displayed. The user can modify only the ETD . Details of Division Entry Station, Division Exit Station (Interchange point) and Route shall be displayed by default. • Alternatively if the user does not select any train, he shall enter Train

number/name, Train Type, Train Sub-Type, Originating Station, Destination station, Day(s) of service (only for new passenger services), Booked speed of the train (only for Goods) and Expected Departure Time (ETD). In the case of trains originating from non-computerized divisions, the user shall select the Division Entry Station, Division Exit Station (Interchange point) and Route

• Whenever a Light Engine is ordered to proceed to an accident spot, the

relevant sub-type shall (Traffic/Loco/ART) be selected.

• User shall submit the details.

• System shall validate the from/to station and handing over station against a

referential table containing all stations (populated from FOIS). • If validation fails,

 Alternate flow Invalid Station is followed.

• If valid,

 System shall save the information.

 System shall generate Train Id. for the train saved and that

shall be the system identification number.

 System displays a confirmation message.

Plot Graph / Automatic Ordering.

System shall display a dot on the plot graph in the display screen at pre-determined configurable time in advance of the expected departure time for scheduled passenger services and goods trains ordered by the system including those trains coming from the adjacent division. Refer Plot Graph use case.

(10)

2.1.3 Alternate Flow

2.1.3.1 Modify Train

This option will enable the Section Controller or the Dy.CHC (Trains) or Dy.CHC (Punctuality) to modify only the Expected Time of Departure.

The screen displays following options:

(i) Passenger Trains

(ii) Other Trains.

• On selecting any one of the above options by default a complete list of trains

due to depart within a configurable interval shall be displayed on the screen sorted by ETD and direction.

• The user shall select one or more trains and then click on one of the

following options

(11)

 User can select any one of the following options (i) Put Back (ii) Put Forward.

 If more than one train is selected, user shall enter No. Of

hours/minutes by which each train is to be Put Back/ Put Forward

 If a single train is selected user shall enter modified departure time.

 User shall then submit modified Train Details.

 When a train is put forward, the system shall validate that the revised

ETD is not earlier to the current system time.

 If validation fails,

 Message is displayed. Use Case ends.

 If valid,

 The modified ETD shall get displayed on the screen.

(12)

Change Of Destination

 Section Controller shall enter new destination station.

 If there is change in the route but destination is in the current division

then

 User shall select required route.

 User shall also give authorization details.

 If there is change in the route but destination is in other division then

 The system shall display all the divisional exit stations.

 The User shall select the corresponding exit station.

 User shall then select required route.

 User shall then submit the modified Train Details.

 System shall validate destination station and division exit station.

 If valid,

System displays a confirmation message.

(13)

Diversion

Diversion task shall be invoked when there is change in the route in current division but no change in destination.

 If there is change in the route and destination is in the current division

then

 User shall select required route.

 If there is change in the route and destination is in other division then

 User may give division exit station (Interchange Point).

 User shall then select required route.

 User shall then submit modified Train Details.

 System shall validate division exit station.

 If valid,

(14)

. Cancel Train

Only the Dy. CHC (Trains) in respect of goods trains and Dy.CHC (Punctuality) can cancel a train whose departure is scheduled for that day or within a specified time interval and which has not yet departed.

• The screen displays following options:

(i) Passenger Trains (ii) Other Trains.

• On selecting one of the above options, by default, the list of trains scheduled

to depart over the Division for a configurable time interval shall be displayed on the screen.

• The user shall select one or more trains for cancellation.

• The user shall select the reason code from the

pre-defined list for cancellation. If reason code is OTHR, specific details shall be entered.

(15)

If successfully saved,

• On saving, modified data shall be sent to CAS for

updating the external/adjoining database.

An indicative screenshot illustrating the User Interface elements is shown below

Link Train

Linking is facilitated to be done between trains created in COA and train details that would come through CAS system from other applications like FOIS or from COA of a contiguous division.

• A list of trains received from CAS system and trains created through this

system shall be displayed.

• A train shall be selected from the list under CAS system, dragged and dropped on to COA trains list using identification parameters like Train Name, From Station, To Station, ETD and other details.

• It shall be possible to drag and drop multiple trains.

(16)

• A list of linked trains shall be shown to the user, on confirmation, the details shall be saved.

An indicative screenshot illustrating the User Interface elements is shown below

Invalid Station

• In case station is not found message shall be displayed.

• Station entry may be corrected and submitted again or use case ends here.

Pre-Conditions

• Section Controller should have successfully logged on to the system.

• Static database information should be available.

Post-Conditions

• Graph should be refreshed whenever a new train is created or there is

change in the details of a train.

(17)

• If train is coming from non-computerized control charting territory, train shall have to be created afresh in this system.

Assumptions

• Data from external systems should be available to this system through CAS

server.

USE-CASE Specification – Maintain Train Information

The purpose of this use case is to allow adding or updating details in respect of ordered/running trains. The information captured through this use-case shall include locomotive attachment/detachment, consist reporting, crew reporting and BPC reporting. These details may be entered even after the departure of a train.

Actors 1.Primary Actors a)Section Controller b)CAS System 2.Secondary Actors Flow Of Events

2.1.4 Basic Flow – Maintain Train Information.

The use-case starts when user selects “Maintain Train Information” option from the menu.

• The following options shall be displayed to the user.

(i) Trains To depart

(ii) Trains Running

• On selecting the option “Trains to depart”, the list of trains expected to depart

within a pre-defined time interval shall be displayed on the screen.

• On selecting the option “Trains running”, the list of trains running within the

section based on specified direction shall be displayed on the screen.

• On selecting a train from the list, the available train details shall be displayed

on the screen.

• The train details displayed shall include train number/name, train type, direction, from station, to station.

The following options shall be available to the user for entering/updating train information.

(18)

2.1.4.1 Loco Attachment/Detachment

This screen captures all the details related to Loco Attachment/ Detachment for the selected train.

• User shall have the following three options

(i) Attach

(ii) Detach

(iii) Re-Sequence

If User selects Attach option then User shall select the train number. User shall enter the Loco number(s).

 If Loco Type, Traction, Brake Type, Base shed, Schedule type, last attended/ Next due date are available, these details shall be displayed.

 If loco number is not available in the database, then user shall enter the

loco details.

 The system shall provide for attaching one or more locomotives.

 If more than one locomotive is attached, the position of the locomotive,

working mode (double heading/Multiple operation/Banker) and working status (Working or Dead) shall also be captured.

 The user shall select the station where the loco attached, reason code

and attachment date/time

• If User selects Detach Option then

 User shall select the train number

 The system shall display row wise the loco number(s) attached to the

selected train. The user shall select the loco number to be detached. Details of selected loco shall be displayed explicitly on the screen.

 User shall then give details of detachment station, reason code and detachment date/time.

• If user selects re-sequencing then

User shall select the train number

 The system shall display row wise the loco number(s) attached to the

selected train in the order of their position.

 The user shall have the facility to drag and drop any of the rows, which

shall cause the re-sequencing of the position..

• In case of change of loco en-route, the detachment task shall precede the

attachment task. On saving

 Saved changes details shall be shown on screen.

(19)

2.1.4.2 Consist Reporting

This screen captures all the Consist details for the selected train.

• If train type selected is Freight and consist details are available through CAS

 Details of consist shall be displayed (rake type wise) on the screen.

 In case the user desires to modify any consist details, he shall select

the required row corresponding to the particular rake type which shall cause corresponding details to be displayed

 User can change the details displayed on the screen.

 By default, the reporting station shall be the train-originating station

but the user can change the reporting station.

(20)

 Summary line shall be displayed at the bottom of screen. It shall display total no. of wagons/total 4 wheeler units/total gross weight of the train

• If train type selected is Freight and consist details are not available through

CAS

 User shall select one of the following options

(i) Summary Reporting

(ii) Rake Type-Wise Reporting

 In case of summary reporting, the user shall enter total number

of wagons and total gross weight.

 In case of rake type-wise reporting user shall enter consist details like Reporting station, Rake Type, Loaded/Empty, Units, from Station, To Station, Gross weight and commodity.

 By default, the train originating station shall be the reporting

station, but the user can select any other station.

 User shall click Next for entering more than one rake type by the train,

which shall cause a new row to be added. The rake type shall be selected by the user from the pre-defined list maintained as a referential table by populating the data from FOIS.

 Summary line shall be displayed at the bottom of screen. It shall display total no. of wagons/total 4 wheeler units/total gross weight. If train type selected is Passenger and consist details are available.

 The user shall select the train number.

 The details such as owning railway, coach type, coach number and

coach position shall be displayed on the screen.

 In case the user wants to modify any consist details, he shall select

the required row and modify the details.

 By default the originating station of the train shall be the reporting

station, but the user can change it by selecting any other station

 Summary line shall be displayed at the bottom of screen. It shall display total no. of coaches/total 4 wheeler units/gross weight of the train.

• If train type selected is Passenger and consist details are not available.

 The user shall enter consist details like Reporting station, Owning railway, Coach Type, Coach Number (optional), Reservation coach position, From Station, To Station.

 The originating and destination station of the train shall by default be the from and to station. The user can enter any other station name.

 The originating station shall be the reporting station by default

(21)

 Summary line shall be displayed at the bottom of screen. It shall display total no. of coaches/total 4 wheeler units/gross weight of the train.

 User shall click ‘Next’ for subsequent entries

• After entering/modifying consist details the user shall save the details.

• On saving, from station, to station shall be validated.

 If valid,



(22)

2.1.4.3 Wagon/Coach Attachment/Detachment

This screen allows for capturing attachment/detachment details for wagons/coaches for selected train.

• Details of consist shall be displayed on the screen. Consist may be in summary or detailed form.

• User shall select whether attachment or detachment is to be done.

• User shall select the required row (rake type wise in case of a goods train)

and corresponding details shall be displayed on the screen.

• User shall then enter the number of wagons/coaches to be detached or attached, if the details are in summary format.

• User shall also select the reason code, attachment/detachment station, line

number (only when detaching) and date/time of attachment/detachment.

• User shall then submit the details.

• In case of detachment of wagons/coaches at a station, the stock inventory at

the station and the line occupation status shall also get updated. If successfully saved,

Details displayed on screen to reflect the saved changes. An indicative screen is illustrated below

(23)

2.1.4.4 Crew Reporting

This screen allows for capturing crew details for the selected train.

• User shall select one of the following options

(i) Sign On

(ii) Modify

• If user selects Sign On option

 The user shall enter the crew details such as crew name, crew type,

working from station, working to station and sign on time.

 In case of more than one engine on the train, the user shall click ‘NEXT’

which shall cause a new row to be added for entering the details.

 In case of change of crew en-route, working to station against the first

crew shall be filled up before the details for the second crew is entered.

• If user selects modify option

 Crew details shall be displayed locowise on the screen.

 User shall select the required row and modify any of the details displayed on the screen.

(24)

• On saving, from station, to station shall be validated.  If validation fails,

 If valid,

An indicative screen is illustrated below

2.1.4.5 BPC Reporting

This screen shall allow for capturing/modifying BPC details for the selected train.

• On selection of this option, if the BPC details of the train are available, the

same shall be displayed on the screen.

(25)

• If the BPC details are not available, User shall enter the Station of Issue, BPC No, Date, % Brake Power, Valid From, Valid To, Std of Exam, BPC Type, Base Station, Days Valid For and Kms Valid for.

• On saving.

An indicative screen is illustrated below

Invalid Station

• In case station is not found message shall be displayed.

• Station entry may be corrected and submitted again or use case ends here.

Pre-Conditions

• Detachment of loco option shall be enabled only when at least one loco is

(26)

Post-Conditions

• Changes saved should be shown on the screen after successful save.

• Changes in any of details shall affect the graph.

Business Rules

• If train is coming from non-computerized control charting territory, train shall

have to be created afresh in this system. The various details pertaining to the train such as consist details, loco details, BPC details, Crew details shall also have to be entered.

Assumptions

 Data from external systems should be available to this system.

USE-CASE Specification – Train Movement

This use case shall capture arrival and departure or run through of trains at a station, details of stabling, detentions and their reasons, facility to change priority for trains in case of necessity, special movement practices involving track machine and material trains. The details captured through this use-case shall be the input to plot graph use-case. These details may be entered even after the departure of train. (To be configured locally)

Actors 1.Primary Actors a)Section Controller b)Data Logger 2.Secondary Actors a)CAS System Flow Of Events

2.1.5 Basic Flow – Manage Train Movement.

The menu defined by this use-case shall be the default option in the touch screen.

The list of running/ordered trains over the board shall be displayed direction wise separately for selection.

On selecting the train number, the current location of the train shall be displayed The user shall then select any one of the following options:

 Report Arrival/Departure/ Run Through

 Line Occupation (Optional)

 Detentions

 Priority change

(27)

2.1.5.1 Report Arrival/Departure/Run-Through

Through this screen details of arrival/departure/run-through shall be captured for trains currently running on the board.In the data logger mode, the details pertaining to above activities shall be system driven through the interface software.

In the manual mode,

If the tracking of the selected train is current (up to the last station), then

• User shall select the relevant option through mouse click or hot key.

• He shall enter the corresponding timing at that station.

• System shall compare the actual inter station running time with the permitted

running time (over the block section) or actual duration of stoppage against booked stoppage(at a station) and calculate the difference between the actual and the scheduled.

• System shall indicate the Loss (+) or Gain (-) and record it against the block

section or station. The loss shall be indicated in red and gain in green color preceded by + or – sign.

• The system shall also provide facility to enter the reason for the loss/detention

whenever immediately known.

• When a train is delayed in a block-section beyond normal running time plus a

margin of 10 minutes in case of a passenger train or 20 minutes in case of a goods train, the system shall throw an alert message to the user, which shall be acknowledged. (For subsequent flow, Refer Abnormal working use case-Accidents).

If the tracking of the selected train is not current due to communication disturbances (timings at a station or a series of stations were not obtained), then

 User shall select the relevant station over the section

 User shall then select the train number based on the direction.

 User shall then enter the corresponding timing at that station.

 System shall compare the actual inter station running time or actual

duration of the stoppage with the permitted running time or duration of stoppage (over the block section or at station as the case may be) and calculate the difference between the actual and scheduled.

On saving,

 System shall validate that the time reported for the event

(arrival/departure/run through) is neither less than the last reported time nor greater than the system time.

2.1.5.2 Line Occupation

This option shall enable the user to enter the line number in which the particular train was dealt with at a station.

(28)

In the data logger mode, the details pertaining to above activity shall be system driven through the interface software.

In the manual mode, in case of occupation of a line by a full train

• User shall select the train number and type

• The station at which the arrival was reported last shall be displayed by default.

• Only the line numbers that are free at the chosen station shall be displayed for

selection.

• The selected line shall be deemed to be occupied by the specified train till the

time of clearance either by departure or removal to yard.

• If a line has been blocked by a goods train either due to termination or for

other reasons and remains to be occupied for more than 24 hours from the time of arrival, it shall be deemed as stabling.

• When the line has been cleared by the departure of the train after a brief

stoppage, the system shall reckon the time of departure as time of removal by default and cause the line to be shown again as “Clear”.

• When the train has reached the destination or terminated at a station, the time

of removal shall be entered by the user on receipt from the station / cabin with brief reason which shall cause the line to be shown again as “Clear”.

• If a train is to be dealt with on a line which is shown as already occupied, then

 User shall select the station.

 The list of occupied lines at the selected station shall be displayed for selection.

 The user shall select the line number and fill in the time of removal for the

previous train. This shall cause the line to be shown as “clear”. The user shall have the facility to enter the new train number for the same line. When the user enters the new train number, the time of arrival of the train at the same station shall be the default time of occupation and also cause the line to be shown again as occupied.

• In the case of outgoing train at a station, the nominated platform line shall be

shown by default as the line occupied by the train from 30 mins before the scheduled departure.

• The details of nominated line, train wise, station wise shall be maintained as

part of the referential data. The line shall be deemed to be “Clear” with the actual departure of the train.

• If some other train already occupies the nominated line, the user shall have

the option to choose one of the unoccupied lines for the other train.

In the manual mode, in case of occupation of a line by part of a train(one or more vehicles )

• User shall select the station.

• Only the line numbers that are free at the chosen station shall be displayed for

(29)

• User shall enter the number of wagons and rake type/ coach type and the time of detachment (occupation) on the line.

• The selected line shall be deemed to be occupied by part of a train until the

time of clearance either through attachment to another train or removal. When the line has been cleared by attaching the above wagons/coaches to a different train or through other means, the user shall enter the train number to which they were attached, time and date of attachment, remarks( if any). The line shall be deemed to be clear from the time of attachment or removal.

2.1.5.3 Detentions

This option shall facilitate assigning the exact reason for all detentions affecting a train on its run over the board.

The options under this task shall include the following :

• Detention on run – Instantaneous Reporting

• Detention at Major Stations or Yards

• Detention-Based on Guard’s LTM (Only for passenger services)

Detention on run – Instantaneous Reporting

When the cause of the detention at a station or block section, is instantaneously known to the Section Controller (through the station staff or Guard of the train), then

System shall display, by default, the station code or the block section code,

where the loss has been computed.

 If the arrival has been reported for a train, the default display

will be only the preceding block section.

 If the departure has been reported for a train, the default display will be only the preceding station.

 If run through has been reported for a train, the default display

will be only the preceding block section

It shall also be possible for the user to select any other station or block

section from the graph display through GUI, where the train has suffered detention.

 System shall display by default the exact detention(in minutes) .

System shall also display the pre-defined list of departments to which the

detention is attributable and the user shall select the concerned department.

(30)

 System shall also facilitate adding any remarks.

System shall also provide for a new cause to be assigned (when not found in

the pre-defined list).

If the total detention was attributable to more than one department, system

shall facilitate multiple entries for each department, cause and detention. The total detention under various heads should not be less than the loss calculated by the system.

 User shall then submit details.

o On successful saving,

 Confirmation Message shall be displayed

Detention at Major Stations or Yards

This option shall be chosen by the user to enter detention details at major stations and yards including originating station, enroute station where shunting is involved for attaching/ detaching wagonsor coaches.

 The user shall then enter the station code where the task is to be reported.

 In case of trains ordered but not departed, the ETD shall be displayed.

 In case of trains on run, the Arrival time and Departure time shall be

displayed for guidance, if already reported.

 The form shall include the following fields :

 Time from

 Time to

 Activity

 Remarks

The system should provide for multiple entries at the same station covering all activities.

 The system shall facilitate back reporting for this task upto a period of 2

hours.

 The system shall also facilitate reporting of this event by any other actor

like TNC or Dy.CHC.

Detention-Based on Guard’s LTM

When the cause of the detention at a station or block section is immediately not known to the Section Controller and subsequently obtained from the LTM given by the Guard of the train, then

(31)

 The system shall display all train numbers based on direction for which the LTM has not been recorded (for a time interval of 6 Hours)

 User shall select the Train number.

 The system shall display the list of stations, block sections (over the

route of the train pertaining to the board) and enable the user to enter the detention time against each. The system shall also display the list of departments to which the delay can be attributed and the user shall select one of them.

 The system shall then display the possible causes under the particular

department for the user to select one or more of them.

 The user shall also have facility to assign any new reason not defined

in the list.

 In case the reason for a detention had not been instantaneously reported, the system shall assign the reason specified through the LTM form after validating the block section or the station to be the same. The sum total of detentions that was reported through the LTM task in the same block section or station should not be more than the detention shown by the system (as per charting).

 In case, the sum total of detentions reported through the LTM task in

the same block-section or station is more than the delay shown as per charting, the same shall be maintained separately.

 If the reason assigned for any detention (through LTM task) is

different from what had been assigned earlier, such details shall also be maintained train wise separately without overwriting the reason initially reported

Reckoning of utilization or non-utilization of Allowances

The following are the allowances provided as part of the inter-station running time (shown distinctly) over each section to set off the loss on account of speed restrictions and traffic causes.

1. Engineering allowance. 2. Traffic Allowance

The utilization or non-utilization of the allowance where provided should be arrived at based on comparing the actual inter station running time with the inter station running time excluding all allowances as per WTT.

Engineering allowance

 A specified time is given (train wise) at the last block section or in

(32)

 If loss had been calculated by the system due to one or more speed restriction in a block section, the default reason for the detention to be shown as CD.

 If gain had been calculated by the system due to absence of a speed

restriction in a block section (only where engineering allowance has been provided), the gain shall be assigned to CD.

 The cumulative loss on account of speed restrictions alone (not other

engineering failures) should be compared against the total engineering allowance for the train in the section to arrive at net loss or gain under ‘Engineering’.

The gain under engineering shall always equal the allowance provided over the section for the train.

Traffic Allowance

 A specified time is given (train wise) at the last block section or in

more than one block section over the section.

 The loss due to traffic may be due to any of the events given below :

o Unscheduled crossing or precedence

o Detention at signal (block section) due to arrival of a train from opposite direction.

o Acceleration/Deceleration for any unscheduled stopping.

 The gain due to traffic may be due to any of the events given below :

o Shifting of scheduled crossing including the time for acceleration/deceleration and stoppage at station.

o Reduced time for scheduled crossing.

o Starting a train from a station as per shifted timings (PTT).

o Traffic allowance provided as per WTT at a station or block section not being availed.

The gain under traffic will include the allowance and additional time made up on run as described above.

Loco Gain / Loss

 There is no system of providing any allowance under this

category in the inter-station running time (WTT).

 The loss on account of loco in a section can be due to:

o Bad running by the driver of the train. o Engine defects

o Excessive load over and above the hauling capacity of the engine.

 The gain on account of Loco can be due to:

o Running at Maximum permissible speed by the Driver. o Excessive over speeding

(33)

These details can be assigned by the system where explicitly known or obtained from the LTM and the loss or gain so reflected should get assigned to the (+) or (-) shown in the chart.

Any gain of more than 3 minutes in the inter station running time should be reckoned as ‘suspected over speeding’ and cause a blinking of the plot over that segment, till acknowledged by the user. This shall be repeated for every block section.

At the end of the section, the details of (engineering/traffic/loco gain or loss) shall get saved and shown in summary form for each train as a tool tip.

2.1.5.4 Priority Change

This option shall enable the user to change the priority for a train within the same group and over other groups on a particular day to cater to specific operational needs. However, the running of trains will be defined by pre-assigned priority under normal circumstances. In case of a need for assigning higher priority to a specific train within the same group, then

• The user shall choose one of the options :

o Passenger o Other trains

• The user shall then select the sub-group under the broad category (as above)

and the system shall display the list of all running trains under the same group.

• The user shall then rearrange the sequence order for a train (to be accorded

the higher priority) through drag and drop feature.

• The system shall then display a message seeking confirmation of the task. If

the user confirms, the information shall be saved. The system shall also signify this train in the chart through suitable visual indication.

• The system will cause all other trains within the defined group (based on relative position of the train) to wait for the prioritized train in case of a precedence/crossing. In respect of conflict with trains with lower or higher priority, the normal rules shall apply.

• In a double line section, such kind of prioritization can be assigned for one

train in each direction.

• On successful saving,

 Advance plotting graph shall get automatically refreshed. Refer

to Plot Graph use-case.

In case of a need for assigning higher priority to a specific train over all other groups, then

• The user shall choose one of the options :

o Passenger o Other trains

(34)

• The user shall then select the sub-group under the broad category (as above) and the system shall display the list of all running trains under the same group.

• The user shall then shuffle the priority group for a train (to be accorded the

higher priority) through drag and drop feature. If the sequence within the higher group is also to be changed, the same shall be facilitated as explained earlier.

• The system shall then display a message seeking confirmation of the task. If

the user confirms, the information shall be saved. The system shall also signify this train in the chart through suitable visual indication.

• The system will cause all other trains with priority lower than the specified

train to wait in case of a precedence/crossing.

• In respect of conflict with trains with higher priority, the normal rules shall

apply.

• On successful saving,

o Advance plotting graph shall get automatically refreshed. Refer to Plot Graph use-case.

2.1.5.5 Abnormal Working

This option shall enable the user to control the movement of trains during abnormal working situations and capture all essential data concerned with such movements.

The following situations shall be grouped under abnormal working of trains :

 Obstruction in Mid-section.

 Train Engine failed in Mid-section.

 Trains unable to haul its full load & Train parting.

 Work on line – Material Trains/Track Machines/Tower wagon

 Single line working on Double line.

2.1.5.5.1 Obstruction in Mid-section

This option shall enable the user to capture the movement of a train back to the starting station owing to obstruction on the line (block-section).

 The user shall select the train number

 The user shall select the block section by default.

The time of stoppage at the mid-section and the location (in terms of KMs or

OHE Mast) shall be entered.

 The reason for stopping shall also be entered.

 The time of restarting from the spot shall be entered.

 On reaching the starting station, the time of arrival shall be entered.

 The date and time of removal of the obstruction and the certifying authority

(35)

The affected block section shall be shown as obstructed in the plot graph from the date and time of message until the date and time of removal of the obstruction.

No other train shall be facilitated to enter the affected block section till the removal of the obstruction.

2.1.5.5.2 Train Engine failed in Mid-section.

This option shall enable the user to capture the movements associated with failure of Train engine in a block section.

The user shall select the block section by default.

The time of receipt of the message, location of failure and brief details of the message shall be recorded.

Any engine that is available closer to the location shall be made use of to

clear the affected train from the block section. This would mean using the engine of a train (Exp or Pass or Goods) waiting for crossing/precedence.

The system shall validate that an engine of a waiting train cannot be sent for

assistance unless detached from the said train. Like wise starting of a waiting train shall not be made possible unless an engine is attached to it.

The station from which the relief engine is sent shall be selected and the

time of departure shall be recorded.

The time of arrival at the spot shall be recorded.

 The time of departure from the mid-section shall be recorded.

On arrival at either of the stations, the time of arrival shall be recorded along with the station code.

2.1.5.5.3 Train unable to haul its load & Parting

This option shall enable the user to capture the movements associated with situations where the train is unable to haul its load or the train has parted in a block section.

 The user shall select the block section by default.

 The time of receipt of the message, location and brief details of the message shall be recorded.

The time of departure of the front portion (haul able no. of wagons)shall be

recorded.

 On arrival at the station in advance, the time of arrival of the front portion

shall be recorded.

 The same engine or any other engine shall be sent from either of the stations to clear the rear portion.

(36)

 The system shall validate that an engine of a waiting train cannot be sent for assistance unless detached from the said train. Like wise starting of a waiting train shall not be made possible unless an engine is attached to it.

 The time of departure of the engine and the station from it was sent shall be

recorded.

 The time of arrival of this engine at the spot shall be entered.

 The time of departure of the rear portion from the spot shall be entered.

 The time of arrival of the rear portion at either of the stations shall also be

recorded.

 In case of clearance in more than two portions,entry of details shall be

facilitated for each such movement.

2.1.5.5.4 Work on line – Material Trains/Track Machines/Tower wagon

This option shall enable the user to capture the movements associated with work on line permitted in the block section for maintenance or unloading of materials etc.

 The user shall select the train number from the list of running trains.

 The user shall select the block section and the line (Up/Dn) where required.

 The duration for which the work on line is permitted, reason and the

station where the train/machine shall clear section shall also be entered.

 The departure time and the station shall be entered.

 The train/machine shall be deemed to remain in the block section for

the specified duration.

 The arrival time and the station shall be recorded.

 The actual duration for which the work on line was availed will be

reckoned between the departure from the starting station till clearance of the block section at either of the stations.

2.1.5.5.5 Single line working on Double line

This option shall enable the user to capture the movements associated with temporary single line working on a double line section either due to maintenance blocks or due to accidents.

 The user shall enter the time and date of introduction of single line

working.

The user shall select the block section and the line (Up/Dn). In the event of

single line working spanning over more than two stations, then from station and to station shall be captured. The name of intermediate stations being temporarily closed shall also be captured.

(37)

The user shall also select one of the pre-defined causes for imposition of single line working.

The movement of trains during this phase shall be captured by the Arrival/Departure use case. Any wrong line movement shall be distinctly shown in the chart.

The inter station running time for wrong direction trains shall be calculated at a speed of 25 KMPH. A delay of 10 minutes shall be added for dispatch and reception of each wrong direction train between the two stations for the purpose of advance plotting.

The date and time of cancellation of single line working along with the certifying authority shall also be captured.

2.1.5.5.6 Accidents

This option shall enable the user to capture the movements associated with accident situation including ordering of relief trains and their despatch details from the base station.

 The time of sounding the siren shall be captured along with the names

of stations. This shall be deemed as the ordering time for accident relief trains. The user shall use the “Add New Train” option and create train for all the relief trains ordered immediately.

 The system shall automatically suspend “advance plotting” of all trains

in the section excluding accident relief trains.

 User shall enter the details pertaining to Accident relief trains (ART)

through this screen such as Time of sounding siren (appears by default), Time Train Engine Bahar line out, Time of attaching Train Engine, Train Ready time, Driver Name, Guard Name, Load summary.

 The details of coaches/ wagons by train such as coach/wagon type,

coach/wagon number and position from engine shall be entered.

 The date/ time of departure and the station with reason for late departure, if any, shall be recorded.

 After entering the details, the user shall submit details.

 On successful saving,

 Confirmation message shall be displayed.

 The movement of all other trains except the ART’s shall be regulated

at convenient stations until further instructions.

 In the event of other trains running in the section to be diverted/terminated short of destination/cancelled, the task shall be carried out through the menu under Train Ordering use-case.

In respect of movement of relief trains, Light Engine, Tower wagon and other departmental trains into the affected block-section, the following events shall be captured by the system.

(38)

 The time of departure of the train/vehicle and the station from shall be recorded. The destination shall be the affected block section. In case of a double line section, the line on which the train/vehicle was sent shall also be recorded.

 On arrival in the mid-section, the time of arrival shall be recorded (whenever known).

 The train/vehicle may be sent from either or both of the stations into

the affected block section.

 When the train/vehicle departs from the mid-section, the time of departure and the to station shall also be recorded (whenever known).

 The time of arrival of the train/vehicle at the station and the station

name shall also entered.

 The date and time of removal of obstruction, the date and time of

track certification, certifying authority shall also be captured.

 The affected block section shall be shown as obstructed in the plot

graph from the date and time of accident until the date and time of removal of the obstruction.

 The movement of trains at restricted speed, if any, after certification

shall be captured through the Caution Order use-case.

Pre-Conditions

• Detachment of loco option shall be enabled only when at least one loco is

attached to the train.

• Static database information should be available.

Post-Conditions

• Changes saved should be shown on the screen after successful save.

• Changes in any of details shall affect the graph.

• In an accident situation, the system shall be capable of retrieving and displaying

essential information on the various resources available (department wise) at stations over the Control Board for decision making by the Controller.

The information shall include the following:

o List of Level Crossings in the affected block section.

o Availability of Medical relief-Railway Hospitals/Dispensary, Portable Medical kit at stations, Location of Medical Relief Van.

o Availability of Catering facilities-Refreshment room, Restaurant

o Availability of Travelling Crane, Re-railing equipment under Mechanical department.

o Telephone number of the Railway Stations.

o Civil district of the place, important phone numbers of civil administration.

(39)

Business Rules

• In the event of any abnormal working like, Single line working on Double line

due to Engineering Blocks and Accident situation, the clearance of all trains that have entered the section from either end shall be ensured before allowing any traffic train into the block section. The ‘Advanced plotting’ use-case shall be functional only after ensuring this pre-condition.

• All timings reported under ART details should be between Time of sounding of

siren and Departure from the base station.

Assumptions

• Data from external systems should be available to this system.

• Maintenance of referential data on essential information pertaining to

assistance required during accidents and updating of the information.

USE-CASE Specification – Report Unusual Occurances

The purpose of this use case is to capture unusual happenings in the section. It also affects the plot graph use-case. It helps in locating the place of unusual occurrence over the section, cause, time/date and its effect on train movement.

Primary Actors

Section Controller (SC) Dy. Controller (Punctuality)

Flow of Events 2.1.6 Basic Flow

• System shall provide facility for the User to capture the unusual occurrences

over the sections within the board.

• System shall facilitate entering start date/time of all unusual occurrences.

• If an Unusual occurrence has happened at a station then

o System shall provide option for choosing the respective station where it has happened. This will also include provision for capturing the failure at a cabin, level crossing within the control of the station.

• If an Unusual occurrence has happened in a block section then

o System shall provide option for choosing the block section.

o System shall also provide option for entering exact location in terms of Kilometrage or OHE mast number.

o If the failure has occurred at level crossing, then the level crossing number and its location shall also be captured.

(40)

• System shall have facility to enter the expected rectification time for the unusual occurrence (This shall be useful for plot graph use-case (For Advance Plotting))

• User shall have facility to enter the preliminary cause of failure and expected

delay time for UP/DN/all Trains.

• System shall also provide option for entering any remark for each train

affected by the failure.

• During periods of fog, heavy rainfall and other adverse weather conditions

affecting train services, the system shall be capable of capturing the duration of such phenomenon and display the same against a station through suitable icons.

• After the failure is rectified or the cause of occurrence no longer exists, the system shall provide entering the end date/time of failure and the actual cause of failure (occurrence) as communicated by the maintenance staff or the station master. The duration of failure shall be computed automatically by the system.

Unusual occurrences in Block-Section

• If an unusual occurrence will result in detention to train(s) passing through

the affected block section during the period of failure, the system shall provide facility for identifying those trains distinctly as under:

 Up Trains

 Down Trains

 All Trains

 Select Train.

The default option shall be ‘All Trains’.

• Based on the above selection, the system shall implicitly assign the same as

the reason for detention. This shall be facilitated in both ways-instantaneous reporting and back reporting.

• Whenever back reporting is done, the cause shall be assigned only in

respect of trains where manual reporting has not been done. If already done, the specific remarks shall prevail.

• Where the total detention in a block section or station is to be apportioned to

more than one unusual occurrence, the same shall be displayed for

guidance and the user shall manually enter the detention pertaining to each occurrence.

Unusual occurrences at Stations

• In respect of failures at stations (e.g Signal or Point failure), which may or may not affect all trains, the system shall provide facility for identifying those trains distinctly as under:

 Up Trains

 Down Trains

(41)

 Select Train.

The default option shall be ‘Select Train’.

• Based on the above selection, the system shall implicitly assign the same as

the reason for detention.

Unusual occurrences affecting select trains

• The user shall select the Train number based on direction.

• The system shall facilitate entering brief details of the incident.

2.1.6.1 Unusuals – Signals

System shall have facility to capture different type of Signal Failures. They include o Signal Failure o Point Failure o Track Failure o Block Failure 2.1.6.1.1 Signal Failure

• User shall have facility to choose the Type of Signal, Signal

Number, Direction and Road Number for which the failure has occurred.

• User shall have facility to add new Signal type.

(42)

2.1.6.1.2 Point Failure

• User shall have facility for capturing the Point Number, Position

of Point and also the road number (line) for which the failure has occurred.

(43)

2.1.6.1.3 Track Failure

• User shall have facility to choose the Road number and the specific

Track number.

(44)

2.1.6.1.4 Block Failure

• This failure shall be block section and direction specific(only in Double

line) and not station specific.

• User shall have facility for selecting the pre-defined block failure types.

• User shall have facility for adding any new type of Block Failure also.

• This feature will also cater to circumstances in which Block instrument

working is suspended for obvious reason like entry of motor trolley into the block section, etc.

(45)

2.1.6.1.5 Unusual – Telecommunication

• System shall have facility for capturing Telecom failures affecting stations,

cabins, level crossing gates and control.

• The user shall enter the location1 and location2 between the equipment has

failed.

• System shall have facility for selecting the pre-defined list of types of failures under this head.

• System shall also provide facility for adding new type of failure, which is not

present in the pre-defined list of causes.

(46)

2.1.6.2 Alarm Chain Pulling (ACP)

• System shall have facility for capturing instances of ACP

• User shall have facility to choose the UP/DN passenger Train in which the

event has taken place.

• User shall also have facility to enter or select the Coach Type, Coach Number, position from engine.

• User shall also enter brief description of the incident.

(47)

2.1.6.3 Unusual - Commercial

• System shall have facility for capturing unusual occurrences

attributable to the Commercial department.

• User shall have facility to choose the UP/DN Trains.

• User shall have facility for selecting the pre-defined types of occurrences under this head.

• User shall also have facility for adding new type of occurrences

• In case of delay in loading/unloading, the user shall also have facility to enter the number of articles loaded/unloaded by the train leading to the extra time delay.

• User shall have facility to enter the preliminary cause for the occurrence and

expected time delay for each or all Trains.

• User shall also have facility to enter the actual delay for single/multiple

trains, which have been affected by the occurrence. System shall provide option for entering additional remark for each train affected by the event.

(48)

2.1.6.4 Unusual -Traffic

• System shall have facility for capturing unusual instances attributable

to the traffic department.

• User shall select the UP/DN Train number.

• User shall have facility for selecting the pre-defined instances under

this category .

• User shall also have facility to add new type of instances.

• User shall also have the option to indicate the exact cause for all

instances under this category.

(49)

(50)

2.1.6.5 Unusual - Loco

• System shall have facility for capturing all types of delays attributable

to the locomotive including failure.

• User shall have facility to choose the UP/DN Train.

• System shall provide the list of Locos attached to the selected Trains.

• User shall have facility for selecting the one or more of pre-defined

Loco Failures types and other occurrences.

• User has also facility to add new types of failures or instances.

(51)

2.1.6.6 Unusual - Engineering

• System shall have facility for capturing all delays and failures attributable to the Engineering department.

• User shall select one of the options :

o Open line (Default option) o Construction

• User shall have facility for selecting the pre-defined types of failures

and other instances.

• User has also facility to add new type of failures or instances.

(52)

2.1.6.7 Unusual – C&W

• System shall have facility for capturing all delays and failures attributable to the mechanical department.

• User shall have facility to choose the UP/DN Train.

• If selected train is passenger type, then

 User shall have facility to select or enter the Owning Railway, Coach

Type and Coach Number.

• If selected train is goods, then

 User shall have facility to select or enter the Owning Railway, Wagon

Type and Wagon Number.

• User shall have facility to select one or more of the pre-defined failures type or instances.

• User shall have facility to add new types of failures or instances.

(53)

2.1.6.8 Unusual - Electrical

System shall have facility for capturing various type of failures or instances attributable to the following branches of Electrical department

o Train lighting and A/C o Traction

2.1.6.8.1 Train Lighting and A/C

• User shall have facility to choose the UP/DN Passenger Trains

• User shall have facility to select one or more of the pre-defined

failure types or instances.

• User shall also have facility to add new types of failures or instances.

(54)

2.1.6.8.2 Traction

• User shall have facility to select one or more of the pre-defined

failure types or instances.

• User shall also have facility to add new types of failures or instances.