Facility provided in CMS Application

The New Software Functionality Developed in CMS ver. 5.1 shall have the following features.

    APPLICATION

  1. Footplate Km along with promotion date in biodata.

    Presentl footplate km were shown against the current desigantion only.
    1. Add button provided in Biodata OTHER tab for promotion/demotion, to add all present and past designations
    2. Generate Footplate Km button added in Biodata OTHER tab.
    3. Now after promotion / demotion date is filled and generate button is clicked, the footplate km relevant to the date and designation will be generated.
  2. LI grading and counselling through SMS

    Sign On/Off at places other than CMS lobby (wayside stations/ASM Point) is sometimes required because of –
    1. SMS based grading and counselling provided
    2. In case of Grading, only final grade will be sent by SMS by LI, separate form is required to be filled for other details like marks to complete the Grading
      In the present system grade is generated based on marks given. However if grade is directly filled by SMS same will be validated once marks are filled and marks will not be allowed to be saved if validation fails. In case marks are not filled within 15 days an SMS will be generated for reminder to LI. LI will be taken to the marks form directly once he log in in the system.

      LI Grading SMS String format : GRAD <CREW_ID> <DATE> <GRADE>
      <CREW_ID> = CREW ID, which crew's grading is to be done
      <DATE> = For which date grading to be done, Date should be in format DD-MM-YYYY
      <GRADE> = Grade that is needed to be give to CREW, possible values - A,B,C,D
      Example: GRAD ABR1001 22-04-2014 A

      LI Counsalling SMS String format : CONS <CREW_ID> <DATE>
      <CREW_ID> = CREW ID, which crew's grading is to be done
      <DATE> = For which date grading to be done, Date should be in format DD-MM-YYYY
      Example: CONS ABR1001 22-04-2014

      Above SMS are need to be send on 08860622020
  3. Suburban for Guard

    suburban module for Gurads provided.
  4. CMS Loco Type master to be changed and synced to FOIS locotype master

    Old Loco group (with multiple loco type) to be changesd to new loco group (with single loco type) Seperate Loco group name provided in CMS so that FOIS loco master and CMS loco master can come in sync and Loco integration is made easy.
    Traction - Electric (Conv/3Ph/DCAC/EMU)/Diesel (Conv/MG-NG/DMU) / DUAL Loco Type - drop down of all loco type of that group, with AJAX (Auto suggest)
  5. Integration with FOIS on Loco master to be done and loco group master to be redesign

    Earlier TA was made by selecting
    1. Traction:
    2. a) ELEC
      b) DSL
      c) ELEC+DSL
      d) 3PH
      e) ACDC
      f) MEMU
    3. Loco Type:
    4. The Loco types were earlier appearing as group, with competency being upgraded for all the loco type in a group.
    5. Loco No:


    Now this has been redesigned in line with FOIS data and loco master database is synced to FOIS database
    1. Traction:
    2. a) ELEC
      b) DSL
      c) ELEC+DSL
    3. Loco No:
    4. Writing the loco no gives the loco type as per data base (user can edit the loco type for that TA with correct loco type if required.
    5. Loco Type:
    6. Now all loco types are arranged seprately. Loco competencies to be upgraded for other loco type as a result of running a particula loco type has been made flexible.
    7. A list of all loco types and the competencies of other loco type to be updated for any loco type is enclosed as annexure.
  6. Officiating

    Mail exp Guard added
  7. Edit phone no.

    Presently if a CUG no is linked with a crew ID same no can not be allotted to another crew.
    Now if an existing no is re-entered for another crew ID, reason will be required to be recorded and no will be deleted from old crew biodata
  8. Edit facility in divisional console

    Presently if a CUG no is linked with a crew ID same no can not be allotted to another crew.
    Now if an existing no is re-entered for another crew ID, reason will be required to be recorded and no will be deleted from old crew biodata.
  9. Edit facility in divisional console


    Presently PF and Employee no, can be reset from CRIS only. Now Divisional consloe can reset PF no and Employee (log of reset to be kept). Lobby can enter fresh PF no once it has been reset from Div console.
  10. Selective display of circulars Lobby wise / Cerw typ wisw / Traction wise

    Circular up loaded in Divisional console are become available for all lobby. Option has been given to select lobby for which circular is meant.
  11. Making crew available at lobby from where he has been sent on enquiry.

    Presently a crew if sent for enquiry from OS is made available at HQ. Hence OS lobby can not book the crew even if crew is at OS lobby.
    Now while sending on non run from OS lobby additional field has been provided for indicating station of availability. (default will be station of sending,)
    1. Non Run Reason for these cases will be same as those allowed in sending non run from other station.
    2. In case station of availability is not same as station of sending option for spare mileage similar to transfer to be provided
    3. Station of availability can only be station of sending or HQ lobby
    4. At present system does not cater for mileage (spare) if a crew is sent to any location other than HQ from an OS lobby for non run reason. Third location even if different from OS will not be captured in the system
    5. Crew will start appearing in non run list of available station.
    6. Option to add PR while sending will be available only if station of availability is HQ and not OS
  12. BA token no

    A new field for BA token no (numeric 4 digit) added in
    1. Sign ON
    2. Sign OFF
    3. Signon Approval ( Read Only)
    4. Signoff Approval ( Read Only)
    At time of sign on/off approval the BA Pass/ Fail column will now require to be filled with Alcohal value, based on value filled colour of the box to change as Red, Yellow Green Range has to be specified for colour. At present colour will be green for '0' and Red for all values other than zero.
    In case of integrated BA device value will be captured automatically.
  13. Field Resign not available in Biodata.

    one more reason for resign added in permanent inactive
  14. Crew LR for particular section done date is lacking.

    In case more than one trip is required for LR the done date is changed only when all LR trips are complete. Footnote has been provided for such cases to indicate privious run on that section for LR.
  15. Validation check for Shunting hours to be lesss than total duty hours

    Validation check has been provided so that sum of all shunting hours filled is not greater than total duty hours from sign on to sign off
  16. Total duty not correct in availablity list of crew

    Presently if crew works duty as working and returns back as spare, system is spliting duty hours on the basis of duty type and calculate and provide rest as per last spare duty type only.
    In case of continuous duty even though duty type is different the rest shall be based on combined duty hours. (release may 2015)
  17. Shunter module Manual sign off

    Shunter module - Manual ENTRY FORM presently allowed for crew on temp transfer cases only.
    For shunter module - manual entry form has been provided for crew who sign on at HQ kiosk, as is the case for freight crew.
  18. Inactive crew to be removed from Bio-data table

    Inactive crew removed from main datatbase, resulting in reduction total biodata count.
  19. Facility to generate Traffic Advice from Divisional Console:

    In normal practice TA details are relayed to crew controller stationed at lobby by TA clerk sitting at Divisional Control Offices, facility to generate Traffic advice from Divisional Console is provided with following feature:
    1. Divisional console has a new form to generate Traffic Advice with lobbies selectable in radio button.
    2. TA generated will start appearing in the TNC console present in Lobby.
    3. System will check for duplicity by mapping the Train Ordering & FROM-TO station and will alert Lobby user to make same TA and vice versa by displaying maching TA at the time of saving the TA.
    4. Display logic for TA in crew booking form is unaltered.
    5. This feature to be enabled for a division only from CRIS Admin console on the basis of request received from railways. Presently feature to be given to BSP division.
  20. From and To station in Abnormality Entry

    User is required to select 'To' and 'From' station for every abnormality entry.Drop down list will display all the stations in that route.
  21. Routes creation through front end

    Presently routes are created at database level. Now a new form for CRIS use has been made for creation of routes. At the time of new route creation, if the route aleardy exists in database, alert message "Route already exists" will be flashed, to avoid route duplicity. Necessary fields for date and time of creation of route has also been included in the database.
  22. Memo no. entry in PME

    At the time of return back from Non Run for reasons PME and SICK, a new field for memo no has been provided. This memo no field is a text filed which will have no validation on the text entered
  23. New Group for SMS

    New Group in SMS alert 'DND Alert' Any mobile no fed for receining SMS in any SMS group is sent a SMS for giving consent through return SMS for receiving SMS through CMS system. Now a SMS wil be sent to preconfigured no in DND alert for all such crew/user who have failed to give acceptance by return SMS
  24. Coaching Call Serve

    IN Coaching Serve Call, The crew status showing SIGNON,BOOKED,CALLED etc.If the Crew is BOOKED or SIGNON or CALLED for the same train as in the link, The status will be shown in Green color.If the crew is SIGNON for some other train,the status will be shown in Red color.
  25. Forced sign OFF

    A new provision of forced sign OFF has been given at Divisional console (to cater cases like BA fail, death etc.). Reason for forced sign OFF has to be recorded. No record like LR and Mileage will be generated in case of forced sign OFF Scheme of things-
    1. Link on Div Console
    2. LIst of all Signon Crew after Signon approvalof that div
    3. Forced Signoff Reason may be Dead,BA FAIL, Accident, SICK + user provided reason
    4. Mileage will not be prepared
    5. Compitencies not to be updated
    6. For these cases journey will be deemed to be incomplete.
    7. Forced Signoff station to be entered (autofill textbox/combo for station code)
    8. Forced Signoff time.
    9. After Forced Signoff crew will be in REST/InActive/absent(intellegent default based on reason) selectable by div
    10. Signoff Approval not needed for such cases.
    11. Bring to HQ
    12. Remarks
  26. SMS to multiple crew at a time

    At present SMS can be sent for maximum 5 memebers at a time. Provision to be made to sent all crew at a time
    New function on Divisional console
    Select (with multi select option) Lobby
    Crew type (including LI)
    CMS users (Supervisor and TNC)
    Traction
    Text field for message entry (140 character)
    A Master of lobby officer JAG (JAG officer incharge, Sr DEE, Sr.DME, Sr.DOM) and Lobby officer Sr/Jr scale (AEE, ADME, AOM) will be created at CRIS level with address and mobile no.This no can be added in addition to 5 nos in the group. SMS group configuration screen to be modified accordingly. Lobby officer will also be notified by default if the count of messages from the above function exceeds 100
  27. Conversion of ABSENT to other Non Run

    At present only NO CHANGE, CCL, CL, IOD, LAP, LHAP, MNTL, PNTL, PSICK, SL, CHCL are available in drop down
    Conversion of absent to the following reasons is requested
    1. NHA
    2. LWP
    3. SCL
    Disabling finger print scan for selective crew witout the need to
  28. Disable the scanner on the kiosk

    It has been observed that in case of old crew or crew with injury, finger scan is not possible.
    A new field for 'Bio Enable' has been provided in crew biodata other page for enabling bio to Yes or No for the specific crew. Default status is YES. If disabled such crew will not be required to do finger print scan even if thumb reader is attached to kiosk
  29. Crew Bio data

    In crew bio data screen mail Id entry will be added which help to contact through mail also.
  30. Cadre strength for suburban

    One new Cadre strength column for suburban motorman has been provided in lobby configuration console
  31. Provision to Calculate Average Detention

    Two more fields Train Arrival Time and Fois Train arrival time will be added in PDD form.Avg detention will be calulated through ...Avg Detn.= Train Dep - Train Arr. An additional field for reason for detention
  32. Abnormality by LI

    Facility has been provided so that LI can enter abnormality on behalf of Crew as is the case for supervisor. For this link for entering abnomality has been provided on LI Console
  33. Facility to send crew directly from one training institute to other training institute.

    Presently crew can be sent to one training institute from HQ and admissible km are paid for to and from journey w.r.t HQ
    There is no provision for spare movement of crew in CMS from one training institute to other Admissible KMS option is available in configuration console. Training centre to other training location facility is not currently available.
    The provision has been made for above with work flow as under-
    1. For any lobby training location are cofigured in Lobby Configuration console.
    2. A sattelite training location will be required first to configured as main training location for the lobby Any training location can be added as satelite location out of available main location. maximum three such satelite locations can be added for such main location.
    3. In the Non run form additonal plus button has been provided to add sattelite training location.
    4. It will be assumed that crew will return to headquarter from sattelite training location unless an additional row from satelite to other or main training location is made.
  34. configurable available time after non run (leave)

    1. Division can configure Thru ADMIN console - Next availability (for leave type of non run only) i.e 00,06,08 hrs
    2. In Non Run module the non run for such types to start from the configured values (release by may 2015)
  35. Provision for 22 or 30 hrs REST along with CL & LAP

    While sending a crew in non run additional option on the form to include a PR after non run (System will get crew out of non run as is the case now and will automatically convert his status to PR in the availability if PR is there instead of showing normal rest)
  36. NH modification

    Non Run Roster
    1. In non run roster if duty is preformed for a part of day on pre configured NH, Count for NH will be given.
    2. Roster shall have the option to change non run reason as NH in that case no count will be given. Non run Module
    3. In case of training also NH count will be given if NH falls during training.
    4. Absent to leave conversion shall have option for NH too.
  37. Cancellation of combined PR

    In case of cancellation of PR (44, 52, and 60) both PR are cancelled even if cancellation is after completing on PR of 22 or 30.
    In case of combined PR count shall be for two PR of 22/ 30 as the case may be If combined PR is cancelled , check if 22, 30 hrs have been completed in case of 52 hours of PR and 22 or 30 respectively in case of 44 and 60 hrs PR
    The following is to be done in application -
    1. In Case of PR cancellation the part of PR coverred at the time of cancellations is to be coutned as PR and teh uncoverd part needs to be canceled only.If combined PR is cancelled , check if 22, 30 hrs have been completed in case of 52 hours of PR and 22 or 30 respectively in case of 44 and 60 hrs PR
    2. SMS for such cases to be given to crew only.
  38. PR before Leave

    PR can be combined post leave. PR will start at the end of leave i.e. 23:59 hours
    PR can be combined pre leave, only if PR is ending before 12:00 hurs, but this result in cancellation of PR as leave starts from 00:00 hrs.

    Change
    In case PR is ending before 12:00 hrs leave can be given (leave cannot be given for the same day if PR is ending after 12:00 hours) but in such cases leave time will start from end time of PR and PR will not be cancelled (as is being done in Non run reason having immediate availbality from the time of coming out of non run through manual)
    This should also be followed for future leave. Since future non run thread is operated at 23:50 hours, crew status will change to leave, even though crew is in PR. Such crew though in PR will not be made available for booking in fetch crew. Report generated during such period will also shoew crew in leave though he is in PR.

    Further extension for other non run (ver 5.2)
    This logic will apply to all non run reason in addition to leave. For other non reason restriction of PR to end before 1200 hours will not apply. In case non run is to be granted on the same day and PR is contnuing then non start time by default will be PR end time and PR will not be cancelled. (In case time of NOn run is altered before end of PR, the PR will be cancelled)

    Report
    Muster report to have dual status on all such day
  39. Period of working before PR

    Presently Working period is counted from the last worked status befor going for PR.
    Working period should be counted from end of PR and also from end of non run.

    Report
    Alerts to be modified accordingly
    Report also modified accordingly
  40. Rename Promotion tab in Biodata

    Promotion Tab to be renamed as Promotion/Demotion
    Next entry can have lower designation also
  41. Permanent transfer

    Currently when a crew is transferd permanetly the old id of the crew is not mapped to the new ID.
    Now it is provisioned that the new Id generated will have mapping with the transferd ID as well. This willl help in fetching the footplate KM of the CREW irerespective of his ID.
  42. Slate Module

    Slate lobby Configured for Slate next booking.A configuration screen for slate lobby.Two options will be there 1. TA to TA,2.TA to Slate . As per selected option crew next working will be displayed in kiosk signoff.In sign off approval supervisor has the option to book that crew, not as per configured option for that lobby by giving valid reason.
  43. VCD entry

    Application has been modified to carry forward kiosk entry. If crew opts for manual entry after signing off at Kiosk, VCD position as filled in Kiosk will be carried forward in the manual data entry form..
  44. SMS

    Priority SMS sending as : 1. CMS, 2. AIMS, FOIS, ESS, 3. Other CRIS groups, 4. New SMS Group for Division Console.

Reports

  1. Management - Sectionwise Train

    Monthly Section wise & Total no of Goods & passenger Trains :
    1. Section
    2. Nos of Goods Train (count)
    3. Nos of Passenger trains including service types CCHP, (count)
    4. Nos of M/exp train CCHM,CCHR,CCHS (count).
  2. Management - Sectionwise Train

    Drill down provided with following details
    1. Date
    2. Train No
    3. From station
    4. To station
    5. Loco No
  3. NonRun - Ineffective Crew

    Duty hours of running staff working in NON RUN ROSTER also shown Name of running staff also appear in 'Ineffective crew report".
  4. Management - Booked W/Wo rule

    One more column for Reason is added
    Rule violation reason in "Fetch all" were not available for Caoching and Shunting cases. Reason for this to be recorded.
  5. Management – Crew position

    Drill down on Total count provided.
    Position of LPG/SLPG and ALP/SALP combined and put side by side
  6. Management - Wheel Movement

    For continuous run
    Wheel movement is calculated as {(Arrival time-Dep Time)-spare duty time} Report modified for count (with drill down) for following range of wheel movement <8, 8-10, 10-12,12-14, >14, Total Drill down gives details of each run
  7. Non Run - From Non Run

    Field for Non Run code to have PME / Memo No, SICK / Memo No
  8. Management – crew position

    Additional column for total count in running as well as non run added, both in current and midnight
  9. Manage - Avg Rest

    Detailed report available. Summary provided
    1 Out Station wise - count , Total Rest hrs, average rest hours
  10. New mobile Application Reports

    Some reports are being displayed on mobile internet for officers. following reports which are very useful LI/LP/ALP has also been displayed on mobile internet.
    1. ALP/LP can see his crew sign on detail and crew availability report by placing his CMS ID and Password.
    2. CLI can see Crew availability report and counseling and grading report ( as given in Loco Inspector report).
  11. Manage - Turnaround

    Only count for crew below 36 hrs duty was provided. New column for duty hours 24-36 hours added. column for 0-36 now shows 0-24 Hrs. Detail list below count shows all cases > 24 hours
  12. In PR count, date PR given to running staff is not shown

    Date of PR will be shown on clicking the count.
  13. Crew Run Details

    1. Admissible KMS were paid two times once at the time of sending crew on non run and secondly at the end of slot.
    2. Tantative mileage calculated at the end of period is correct but once crossed next slot and crew brought back from non-run this also include mileage of earlier slot on final calculation.
    3. Crew in non-run roster if brought back from roster, his cumulative hrs of previous slot are not adding.
    4. Current slot to show the tentative Mileage, if crew is in nonrun.
  14. Mileage - Over Time

    Tentative Mileage for Current Slot also added in the report.
  15. Mileage - Mileage Summary

    Tentative Mileage for Current Slot also added in the report.
  16. Mileage - Mileage Summary (New)

    Tentative Mileage for Current Slot also added in the report.
  17. Mileage - Over Time (New)

    Tentative Mileage for Current Slot also added in the report.
  18. Mileage - NonRun Allowance

    Tentative Mileage for Current Slot also added in the report.
  19. Mileage - Shunt Count

    New report to cross check the shunt count entered by the crew :
    Crew ID
    Crew Name
    Shunting stations
    Shunting date
    Engine No
    Start Km
    End Kms
    Duty min
    Total Shunt count
    Sign Off Lobby
    Supervisor id
    Supervisor Name
  20. Mileage - Mileage Summary

    Shunt Count Drill down on click of shunt count of perticular crew
  21. Crew Non run Allowance report

    Filter for traction type i.e Dsl, Elect given
  22. ==
  23. Promotion/Demotion date to be shown in Crew Personal Data form

    Crew - Crew Biodata detail : To show promotion history instead of last promotion only Column required:
    1. Old Designation.
    2. New Designation
    3. Last promotion Date
    4. Promotion done by user_ID
    5. Footplate KMS of original designation a) CMS calculated b) User filled c) Total
  24. CREW -> TA Booked

    S.No., TA.No., FROM, TO, Dr1 Id, Dr1, Name, Dr2 Id, Name, Ordering Time, PDD, Sign On, Departure
  25. expdb MILEAGE REPORT

    Crew working under non run roster, this crew name is not apearing in expdb mileage report.
  26. Provision to Calculate Average Detention

    Average detetion & PDD report Daily average with column
    1. No of trains
    2. Avg detention (Avg detn=T dep - T arr)
    3. Avg PDD
    Monthly progressive avg with column
    1. No of trains
    2. Avg detention (Avg detn=T dep - T arr)
    3. Avg PDD
  27. Manage > Crew due for PR

    Report regrouped in three categories
    1. PR due for any of the reason (rows having red in one or more column)
    2. Crew not due PR (but not in non run)
    3. Crew in non run
    Also indcated
    1. No of days since last PR along with N and Y
  28. Manage - Sign On/Off

    Manage - HQ Sign On, HQ Sign Off and Sign On / Sign Off Monthly Summary Merge
  29. Manage - Sign On/Off

    New Radio button for Continuous Duty Sign On Report:
  30. Manage - Sign On/Off

    New radio button for Continuous Duty Sign Off Report:
  31. Manage - Avg Rest

    Detailed report available. Summary under developemnt
    1. Out Station wise - count , Total Rest hrs, average rest hours for all crew
  32. Cancellation of combined PR

    Such modificaion will be intimated to crew throgh SMS ("Your 60 hours PR has been modified to 30 Hours PR")
    1. All report shall be based on PR availed (not on sent to PR)
    2. In case combined PR is cancelled after one PR in combined PR is availed fully such cancellation will not be counted in PR cancelled report.
  33. HQ sign off/sign off

    BA test result also displayed in HQ sign On report
  34. New report

    Train wise working particulars are not available. To know the running of schedule coaching trains, train wise working partculars for a period to be provided.
  35. PAD, PDD reports-Running

    Facility to generate PAD and PDD Section wise
  36. Report->RUN- > Rest > 12 Hours

    Rest Modification cases has to be included in this report.
    i.e If rest is modified as 22,30,52,44,60 hrs, it should reflect.
  37. Foot Plate KM

    A new report for footplate difference from earlier report. Columns are
    1. Data since march 2012 to jan 2015. Data to include
      1. actual
      2. spare
      3. LR
    2. Data since begining of CMS to current date
      1. Actual Km
      2. Spare Km
      3. LR
      4. Total
    Footnote for explanation of data to be provided i.e The data of footplate KMs is CMS has been corrected since Jan,15. Now Spare and LR Kms are not part of footpalce KMS for all data available in CMS.
  38. Cut-off Date for footplate

    1. Cut Off date required for Actual FPKM report, for promotion purpose
    2. Report will be segregated as crew with LPG promotion date and W/O LPG promotion date
    3. In case of transferred Crew report will give the data as per the new ID with a remarks that old data needs to be collected from transferred lobby.In future after mapping of new and old Id the data for such cases will also include previous run kms.

Integration

  1. DRUMS Integration

    Whenever abnormality is filled by the crew of ECO Railway it will be forwarded to DRUMS software.
  2. CMS - ICMS Integration

    CMS will share the detail data of running loco in the CMS system through TIBCO.