Software Functionality Provided in CMS Version 5.2, Released on 24th Nov. 2015

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

    APPLICATION

  1. PR before Leave

    Done in 5.1
    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 hours, 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 availability 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 show 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 continuing 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.
  2. Absent in Non run roster

    In roster - non run reason "absent" has been given.
    These cases have also been tackled in conversion of absent to other reason as is done in case of non run without roster.
  3. Cation Order Header

    Caution Order header currently have -
    1. DATE
    2. Issued By
    3. Lobby
    4. Caution No
    Now the caution order header is modified to have the following-
    1. Current Date
    2. No of cautions
    3. Lobby
    4. Route Name
  4. Route no in TA

    Currently only route name is visible in the selection dropdown of routes. Rotue no will also be visible along with route name. Display will be Route name - Rote no. Sort order will be on route name. The following forms have been suitably modified -
    1. TA
    2. Manual
  5. Facility to mark LI Inactive

    Facility to mark LI as inactive has been provided. LI who has been marked inactive will not be allowed to log in .
  6. Abnormality reporting

    Addition fields for abnormality repprting has been added
    1. From KM
    2. To KM
    Forms affected are
    1. Abnormality form - CREW
    2. Abnormality form - Sup
    3. Abnormality form - LI
    4. Abnormality approval form
  7. 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 password
    2. User Name cannot be part of password
    3. Lobby code of that particular lobby cannot be part of password
    4. Password cannot be same as last password.
    5. Password must be Alphanumeric
    6. Password length must be >=6 and <=8
    7. Password cannot contain special character
    8. Password for thin client users (TNC, SUP etc.) is case sensitive.
    9. Password will expire every six months
    10. Password have to be changed on first Login
    11. 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 characters
    2. Password cannot contain three or more sequential numbers
    3. Password cannot contain three or more repeating characters
    4. Password cannot contain three or more repeating numbers
    5. Special characters to be allowed to increase the strength of the password
    6. One special character will be made mandatory in password
    7. cases of frequent reset will be notified to authorities through sms/reports for 5 or more reset in a month.
    Password Policy (Not Recommended)
    1. 1. Restriction on duplicate password in a lobby.
      1. Security concern – It may reveal other users password and may tempt user to try to hack others account by hit and trial.
      2. Privacy Concern – For determining duplicity others passwords needs to be read and compared.
      3. Load concern- Although minimal since password is to be matched against all users of a lobby only (avg. 700 comparisons)
    2. 2. Password having a defined pattern eg. Crew ID+123 / crew ID + crew name initials etc.
      1. Security concern – It will defeat the basic purpose of password security
  8. Reset Password

    Password can be reset by done by next higher authority. e.g.
    User/Crew by SUP console
    SUP by Lobby configulation console
    Lobby / Div by CRIS
    User / Crew can request for reset password. Supervisor has been given a new function to reset password.
    Once reset the new password for
    User : default new password is filled by supervisor
    Crew: default new password is 123
    This new password can be used for login only. User/Crew will be required to change password on first login to change password after reset password.
    A SMS is given to the concerned User/Crew "Your password has been reset by on "
  9. Div console CUG Mobile bill loading

    New Function provided on divisional console for up loading of CUG bill for the purpose of identifying cre who has used mobile between sign ON and Sign OFF
    JPO issued vide Railway Board Procedure Order No: 2010/Tele/2(1)/1/Pt. dated 12-10-2015 Click Here to view
    For uploading user has to Select
    1. Lobby
    2. Bill cycle (for refernce only)
    Excel files (All excel format .xlsx, .xls, .csv) loaded will be displayed as
    1. loaded
    2. Processed
    Validations
    1. File with the same name can not be loaded by the same division. (However same file name can be loaded by different division)
    2. File size greater than 2 MB can not be loaded
    3. Loaded file if not processed due to corrupt/invalid data will not be processed and same will be indicated as NOT processed.
    4. Duplicate files even if loaded will not affect the report
  10. CMS on internet

    CMS application can be accessed on Internet for LOCO SUP and LOCO TNC users
    Lobby needs to be enabled for internet access. A new user id for internet access needs to be vreated for these functions even for the same person. Existing user id will not be allowwed for internet access as on date.User will be sent an OTP (one time password) every time he tries to access CMS over internet.
  11. Change in LR due scheme

    New LR design with division configurable LR types
    1. Period of abscence shall be calculated from drive date instead of LRdue date (This implies that where periodicity of LR is selected as 6 months, 3 - 6 months period of absence will never arise)
    2. LR requirement will be configured by division for no of trips
      Period of absence from drive date Type I Type II
         D   N   T D   N   T
      3 to 6 month   1    0   1 1    1    2
      6 month to 2 years   2    0    2 2    1    3
      2 years and above   2    1    3 2    2    4
    3. For LR total no of runs must be completed.
    4. Night Runs over and above the min requirement will be credited to day
      1. a) In case of change by the division of the applicable LR type, The additional night run due date will be updated same as last Day run.
      2. b) This implies that if LR was not due and Type is changed (say from Type I to Type II) crew may get a window of 1 day to 3/6 months (depending on date of change and his due date for updation 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 trip required 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 1700 to 0800) with duration for night from 1 min to max hrs
    7. Log of change to be maintained
    8. Form affected
        1. Crew Sign OFF approval
        2. Manual CTR
        3. lobby configuration -> LR config
        4. crew booking form
  12. Night in bed in PR

    Present system accepts any period between 22:00 to 06:00 falling in sanctioned PR as night in bed. An alert to be given to the crew / supervisor if the opted PR does not cover 22:00 to 06: 00 fully Alert
    "Said rest does not cover night in bed from 2200 hrs to 0600 hrs please choose other value
    22 hrs PR can not be given if sign off is from 2201 to 0759
    30 hrs PR can not be given if sign off is from 2201 to 2359"

    ON KIOSK
    CASE 1 sign off time is between 0001 to 0759 hrs : crew will be prompted to select 30 hrs rest
    CASE 2 sign off time is between 2200 to 2400 hrs : crew will be prompted to select higher rest (30+2, a new category which effectively is 30 hrs rest extended by 2 hrs to cover night in bed) SUPERVISOR APPROVAL
    1. 12/16 hours rest can be converted to any PR (22, 30, 32, 44, 54, 60) subject to above case
    2. PR requested by crew can be converted to 12/16 hrs rest (validated for duty hrs)
    SMS will be given to crew for approved rest IN no case
    1. 22 hrs rest can be granted for sign off time is between 2201 to 0759 hrs
    2. 30 hrs rest can be granted for sign off time is between 2201 to 2359 hrs
    Form affected
    1. Crew Sign OFF
    2. Crew Sign OFF (Manual)
    3. Sign OFF approval
    4. From Non run
    5. Rest Modification
    6. To NonRun(Back date Entry)
    7. To NonRun- Back date mileage generation
  13. Modifications in Energy meter reading for Regeneration and SFC etc. Removal of multiple loco detail from TA

    Following fields have been added
    1. Regenerative meter reading at start
    2. Regenerative meter reading at end
    3. Gross Ton (for GTKM)
    (ultimately to be integrated with FOIS and pre populated)
    Additional fields demanded are (but not provided)
    1. blowers off time
    2. coasting KMs
    3. panto lowering time
    SFC = Diesel - Fuel consumed/(GTXKM)
    SFC = Electrical - (Energy consumed - Energy generated)/(GT X KM)

    Energy and load related field to be active for driver only

    Validations
    1. regeneration can be entered for Electric traction only.
    2. GT should not to be > 15000 = A,
    3. Energy Consumption to be < 25000 = B,
      Note: Value A & B are variables which can be changed later on.
    4. Energe consumption fields will not be visible if duty type is SPARE.

    SFC will be displayed on click on (5 previos run excluding current run)
    1. Sign OFF screen
    2. Sign ON screen

    Proposed Validation
    Entry for regenerated energy will be captured only for run with 3 PH Loco/Loco with Regeneration meter.
    Such as (WAP5, WAP7, WAG9 & WAG9H).
    Loco No.2 option has been removed from TA. 2nd an additional Loco are handled through energy meter reading during sign OFF on KIOSK as well as in manual data entry The additional column has the following fields:
    1. Loco Dead
    2. Loco Spare
    3. Energy Meter defective
    4. Working loco
    For 1-3 points above, Energy meter / regeneration reading meter column is be non editable.
    But if user is filling working loco then data entry is required.
    All above fields to be captured in database for further reports.
  14. Shunting Module with BA TOKEN NO.

    Shunting module has been provided with option for BA Token No. & BA % Value.
  15. BA Value in Manual Entry

    Option has been provided for BA% in Manual entry form for Coaching/Freight/Shunting.
  16. Swapping TA, CREW

    During swap following checks are missing

    Case 1
    TA1 Fetch all & TA2 Fetch all
    (LR, Lcoo competency, Auto signalling, Ghat, Officiating)
    No validations to be applied only alert has be given

    Case 2
    TA1 Fetch all & TA2 Fetch by Rule
    (LR, Lcoo competency, Auto signalling, Ghat, Officiating, REFE/REFD)
    alert has been given till validation is applied

    Case 3
    TA1 Fetch as per rule & TA2 fetch as per rule
    (LR, Lcoo competency, Auto signalling, Ghat, Officiating)
    alert has been given till validation is applied
  17. Accident Allowance

    Check box for accident allowance to be shown only to those crew whose duty hrs is >=8 Hrs. On manual & Kiosk.
  18. MCC Lobby is Replaced by BCT Lobby

    Lobby code has been changed to BCT from MCC
    1. All the data in the database including history data has been corrected.
    2. Application wide changes has been implemented
    3. user ids have been retained even though the user is now linked to new lobby code
    4. Crew id and LI id have been modified with new lobby code.
    5. MCC has been replaced with BCT in various cases e.g. Routes, Training locations, LR etc. B26
  19. Coal pilot

    Presently rounding off for hours is done at individual set as per Railway Boards rule for rounding off for individual run. In case of coal pilot rounding off shall not be applied and mileage to be given on proportionate basis for each minute.
  20. option for EOL

    Service type - ENONL has been renamed as EOL
    Port shuttling and EOLhas been separated
    Mileage - EOL
    @20 km per hour max 200, No minimum
  21. VCD values entered at Kiosk should be captured for CTR entries

    VCD entries already made on KIOSK will be carried forward in manual data entry forms if crew opts for manaul data entry from KIOSK
  22. PME SICK

    Demand has been raised that PME SICK should always be followed by PME
    This can be be tackled through Multi Non Run
    Cut off time for PME and PME Sick mileage on a date should be as per 12:00 Hrs Logic.
    PME SICK shall be treated as leave only (TEST/Traning "Y" flag to be removed for PME SICK. PME SICK is only a Leave not TEST/Training.)
  23. OSRA in Manual data entry

    OSRA was being given as per data entry in manula data entry form.
    Now OSRA is required to be given in case of crew on temp transfer. Facility to claim OSRA in Manual data entry has been removed. OSRA will be based on temp transfer and will be decided by the system.
  24. Associated Crew display at Sign ON.

    After crew completes his sign on the last screen (wish u a safe journey ) will also display crew ID, name,desig and CUG no of associated crew.
    Normally screen auto refreshes in 10 sec. Now since detail of associated crew are also displayed a 'HOLD' button has been provided on the screen. Pressing it once will delay the refresh cycle by 40 seconds.
  25. Duty Hours Alerts(<30Mins , >16 Hours) and Restriction(>24 Hours)

    Alerts For
    1. Duty hours <30 Mins ,
    2. Duty hours >16 Hrs And
    3. Duty Hours>24 hours
    Forms affected
    1. 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)
  26. Same sign ON time for different runs in manual data entry

    Action proposed:
    Following validation will be provided
    Difference between Sign OFF to Sign ON shall be more than1 min.
    This will ensure that sign OFF and hence subsequent sign ON are not same as previous sign ON.
  27. SHUNTING

    BA fail functionality extended to shunter module.
  28. Supervisor KIOSK Functions

    Additional functions have been provided for supervisor on KIOSK
    1. BA device test - Supervisor can test the BA device for functioing
    2. Reregistration of finger print - This will rewrite on the old finger print image.
  29. CMS client image ver 3

    1. Bulk registration of finger print - Additional function has been provided where finger prints can be registered in bulk even in OFFLINE mode. However if fingerprint is already available on client or central server database, registration of same will not be allowed through this function. It will require reregistration through Supervsor KIOSK function only.
    2. Client image has been tested with differnt technologies for CMS access
      1. TOMCAT Server
      2. Webview (particularly for using android devices as client)
      After trials TOMCAT is being used at present.
    3. The finger print image is initially stored at Client and is synced to CMS database as the client is connected to server.
    4. Finger print image for any crew who tries to log in is searched on Client database then on Server databse. In case image is available on server database same is loaded to client database. Registration is initiated if image is not aavailable on Client as well as server database. On registration both database are updated
    5. At initial loading of image user can select the BA and BIO device installed at his lobby (provided device is already integrated into the image). User can also configure the time out interval for BIO and BA after which flow will be taken further.
    6. Client needs minimum of 4 GB ROM and intel or compatible processor for Client image ver 3 to run. For clients with right processor but less ROM facility has been developed in image itself to boot the client with pen drive.
    7. Client can detect if BA or BIO device has been connected to client.
    8. User can enable or disable BA and BIO device in the image
    9. Following BIO devices are integrated
      1. SECUGEN HFDU06
      2. SECUGEN HU 20
      3. NETGEN HFDU06
    10. 8. Following BA devices have been integrated
      1. TAYAL TECH KATS
      2. MISCOS KY8000 (does not support device turn ON command from system, function)
    11. Client image can be configured to be used for Thin Client or KIOSK on a singlr click.
  30. BA BIO enhancements

    1. LED functionality at kiosk.(Only with latest CMS image) BA ,BIO devices are connected or not can be monitored with this lights.Green light means device is connected and enabled.Red light means it is disconnected and disabled.Yellow light means some error is there.
    2. Flow of KIOSK login has been changed.
      1. If KIOSK is BIO enabled, login will be through BIO only and password will not be required
      2. If KIOSK is NOT BIO ENABLED or Crew has been exempted from BIO through Biodata, password will be required for login
    3. After login crew will land on crew activity page.
    4. On selecting Sign ON /OFF
      1. Crew will be checked for sign ON/OFF eligibilty (no change)
      2. Valid crew will be checked for unread circular
      3. Circular cleared crew will be taken to BA test page (for BA ENABLED KIOSK) only
      4. Crew will be taken to Caution Order page (with or without BA as the case may be)
      5. rest of the Sign ON/OFF as per existing scheme
    BA FAIL
    In case of BA FAIL
    1. IP of that KIOSK is blocked
    2. KIOSK screen will become RED
    3. Crew is automatically sent to system Nonrun
    4. A red icon alert starts flashing on all supervisor consoles of that lobby
    5. IP can be unblocked from supervisor console onThin client
  31. Signoff page

    SIgn off page has been redesigned to avoid scrolling even with large no of fields being added to Sign OFF page.
  32. Crew log in page

    1. Alpha numeric key pad has been standardised even for login. Now key board is uniform for all data entry.
  33. Absent to leave

    Presently the whole absent period can be converted to a single leave type.
    New Function has been provided in
    Supervisor console - Freight - Non Run
    In Non Run select absent conversion ( new tab for multi absent has been provided)
    1. Now Period can be split into various leave types.
    2. Logic of combination of leave will not be verified by the system
    3. For multiple leave type conversion, only one crew at a time can be selected.
    4. In case more than one crew is selected than whole period of absence can be converted to single leave type for a particular crew
  34. Data base Security

    Security privileges for DBA access has been modified. Individual access given to individual DBA. Audit trail is being maintained since Sep 2015.

Internal works

  1. ICMS integration

    A new WSDL file has been provided by ICMS group. Then we replace old wsdl file with new one and again created a Web service client and now this integration has been completed with new WSDL.
  2. Remove NT from Sign OFF and Manual

    Facility provided to enter NT along with GT has been removed.

Reports

  1. Div console CUG Mobile bill loading

    CUG usage report for lobby
    1. Lobby wise (select period)
    2. Crew ID wise (select period presently missing) Fields

    S. No., Crew ID, TA no. Sign ON station. Sign ON time, Sign OFF station, Sign OFF time, call time , Mobile no called, Call duration, Call details)
    1. Facilty to see crew CUGno on mouse over on crew id
    2. Facility to sort on any fild by clicking field name tab
  2. Modifications in Energy meter reading for Regeneration and SFC etc. Removal of multiple loco detail from TA

    SFC = Diesel - Fuel consumed/(GT * KM)
    SFC = Electrical - (Energy consumed - Energy generated)/(GT * KM)
    Additional report - Section wise SFC, Loco Pilot wise SFC, Loco wise SFC with Flexi dates
    Filter for Loco Type Diesel and Electric
    1. Elec :
      1. Elec.Conv.
      2. Elec.3PH(GROUP_NAME_V IN ('WAG9','WAP5','WAP7')).
      3. Elec.ALL.
    2. Diesel
    3. ALL

    (Section Should be Lobby to Lobby)
    Columns:
    Section
    Driver
    GTKMN
    LocoType
    Energy Consumed
    Eng Regen.
    Net Consumed From & To
    Name & Id
    Start & End

    Section wise SFC:-
    SR.No.
    Section (Station-Station)
    Total No of Trip
    Total no of Trip with Energy Readings
    Average SFC/SEC

    Loco Pilot wise SFC:-
    SR.No.
    Crew ID
    Total No of Trip
    Total no of Trip with Energy Readings
    Average SFC/SEC

    Loco Type Wise SFC:-
    SR.No.
    Loco Type
    Total No of Trip
    Total no of Trip with Energy Readings
    Average SFC/SEC

    ***SEC/SFC not to be >25. If >25 then it should not be counted of average SFC/SEC.

    Note: New Coloumn "Reason for SFC NA" to be added, Which will provide remarks like "GT not filled", "From Stn Energy Rdgs not filled", "To Stn Energy Rdgs not filled", If GT, From & To rdgs all three record not filled then remark will be "Energy Rdgs & GT not filled" & "Meter Faulty".
    Also a new remark "SFC without Regeneration Rgds" will be introduced when entry for regenerated energy will be captured only for run with 3 PH Loco/Loco with Regeneration meter.
  3. Shunting Module with BA TOKEN NO.

  4. BA Value in Manual Entry

    Report to be built which maintain BA Token Nos (MANAGE - SIGN ON/ OFF)
  5. Accident Allowance

    Report for list of crew in a lobby who have availed accident allowance in the given period. Period to be selected by user. Report given in Management-working hrs (contineous)
  6. Management > Sign/Off report

    Management > Sign/Off report
    date & Time filter provided
    Now Sign on/off data can be generated for any period instead of fixed period from 1st to 30/31st day of the month.
  7. Crew Run Detail

    Duties with run > 10 hrs background to be shown in light pink colour (Continuous duty will be considered)
    Weekly OFF shown in ngreen colour (simoilar to PR)
    Two columns added (User ID, Sign OFF Type - Manual/KIOSK)
    IF sign ON ?OFF not filled and only Arr/Dep is filled. Sign ON / oFF not to be shown
  8. Edit history Bio-data

    In edit history following items are added
    PME
    All Training
  9. Provision to Calculate Average Detention

    Average detention & PDD report Daily average with column
    1. No of trains
    2. Avg detention (T dep - T arr)/ No of trains
    3. Avg PDD
    Monthly progressive avg with column
    1. No of trains
    2. Avg detention (T dep - T arr)/ No of trains
    3. Avg PDD
  10. Management > Turnaround report

    Turnaround Report : Drill down provided
  11. New Report - Data Filed On Behalf of Crew

    1. SignOn On Behalf of Crew By SuperVisor
    2. Signed Off On behalf of Crew By divisional Console - done
  12. New report SMS > LI SMS DND REPORT

    New report to show SMS DND status of all LI of particular Division
  13. Morning Postion (SMS)

    1. Traction wise
    2. Guards
  14. Manage - Leave Summary Report

    All Leaves to be summarised crew wise from Jan to Dec
    1. S.No.
    2. Crew Id
    3. Name
    4. CL
    5. LAP
    6. LHAP
    7. SL
    8. LWP
    9. ABSENT
    10. MNTL
    11. PNTL
    12. TOTAL
    Drill down of all counts including TOTAL
  15. Crew Bio data REPORTS

    The additional field to be displayed in crew bio data report- crew:
    1. Unit bill
    2. Aadhar No
    3. PAN no
    4. RUID no
    5. Employee No
    6. Email ID
  16. New report-Run Mileage breakup report

    New report in Mileage-Run Mileage Break up is required with following column
    GHATKM, MIN FRGHT, MIN DEPT, WORK KM
    LEARNROAD KM, YARDRELIEF KM ,
    SPARE KM, SHUNT KM , WAIT KM, COALPLT KM
    MEDVAN KM, BRKDW KM, BALAST KM, MATERL KM ,
    CRANESPL KM , LIGHT KM, DEAD KM, BANKER KM ,
    OSRA_KM,ACCIDENT KM, LELA KM, OFF KM ,
    SISTERLOBBY_KMN, SPL SHT, PORT SHT,CWORK KM,
    CBANKED KM,DBANKED KM, BDBANKED,CP KM,
    SH STNENDKM,OPTION C, SHUNT VAN,DISCONTI WORK KM,
    DISCONTI BANKER KM,DISCONTI DBANKED KM,
    DISCONTI MIN FRGHT,DISCONTI MIN DEPT
  17. Consolidated Leave Report & Consolidated Leave Summary Report

    Inclusion of NonRunRoster Crew in Consolidated Leave Report & Consolidated Leave Summary Report
  18. Turnaround Report

    Drill down all SignOn/Signoff Stations between Signon time at HQ and next Signoff time at HQ.
  19. Msc > Energy Consumption Reprt

    1. LOCO wise Energy consumption report
    2. Train No. and Train Load column Added
    3. Flexi for S/on & S/off station provided
  20. Show headings on each printout of reports

    At the time of print mileage summary report on A4 size paper then the initial detail like Name, Designation, Crew ID, Scale, Pay, PF No should be available on every page.
  21. Manage- Average Rest

    Average Rest report
    (Columns value modified)
    1. 12 hrs
    2. 16 hrs
    3. Others (All HQ excluding 12 and 16 hrs),
    4. Normal ( All HQ excluding PR availed) (1+2+3)
    5. 22
    6. 30
    7. >30 (32, 44, 52, 60),
    8. PR (22+30+>30) (5+6+7)
  22. New Report - Irregular Crew Report

    "New Report
    1. NOT ACK (AFTER CALLED) > 24 HRS
    2. NOT SIGN (AFTER BOOKED) > 24 HR
    3. OS REST > 72 HR
    4. ON TRAIN > 24 HR
    5. SYS NON RUN > 24 HR
    6. NON RUN > 7 DAYS
    7. CREW IN REST (AFTER AVAILABILITY) > 36 HR
    8. UNPLANNED (DUAL STATUS< NON TRACEABLE, BUG)
    9. APPROVAL FOR Sign ON / OFF pending > 8 hours
    Alert as pop up on login screen will be removed"
  23. Spare Duty Type

    When duty type spare data should not be shown in energy Consumption report.
  24. SMS Summary Report

    SMS Summary report that show total No. of pending / Received /Sent SMS of SMS and other groups