New Software Functionality in CMS ver 3.8.0

The CMS version 3.8.0, the release in March 2012 shall have the following features.

    Application

  1. Updation of Road Learning (LR)

    LR at present is updated on a single trip now LR to be updated as per following logic based on Period of absence from the last journey at that route Period of absence No of trips No of trips No of trips NIGHT DAY a) 0 to 3 months 0 0 0 b) 3 to 6 months 1 0 1 c) 6 to 24 months 2 0 2 d) More than 24 months 3 1 2 e) Fresh driver 3 1 2 f) Ghat section / fresh 5 2 3 or more than 24 months DAY trip can be performed in NIGHT but not vice versa Night trip implies a whole or part of trip to be between 2200 hrs to 0600 hrs. Lobby configuration console can choose LR due between 3 and 6 months, which is now made 3 months only. On promotion it will treated as Fresh driver If the crew is required to have more than 1 trips for LR then all the trips shall be with in 3 months from the first trip. The trips for LR will normally be with duty type as LR. However since it is possible to book crew even due for LR through fetch crew all (in case of emergencies), in such cases trip with duty type as working will be treated as a valid LR trip. Up dation is done based on LR sections only. In case two routes have common station sections but different LR sections, running on one route will not update LR of other route and hence even matching station sections of other route will not get updated.

  2. Additional groups for SMS alerts

    Groups for SMS for loco to be bifurcated for "Alert Loco", "Other Loco", "Morning Position Loco", Alert Loco (Electric Traction) Alert Loco (Diesel traction) Other Loco (Electric Traction) Other Loco (Diesel traction) Morning Position Loco (Electric Traction) Morning Position Loco (Diesel traction)

  3. Crew bio data to include cadre

    An additional field is required to be added in crew bio data for cadre (Electrical / Mechanical) ONLY this field can be edited. At the time of promotion the value in the field will be required to be filled again. It shall be possible to select cadre for crew type in all reports and listing for Electrical / Mechanical / Both.

  4. Service type LR, Traction not to update

    Service type LR, Traction not to update.

  5. New option to fetch crew

    Presently there are two options to fetch crew Fetch crew by rule Fetch crew all Check for Safety camp to be added. This check shall apply to all modules. As per rule Fetch all Fetch all with LR w/o LR 1 PME - Y Y Y 2 REFT - Y Y Y 3 Traction - Y Y Y 4 Road / Yard learning - Y Y N 5 Safety camp - Y N N 6 Loco competency - Y N N 7 REFE- Y N N 8 REFD- Y N N 9 Automatic signaling - Y N N In addition crew should not be in shunting roster, Crew can be fetched even if he is already on a coaching link to complete the link to cater to crew shortage. link no for Crew already on some link is displayed in availability list. A pop up alert to be given, if an already linked crew is linked again on some other link. ("This crew is already attached to a link, do you still want to link him again") SPl occasions is primarily to cater to situations when trains are run from diverted route

  6. Alert for crew on link / roster

    In case of Crew to be booked on coaching TA an alert to be given if crew is already on some link. Crew will be visible in different color in availability list even if linked on some coaching link BUT on rest. How ever crew can be selected for booking even if he is linked. This will hold good for ALP also for the lobbies which has segregated ALP working.

  7. Calling the crew as per progressive hrs

    While booking the crew with call crew as per Progressive Hours, crew shall be displayed in following order Crew with lowest Progressive hrs but rest complete. Crew with lowest Progressive hrs but under rest.

  8. Facility to modify values on sign off approval

    At the time of sign off approval, supervisor can direct TNC for manual entry but he will be required to give reason for marking him to manual and not giving approval straight away. A check is to be provided so that TNC can edit the sign off time through manual data entry, subject to a maximum of +/- 15 min only.

  9. Simultaneous Booking of LP and ALP on single coaching link

    At present Pilot and ALP are booked separately for the same coaching link. As a result if particulars of LP are entered through manual crew movement detail same is not updated for the ALP on that link. Facility to book LP and ALP from the same screen simultaneously is to be provided.

  10. Bringing crew out of non run with out result of training etc

    When crew is brought back from non run many a times the result of the course attended is not known immediately. It should be possible to bring the crew out of non run w/o result as per following action. Option Result "awaited” shall be given in addition to Pass / Fail for training courses. When this is selected Supervisor shall be directed multi non run option for that crew. (One additional non run type "Shed duty” to be added for permitting working w/o result.) In this case the pass date shall not be required and non run available dare for the next non run shall also not be mandatory. When bringing him back from non run it should be possible to enter the pass date for the training The above scheme is applicable for refresher courses (REFT, REFD, REFE, RDE, RDET, RDT, RET) For promotional trainings (PD,PDET, PDT, PE, PET, PRSEL) if the result status is "awaited" edit non run option to be given to fill the result date as PASS / FAIL

  11. Duty hrs for certain non run reason

    "Duty hrs shall be given for the following non run groups Group 4 Group 8 Group 9 Logic of NIL duty hrs from 00:00 hrs to 12:00 hrs will not apply to these groups, configured hrs will be given irrespective of time of back from non run"

  12. SMultiple entry in "To non run"

    Facility for making multiple entry to be provided while crew is being sent to non run from the list of crew "awaiting to be sent on non run" Edit facility for the crew already in non run to delete or modify an entry in a row shall be provided in the option "to non run". This option shall be named as "To / Edit non run". This will be possible only for that crew who are yet to be taken back from non run. Current option of "multi non run" to be dropped.

  13. Non run form to have provision for cancel non run

    One additional check box to be provided in non run form for canceling of non run. This will eliminate the need for filling the date and time for canceling of non run.

  14. Non run group to be reorganized SCL and Inquiry to be changed from existing group

    Non run reason to be re grouped New groups to be formed Group 11 misc Group 12 other Above two reason will be removed from group 5 Edit non run allowance page to be modified for addition of following fields Admissible km All fields including above to have drop down feature for configuration. Drop down option to be as per table in running allowance document. If table does not have multiple option then only table value will be displayed with drop down disabled The default value should be N if not configured earlier, else show pre configured value

  15. Single Shift shunting TA

    In shunting module a new provision to be made for assigning duty to shunter for fixed hrs (minimum 8 hrs) shift, , under the name of shunting TA, On shunting console. Shunting duty to be assigned for one shift on the same day or next day only. Validity of the Shunting TA expires after the sign OFF. This duty is not to be repeated in coming week. All calculation to be done after sign OFF. flow is as under: 1 Call serve to be minimum 2 hrs before start of roster 2 OT will be calculated on fortnightly basis and not on the basis of individual shift. 3 date to be filled at the time of linking the crew on the roster 4 Max 10 shunters can be linked to a single shunting TA 5 Calculation of mileage is as per existing shunting mileage.

  16. Sister lobby concept for shunting

    Sister lobby to be defined for operation on shunting TA / roster. Sister lobby is required to work for Freight AND / OR Shunting module. This shall be configured at the time of creating sister lobby. At present all locations of the division are visible for creating main yard. Now only those CMS locations will be visible which have already been defined as sister lobby and all NCMS locations(NCMS lobby wayside station) Flow of work for Shunting sister lobby CMS location: Lobby A can create a shunting TA roster for Sister lobby B. Crew can then sign ON and Sign OFF directly from lobby B and also from A, depending on train pulling location. If lobby A requires to book the crew again from a different lobby or even from lobby A/B, the crew will be brought back to lobby A through a existing form (similar to Freight). After sign OFF at lobby B crew will not be available at any lobby till he is brought back. After this crew will be available at parent lobby (A), till he signs ON at any of the lobby. NCMS location: To cater to shunting from NCMS location (lobby / station), concept of associated yard / location name is provided. In case of sister yard crew will sign ON / OFF from parent lobby. No allowance for traveling from parent lobby to sister yard is payable. Lobby A can create a associated yard / location say B. Crew will sign ON / OFF at lobby A though he performs the duty at lobby B. Associated yard can be made only for NCMS location / Station

  17. Feeding of caution order in Hindi.

    Caution order to be filled in Hindi as well as in English. User should be able to view it as per the language opted on kiosk. In case Caution order is filled in only in one language, user should see it in that language irrespective of language selected on the kiosk.

  18. Alert for crew on link/Roster

    An additional alert to be given on the supervisor / TNC home page for crew on multiple link/Roster. On clicking the alert all such crew will be listed along with the link/Roster details.

  19. Cumulative km in present grade

    Personal detail should have two additional fields 1. Footplate km (Actual km, not mileage) for the month 2 Footplate Km cumulative since date of promotion / recruitment in the present grade)

  20. separate text field for ALP and LP rule violation

    Only one text field is provided for rule violation (jumping the crew order) Separate text field for ALP and LP is to be provided as rule may be violated only in one case and even it is violated in both the cases reason may be different for ALP and LP.

  21. No rule violation for crew booked on duty type as LR

    In case crew status has been ticked for LR (crew under LR) then crew name should appear in the list of crew as per rule. Even if order is not adhered to reason for rule violation shall not be required. For all those crew whose LR is not over due and they are available at HQ, crew name can only be fetched through "Fetch crew all" . This will not be taken as rule violation for fetching the crew. (This will be counted as Fetch crew by rule only.

  22. Automatic signaling over due

    Automatic signaling to be due after 6 months (as per GR) and not 1 year (as per SR)

  23. Retirement date

    For crew with DOB on 1st of the month the retirement date shall be last date of previous month.

  24. Redesign ate NON RUN OSRA

    The heading OSRA in NON run should be redesignated as NRDA (Non Running Duty Allowance) (Ref table of non run group).

  25. Fixed mileage routes

    Fixed mileage route to be extended even for non circular route (such that where FROM and TO station are not same).

  26. Booking of linked crew

    Crew is not available for linking from "As per rule" option

  27. Mail Exp link

    1. Same To station to be allowed (FROM and TO) 2. A new duty type "Waiting" to be added Mileage for Waiting to be @15km /hr

  28. Additional requirement for PAD and More than two hrs PAD/PDD to be highlighted in PDD reports.

    New form for PAD (similar to PDD ) to be provided in supervisor console with matching changes in report Data for Train Arrival and Departure to be filled in by supervisor. Additional field for Train Arrival to be provided in PDD form of supervisor console PDD = Sign ON to Departure PAD = Sign ON to Arrival Report shall be able to select the PDD / PAD duration for reporting Data for Train Arrival and Departure to be filled in by supervisor

  29. Shunting at starting and terminating station

    Presently Crew at the time of sign OFF can select a station en route (3rd from starting and last but one) he is required to select shunting en route and fill the station , shunting order and date Now he can select first or last station and will be required to enter shunting order no and hrs of shunting So a count will be given for each entry in mileage and shunting mileage @15 km / hr will be given for hrs (hr:min) entered (rounded off as per existing rule).

  30. Additional alert for PR

    In the list of crew availability (at the time of booking) Last PR date and PR hrs also to be displayed in alert for crew parameters (PME , REFT etc) NOTE- Instead of alert a separate column has been provided.

  31. Details of CMS users working on NON RUN

    Presently details of CMS users sending crew on non run and bringing him back from non run is not captured. Now the details of CMS users sending crew on non run and bringing him back from non run is will be captured and shown in reports.

  32. Lobby configuration console to have view rights on routes

    Lobby users can view the details of the routes eg inter distance km of stations in the route, min guaranteed section marking, ghat section marking etc through the Route display screen. This will be available on the click of the route no in the Route display screen of lobby configuration console.

  33. Alert while booking crew already on Coaching Link.

    In case of Crew to be booked on coaching TA an alert to be given if crew is already on some link. Links will be visible on mouse over in Crew ID in availability list even if linked on some coaching link BUT on rest. However crew can be selected for booking even if he is linked. This will hold good for ALP also for the lobbies which has segregated ALP working

  34. Abnormality reporting in manual entry

    Field for abnormality reporting to be added in manual entry data form. Related field and drop down menu will be given if TNC select YES option for abnormality reporting.

  35. Guard in coal pilot

    Option for booking of guard in coal pilot is to be given. Configuration table for loco pilot will be used for guards also. Mileage will be same as loco pilot.

  36. Time before sign On

    At present crew can sign ON 30 min prior to sign ON time in all modules. This is to be made 1 hr 30 min for shunting module for all the lobbies.

  37. Shunting TA group booking

    Sign On date on TA is open till first crew is attached Crew can be linked till 1. Sign ON time of the TA 2. Only exception is rebooking on the same TA if crew is in system non run TA visibility TA shall remain visible in link shunter form till all the crew linked on that TA has signed OFF and sign off is approved, but editing on this TA will not be permitted (View Only)

  38. Allowance to be given for both going and coming from Outstation

    At present Outstation allowance was given only for sending the crew to non run. It is required to be given for his return journey as well.So for non run reasons 1,2,3 , where crew was given Admissible kilometers just once, should now get it for his return journey also.

  39. SMS alert for PR cancellation

    When crew is called before completing the PR but after completing the 12/16 rest hrs, SMS alert to the crew/ guard and LI for PR cancellation.

  40. Min guarantee section mileage for shunting duty / spare

    In case of continuous run no mileage will be given for Shunting duty / spare duty type (For Freight only) if minimum guaranteed is applicable. Minimum allowance shall be given only if above combined runs includes a minimum guarantee section either completely or partially Note:-minimum guaranteed is calculated separately for all service type e.g. FGHT and DEPT

  41. Alert for mandatory requirement

    If crew is selected through fetch crew all option Alert thorough POP UP shall be provided for mandatory requirement overdue(if any) This shall also be indicated in report (New report console – Management – Crew counting).

  42. To check the respective training REFE/REFD

    At the time of booking the training to be check for REFE/REFD is as per the sheet provided.

  43. In WR duty type same station sequence not to be allowed for FROM and TO station

    In case of TA and manual entryif duty type is WR, same sequence no for a particular station shall not be allowed for FROM and TO station.

  44. Freight - Non run - To non run to be modified

    Rearrange the reason tree according to groups. First screen should show group name and configured values for the group. Non run reason for that group to be displayed on selecting the group.

  45. New form for FAILED NON RUN

    Alert for New form to be provided at Supervisor and TNC console Crew id, Crew name, designation, NON run reason, To Non run time, Compared sign off time, current status.

  46. Addition of New Button Fetch Crew All with LR Check

    New option Fetch Crew All With LR Check will be there in Crew Booking page.

  47. Capturing LR Violation Reason in Crew Movement Detail

    If in a run of crew movement detail LR of the crew is due then there will be alert to enter LR violation reason.

  48. Additional Field of Mandatory Requirement in Crew Booking

    In Crew booking list there will be an additional column of mandatory requirement due.

  49. Alert of LR Due at the Time of Call serve.

    There is an additional alert of LR Due at the time of call serve.

  50. Modification in NonRun Thread

    Modification in Nonrun Thread as per the logic of Multi Nonrun.

  51. Loco no and train no in abnormality reporting

    When crew is entering data to mention abnormality in system, loco no. and train no. should be captured and reflected in report, appended in SMS.

  52. WCAM1 / WCAM2 groups

    AT present only one group for WCAM1/WCAM2 Two seprate groups for WCAM1 and WCAM2

  53. Alert for loco no in TA

    An alert at the time of TA creation will pop up if the TA created does not have the loco no. User will be prompted for entering the loco no. although this alert will be optional to follow.

  54. Modification in Pop Up of Mandatory requirement due

    In case of Mandatory requirement check popup, if crew never worked on a particular section then their will be NEVER WORKED against the LR due date column.

    55. Kurla Issues

  55. Kurla Shunting duty ceiling of 240 hrs Special shunting

    Min 160Km, Hrs of duty (rounded OFF- Rule2) x 20, max limit 240 Km instead of 200 km for IR, to be hard coded for Kurla.

  56. Kurla Shunting hrs

    Mileages should be calculated on 8 hrs shift where as OT shall be paid after 9 hrs of working such that after 108 Hrs instead of 96 Hrs for shunters 108 Hrs instead of 104 hrs for LPG used on shunting as is the case for other lobbies. This implies At Kurla OT will be calculated after 108 hrs for LP, ALP, and Shunters.

  57. Kurla New designation for loco pilot ghat

    New Designation of ghat driver for CR crew of Bombay division. Provision will be made to designate particular crew as LPG Ghat in Bio-data. All functioning will remain same as Sr LPG .These crew will appear as LP Ghat in Reports only and does not affect Mileage statement. Non Standard designation, will affect the flow mainly for Officiating promotional hierarchy Addition in reports Not advisable for lobby specific designations, shall be done for designations common across IR Provision will be made to designate particular LPG as LP Ghat in biodata. All functioning will remain same as LPG. These crew will appear as LP Ghat in the reports only. ).