System shall provide reports related to punctuality, loco and operation of trains to the Management users.
2.1.17.1 Reports related to punctuality of trains: 1. Trains Lost
• This report shall show the details of the trains lost over a division
Passenger trains) and direction wise and train wise, which shall include the time lost, station at which the time is lost, reason for time loss and remarks.
• System shall provide option for choosing the date for getting the Divisional
Trains Lost report.
• System shall show the data for time loss at different stations and reason/remarks against a train. The report shall have following attributes:
o Sl.No
o Train Number
o Orign/Taking over station code o Dep Status (RT/LT-If LT in Mts) o Enroute Junction code
o Arrl/Dep Status (RT/LT-If LT in Mts) o Destn/Handing over station code o Arrl Status (RT/LT-If LT in Mts) o Primary Responsibility-Department
o Place of Detention (Sttn or Block-section) o Time Loss
o Reason o Remarks
o Recovery Details [Summary for the entire run over the Division]
Engg Gain Engg Loss Traffic Gain Traffic Loss Loco Gain Loco Loss 2. Punctuality Performance(Summary)
• This report shall show the punctuality performance of all
trains as a percentage in summary form.
• System shall provide option for choosing the date for getting the Divisional
Punctuality Report.
• System shall have capability to show report for the following categories of
trains.
M.R. Trains
Mail Express Trains
Passenger Trains
• The report should include the following headings
Daily percentage (% of RT Trains over Total No of trains run)
Average Percentage for the year (1st April to 31st March)
Late Trains for the day
• Under each category of trains, the punctuality performance to be reckoned separately under following categories:
On dot Trains – RT Dep and BT/RT Arrl
NLT Trains-Taken over Late and Arrl Late(No additional loss)
o Example –TO 45 Mts and Arrl 45 Mts
3. Punctuality performance of all trains
• This report shall show the punctuality performance of all trains run
over a division on a particular date. The details shall be shown category wise(MR Trains,Daily Mail/Exp trains, Non-daily Mail/Exp trains, Special Trains and Passenger trains) and direction wise and train wise.
• System shall provide option for choosing the date for getting the Divisional
Punctuality performance report.
• The report shall have following attributes:
o Sl.No
o Train Number
o Orign/Taking over station code o Dep Status (RT/LT-If LT in Mts)
o Enroute Junction code * - Only for Express Trains
o Arrl/Dep Status (RT/LT-If LT in Mts)* - Only for Express Trains o Destn/Handing over station code
o Arrl Status (RT/LT-If LT in Mts)
o Place of Detention (Sttn or Block-section code) o Time Loss
o Reason
The details in respect of the last three columns should be be shown in a delimited form in a single row for each train.
4. Punctuality performance of specified train
• This report shall show the punctuality performance of a specific
train run over a division for a configurable period
• System shall provide option for choosing the Train Number, From date and
To date for getting the Punctuality performance Report.
• The report shall have following attributes:
o Sl.No o Date of run
o Orign/Taking over station code o Dep Status (RT/LT-If LT in Mts)
o Destn/Handing over station code o Arrl Status (RT/LT-If LT in Mts)
o Place of Detention (Sttn or Block-section code) o Time Loss
o Reason
The details in respect of the last three columns should be be shown in a delimited form in a single row for each date of run.
2.1.17.2 Reports related to locomotives: 1. Locomotives due for Schedule
• This report shall show the details of locomotives due for
schedule as at 0000 Hours.
• If there is more than one gauge in a Division, the report shall be gauge wise
• The report shall be grouped traction wise-Diesel and Electric.
• The No.of locomotives on line at 0000 Hrs shall be shown under each group.
• The report shall have the following columns :
o Loco Number o Base shed o Train worked
o Location at 0000 Hours o Schedule Due Code o Schedule due Date
2.1.17.3 Reports related to freight operations. 1. Interchange of Trains (‘Y’ day)
• This report shall give the details of goods trains including Light engine taken
over and handed over from/to adjacent divisions during 24 hours for (D-1) day i.e yesterday.
• The details shall be furnished division wise.
• The sub-division shall include :
Taken over
Handed over
• Under each sub-division, the details shall include :
Sl.No Train Name Loco Numbers(s)
Double headed or Multiple Unit (If more than 2 locomotives) Time
No.of units (Load)
• Summary for each sub-division showing :
No.of trains
No.of Engines-Electric
No.of Engines-Diesel
Total No.of units
2. Interchange Forecast
• This report shall give the details of goods trains including Light engine planned to be taken over and handed over from/to adjacent divisions during 24 hours for the current day (Sys date).
• The details shall be furnished division wise.
• The sub-division shall include :
To be taken over
To be Handed over
• Under each sub-division, the details shall include :
Sl.No Train Name Loco Numbers(s)
Double headed or Multiple Unit (If more than 2 locomotives) Expected Time
No.of units (Load)
• Summary for each sub-division showing :
No.of trains
No.of Engines-Electric
No.of Engines-Diesel
Total No.of units
3. Hours of Run (Section wise)
• This report shall show the details of the goods trains run in a division, section wise and direction wise on a particular date.
• System shall provide option for choosing the date for generating the Divisional Hours of Run report.
• System shall have capability to show report with the following attributes.
o Section
o Length in Kms o No.of Trains run o Total Hours of run
o Average Hours of run per Train o Average speed per train
4. Hours of Run (Train wise)
• This report shall show the details of the goods trains run in a division, section wise and direction wise on a particular date.
• System shall provide option for choosing the date for generating the Divisional Hours of Run report.
• System shall have capability to show the following headings :
o Train Name o Train sub type o Loco Number o Gross Load o Stock Type
o Arrival and Departure Timings at various stations o Time taken sectionwise
o Average speed section wise o Total Time taken for the entire run o Average speed
5. POL Rakes Position
• This report shall show the details of POL rakes in a
division at 0000 hours for a given date.
• System shall provide option for choosing the date for
generating the report.
• The report shall be grouped under :
Loaded Rakes
Empty Rakes
• Under each group, the details shall include :
Train Name
Station (Based on departure)
2.1.17.4 Reports related to operations of trains:
1. Unusual Occurrence Report
• This report shall reflect the details of of all unusual
occurrences occurring within the division during a day (from 0000 hrs to 2400 hrs).
• System shall provide option for choosing the from and to date for getting the
Divisional Unusual Occurrence report (By default it shall be only for D-1 date)
• System shall have capability to report the occurrences under two major parts:
Part-A : Events affecting punctuality of trains.
Part-B : Events not affecting punctuality of trains.
• The report shall be grouped department wise.
• The first part of the report under each department shall include the summary details :
Total no.of failures for the day (Section wise)
Cumulative no.of failures for the current month(section wise)
Cumulative no.of failures for the current year(section wise)
Under each department, the details to be shown shall include :
o Failure sub-type [e.g Signal/Point/Block/Track
Failure]
o Place of failure [ Station or Block section]
o Time & date of failure
o Time & date of rectification
o Id of Equipment or Gear at fault. [Signal No./
Loco No. etc]
o Base Shed [Only in case
of Loco failure]
o Train Number(s) affected
o Delay in minutes
o Remarks
2. Temporary Speed Restrictions (Day Wise)
• This report shall show the details of temporary speed
instructions in force over a division on a given date.
• The user may also specify a period (by giving the from and to date) for which
the report is to be generated. In this case only the cautions in force during the specified period shall be listed [(i.e) imposed and cancelled/not cancelled as on to_date]
• The user may also have option to select a particular gauge or section. The
default parameter will however be all gauge and all sections.
• The report shall be grouped – gauge wise, section wise
• In respect of Double line and multiple line sections, the report shall be shown
separately line wise and direction wise
• The report shall also be sub grouped on department-open line / construction / others.
• The number of temporary speed restrictions permitted for each department,
section wise ith permitted time loss shall be maintained as a referential table. This shall be shown against each section as under :
o Number of works permitted o Total duration (in minutes)
• The report shall include the following columns:
o Sl.No
o From station o To station
o Location from (Kms or OHE post) o Location To (Kms or OHE post) o Length in Kms
o Speed o Reason
o Date of initial imposition o Date from which changed
o No.of days in force (reckoned as on to_date) o Date of probable removal
[ Any caution with more than one stretch of speed restriction for the same work will be deemed as a single caution. If two or more works are in force in the same block section, they shall be deemed as separate cautions]
• This report shall give the details of maintenance blocks requested and blocks granted during a day (24 Hours) for a given date.
• The user shall also be facilitated to specify from and to date for the report to be generated for any period.
• The details shall include :
Sl.No
Section
Between Stations
Line – Up/Dn (where applicable)
Location (Kms or OHE mast)
Requested-From time Requested-To time Requested duration Permitted-From Time Permitted-To Time Permitted Duration Availed-From Time Availed-To Time Availed Duration
Purpose or Nature of work
Whether corridor block or not.
% of Permitted Duration to Requested Duration.
% of Availed Duration to Requested Duration.
Remarks
4. Programmed Maintenance Blocks
• This report shall reflect the details of blocks requested
during the period of next 72 hours (D + 2day)
• System shall provide option for choosing the from and to date also, if when
required.
• The details shall include:
Date
Section
Line No
Between stations
Location (Kms or OHE Mast)
Requested-From time
Requested-To time
Requested Duration
5. Running Lines out of use at Stations / Yards
• This report shall reflect the details of running lines not
available for traffic use at a station/yard either due to maintenance work or other reasons.
• System shall provide option to the user for specifying the from date and to
date in case of any specific requirement.
• The details shall include :
Station code
Line Number
Main or Loop
With or without Platform
Date from which not available
Reason
6. Stabled Trains Report
• This report shall furnish the details of stabled loads over
the division as at 0000 Hours for each day.
• System shall provide option to the user for specifying the from date and to
date in case of any specific requirement
• The report shall be grouped under :
• Coaching stock
• Freight Stock
• In respect of Freight stock , a train shall be deemed to have been stabled
only after lapse of 24 Hours from the time of arrival at the station. This factor should be taken care of while identifying such trains.
• The details shall include :
o Station
o Train Number o Load Summary
o Time & Date of Arrival o Reason
7. Delayed Wagons Report
• This report shall include the details of delayed loaded and empty wagons at
intermediate stations in a division as at 0000 Hours.
• The report shall include the following columns :
o Sl.No o Section o Station code
o Wagon Details – Owning Railway, Wagon type, Wagon Number o Load/Empty
o From station o To station
o Detachment-Train Number o Detachment-Time/Date o Detachment Reason
o No.of days since detachment (Sys date – detach date) o Remarks
Any other user requirement in the form of MIS Reports shall be taken up in the later phase of development based on mutual discussion.
Assumptions
Data from external systems should be available to this system.
USE-CASE Specification – Yard Management
This use case shall facilitate capturing of line position at configurable intervals at nominated yards/stations or at specified hours of the day.
Primary Actors
Section Controller Train Clerk.
Flow Of Events