Crew which is booked for train is called staff on running duty. Such staff is taken out of the running duty for cases like leave, Training, Medical etc. Such status where the crew is not available for running duties is called as non run. A crew can be sent to non run not more than 84 hrs from the system time. This check avoids data entry errors like wrong selecting a year or a month while typing. Also the N.R. does not allow overlapping data entries like overlapping times for 2 non runs, going back into system time prior to the last sign OFF.

For various non run the logic built into CMS is as following:-

• The crew must be in rest (completed his earlier assignment)before he can be sent to a non run.
• For one day working the Hrs credited into a crew account is 7:26 Hrs for each day.
• The day starts from 00:00 Hrs and ends at 23:59 Hrs.
• In case a crew is sent on Non Run at 23:59 of 1.1.08 then 1.1.08 is counted by the software as complete day. Normally the crew should be sent from 00:00.
• In case the crew comes back from NON RUN before 12:00 Hrs then that particular day in not counted by the system in the NON RUN. Only if the crew returns back from non run after 12:00 Hrs then 7:26 minutes is credited to his account.
• For cases like ABSENT, LWP, MISC, NHW, NTB, OTHR, SNRUN, SUSP, SYSRF no Non-Run Hrs are given by the system.
• For case like ABSENT, IOD, SICK, SYSNR, SYSLT the CMS does not ask for a non run return date. While in the other case it does ask for a NR return date. A rep rot is generated by the system for crew overshoot the NR return date. For these case the rep rot is not linked.
• The crew who is absent for a period of more than 90 days in given a popup message advising the user to send him for a medical checkup. It is left to the user to send him for a medical checkup or no.
• In case of multiple non runs, the same should be tackled in CMS system one at a time.
• System has capabilities to sanction standard rest 12, 16, 22, 30 on coming back from non run through combo selection or giving a non standard rest upto 12 Hrs by selecting the ca lander. This functionality exist in CMS software from version 3.3.1 onwards.
• From version 3.4.1 onwards a check in the non run has been introduced so that when the crew returns back from Non Run the actual Arrival date, time should not be beyond the system date and time. This ensures accuracy of data entry and correct milage calculations.

The crew may return from non run and be sent to a running duty or non run of another type. A Crew coming back from one type of non run can be sent to another type of Non run. Whenever the non run duties are completed the system require 2 dates / times. The date and time when his N.R. was completed based on this his records of trg, leave, PME are updated or the next due date found. Another date is the available date / time i.e. the time when you want him to be available for running duties after availing rest.