Railway crew management in India

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Indian Railway, the world's largest network (under a single management), consists of more than 100,000 Train Drivers/Assistant Drivers/Guards, which forms the basic functioning team, responsible for Train Operations.

Classification of Loco Pilots and guards[edit]

How vigorous is the job profile can be noted from this very fact that the Railway recruits persons as 'Assistant Loco Pilot' . They work on freight trains for as long as 10–12 years. During this tenure they are supposed to work with experienced Train Drivers and perform only assisting work during the run of a locomotive i.e. a train. An Assistant Driver thus learns the tactics and dos and don'ts required for train operation. Thereafter they are promoted as 'Loco Pilot Shunter', after proper courses and practical trainings, wherein they are supposed to drive locomotives in sheds/yards at not more than 15 km/h speeds. After experiencing for not less than two years, they are promoted as 'Loco Pilot/Goods', who are always monitored by their respective 'Loco Inspectors'.

A train has typical an Assistant Loco Pilot and a Loco Pilot on the Locomotive. The Assistants are normally common but Loco Pilots fall in various categories like Goods Drivers (or Loco Pilots used for running goods trains), Passenger Driver (Driver used to run slow moving Passenger carrying Trains), Mail Express Driver (Driver used to run high speed Passenger carrying Trains) and Rajdhani Drivers (Used for very high speed passenger carrying trains). There is yet another category of crew called 'Shunters' who operate only in yards, for moving trains within a particular station yard. Normally Shunters work alone without an Assistant.

The train at the rear end has Guards as its crew. They are categorised as goods guards, passenger guards and mail express guards based on the type of train on which they are working.

Earlier working scenario[edit]

The job of a Loco Pilot consists of irregular rest and working hours, eating disorders, and sleep disorders. That is why the Railway spends a lot on their trainings and resting time. They are booked from a crew changing point, informed well in advance, after ensuring that they have taken sufficient rest and completed all required trainings and requirements, those are mandatory for train operation. At the end of the journey, they are sent to well maintained rest rooms, given meals (home cooked) and rebooked back to their headquarters after giving minimum stipulated rest.

Latest developments[edit]

Centre for Railway Information Systems New Delhi, an IT development unit for Indian Railways, has developed a software named 'Crew Management System', wherein bookings of this sensitive category of people, which was done manually till now and monitored at various levels by Inspectors and Officers, is arranged through software. Crew Management System(CMS) is a unique system in which accuracy and monitoring is automatically maintained. The software system was rolled out in December 2007 and already installed at about 2200 data entry nodes at over 290 crew booking points. These are spread over entire Indian Railways. CMS at present has a database covering 89,000 crew members and over 30000 crew members are being booked daily through the system. The work has been completed and provided with Thin clients connected to a server cluster at CRIS, wherein all the functions like crew bookings, call served to crews, their signing on duties are done through computers after ensuring their rest,training and medical particulars. The job which was done manually till a few years back is now monitored automatically. Not only it has a single data base of all the running staff of Indian Railways, but also have an all around reports(more than 500 reports of these crews are visible to the monitoring authorities of the Railways). All the officers sitting in their offices can monitor performance reports of the train operating staff. This enhances the performance planning by the officers. The Ministry of Railways is also doing a great job by motivating such projects and giving sufficient funds for same. A Project which was initially started in Nov 2006 with a team of 5-6 software persons is now managed by a GM rank officer with a dedicated team of software developers and domain experts, who are basically attached to driving jobs since the last 15–20 years. The system caters for All gauges BG, MG, NG now.

Brief technical particulars[edit]

The CMS software is Industry standard software using middle-ware and products, hardware components and LAN/WAN network components. The business transactions are transacted so as to provide timely information with increased productivity and reduced paper work to a great extent at the lobby locations. The CMS system is being implemented in the Railways Lobbies at 306 lobby (Location where Railways crew are booked) locations with touch screen along with biometric devices for Sign-On/Off of crew from their duties. The CMS software uses FOIS and Railways network with adequate provision for security in the system so that it is not be vulnerable to hacking from outside. It also has on-line application processing (distributed) & data inter-viewing at the Divisional and Zonal offices.

The different applications of CMS require various levels of organization hierarchy to access it via a web browser. This application extends to various stakeholders and provides a single window interface to the Train Crew.

The CMS software is a centralized architecture using n-tier Java EE architecture with Web Services/Struts framework which works in online mode. All the stakeholders access the applications after user authentication and authorization. The solution has high scalability, flexibility, reliability and is complaint to industry Open Standard specifications. The software solution is :-

• Compliant to n-tier Java EE architecture.

• Seamless integration of enterprise systems with the existing business applications.

Single sign-on feature.

• Open-standards platform supports web service.

• Extending existing applications for multiple devices.

• Utilizing full advantage of device features for management and interactions from a central location i.e. CRIS.

• User friendliness.

• End to end linux based System.

• Browser access via kiosks and thin clients access.

• Comprehensive data validations during capturing.

• Industry standards security features.

• Interface with SMS gateway for information dissemination and verification.

• Online pre-formatted and flexible period report generation.

• Highly flexible and high available solution with 24 x 7 uptime.

Context sensitive help.

The software is in house software assisted by IBM & HCL in the designs and performance optimisation of the software. These steps are primarily for ensuring a robust and scalable architecture that conforms to open standards and promotes inter-operability duly taking care of the security concerns. The design and implementation of the CMS is expected to lead to the evolution of a truly robust architecture based on the principle of inter-operability and open standards.

SMS feature[edit]

The Crew Management System software has a unique feature of booking the crew through SMS. It is sent to the crew through the central database to serve it a call.If the crew acknowledges the call by sending back an acknowledgment through SMS, the crew is booked. This is done for those crews who reside farther than 7–8 km from the crew booking location, else a call boy is sent for the same.Thus the software facilitates faster crew booking.

System generated alerts are also sent to the required personnel in the following manner:-

a) Morning position of crew strength at various crew booking locations.

b) Alerts for crew strength at particular crew booking point going below a critical limit.

c) Automated alerts for their nominated Inspector, for crew becoming due for monitoring.

d) The crew can have his personnel information like turn of crew booking, Status, PME, Mileage and other Training due dates on his Mobile.

e) Congratulations on birthdays to crew members of whom date of birth are with the database.

Biometrics sign on/off feature[edit]

With the help of the Crew Management System software, sign on/sign off of crew members has become extremely easy. At the lobby, they are provided with Kiosks, where they use their thumb impression to sign on/sign off.This has removed the need of their signing in registers or remembering passwords. It is very user friendly and easily adaptable by the crew. Also, it has increased security and authentication as it eliminates the possibility of Proxy reporting.It is legally binding. Now BA (Breathalyzer) capabilities are being added to Kiosks.It is very important from the point of view of safety running of the train. Herein, the crew blows from his mouth into the device, and if there is any alcohol content found,a thorough check is done.

Central server architecture[edit]

Central server architecture consists of a set of 13 server which work in unison. Users access the CMS applications via browser interface. As per the CMS application requirements, the application is deployed in centralized environments with online LAN/WAN (FOIS) connectivity. The CMS system supports the stakeholders and has a centralized architecture based on the deployment pattern. The CMS system supports the browser-based clients originated from respective places.

The details of servers are

  1. Edge Server in Active / Passive cluster mode.
  2. Web sphere ND in cluster Mode at OS as well as Application mode.
  3. Database servers in Main Standby Cluster mode.
  4. Tape Back up in LTO
  5. SMS server to upload the smses to SMS gateway and response to the incoming smses to the clients.
  6. LDAP directory server for user Authentication and security also in cluster.

Benefits of computerization of Crew Management System[edit]

• All crewing information is readily available through a common data platform.

• All offices are synchronized at all times.

• Graphical User Interface for planning as well as for running daily operations with full checking mechanism.

• Time saving: crewing and payroll data need only be entered once.

• A combined system for crewing and payroll saves time and money

The software solution automates the day-to-day business functions of the crew thereby providing information of their status, rostering their duty allocations, providing information on the availability of crew at their home station and assigning crew to the trains. All this leads to better crew management. CMS has been developed to bring in transparency and greater accuracy of information so that decision makers can take effective business decisions to control crew and optimize on crew utilization. It provides for global tracking of all the crew on the CMS system in real time whether the crew is on train, resting at HQ, resting at outstation, on leave or training.

The system gives the planner optimum flexibility to construct highly efficient crew duty blocks resulting in improved crew utilization based on all national and company legal requirements. This can create corresponding reductions in manpower and costs. The solution architect for the CMS Solution is Environmental friendly and has been designed in such a way that the CMS uses the TFT and thin client technology which saves lot of power for each crew booking locations over the conventional PC's and CRT monitors based system.

CMS is fully integrated, it maintain complete overall day-to-day administrative and operational control of the total crew resources throughout Rail route network. Quickly identifies additional crew resources to meet unforeseen situations. Availability, priority of presentation and any restrictions are listed in accordance with User-defined rules. Automatically identifies illegal or unqualified crews in accordance with pre-defined User rail regulations. Automatically generates crew schedule.

CMS database holds all the necessary information about each crew member including: basic data such as name, address, gender, nationality, date of birth and phone numbers

personal skills such as language speaking and professional skills such as the types of Crew and trainers' qualifications complete record of promotions - changes of rank, Keep a record of all training taken and the dates when they need to be renewed.

To break the monotony of crew while waiting for their turn at the crew booking lobby a quiz has been provided. QUICK implies Quiz for Improving Crew Knowledge. This is a crew knowledge evaluation and improvement Game.New Software Functionality in CMS ver 4.0

The CMS version 4.0, the release in Oct - 2013 shall have the following features.

   Change in Sign ON time after Sign ON approval
   Sign ON time can be edited at the time of Sign ON approval . This and other data can also be edited if flow is directed to manual at the time of Sign OFF. Editing of already approved sign ON time shall not be permitted in manual
   Conversion of absent to non run
   In the current system non run can be edited upto the time crew is not broguht back. A new provision is to be provided for conversion of absent cases to a valid non run reason at a later date.This new development will have the following aspects-
       Non Run to have additional button for converting absent to non run
       list all the crew who were absent (atleast once) in last three(defineable) months.
       Select the crew whose absent entry needs to be changed
       Display all the absent occassions of that crew for last 3 months
       Absent reason for the absent period can be changed to any of the following reason only CL ,CCL,ChCL,IOD,LAP,LHAP,ML,PL,PSICK,SICK,SCL
       data entered in this form will have no repurcurssions to the crew working data in CMS database. (e.g. working hrs etc)
       all the data entered in this form will be saved seperately without any linkage to any other CMS data
       After changing absent to other non run , monthly, forthnightly, overtime, crew run detail, muster roll, reports printed / viewed after the change, will show the details of the change and its impact on mileage as a seprate entry at the end of report / page. The original mileage/OT generated will not be changed on account of regularisation.
       Progessive hrs: Credit for hrs because of conversion from absent to leave will be added to progressive hrs only if period is an active fortnight and also will be added only after date of conversion. For the past fortnight no such addition is required in progressive hrs.
   Logging of reason at the time of supervisor approval
   Supervisor can edit some values date / time of sign on off of crew , Rest availed Loco no (for Loco pilot only, same will be stored against ALP and Guard) (Loco no cannot be edited after this in the application from any other form) at the time of approval. Now supervisor will be required to give a valid reason for any change done at the time of approval. Both the values i.e. previous / changed will also be stored for reports.
   Departure date and time validation in PDD form
   A the time of departure date time entry in PDD form system will validate the date and time entered against the highest date and time of Sign On for any crew on that particular TA.
   Entry of Dep and Arr time for PDD/PAD for manaul runs
   PDD/PAD form is populated for Sign ON / Sign OFF through KIOSK. This for shoul be populated for run from manual data entry. Runs originating / terminating at a particular lobby will only be shown in the PDD/PAD form of that lobby. Two new columns to be added in mannual crew movement Arrival time (<signoff time) and departure time(>signon time)
   Rest modification for shunter
   In the rest modification form a new option only for shunter and Sr Shunter (original designation) given 16 hrs to 32/56 hrs
   Station sequence no in sign off approval
   Change the colour of TO station if changed from TA Indicate the sequence no of the TO station in bracket (applicable for multiple occurences only)
   Panelled Crew in biodata
   Add one more filed in biodata Panelled. Now ony panelled crew can be officiated.
   Ghat competency
   If a route has ghat section , Ghat section competency (GHC) shall be checked while fetching crew as per rule (Requirement similar to auto signalling)
   Seperate option of WR/WOR for pilot and ast
   In booking page sepereate option of booking with rule and without rule to be provided for pilot and asst pilot.
   Psychological Test Date feeding Option
   Prior date feeding option to be opened for Psychological test. i.e. Psychological test date can be before date of appointment.
   Reason for fetch crew all booking
   reason is to be recorded for exercising the fetch crew all option.
   Grade D
   Crew in category D is to be treated as inactive like Drafted but will appear in on roll strentgh Mileage will be 1% Similarly temp transfer shall also be shown as on roll
   provision for RUID
   provision for RUID
   prevent tab based usage
   Critical forms like crew booking, biodata,singon on behalf of sup etc are to be attempted first
   Coal service types
   Option in manual CTR form to fill all service types of coal pilot lobbies has been given for all lobbies even if they are not coal lobbies, Now service type will be linked to the fact of lobby beign coal lobby i.e if there is any coal configuraion.
   Traction should not be updated for duty type SPARE
   we are checking traction while booking crew through TA and updating crew traction on the basis of TA. Traction should not be updated for duty type spare.
   For TA Duty type spare and dead in Fetch crew as per rule option LR is not to be checked
   While booking crew Spare and dead through TA as per rule, LR not to be checked for fetching crew.
   Date of imposition in caution order
   In caution order entry form a new field Date of Imposition should be entered by the user In caution order entry form cautionorder to be sorted on starting station
   Last promotion date
   Last promotion date should now be verified from appointment post in biodata. Eg:1. Â If designation is ALP, and appointment post is APP Asst, then last promotion date should not be mandatory. 2. Â If designation is ALP, and appointment post is other then APP Asst, then last promotion date should be mandatory.
   mileage for continuos duty
   configurable if min guranteed is to be taken into account for continuosu duty cofigurable for lobby. In this case if run is for min gurantee section then next / previous run will always be treated as discontinuous run
   Temp transfer
   Temp Transfer of crew of base lobby A can be performed by base lobby . temp transferd crew can be send back to the base lobby only
   Dual status of crew
   If the crew has worked partially on that day and also available before 00.00, then leave can be granted from the day but leave will start from the time of availability insted of 00.00 hrs. The muster will show dual status - working/leave.
   Updating ASIG through Non run
   ASIG should be updated through non run and due date to be calculated based on the configured value by the user in lobby configuration. If the result is awaited or fail, then crew can work the trains in non automatic signalling routes. automatic signalling routes will be defined by the user while creating the routes.
   Shunter temp transfer to CMS lobby
   Shunter can be transferred temp to NCMS point at present Facility extended for temp transfer to CMS lobby (Rule not available) OSRA and spare allowance for going and coming back will be applicable as in case of LP and ALP etc.
   An option to be provided where user can search the circular entered by them and then delete if required. now user can enter only the valid till date.
   Abnormality reporting for Shunter worked through TA as well as roaster
   shunting TA will come while searching in sup.reort abnormilty console.
   Further development in Roster for non run
   Night rest cannot be followed by Weekly rest. Provision to add leave has to be introduced in non run roster with leave logic of < 12:00 hrs leave on the same day > 12:00 hrs leave from next day
   facility to bring back drafted
   Drafted should be treated as temp inactive so that lobby can bring it back and make it active
   PR cancellation
   Record of PR cancellation to be maintained for the reports( PR Cancellation,PR due,Crew Run Details). at the time of call serve itself PR will get cancelled if applicable.
   Inactive reason
   Inactive reason to be bifurcated in biodta as Temp Inactive and Permanent Inactive
   CMS - FOIS Integration
   Integration in PDD form
   Presently in PDD form loco no is non-editable once mapped with FOIS data, however in most of the cases loco no also gets changed at crew changing point, so facility to edit loco number in PDD form to be given.
   Crew Data to FOIS
   Crew Position for previous date is required to be integrated with FOIS application. FOIS will show the data in its report- RB404:Availability of Loco Pilots and Guards as on date :DD-MM-YYYY
   CMS - RBS Integration
   Route Creation
   Now at the time of creation of routes data is taken from live Route data from RBS. Apart from the Freight Routes now Coach routes will also be selected from the applications form.
   Management - Avg Rest
   Zone - Div - Lobby Single day report (previous day), Select period (Date picker) not possible as on roll strength may vary from day to day Select crew type (standard list) Display fields Crew type, HQ crew/ HQ rest (drill down crew wise) HQ crew / OS rest (drill down lobby wise - crew wise) OS crew / HQ rest (drill down lobby wise - crew wise) On roll strength {SUM rest / sign on (sign off at Lobby)} Count of no . of CREW
   Personal mobile no report
   Report to have date filter with following fields with drill down feature Crew type, total sign ON (COUNT), Sign on with pers mobile COUNT), pers mobile used (COUNT) Drill down to have following fields Crew ID, Crew ame, Sign ON Time, Sign ON station, Sign OFF time, Sign OFF Station, Route, Pers mobile no, Reason for use
   delay in Feeding of Manual data entry or in sign of approval
   Management - Delay in Sign OFF Crew id, Name, From, To, Train, Loco No., Train arrival time (from FOIS and ICMS), train arr time (as per PDD form), Sign off time, TNC id, Sup id, Dif in train arr(FOIS) and actual sign off, dif in train arr (PDD) and actual sign off
   Ver 4.0 New report for LR
   Fields Crew name, crew id, LR sections (as per LR master) Y for crew having LR at any time N for crew never having LR in that section Additional character with Y if # LR due in 10 days (tool tip to give exact due date) * LR over due
   Insert of three column in current crew position grill doen.
       Train (Last Train Booked for rest and current for signon)
       Duty Type for Signon (Last Duty Type for rest)
       Last Periodic rest (Date Time/Duration) 
   Insert of One column in all five crew availability report for Last Duty Hours
   1. Last Duty Hours
   One more Mileage Report for the crew who are inactive in status
   The crew who are inactive can have mileage of the period when they are active.
   Mobile No authentication in all places
       12 Digit
       Starting with 91 
   Configuration of SMS in Lobby configuration console
   Configuration of SMS in Lobby configuration console according to new SMS configuration table designed by GM Sir
   Management-Working report
       New column for Total duty hrs against contineous run to be added.
       Sorting in contineous run to be corrected.
       Another field to select date filter is required. 
   SMS groups Data
   All the groups of SMS which are configured from Lobby Configuration Console to be shown in the report along with their whole data stored in Database.
   DataBase Work
   Addition of two column in mileage table for Departure and Arrival time. The precedence by which they are to be populated are:
       Data filled by Lobbies.
       FOIS Arrivale and Departure Data.
       N.A. (Not having information) 
   The data to be populated along with other data while generation of Mileage.
   Crew Search - CREW Run Details
   Addition of two columns in Crew Run Details for Departure and Arrival of the Loco.
       Departure - Data to be populated after Sign On column
       Arrival - Data to be populated before Sign Off column 
   Management - Working Hours
   One more option for the selection for the data of working hours for Wheel on-off along with the sign on-off in the new selection criteria with Radio Buttons. One Column to be added for the Data which have not any filling of data for Arrival OR Departure Time with Heading 'NA' Addition of Three columns in Drill Down Report.
       Departure - Data to be populated after Sign On column.
       Arrival - Data to be populated before Sign Off column.
       Wheel Movement - Time difference between the two columns. 
   non run cancellation
   New report for cancellation of non run with following columns
       CREW ID
       CREW NAME
       CREW TYPE
       FROM DATE
       TO DATE
   Manage - Crew Position
   Traction and Cadre to be included in Filter
   Crew Search - CREW Run Details
   A list of the Name of the Lobby crew and Crew Id to be shown in the drop down table after the data of list be selected the crew id to be shown in the crew id text box and crew search can be executed then.
   PR count due
   The Query to be refreshed (as in CMS application)
   Loco Inspector
   The query to be modified for Divisional level setting in place of Lobby. The councelling and grading settings for due date is fixed from division now.
   Mileage --> Over Time
   one column added and three columns altered in this report.
       Low rate OT (Running Hrs. - Roster Hrs (Low)) (If Running Hrs. > Roster Hrs (Low))
       High rate OT (Running Hrs. - Roster Hrs (High)) (Running Hrs. - Roster Hrs (HIgh))
       Roster Hrs (Low) = 104/14*No.of Hrs Worked
       Roster Hrs (High) = 108/14*No.of Hrs Worked
       Over Duty=Running Hrs. - Roster Hrs (Low) 
   In over time statement add two Column
       Crew Type
       Absent Days 
   Manage --> Working Hrs (Zonal Level)
   Division Column along with other
   Manage --> Working Hrs (Division Level)
   Lobby Column along with other
   Manage --> Working Hrs (Lobby Level)
       Percentage of each column with respect to Total.
       Columns are Wheel movement of 10 Hrs, rest are from signon-off 10, 10-12, 12-13, 13-14, 14 and above 
   Working Hours report
   In Working Hours report all the working particulars of crew < 8 Hrs, 10-12 Hrs, 12-14 Hrs, >14 Hrs are displaying through hyper link but in Total Hrs hyper link is not provided. Provide hyperlink to Total Hrs thus it is easy to get all the working particulars of the crew in one report.
   The following reports are showing current and last two months particulars only. In the slot provided for selecting the period it is showing future three months. Kindly provide last six months particulars.
       10 Hrs
       Working Hrs
       Consolidated leave
       PR count
       Booking on TA 
   Crew --> Crew Biodata (1/Page)
   In Crew Bio-data add one more field Training done date (At present only training due date is showing, for the training done date we need to check for one more report)
   Manage --> Cumulative Hrs
   Provide Cumulative Hours report separately with sort option.
   PDD PAD report
       Dep Arr data will be stored in a separate table (other than mileage table) (Done)
       User will be allowed to feed
           Dep upto 10 hrs from sign ON (earlier it was 10 hrs from ordering time)
           Arr upto 24 hrs from ordering time (ealrlier it was 48 hrs from ordering time)
       Report will show Dep Arr not filled for corresponding Sign ON and Sign OFF respectively for 24 hrs data (from 24 hrs back from the time of report) 
   HQ Sign ON/OFF Report
   Designation available in main report. Drill down SHOULD ALSO HAVE designation.
   NonRUN-Ineffective report
   Duration in which List of crew are Ineffective
   All the groups to be shown in SMS sending utility of TNC and Supervisor.
   All the groups which are configured from Lobby Configuration Console to be give at the SMS sending facility for TNC and Supervisor.
   Crew Search --> Complete Crew Details
   In Crew complete details of individual sheet only PME, REFT and SFCM is provided, add done and due particulars of technical trainings (REFD/REFE).
   Management - Avg Rest
   Crew rest particulars at head quarters and out station is available in their individual statements only, kindly provide a separate report for getting all the head quarter and out station rest particulars of the crew for a specified period.
   Inactive classification
   Crew – Summary (1 crew / row ) At present except for temp inactive all other reasons are shown in Inactive (permanent) report. Report provides for three radio buttons for
       Temp Inactive
   It is also proposed to have tree structure for inactive reasons, grouped under Temp Inactive / Permanent Inactive)
   Management – Book(WR/WOR)
   Reason is to be recorded for exercising the fetch crew all option.
   Crew – Periodical courses (DUE)
   Sorting on field proposed
   Crew – Periodical courses (DONE)
   Sorting on field proposed
   misc - Caution Order
   Form No T409,T/A 409 and T/B 409 to be generated through CMS containing unique serial number in similar formate as used in Railways.
   Run – Crew Availability
   It is proposed to view availability at user defined time
   Crew - Footplate K.M.
   Footplate Km Report for the promotion (from last promotion date) Columns are as follows:
       Crew ID
       Crew Name
       Last Promotion Date
       KMs Calculated by CMS
       KMs added manually in CMS
       Total Kms
       User Id 
   nonrun - consolidated leave
   In consolidated leave report, crew who had cancelled, edited their leave are also coming in report, It is very inconvenient while preparing statements. In this statement we are getting actual leave taken from and to date instead of period we specified.
   Availability -> OS crew at HQ
   Field for last Sign ON station to be added in report
   CREW --> Panelled Crew for officiating
   Non run , monthly, forthnightly, overtime, crew run detail, muster rol
   In the current system non run can be edited upto the time crew is not broguht back. A new provision is to be provided for conversion of absent cases to a valid non run reason at a later date.This new development will have the following aspects-
   Non Run to have additional button for converting absent to non run
   list all the crew who were absent (atleast once) in last three(defineable) months.
   Select the crew whose absent entry needs to be changed
   Display all the absent occassions of that crew for last 3 months
   Absent reason for the absent period can be changed to any of the following reason only: CL, CCL, ChCL, IOD, LAP, LHAP, ML, PL, PSICK, SICK, SPENQ, SPPME, SPTRN, SCL
   data entered in this form will have no repurcurssions to the crew working data in CMS database. (e.g. working hrs etc)
   all the data entered in this form will be saved seperately without any linkage to any other CMS data
   After changing absent to other non run , monthly, forthnightly, overtime, crew run detail, muster roll, reports printed / viewed after the change, will show the details of the change and its impact on mileage as a seprate entry at the end of report / page. The original mileage/OT generated will not be changed on account of regularisation.
   Progessive hrs: Credit for hrs because of conversion from absent to leave will be added to progressive hrs only if period is an active fortnight and also will be added only after date of conversion. For the past fortnoght no such addition is required in progressive hrs.
   non run - From Non Run
   Reason should be displayed in cancel
   Circular Report
   Management – Circular Master Category wise circular report Fields Under Each category
   Date of circular
   Drill down on subject will display the circular content


  • CMS on Economic Times "Railways Get ticket to ride" [1]
  • Automated crew booking at Ind Rlys [2]
  • Article in Times of India [3]
  • Computerworld Honour Program Finalist [4]
  • Article by Network Computing [5]
  • Indian Railways automating crew management [6]
  • Instructions to railway drivers and guards now via mobile SMS [7]
  • Now, tech-savvy railways to keep tab on staff through web-based system [8]
  • CRIS get CIO bold award for Crew Management System [9]