Ltr to CAO Release of Ver 5.3 With Annex 20160316

Annexurev ATo letter no: 2008/CRIS/NDLS-HQ/CMS/project//Rollout Ph/0026/Pt-II, dated 16-03-2016

Issue Facility provided in CMS Application

Auto call serve forShunter

Presently call serve through available for freight,coaching and slate modules. Now thisfunctionality has been extended to shunter module as well.

Items which can bereset in biodata

Facility was provided to reset biodata values from different console as indicated below.

Trainings - Lobby configurationTraction Delete - Lobby configurationPassword reset - Lobby configuration

Now all reset has been given to Division consoleFollowing additional reset has been addedLoco competency

In coaching module,Alert for under restcrew and forparameter beingviolated requiringfetch crew all option.

Parameters as per 'Fetch crew by rule' and 'Fetch crew all', are checked at the time of crewbeing linked and also at the time of call serve

A new fieldhas been added in the crew list for the parameters being violated in case of fetchcrew all because of which crew is not appearing in fetch crew as per rule.

Rest was not checked as crew being booked are as per sanctioned link.. How ever rest ischecked for duty < 8 hrs and duty > 8 hrs as the case may be and an alert is given that crewhas not completed its required rest of 12/16 hours. This alert is in the following forms.

1 Call serve2 Swap option in link crew.

At OS rest will be checked against configured value (as per type) and not against 12/16(which is used at HQ only)

Circulars divisionalconsole

Circulars remain visible for the period mentioned against each during entry of circular.Extending the TO date will keep the circular in visible zone. Extending the date will have noaffect on the unread circular status

OSRA for shunter atNCMS point

OSRA is being given in case of temporary transfer. Presently it is limited to temp transfer toanother lobby. Now it is extended to temp transfer to NCMS point as well. Only Shunter(Crew officiated as Shunter) can be sent to NCMS point through Temporary Transfer fromBiodata.

Drafted Non-runroster

Presently drafted and non drafted crew in roster are paid same mileage and duty hoursDrafted crew in roster1 mileage is to be paid @120 KM per day for rest, working and leave2 Duty hrs for rest and leave will be 0Non drafted crew in roster1 configured value to be paid for working and leave mileage .2 Duty hrs credited will be as per configuration

CMS version 5.3 - Application Enhacements & Changes

Page 1 of 9 pages


Issue Facility provided in CMS ApplicationCMS version 5.3 - Application Enhacements & Changes

Mileage for BA FailCrew (BA BIOEnhancement)

In case of sign OFF, Crew shall be required to take BA test after completing all the Sign OFFdata. After log in Crew will select sign ON/OFF on crew activity page. Presently for BAenabled Lobby he is taken to BA test. Failing which he is sent to SYS NONRUN. Hence histravel data cannot be captured. Now On selecting sign ON/OFF on crew activity page, crewwill be required to fill all data as is the case in BA disabled lobby. After filling all the datacrew is required to click on Sign ON/OFF. Now for BA disabled lobby signON/OFF will becompleted as per existing practice. Whereas for BA enabled lobby he will be required to takeBA test. Crew Sign ON/OFF will be completed with BA (PASS/FAIL)

Supervisor approval will be required in all cases BA PASS/BAFAIL. After approval

Case 1: If crew pass BA test crew status will become ON/REST.

Case 2: If crew fail BA test the crew will in SYSTEM NON RUN and status will be BAFAIL

This is essentially required to make supervisor approval necessary for all the cases and alsoto give mileage for completed run (Sign OFF) even in case of BA fail which is not given atpresent. In case device malfunctioning crew will come back to Final sign OFF button and testwill be repeated. However in such cases data already filled will be retained. If device isfinally by passed then clicking on Final sign OFF will complete the sign OFF withtemporarily saved data.

RedesignReregistration formfor bio

Drop down menu for lobby selection (logic and screen will be same as that for logineligibility on crew login screen)

SUSPENSION &ENQUIRY in SystemNon Run

BAFAIL CREW goes to SYSNONRUN Supervisor has the option to mark crew ABSENTREST LAP / LHAP / CL /SL BOOK ON SAME TAFollowing option is addedSUSPENSIONENQUIRY

Editing in BIODATA

Presently following fields can be edited in divisional console on EDIT BIODATA FunctionPF NOFollowing fields can now be edited PAN NO/AADHAAR NO/RUID NO/CUG NONow old value will also be displayed as existing data with facility to enter new data againsteach

Swap Crew Reason for swap crew is also asked & saved just as it is in swap TA. Facility is notsegregated for ALP and LP at present

Page 2 of 9 pages



Rest Modification Supervisor Console > Rest Modification At present only higher side of REST (from 16 to 22hr etc.) option/dropdown list available, it should contain all type of Rests (12 to 60 Hr)

Following changes shall be permitted

1 PR to normal rest 22/30/32/44/52/60 to 12/16 validated as per duty hours

2 PR to PR

Higher PR to Lower PR also to be permitted subject to it not violating night in Bed (one ofthe implication is 32 hrs rest can not be converted to a lower PR)

Rest can be modified for one or more than one crew

Once the new value is selected in the dropdown the modified value is indicated in sanctionedrest column clicking on save - pop up appears as "DATA SAVED" and modified valueappears as last rest,

Now once the new value is selected in the drop down a POP UP will appear "Old Rest /modified rest and OK and CANCEL button." the modified value will be indicated insanctioned rest column after clicking OK. clicking on save - pop up appears as "DATASAVED" and modified value appears as last rest

DIsplay Route no Route no to be displayed along with route name This facility has been provided in1 TA creation2 Crew Movement Detailfacility extended to1 LR Details in Crew Biodata

Additional non runreason

Spare for non run To be used in case journey date and start of non run happens to be differentdate.MileageAdmissible km will be given for "spare for non run". Admissible km will not be given foractual non run following or preceding actual non run This will also apply for training totraining cases also.

Check LR at signOFF

In case crew a the time of sign OFF select a route for which he did not have valid LRfollowing action is taken1 Count for Fetch as per rule will be converted to count Fetch all2 ALert crew that he has selected a route without valid LR3 In case crew still selects that route, SMS alert to configured no4 LR count for that route will be updated

reminder Call serveand automated callserve

Crew which has been served call by TNC through SMS (automatic) appears in SMS crewAck screen1. Screen now also show list of crew served call manually under separate tab(Acknowledged, Pending, Refused, MANUAL)2. Additional button for "Repeat SMS" is provided against each crew in Acknowledge andPending tab3. Additional tab for "repeat Print" is provided against each crew in Manual tab.(In Manual case repeat SMS is not required as it is assumed that manual was selected forcrew where SMS is not be1ng used/SMS is not reliable/Crew phone is not registered)

Page 3 of 9 pages



Validations inBiodata

Following validations has been added1 Difference of DOA to DOB shall not be less than 18 years and shall not be more than 35years. (Done)2 DOA and DOP cannot be same and DOP > DOA3 Age of crew will be calculated w.r.t to DOB on 1st of every month. If it is equal to or morethan 60 years, crew will be made inactive from 1st of the month. (Crew shall be in REST)4 PF no field will be restricted to 8 numerals5 Gender will be filled automatically by the system.6 Marital status of spouse will be married by default.

validation for callserve time

Validation introduced to check if1 While selecting TA for fetcing crew if Train Ordering time is less than current time, TNCwill be asked to modify the Train Ordering Time (through put back) (atleast 15 min morethan current time). (Done)2 When crew is fetched and assigned to the TA (call is served automatically to the crew) ifthe gap between calll serve time (click on the page) and calculated sign On time as perrevised Train ordering time is2.1 Can not be negative (Call serve time > original / revised calculate sign ON tine). In thiscase TNC will be forced to change the TO time2.2 less than 2 hrs for HQ crew and 1 hrs for OS crew , TNC will be required to accept "Thegap between call serve time and TO time is less than 2 hrs please acknowledge thatprecautions have been taken to ensure crew availability". for call to be served.Assumptions1 This is done to give flexibility for operation. Responsibility of ensuring sufficient margin tocrew which may be less than two hrs is that of TNC.2 Both Train Ordering time one at the creation of TA and second at the time of call serve willbe stored.3 Call ack time shall be < original/revised sign ON time (no action required)Under consideration1 If Call ack time > original/revised sign on time then sign on will not be permitted till TOtime and hence calculated sign on time is revised so that call ack time < revised calculatedsign on timeForms affected1 TA Pending (for Fetch crew)2 Crew booking3 System Non Run (book on same TA) (next version)

Option for selectingO/S Location as HQ.

Out station locations within 8 KM of HQ to be treated as Headquarter for Non Run mileage.Check box introduced on OS Location page for marking OS as Head quarter irrespective ofdistance.

Page 4 of 9 pages



Alerts for irregularcrew

Alerts on supervisor console provided for1 NOT ACK (AFTER CALLED) > 24 HRS2 NOT SIGN (AFTER BOOKED) > 24 HR3 OS REST > 72 HR4 ON TRAIN > 24 HR5 SYS NON RUN > 24 HR6 NON RUN > 7 DAYS7 CREW IN REST (AFTER AVAILABILITY) > 36 HR8 UNPLANNED (DUAL STATUS< NON TRACEABLE, BUG)9 APPROVAL FOR Sign ON / OFF pending > 8 hours10 Missed duty as per Coaching link in LAST 48 HRS11 Missed duty as per shunting roster in LAST 48 HRSDrill down of ALL above COUNT on clicking the COUNT

ALert as pop up on login screen removed

Coal Pilot BonusHours

In coal pilot Time is taken from Sign ON to Sign OFF at lobby / base station for calculatingeligibility for bonus hours. Eligibility now is checked against Dep and Arr from Base station

Transfer of footplatekm history

At present in 'Crew Biodata' on 'others' tab Promotion details displaysDesignationSource (RB, Promotion, Departmental)date of PromotionUser KmCMS KmRemarksA new row for a designation can be created or existing row can be deleted to providepromotion history along with footplate kmnew field addedCREW ID (will display all the old and current ID)TRANSFER DATE (system generated value based of date of acceptance of transfer)Values against CREW ID other than current Crew ID are not editable. It also implies no newrow can be added or deleted by a lobby for any other ID than its own lobby crew id. It maybe noted CMS km are system generated values based of CMS data and dates and can not beedited at any user level

Page 5 of 9 pages



Change in LR duescheme

New LR design with division configurable LR types for lobby1. Period of absence shall be calculated from drive date instead of LR due date (This impliesthat where periodicity of LR is selected as 6 months, 3 - 6 months period of absence willnever arise)2. LR requirement will be configured by division for no of trips

Period of absence from drive date Type I Type II Type III Day Night Total Day Night Total Day Night Totala) 3 to 6 month 1 0 1 1 1 2 1 0 1b) 6 month to 2 years 2 0 2 2 1 3 2 0 2c) 2 years and above 2 1 3 2 2 4 3 0 33. For LR total no of runs must be completed.4. Night Runs over and above the min requirement will be credited to daya) In case of change by the division of the applicable LR type, The additional night run duedate will be updated same as last day run.b) This implies that if LR was not due and Type is changed (say from Type I to Type II) crewmay get a window of 1 day to 3/6 months (depending on date of change and his due date forupdation of night run.5 Exceptional Route where Night is not applicable even if lobby configures Night as Y(select route,More than one route can be selected, applicable to crew of that lobby, Night triprequired will be treated as N, not applicable to parallel route)6 Period to be considered for Night trip (From & TO, default 1800 to 0600, valid range 1700to 0800) with duration for night from 1 min to max hrs7 With above there is no requirement for Night requirement flag8 LR Due date will be based on typea) Type I - either of the run (day or night). And night run requirement will be there only if LRis over due

Shunter Manualoption

Manual button provided for filling crew movement details1 KIOSK2 Supervisor sign OFF approval

Shunter manual Entryform

Following Validations and check introduced1. Sign ON time > last sign OFF time / Back from non run2. Sign OFF time > Sign ON time3. Alert for3.1 Duty hrs < 30 min3.2 Duty hrs > 16 hrs4. Duty > 24 hrs can not be saved5. Sign ON / OFF time < current time6. Manual to be allowed only after sign ON approval7. In case of KIOSK sign OFF without opting manual, Manual to be allowed through signOFF approval8. Sign ON time can be put back till last sign OFF as is permitted in Freight / Coaching SignON9. Rest Hours/loco no./loco type cannot be left blank10. Location of Shunting necessarily to be selected

Page 6 of 9 pages



Temporary TransferMovement - ShunterManual Form

1. Only Shunter can be sent to NCMS point through Temporary Transfer from Biodata2. Shunter is currently brought back from NCMS point through 'Transfer Back From NCMS'form in Freight module.3. Now Shunter is to be brought through temporary transfer function of Shunter ManualForm4. Crew will be brought back to rest only on complete entry of Temporary Transfer details.Further movement of crew to be allowed only after this form.5 Sign On and Sign Off Station to be shown as 'Working Station'(as Sign On and Sign OffStation will be same)

Shunter Sign ON /OFF approval

Remark to be filled if Sign ON or Sign OFF time is edited during approval. Log to be kept.

Shunter Roster Alerts for last sign OFF at the time of Sign ON at KIOSK (This is to alert him for missingentries if any)

Link Shunter Presently crew being fetched for linking is as under1 SHTOptional2 ALP with Off Allowance(only if officiated)3 ALP W/O off Allowance (even if not officiated) (This is enabled only for Shunting TA andeven there option comes once fetch crew button is pressed, one has to select the option andrefresh fetch crew button to get the list)4 SALP (even if not officiated)5 LPG (even if not officiated)6 SLPG (even if not officiated)

Now crew being fetched for linking shall be as under1 SHTMulti select2 Include SALP (original designation, no officiating mileage even if SLAP has beenofficiated for higher category i.e. LPG)3 Include Officiated shunter (Here all crew will come who has been officiated as Shunter orhigher, higher designation can work all designation upto original designation, Here alsoSLAP will not get officiating)OR3 Include All ALP + OFFICIATED (Here all ALP will come whether officiated or notofficiated . Off mileage will not be applicable to ALP irrespective of its biodata officiatingstatus) (This can be enabled for lobby from back end on request from proper autority , atpresent this is enabled for Kurla as hard coded)

The above scheme is applicable for Roster, Short Roster and Shunting TA

Officiating of Crew 1. Presentely Crew which are at outstation can not be officiated on current date/Time. Theycan only be officiated on next day. facility required to officiate same day.2. Officiated crew should be first removed from Link; then removed from officiating.3. If officiating is expired Crew should be removed from link with alert.4. Sign On crew should be allowed to sign off if officiating is expired in between duty. Samecrew should also be allowed to be attched in link till status is sign ON as officiating isextended till sign OFF. (This implies that officiated date shall not only be checked frombiodata but also be checked if it has been extended for sign ON crew)5. officiated status shall be checked at the time of serve Call if crew is not officiated, usershould be asked to first officiate the crew as per link requirment & then serv call should bepermitted.

Page 7 of 9 pages



Link Crew --->Coaching Link (swapwith in link)

1 If a crew already atached on one link is selected for another link also, then at the time ofinitialisation, sequence no of old link gets mixed up with new link sequence.2 Option provided to swap crew within same link.3 Link inirialization page now display the crew as per actual day and not as per the first dayof initialisation.4 The crew already working on some link is highlighted in purple colour on link crew page.

Modification incoaching

Day detail reportDay detail in applicationCall serve in applicaion

Day Detail report (list display crew for 48 hrs from time of dispaly) hours)Crew who is on rest on that day was not displayed. Now all crew of that link is displayedwether on duty or rest.1 Day detail and call serve in application merged (call serve screen, list display crew havingcall serve time on the same day after current time and next calendar day )2 Added from and To field in call serve screen3 Crew to be displayed in three groups3.1 HQ link crew3.2 Outsation Link crew3.3 Rest crew (HQ crew only, )SortingList is sorted on date and time by default with in each group.

Edit link (coaching) A new option 'Rest' given in drop down for field "working/spare"Once Rest is selected all fields will become non editable with 0 value and field of train noand route will show rest Station name drop down list will have scroll

Display of Last tenmovement of the locofrom FOIS in TrainRunning Detail

Presently CMS is displaying last 5 movement of loco in Train running detail .Now last tenmovement will display instead of five.

BA Device values Presently CMS is getting only BA value from BA Device, Now following parameter will alsocome from BA device at the time of Sign On/Off1. Sr No2. Cal No3 Record No4.Date Time5.Exhale vol6.Exhale time.Record No will be used as BA Token No and ll reflect in Sign On/Off approval. Report willbe needed to check these values from front end.

Transfer crew If crew transferred within division presently nominated LI in previous lobby should also go along withtransfer particulars.

Energy Meterreading (EMR)EMR mandatory In current application energy meter reading values are optional.

1. energy meter reading values made mandatory.2. 0 also to be allowed for each entry3. If user has opted 0 as value for any of the entries for energy reading i.e start station or endstation then the other entry compulsarily will be 0 as well.This whole scheme will apply to regeneration readings as well

Page 8 of 9 pages



Regenration for 3 Phloco only

Regeneration energy should be opened to only 3 PH loco which regenerate Energy, Not forall Electric locos.Validation Introduced1 Entry for regenerated energy will be captured only for run with 3 PH Loco Such as(WAP5, WAP7, WAG9).2 Regeneration should be less than 10000, check introuced on Manual & KIOSK.

Rename GT as TrainWt. No Train Wt forLE

Train Wt is to be filled instaed of GT GT is calculated as Train Wt. (filled by crew) + Loco Wt (from data base)Train Wt = 0 for Loco Functionality = LIGHT ENGINE.

Retention of KIOSKEnergy meter reading

KIOSK loco no and energy meter reading are brought forward in manual data entry.CASE 1: Loco no is NOT changed, Clicking on GO button will NOT ERASE energy meterreadingCASE 2: Loco no is changed, Clicking on GO button will ERASE energy meter reading

EMR not required tobe filled

Energy Meter reading not required to be filled for following duty typeYR, SP, LR, ZM, WT, KH, DE, any otherEnergy meter reading required for following duty type onlyWR, PL

EMR for coal pilot Energy data in CTR entries for Coal Pilot can now be filledMisc > EnergyConsumption Report

1 LI wise Radio button added with Crew ID/Loco type/Section2 Detail report for SFC?SEC3 Summary3.1 report at zonal/Div/Lobby level3.2 Report for Energy Consumed/ Energy Regenerated / SFC/SEC3.3 Report segregated for diffferent loco type. Conv, WAP5, WAP7, WAG9, MEMU3.4 Report segregated for Freight, CHg M/E, Chg P, Misc4 In case of multiple locoIn case user selects more than one locoEnergy consumed = sum of energy consumed in all locoEnergy regenerated = sum of energy regenerated in all locoGT = Train Wieight w/o loco + wt of all the loco

Search Crew > crewrun Detail Shunt Count shown in Crew Run details.

Management >Irregular CrewReport

New Report1 NOT ACK (AFTER CALLED) > 24 HRS2 NOT SIGN (AFTER BOOKED) > 24 HR3 OS REST > 72 HR4 ON TRAIN > 24 HR5 SYS NON RUN > 24 HR6 NON RUN > 7 DAYS7 CREW IN REST (AFTER AVAILABILITY) > 36 HR8 UNPLANNED (DUAL STATUS< NON TRACEABLE, BUG)9 APPROVAL FOR Sign ON / OFF pending > 8 hours10 Missed duty as per Coaching link in LAST 48 HRS11 Missed duty as per shunting roster in LAST 48 HRS

Drill down of ALL above COUNT on clicking the COUNTALert as pop up on login screen will be removedReport is consolidated at Div and Zone level

Page 9 of 9 pages

Annexurev BTo letter no: 2008/CRIS/NDLS-HQ/CMS/project//Rollout Ph/0026/Pt-II, dated 16-03-2016

Issue Facility Provided in CMS application

Suburban Changes as proposed by WR and ER

Duty HoursAlerts(<30Mins , >16Hours) andRestriction(>24 Hours)

Alerts For1) Duty hours <30 Mins ,2) Duty hours >16 Hrs And3) Duty Hours>24 hourshave been provided through javascript.Now these will be coded in backend i.e java as wellForms affected1) Kiosk Signoff (Freight and coaching)2) Signoff approval(Freight and coaching)3) Manual CTR form(Freight and coaching)4) kiosk Signoff(Shunting)5) Signoff Approval(Shunting)

Crew Detail CREW DETAIL to showLINK NO/ROSTER (if attached),to avoid cases of Crew in REST but N/Av. for booking.

Swap Crew Reason for swap crew should be asked & saved just as it is in swap TA.Sister lobby When crew sign off at Sister lobby following functions shall be permitted to HQ lobby even without

pulling crew back to HQ1. Rest modification2 Sending to non run (tentative)coaching link1. Call will be served by HQ lobby only even if sign on as per link is from sister lobby.(For using sister lobby crew, crew has to be temp transfered. As using sister lobby crew directly willlead to dual ownership of crew)It should be possible to fill crew movement detail at HQ lobby even when sign off is at Sister lobby

Swapping TA, CREW During swap alerts were provided for following checks. Now validations have been proposed.Case 1TA1 Fetch all & TA2 Fetch all(LR, Lcoo competency, Auto signalling, Ghat, Officiating)No validations to be applied only alert to be givenCase 2TA1 Fetch all & TA2 Fetch by Rule(LR, Lcoo competency, Auto signalling, Ghat, Officiating, REFE/REFD)Validations to be applied (alert provided in ver 5.2)Case 3TA1 Fetch as per rule & TA2 fetch as per rule(LR, Lcoo competency, Auto signalling, Ghat, Officiating)Validations to be applied (alert provided in ver 5.2)Note 1In case sign ON approval has been givenentry will reappear in sign ON approval form and a separate heading "Approval for swapped crew"Note 2Validation for officiating to be handled first The Fetch as per rule case will now be treated as Fetchall caseNote 3After validations have been applied the crew will appear in Sign ON approval form based of servicetype only instead of "Crew type + Service type" as is the case at present

memu refresher in nonrun tree

A new refresher training is required 'Memu refresher" .Periodicity of training 3 yearsTo be checked when service type is MEMU

An option to be givenin "Crew Bio data Edit"tab in divisionalconsole for changing LInomination of all crewunder division.

Now LI is divisional based, but the facility to change nominated LI is available at Bio-data. Butprovision in divisional console is required where LI himself can edit the nominated crew name.

CMS version 5.4 - Application & Report Enhacements & Changes

Page 1 of 9 pages




New duty type CTO(charge taken overduty)

Presently CMS has provision of yard relief where crew called but not utilised is paid mileage@15km/hr.1. New duty type CTO to be added in Manual form.2. Mileage of 120 kms to be paid irrespective of duration from sign ON to Sign OFF3. From and To station will always be same.

Cab wise VCDreporting

In case of VCD working two questions to be there one for each cab. Both questions will bemandatory. Options will be as is for single question. Report will indicate cabwise status.Question for VCD at TOP and Answer-1 is in bottom at presentAdditional rows for answer will be provided just after question and above Loco Function

Spare mileage (km aswell as hrs based)

Spare mileage is 50% of actual mileage1 In case mileage is calculated on km it should be half of km2 In case mileage is given on hourly basis it should be half of mileage rate

Circulars Provide facility to copy/paste Hindi/Eng. circulars available in MS office/word format

Periodical Rest Crew under PR should be taken out of the PR after completion of PR Hrs even if he has not beenbooked, It should show in normal rest instead of PR.

LI Grading &Counseling Alert

Weekly SMS to be given to Officer Incharge for number of Crew whose LI Grading & Counseling areoverdue.LI Biodata to have additional field forLevel of SMS alert for counselling and grading. : drop down for multi select for Level 1 to 4SMS will be generated lobby wise for over dur counselling and grading<"XX" CREW OVERDUE GRADING "YY" CREW OVERDUE COUNSELLING OF "LOBBY"FOR LI "NAME" "ID">No SMS if NIL crew is overdueSMS on every MONDAY

Abnormality - Gatemitra

Abnormality reporting > under Engg. Tab add >GATE MITRA

EDIT MANUALENTRY

New Function for "EDIT last manual data entry" to be providedLast manual data entry will be displayed for editing provided1 CREW status is Rest and no further action has been performed e.g. Booking of crew, to non run etc2 las entry was not made before 3 daysChecks to be performed1 At the time of selecting the crew2 At the time of final save after EDIT

Shunting TA In shunting Roster following shifts are generally being operatedTYPE 1: 00:00-08:00 (8), 08:00-16:00 (8), 16:00-24:00 (8)TYPE 2: 06:00-14:00 (8), 14:00-22:00 (8), 22:00-06:00 (8)TYPE 3: 07:00-13:00 (6), 13:00-21:00 (8), 21:00-07:00 (10)TYPE 4: 02:00-10:00 (8), 10:00-18:00 (8), 18:00-02:00 (8)No validation is there while defining shift timings in Roster.However in TA ashift can be of 8 hours only.based on above following shift timings can be selected from the drop down menu6, 8, 10, Default time will be 8 hours

Sign OFF Form Additional field along with BA token no for BA ValueThis will not ne mandatoryIf crew fills the BA value same will appear in Sign ON / OFF approval.However this will require one more entry by Crew

SMS: Extend wordlimit

Abnormality messages received as SMS has word limit of 70 character only rest of the characters inthe limit iof 160 are used by standard information, if msg. is of 71 character, it shows only startingfew words with caption ADDITIONAL TEXTS.Extend word limit to 250 character. With the present word limit of 160 Character message will be intwo parts now

Page 2 of 9 pages




Departure time enteredin PDD not available inmanual entry form

When any crew sign on against a TA entry for the same appears in PDD form for entry of departuretime. In case separate TA has been created for LP ALP and Guard, separate entries will appear inPDD form for the same train.Departure time can be entered against bysupervisor through PDD formmanual data entryPulled from FOIS for mapped entriesDeparture time entered in PDD form by the lobby supervisor / FOIS of the sign on lobby reflect in themanual entry page at the time of manual sign off.Facility to be provided to edit the departure time in manual entry form individually for each crewwithout cross validation..Value in PDD form will be corrected accordingly. Edited value of departure time has to be greaterthan previously stored value.Supplementary mileage

calculatorNew Function provided in divisional console1 Screen similar to manual entry form but sign on and TA is not a prerequisite and will be filled hereonly2 The entry will be possible for time after sign OFF of and before sign ON of existing entryConstraints1. Starting and end runs in this form will not be linked to main entries for continuous dutyverification.2 Station of last existing sign OFF and sign ON will not be validated3 LR will not get updated4 Footplate km will not be updated

Crew Run DetailCrew run detail will show supplementary entries in shaded/coloured/italicised

Mileage1 At the end of one time entry div will click on save2 Mileage will be calculated as per thread for mileage in the night3 Supplementary mileage form can be used multiple times for the current and two previous monthlyslots4 Supplementary mileage statement will be generated like main mileage statement as a separatestatement

OT1 In case entries for supplementary mileage is done with in OT fortnight, OT will be modified forvalues entered.2 In case entries for supplementary mileage is done after OT fortnight, no modification in OT

Additional LR to bechecked for bankingcrew

While making banking TA crew is fetched by checking LR against one route as mentioned in TAIn case there are two / three banking routes from the point of provision of Banker LR shall be checkedfor multiple route as banker can be provided in any directionTA for banker modified to have three optional route (FROM, TO, Route) for which LR will alsochecked in fetch crew by rule option

Sick leaveregularization

SL shall be treated like ABSENT for the purpose of mileage and duty hours.Conversion of SL to other leave types (LAP LHAP) and PR shall be permittedConverted period mileage will be indicated separately as is the case of absent conversion.FLow for conversion of SL to PR is not clear

BA test flag If crew sign's off through Kiosk and supervisor approves his BA also but finally supervisor opt formanual sign off. Crew directed to manual ctr form. The BA test is indicated as BA not on KIOSKwhere as it should figure under BA on KIOSK.Report HQ wise sign off and sign on to be modified

Division wise QUICK, QUICK scheme will be division specific.Existing questions will be copied against each division.Division will be able to add/delete/modify questions

Page 3 of 9 pages




Standardisation ofviolation of TA orderbooking reasons

This is a plain text field. Standard reasons in drop down menu will be provided to help user to selectproper reason on the lines of crew order violation. ( This facility has been provided with CMS release3.9.0 for crew order violations, released in Oct – 2012)These reasons will be further classified as ‘valid acceptable reasons’ based on exigencies of operationand ‘unacceptable reason’ for further analysis. Moreover these reasons will be defined by user itselfthrough divisional configuration console.

provision to changetrain no at sign OFF

During sign off on kiosk provision is given for changing loco no.but no provision available forchanging train no.Train no to be made editable at sign OFF..Case 1: Independent TA for Loco and GuardBoth to fill independently against their respective TACase 2: Same TA for AllEdit facility in Guard only

Password Policy User ID & Password Policy – Modified password policy has been implemented since 29-09-2015.Password Policy (Current)1. User ID cannot be part of password2. User Name cannot be part of password3. Lobby code of that particular lobby cannot be part of password4. Password cannot be same as last password.5. Password must be Alphanumeric6. Password length must be >=6 and <=87. Password cannot contain special character8. Password for thin client users (TNC, SUP etc.) is case sensitive.9. Password will expire every six months10. Password have to be changed on first Login11. Password expiry reminders 7 days in advance.12. SMS will be auto send to respective users for password reset or change.

Password Policy (Additional to be implemented)1. Password cannot contain three or more sequential characters2. Password cannot contain three or more sequential numbers3. Password cannot contain three or more repeating characters4. Password cannot contain three or more repeating numbers5. Special characters to be allowed to increase the strength of the password6. One special character will be made mandatory in password7. . cases of frequent reset will be notified to authorities through sms/reports for 5 or more reset in amonth.

Password Policy (Not Recommended)1. Restriction on duplicate password in a lobby.a. Security concern – It may reveal other user's password and may tempt user to try to hack othersaccount by hit and trial.b. Privacy Concern – For determining duplicity others passwords needs to be read and compared.c. Load concern- Although minimal since password is to be matched against all users of a lobby only

CMS on internet CMS application can be accessed on Internet for LOCO SUP and LOCO TNC usersLobby needs to be enabled for internet access. A new user id for internet access needs to be createdfor these functions even for the same person. Existing user id will not be allowed for internet accessas on date.User will be sent an OTP (one time password) every time he tries to access CMS overinternet.

Page 4 of 9 pages




Shunting duty type inmanual

Need for duty type shunting in manual entry form for subsequent run is not there.CASE 1A to B spareB shunting for 4 hoursB to A SpareShunting at B can be handled in either of the run through enroute shunting provisionA to B - Shunting at last stationB to A shunting at first station.Mileage for first and last station is paid @ 15 km per hoursOption of duty type shunting is removed in manual data entry form in FREIGHT and COACHINGmoduleIndependent shunting can be tackled through SHUNTING MODULE for eligible crew typeDivisional ID for Spl.

Reports.Presently there is not provision for any authorization required prior extracting .txt file for PRIMEusage.1. User may only be able to generate .txt file from authorised user ID.2. Authority to generate mileage shall lies with configuration authority.3. User may be authorized to generate mileage for the slot which he has already generated, butcounter for that may be recorded.

Lobby Creation Divisional console will be provided a form for defining lobby authority at 4 levelsLevel 1 : Sr DEE / Sr. DME / Sr DOM Permitted mobile no : 1Level 2 : AEE/DEE/AME/DME/AOM/DOM Permitted mobile no : 2Level 3: CONTROL (TLC / PC / TC) Permitted mobile no : 5Level 4: Lobby controller Permitted mobile no : 2The above levels are primarily for intimation by SMS to higher level for any situation requiringattentionInformation to be stored against each levelDesignationMobile No /nosNameIn SMS configuration console these level can be selected for SMS in addition to user defined nos

Auto updation ofincrement

Basic of employees is required to be updated every year in July. Demand is to updated it automaticallyas per following formula..new basic pay = old basic + old basic 3% .Since integration of CMS with AIMS (Accounts Information Management System Is). Value in CMSdatabase will be updated based on AIMS value instead of duplicate calculation in CMS

Circulars Add KRUTI DEV FONT besides Hindi Remington etc.

Crew booking display traction in crew list against each crew in addition to cadreFollowing Reason for violation shall be treated as accepted reasonDiesel crew required laterEclectic crew required later

Test and Training A new training named as "Orientation Course " will be added particularly for Automatic blocksection.At present OCourse stated under Refresher Transportation,for which periodicity is once in 3years.

User definable consoles Division console shall be able to configure functions for various other consolese.g.TA creation in Divisional console or Supervisor console or TNC console

Abnormality feedbackthrough SMS

SMS is sent to configured no for abnormality reported.Each of the configured no can send back action taken on the reported abnormality. Action taken willbe stored along with the no from which SMS is received. This will be in addition to data entered bysupervisor against abnormality.In addition to remarks an additional column for SMS remarks will be added where mobile no andremarks will be stored in non editable form.SMS shall be sent indicating abnormality id followed by action taken.

Lobby configuration forshunt count

Lobby can be configured from CRIS for1 Shunt count can be filled by Crew and edited by supervisor2 Shunt count can not be filled by crew and will be filled by supervisor during approval

Running room module Interlinking of Running Room and Lobby to be linked to inform the incoming outstation crew aboutthe occupancy and availability of beds in respective running room. This system can also beprogrammed to allot the bed and room number when the staff comes to sign off at lobby and alsorelease the bed/room when signing on for duty.

Page 5 of 9 pages




Supervisor Sign On forShunter

Shunter should be allowed to be sign on by the supervisor.

SLATE SLATE Swap Crew screen in TNC console shows S/off Date & time and current status as REST evenif rest is not completeSuggestions:Provide Green colour code on screen as Under RestProvide Availability date/time along with S/on & status.

Abnormality report Provide Abnormality Report in Supv. Console (Application) in Descending order i.e. current date onTOP, at present there is no order neither date wise nor ID or abnormality type wise.

Auto save in manualentry

Each run entered shall be saved as draft till it is finally saved at the time of clicking for next run. Noweven if session is closed without entering all the runs and saving it entries made in the runs will besaved in temporary table. Processing of data will take place only after final save. All the temporarysaved entries will resume once same crew id is selected in manual data entry form. This will putsignificant load on database and transaction.

CMS LobbyCommissioning

New entry form to be provided through which new lobby can be commissioned.

Hindi Font Circular HINDI Font limit to be increased on Circular Body, Presently 1000 letters allowed in hindi Typing.

Officiating of Crew 1. Presentely Crew which are at outstation can not be officiated on current date/Time. They can onlybe officiated on next day. facility required to officiate same day.2. Officiated crew should be first removed from Link; then removed from officiating.3. If officiating is expired Crew should be removed from link with alert.4. Sign On crew should be allowed to sign off if officiating is expired in between duty. Same crewshould also be allowed to be attched in link till status is sign ON as officiating is extended till signOFF. (This implies that officiated date shall not only be checked from biodata but also be checked if ithas been extended for sign ON crew)5. officiated ststus shall be checked at the time of serve Call if crew is not officiated, user should beasked to first officiate the crew as per link requirment & then serv call should be permitted.

Link Crew --->Coaching Link (swapwith in link)

1 If a crew already atached on one link is selected for another link also, then at the time ofinitialisation, sequence no of old link gets mixed up with new link sequence.2 Option to be provided to swap crew within same link.3 Link inirialization page should dis[play the crew as per actual day and not as per the first day ofinitialisation.4 The crew already working on some link will be highlighted in purple colour on link crew page.

Non-run Absentconversion

Presently conversion from absent to other non-run reasons like CL,LAP, CCL, LHAP, etc is availble.Converting Absent period to Rest is not available.

Edit non-run - absent Edit non run - In Absent reason RA count to be freezed 0. In no case that can be configured 1.

Check for Additinal LRand loco typecompetency

In case of spare crew, availability is checked without checking Loco competency and LRIn situation where crew is being sent as spare to work another train, crew may be required to beavailable according to LR and loco competency for subsequent run.

A new check box while making TA for additional runSeperate window will be opened for second runFROM(TO of first run), TO, ROUTE, LOCO TYPE (This record will not be stored for any future dataentry.)While fetching the crew the crew will be checked for LR and loco competency for the subsequent run.

This will further be extended even if first run is not spare and for more than two run including firstrun.In that case Crew will be checked for LR and Loco competency for all such runs.

Since crew is not signingg OFF at the end of first run, the details will be completed only throughmanual data entry at final sign OFF point.

Page 6 of 9 pages




Alerts to crew1 Lobby details to have mob no and other detaisl of Branch officer, Lobby officer, lobby incharge2 SMS alert to Branch officer, Lobby officer, lobby incharge ( item for which alert is to be given Incase crew at the time of sign OFF select a route for which he did not have valid LR following actionwill be taken1 Count for Fetch as per rule will be converted to count Fetch all2 ALert crew that he has selected a route without valid LR3 In cae crew still selects that route, SMS alert to Branch officer, Lobby officer, lobby incharge4 LR count for that route will be updatedSame Check to be applied in manual data entry)

No Loco no. @ traincancellation etc.

LOCO No shall not be require for1 Yard OFF2 CTO3 Waiting duty type

Additioal validatios forSYSTEM NON RUN

Validationalready introduced to check if1 While selecting TA for fetcing crew if Train Ordering time is less than current time, TNC will beasked to modify the Train Ordering Time (through put back) (atleast 15 min more than current time).(Done)2 When crew is fetched and assigned to the TA (call is served automatically to the crew) if the gapbetween calll serve time (click on the page) and calculated sign On time as per revised Train orderingtime is2.1 Can not be negative (Call serve time > original / revised calculate sign ON tine). In this case TNCwill be forced to change the TO time2.2 less than 2 hrs for HQ crew and 1 hrs for OS crew , TNC will be required to accept "The gapbetween call serve time and TO time is less than 2 hrs please acknowledge that precautions have beentajen to ensure crew availability". for call to be served.

Assumptions

1 This is done to give flexibility for operation. Responsibility of ensuring sufficient margin to crewwhich may be less than two hrs is that of TNC.2 Both Train Ordering time one at the creation of TA and second at the time of call serve will bestored.3 Call ack time shall be < original/revised sign ON time (no action required)

Under consideration1 If Call ack time > original/revised sign on time then sign on will not be permitted till TO time andhence calculated sign on time is revised so that call ack time < revised calculated sign on time

Forms affected1 TA Pending (for Fetch crew)2 Crew booking3 System Non Run (book on same TA) ( ver 5.4)

TI working On the lines of LI the grading and counselling of gurads be done as well through TI

Page 7 of 9 pages




Viewing of CMS lobbyapp in zonal fois hq

Divisional Console with followwing functions is already provided1 Circulars2 CUG Bill Upload3 Caution Order (integrated with COA)4 LI Bio-Data5 Crew Gradation \Counseling6 LR Station Form7 User Details/Reset Password Create User8 Crew Booking Violation9 ASM MODULE10 Report Abnormality11 Abnormality12 Edit Crew BioData13 Forced Sign Off14 TA Creation15 Send Group SMS16 LR Configurations17 Add Quiz Questions18 Reset user's Training/TractionConsolidation of lobby report is proposed for Divisional / zonal level (Railwyas may suggest report

SMS REFUSED CALL Rufused call from SMS crew should be moved to SYS NON RUN RF throug button provided onrefused page.

Sign ON / Sign OFFreport

Report to be divided in following columns1 Completed on KIOSK2 Manual ( Straight on manual, did not touch KIOSK for Sign OFF03 KIOSK - Manual ( sign OFF started on KIOSK, completed on manual)4 KIOSK - Resultant Manual (These are previous runs which were completed manually as manualoption was selected for last run) if not possible then merge this with 2 above

Duty type PILOT inCTR form

Like TA creation, duty type PILOT not available in drop down list of CTR (Crew movement detail)form

In biodata ADD (widow)&(Divorced)In biodata (IN OTHER) IN marital status

EMR : Energy Possibility of one tab for energy in sign OFF form and open new form for filling all energy relateddetails.

common no for MEMUand Loco

At present loco no is mapped to loco type assuming unique no for a type.It has been observed that no is common between Loco type and MEMU/EMU/DEMUIn such cases if multiple loco type is available against some loco no, the loco type field will display"select" against loco type and drop down will indicate possible loco type. User will be required toselect the correct locotype before savingForms affected1 TA2 Manual data entry3 Sign OFF

Capture no of powercoaches forMEMEU/EMU/DEMU

For loco type MEMU/EMU/DEMUUser will be asked for :no of working power coaches"Forms affected

manualSign OFF

Page 8 of 9 pages




Energy checksdepending on Loco type

ElectConv. - NO REGENERATION3 PH (WAG9, WAP5, WAP7) - REGENRATIONMEMU - NO REGENERATION, EnergyCONSUMED to be multiplied with no of power coaches,Train wt = 0, Loco wt (combined wt of MC + 3 TC) to be multipleid with no of power coachesEMU - REGENERATION, Energy CONSUMED and REGENERATED to be multiplied with no ofpower coaches, Train wt = 0, Loco wt (combined wt of MC + 3 TC) to be multipleid with no of powercoachesDieselConv. - NO REGENERATIONDEMU - NO REGENERATION, EnergyCONSUMED to be multiplied with no of power coaches,Train wt = 0, Loco wt (combined wt of MC + 3 TC) to be multipleid with no of power coaches

EMR : Energycalculation for Multipleloco

In case user selects ,ore than one locoEnergy consumed = sum of energy consumed in all locoEnergy regenerated = sum of energy regenerated in all locoGT = Train Wieight w/o loco + wt of all the loco

EMR : Energy forWorking of same loadand same loco butmultiple sections

One more check box before energy meter reading in subsequent runsIf check box is ticked, loco no and train load will remain same in subsequent run.Energy consumed = end reading last linked run - start reading first linked runEnergy regenerated = end reading last linked run - start reading first linked runGT = (Train Wieight w/o loco + loco) of first run

EMR for Co Pilot Co pilot will not be required to feed energy readingOption 1:For Co Pilot TA during Sign OFF pilot has to select if he is Co pilot, if selected he will notbe required to fill energy meter dataOption 2: In TA form check box to be provided to declare one of the LP as Co Pilot

Multiple locos When more than one loco is selected Enrgy report shall show one row only

validation for callAcknowledgment time

Action proposedValidations to be introduced• Call ack time shall be < sign ON time• If call ack time > sign on time then sign on will not be permitted till TO time and hencecalculated sign on time is revised so that call ack time < revised calculated sign on time

Mileage summary report

MIleage summary report to show list of crew in temp transfer under a new headerNew ID generated against temp transfer will be shown1 Crew tranferrred and returned from NCMS lobby: only crew id will be shown with remark that themileage dat has been captured and displayed against original id2 crew tranfered and returned from CMS lobby: acual mileage as captured against temp id will bedisplayed

Page 9 of 9 pages

Annexure CTo letter no: 2008/CRIS/NDLS-HQ/CMS/project//Rollout Ph/0026/Pt-II, dated 16-03-2016

Page 1 of 3 pages

Energy Meter Flow Document for CMS1. Crew is required to feed the data of Energy/Fuel Consumed and Energy regenerated at the time

of signing OFF.2. This is required for all sign OFF

2.1. at KIOSK2.2. through crew movement detail manual data entry

3. Following fields are required to be filled3.1. Energy meter reading / Fuel reading at start3.2. Energy meter reading / Fuel reading at end3.3. Fuel added enroute (to be done)

Proposal: In case of Diesel traction only fuel consumed to be filled instead od start and endreading

3.4. Regenerative meter reading at start3.5. Regenerative meter reading at end3.6. Train Wt. (for GTKM) (ultimately to be integrated with FOIS and prepopulated)

4. Energy / Fuel is automatically prompted depending on the loco no5. Regeneration is not required to be filled for following cases

5.1. Conventional Electric Loco5.2. MEMU5.3. Diesel Loco (all types)5.4. DEMU

6. At present regeneration is restricted to following loco type6.1. 3 PH Loco (WAP5, WAP7, WAG9).6.2. EMU

7. Calculation are as under7.1. GT = Train Wt. (filled by crew) + Loco Wt. (from data base).7.2. Diesel

Fuel consumed = Fuel reading at Start +(fuel added enroute) – Fuel readingat end

SFC = Fuel consumed/(GT X KM)7.3. Electrical

Energy consumed = Energy Meter reading at end – Energy meter reading atstart

Energy Regenerated = Regenerated Energy Meter reading at end –Regenerated Energy meter reading at start

SFC = (Energy consumed - Energy Regenerated)/GT X KM)8. At signing OFF crew can select any of the following loco status for energy meter reading:

Loco Dead Loco Spare Energy Meter defective Working loco

Note: Data entry is required for working loco only. For others, Energy meter / regenerationreading meter column is non-operational. This is applicable for Multiple Loco also.

9. Validations9.1. Energy and load related field to be active for driver only9.2. Regeneration is opened for Electric traction only.9.3. GT should < 15000 (A)9.4. Energy Consumption < 25000 (B)9.5. Energy Regenerated < 10000 (C)


Page 2 of 3 pages

Note: Value A B & C are variables which can be changed later on.9.6. Train Wt. = 0 for Loco Functionality = LIGHT ENGINE9.7. Energy Meter reading not required to be filled for following duty type (YR, SP, LR, ZM, WT.,

KH, DE, any other)9.8. Energy meter reading required for following duty type only (WR, PL, CP)

10. SFC will be displayed on click on (5 previous run excluding current run)10.1. Sign OFF screen10.2. Sign ON screen

11. Multiple Loco11.1. Loco No.2 option has been removed from TA. 2nd and additional Loco are handled

through energy meter reading during sign OFF on KIOSK as well as in manual dataentry.

11.2. For SFC Energy consumed will be added for all loco Energy regenerated will be added for all loco. GT = All loco Wt. + Train Wt.

12. Energy meter reading values are mandatory.12.1. 0 also to be allowed for each entry12.2. If user has opted 0 as value for any of the entries for energy reading i.e start station

or end station then the other entry compulsorily will be 0 as well.12.3. This whole scheme will apply to regeneration readings as well

13. KIOSK loco no and energy meter reading are brought forward in manual data entry.13.1. CASE 1: Loco no is NOT changed, Clicking on GO button will NOT ERASE energy meter

reading13.2. CASE 2: Loco no is changed, Clicking on GO button will ERASE energy meter reading

14. Co pilot will not be required to feed energy reading14.1. Option 1:For Co Pilot TA during Sign OFF pilot has to select if he is Co pilot, if

selected he will not be required to fill energy meter data14.2. Option 2: In TA form check box to be provided to declare one of the LP as Co Pilot

15. Common no of MEMU/EMU/DEMU and Loco15.1. At present loco no is mapped to loco type assuming unique no for a type.15.2. It has been observed that no is common between Loco type and MEMU/EMU/DEMU15.3. In such cases if multiple loco type is available against some loco no, the loco type

field will display "select" against loco type and drop down will indicate possible locotype.

15.4. User will be required to select the correct locotype before saving in flowing Forms TA Manual data entry Sign OFF

15.5. For loco type MEMU/EMU/DEMU User will be asked for no of working powercoaches" Forms affected Crew Movement Detail Sign OFF

15.6. MEMU Energy CONSUMED = (Energy Meter reading at end – Energy meter reading

at start) X no of power coaches GT = Train Wt. = 0 + Loco Wt. (combined Wt. of MC + 3 TC) X no of power

coaches15.7. EMU


Page 3 of 3 pages

Energy CONSUMED = (Energy Meter reading at end – Energy meter readingat start) X no of power coaches

Energy REGENERATED = (Regeneration Energy Meter reading at end –Regeneration Energy meter reading at start) X no of power coaches

GT = Train Wt. = 0 + Loco Wt. (combined Wt. of MC + 3 TC) X no of powercoaches

15.8. DEMU Fuel CONSUMED = (Fuel Meter reading at start – Fuel meter reading at end)

X no of power coaches GT = Train Wt. = 0 + Loco Wt. (combined Wt. of MC + 3 TC) X no of power

coaches

Documents

Ltr to CAO Release of Ver 5.3 With Annex 20160316