1. Introduction

Crew management system is aimed to provide information regarding the crew round the clock. It provides information regarding the presence of crew at home station or out station, maintains status-wise records, assigns crew to the trains, maintains information regarding the periodic and other rests, Road Learning, Traction Knowledge, Training Scheduling, PME, DAR actions etc.

Crew management system has being developed with the following objectives: -

i. Optimum utilization of crew by maintaining updated inventory of crew at home stations and at out stations.

ii. Scheduling and assigning the most suitable crew to a train after keeping in view the various factors like the type of traction required sections to be covered etc.

iii. To ensure timely availability of required crew, user can monitor/view various road learning and other training schedules, due dates of promotions/refresher courses for crew operating a certain locomotive of all traction and gauges.

iv. Scheduling periodic rests of the crew based on the total duty hours calculated from the beginning of the present fortnight.

v. Serve as a tool to call crew automatically.

vi. Calculate and monitor crew productivity by calculating total hours of duty worked, mileage earned etc.

vii. Monitor 10 Hrs duty and HOER rules by providing prior information of the crew and past trend analysis of the sections.

viii. To keep a check and control payment for over time and other allowances.

ix. Act as a tool to make the crew lobbies more or less paperless.

The CMS system is a role based, workflow oriented software which requires user to carry out the various steps of the workflow one at a time by the person responsible. The user cannot skip any of the steps. For e.g.:-

· Traffic supervisor creates a TA (traffic advise) based on the availability of crew.

· Crew cannot be booked or served call till TA is created.

· Once the call has been served the crew has to acknowledge the call.

· The call acknowledgement information is fed by the crew through SMS in automated mode and manually by the TNC in paper call mode.

· Unless the crew call has been acknowledged, the crew can not sign into the system.

· Once the crew has signed on, the supervisor approves it.

· The crew signs OFF at the other end if he has performed journey as per the call served particulars, else the system declines him to sign OFF.

· The crew’s sign OFF is required to be approved by supervisor.

· Twice in a day at 02:00 Hrs & 14:00 Hrs (Presently) all signed off crew’s approved movements are credited in their running allowance.

2. Brief Technical Particulars of CMS

CMS is as per Industry recommended standards using middleware, hardware and LAN/WAN network components. The business transactions provide current information, increase productivity and reduce paper work to a large extent at all lobby locations. The CMS system has been implemented at 385 locations (382 Lobbies, 2 ZRTI & 1 CRIS HQ) with thin clients capable of providing solution for intermittent network connectivity and touch screens. CMS uses FOIS and Railway network with adequate provisioning for security so that it is not vulnerable to hacking. It also has on-line application processing (distributed) & data inter-viewing capability at the Divisional and Zonal offices.

CMS can work both in online and offline modes and takes care of the last mile network connectivity and reliability issues. Under the proposed solution, the different applications required at various levels of organizational hierarchy will be accessed via web browser in online and using Web sphere Everyplace Deployment client interface in offline client. This CMS application will extend CMS applications to various stakeholders and will provide a single window interface to the Train Crew.

The CMS software has centralized n-tier J2EE architecture with Web Services/Struts framework which works in both online/offline modes. All the users can access the applications after user authentication and authorization. The solution is highly available, scalable, flexible, reliable and complaint to industry Open Standard specifications. The software solution has:-

· N-tier J2EE architecture.

· Seamless integration of enterprise systems with the existing business applications.

· Single sign-on feature.

· User authentication and authorization with biometric devices.

· Open-standards platform that supports web service.

· Option to extend existing applications for multiple devices.

· Full utilization of device features for enhanced management and advanced interactions.

· Providing out-of-the-box functionalities of device management, application management, synchronization, rules-based development and generic data synchronization with multiple devices.

· User friendly.

· Browser access via kiosks and thin clients, and offline access via thin clients.

· Comprehensive data validations during capturing.

· Industry compliant standard security features.

· Interface with SMS gateway for information dissemination and verification.

· Online flexible period report generation.

· Highly flexible and high available solution with 24x7 uptime.

· Highly customizable and scalable; reduces development time and costs

· Context sensitive help.

The software was developed in house using IBM’s middle ware and hardware. Consultants from HCL have assisted in the designing and performance optimisation of the software. Software development was assisted by SECM level 5 companies like MIND, IBM, and HCL. The design and implementation of the CMS is expected to lead to the evolution of a truly robust architecture based on the principle of inter-operability and open standards.

The software is fully maintainable by logically separating the MVC layers, horizontally and vertically scalable, interoperable by easy integration with any other IT system and supporting open source e.g. ECLIPSE, LINUX, etc.

3. CMS Software

3.1. Software functional requirements

The broad functionality of the software is given as below

3.1.1. List of CMS Modules/Features Developed

1) Freight

2) Coaching

3) Shunting

4) Sub-Urban

5) Crew Console

6) LI Console

7) Coal Pilot

8) SMS

9) CMS Help

10) Bilingual

11) Password Management

12) Universal Reports Console and Flexi Reporting

13) Centralized complaint logging and chasing.

14) Mailing System

3.2. User Name & Password Control Mechanism

User must have a username and password to access the CMS system. The user name for Division & Lobby Configuration Console is unique for every lobby and is issued by CRIS after a letter is received from the divisional authorities about who shall be the configuration manager for that division & lobby.

3.2.1. Hierarchy of user creation

Level 1 CRIS ADMIN 1.Creates Division & Lobby configuration console.

2. Divisional Report users.

3. Mobile Report User

4. CMS Admin User

5. ASM User

6. Divisional Internet User

7. Loco Supervisor/TNC Internet User.

8. CRIS SMS User

Level 2 Divisional Console Allotted by CRIS on an IP which is not a Lobby IP for

the purpose of various options which can be selected for all lobbies within division. Creates LI Bio data, Mobile Report User & Divisional Report User.

Level 3 Lobby Console Creates Supervisors for Traffic/Loco Lobby. Used for

the purpose of various options which can be Selected / Configured for own lobbies.

Level 4 Supervisor Traffic Creates TNC & Crew for Traffic Lobby.

Supervisor Loco Creates TNC & Crew for Loco Lobby.

Level 5 TNC Loco None, Crew booking operations only.

TNC Traffic None, Crew booking operations only.

Level 6 Crew Console Created by the Lobby console for identified KIOSK only.

Level 7 Report user No Separate user is to be created can be login with any

Application/Crew user name & password.

http://10.60.200.168/CMSREPORT is common for all reports. Ensure you have a FOIS connection and a PC

with browser. http://www.cms.indianrail.gov.in/CMSREPORT for reports on internet.

Level 8 Crew / Inspector Created by default while making BIO DATA.

Crew / Inspector may change it.
Loco Crew ID starts from 1000 and from 7000 for Guards,

Loco Inspector ID 0001 to 0699,

Traffic Inspector ID 0701 to 0999.

For a supervisor/TNC, the maximum number of users is 20. Beyond which the system shall prompt the user to delete the inactive users before creating new.

3.2.2 PASSWORD POLICY IN CMS APPLICATION:-

1. Content of password –

· Password cannot contain –

1. User Name(complete) -

2. Crew ID (any crew id of particular lobby)-

3. User ID (Self)-

4. Lobby Code( like GZB user id cannot have password which has string as GZB)-

· SMS will be sent to the user to inform about password updation.

· Password cannot be same as previous password.-

· Password must be Alphanumeric which contain at least one number and one character.-

· Password length must be minimum 6 digits.

· Password will not contain special character.-

2. Change in every 6 Months-

· System will keep the last password change date.

· When login perform system will check for days since last password change If 6 months is completed then password change screen will appear to the user forcefully.

3. Change on first Login –-

· While creation of new user on first login password change screen will appear to the user forcefully.

4. Reminders before 7 days of 6 months – -

Reminder will be alert on the screen just after login screen.

5. User can reset password with Forget Password option & SMS will be generated for same.

6. User can know last login date & time.

3.3. Configuration of New Lobby

Following is the list of essential data that needs to insert by all lobbies for making CMS hardware and software completely functional.

a. Bio-data of the crew and LI.

b. Crew booking routes.

c. Yard details.

d. Training locations.

e. Train pulling Locations

f. Rest types.

g. LI monitoring particulars.

h. Holiday.

i. Crew Gradation.

3.4. Roles and rights for the CMS users

The responsibilities of the various activities for the CMS are as below.

LOCO PILOTS/GUARDS

TNC
Freight	Coaching	Shunting*
Crew Booking	Crew Booking	Day Details*
Crew Ack	Crew Ack	Serve Call*
SMS crew Ack	Crew Movement Details	Crew Ack*
Crew Movement Details	Swap Crew	SMS Crew Ack*
Swap Crew	Coaching Serve Call	Shunting Movement Details*
Swap TA		Shunting Loco Competency*
Train Enquiry

SUPERVISOR
Freight	Coaching	Shunting*
Traffic Advise	Traffic Advise	Create / Edit Rosters*
Sign ON App	Sign ON App	Link Shunters*
Sign OFF App	Sign OFF App	Initialize*
Supervisor Sign On	Create / Edit Links	Day Details*
Crew Bio-Data	Link Crew	Sign ON App*
Non Run	Initialize Coaching Link	Sign OFF App*
Non Run Roster	Train Enquiry (coaching)	System Non Run*
System Non-Run		Shunting TA*
Transfers		Rest Modification Shunter*
PDD
PAD
Abnormality
Report Abnormality
Rest modification
Crew on LR
Transfer back from NCMS*
Train Enquiry
TA Integration

“*” marked are available only for LOCO.

Divisional configuration console
Circular	CUG Bill Upload	Loco Maintenance
Caution Order	LI Bio Data	Crew Grading/Counseling
LR Station From	User Details/Reset Password	Create Report User
Crew Booking Violation	ASM Module	Report Abnormality
Abnormality Feedback	Edit Crew Bio Data	Forced Sign Off
TA Creation	Send Group SMS	LR Configuration
Add Quiz Question	Reset User Training/Traction	Reset LI Password

Lobby configuration console
Route Display	Outstation Locations	LR Configuration	Add Quick Questions
Out Station Rest	Reset Crew Password	Separate ALP	Slate Creation
Train Pulling	Crew Booking Violation	Coal Pilot	Upload Slate(xls)
Shunting Yards	Coal Pilot Configuration	Edit Non Run Allowance	Set Type
Holidays		Sanctioned Cadre	Slate

Common links

Reports

Contact CRIS

Reply from CRIS

Create Users

Edit Password

Hardware Complaint

Crew Console

Sign ON/OFF

Abnormality

Abnormality Reporting

Circular

Personnel

LI Remarks

Quick

Change Password

3.5 Out of the Scope of CMS

1. So far the facility has been made up to 3 months detailed data storage and 6 month statistical data storage.

2. HRMS function, leave accountal, passes accounts.

3. Addition of new hardware beyond the ones approved by CAO/FOIS.

4. Offline data storage, in the event of network disconnections is not technically feasible for large application like FOIS, ICMS etc hence ruled out. Attempts were made on RTM Lobby in 2006 - 07 without a positive workable successful solution getting developed.

3.6 New Functionalities

The following new areas have been developed and demonstrated for technical possibility.

BIO-Metric

The working of BIO-Metrics i.e. sign ON / sign OFF of a crew using Biometric Thumb Impression reader is under testing at lobbies such as DLI, TKD, SSB & UMB in 2015 & will be extended to all the lobbies after the successful completion of testing. The user can Sign On/Sign Off into the system using BIOMETRIC reader.

Breathe Analyzer

The working of CMS integrated Breathe Analyzer while sign On/Sign Off is under testing at lobbies such as DLI, TKD, SSB & UMB in 2015 & will be extended to all the lobbies after the successful completion of testing.

Camera

The working of CMS integrated Breathe Camera while sign On/Sign Off is under testing at lobbies such as DLI, TKD, SSB & UMB in 2015 & will be extended to all the lobbies after the successful completion of testing.

Mobile web site

CMS has been provided for demo purpose on mobile phone web site at http://203.176.113.112/ or http://cms.indianrail.gov.in/, any user having a PDA capable of Internet browsing can come online and start to browse the crew information relevant to his lobby at any time.

CMS Clint Image Version 3.1

CMS CRIS has developed its own linux based thin client image version 3.1 with integration of latest Breath Analyzer, Biometric devices & Camera. Railways are required to use the latest client image.

CMS Application on Internet

CMS CRIS has developed new internet version of CMS application which can be accessed in absence of FOIS network. Sup/Tnc can login with the OTP received on mobile with Internet User IDs on open Internet,

4. Central Server Architecture and Lobby Architecture

Given below is the architectural diagram of CMS System. Users access the CMS applications via browser interface. As per the CMS application requirements, the application is deployed in centralized environments with online LAN/WAN (FOIS) connectivity. The CMS system has centralized architecture based on the deployment pattern. The CMS system supports the browser-based clients originated from respective places.

The above topology provides the horizontal and vertical scalability and high availability configuration with no single point of failure. In order to achieve high availability and business continuity, all the critical components of CMS System have redundancies that are achieved either on application level or on OS level clustering.

Central server architectural consists of a set of 13 servers which work in unison.

The details of servers are

1. Edge Server in Active / Active cluster mode hardware based with Network accelerator

2. Web sphere ND in cluster Mode at OS as well as Application mode on Linux system.

3. DB-2 database servers in Main / Standby Cluster mode on AIX OS.

4. Common External Storage of 1 Terabyte.

5. Tape Back up in “LTO” happing daily for backing up the database.

6. SMS gate way server

7. LDAP directory server for user Authentication and security main / standby.

8. BIO-Metric server

9. Time sync for Server and Client as per NPL standard time.

10. Real IP for information deployment on normal web site.

5. Setting up a CMS Lobby

The lobby for a CMS system can be set up in following step:-

1. Check List to Bring an NCMS Lobby ON Line. http://10.60.200.168/CMSREPORT/JSP/rpt/NCMS%20to%20CMS%20Lobby.html

2. Ensure that you have a trained CORE implementer trained by CRIS. Consult CAO/NR for more information.

3. Ensure that you have 3 KIOSK and 4 Thin client on a Network properly commissioned with a reliable Network and a Electrical power system with proper earthing having capability to come on standby power supply within 5 min of the electricity board power failures. Check http://10.60.200.168/CMSREPORT/JSP/rpt/Site%20Readiness.html

4. Confirm to CRIS that the lobby setup is complete as explained in http://10.60.200.168/CMSREPORT/JSP/rpt/Site%20readines%20Check%20list.html

5. Start using the CMS system with the support of CMS help, Your CORE implementer and http://10.60.200.168/CMSREPORT/JSP/CMS%20Help/Help_main.html

5.1 Divisional Configuration Console:

CMS software is flexible and very user friendly. To begin with, User (one per Division) needs to receive basic training at CRIS for this software. He will be provided with log in details by CRIS to gain access for CMS. CRIS imparts training to CORE implementers on Indian railways. Each railway shall have CORE implementers who in turn have to train the Lobby users for the use of the CMS software.

One Divisional Console user ID & password per division is provided by CMS CRIS for certain changes which remain same among all the lobbies of that division. The configurable items as shown in above figure are used for various activities required throughout the division.

5.2 Lobby Configuration Console:

User Id & Password one per lobby will be provided by CRIS to gain access for Lobby Configuration Console of CMS. Normally the parameters entered in the Lobby Configuration Console should be set once only after consultation with CRIS. Frequent changes should be avoided.

The CMS has to be setup by entering certain essential data these basic data or the master data or the referential data can be entered well in advance by the Lobbies even before the full fledged software and hardware is made functional at the lobbies. These data are based on these settings which are unique for each lobby the user shall be able to run the application and get mileage calculations.

5.3 Route Creation

To create/modify routes, a letter from branch officer/Headquarter with complete details of route such as Route KM, From/To/Via Stations, Min. Guaranteed section, Ghat Section & Automatic Signaling are required to be sent to CRIS Via Mail/FAX. The Routes can be created only by the admin user at CRIS if the route is present in RBS(Rates Branch System). If route is not in RBS the Lobby has to first add the route in RBS with the help of FOIS.

The route creation starts by entering the FROM and the TO station which is the Start and the End station of that route. Appropriate via needs to be added if the correct routes are not found. Once the correct route has been found, further modifications can be done and saved for future use with a default route number provided by the system.

As shown below there are 3 columns for marking “Ghat Type”, “Minimum Guaranteed Sections” and “Auto Signal Sections”.

Please ensure that all your routes are correct before beginning with crew booking. This is mandatory since routes are basic building blocks for all calculations in CMS database.

5.4 Configure Yards

The yards, where the shunting operation takes place, can be configured as below by lobby configuration console.

A yard may have sub yards. And each yard is a subset of itself.

5.5 Loco Inspector BIO DATA

Loco inspector BIO data is fed before feeding the pilot’s bio data as the system shall ask the name of LI while making the BIO data of a loco pilot. Every LI is given a unique ID by the CMS system. ID can be generated from the LI bio data link. Every LI can generate a list of pilots, whose training is due along with their mobile numbers. SMS’ is sent to pilots regarding the same on a weekly basis. There is an activate tab available in the LI BIO DATA screen. LI’s name will be visible in crew’s bio data only when it’s activated.

5.6 Crew Bio-Data

The crew BIO-DATA can be created / edited by supervisors (Loco / Guard) of that CMS lobby.

The supervisor enters crew details like PF No, Name, Gender, Father’s Name, LI Name, Birth Date, Appointment Date, Increment Due Date, Available Date, PME/REFT Done Date & Location, Call Serving Address, P&T No, Railway No, CUG & Personal Mobile No, Mobile Operator, Designation, Grade Pay, Basic Pay, Last Promotion/Demotion Date, Educational Qualification, Appointment Post, Cadre, Alcoholic, Officiating Date if required, The new crew ID is generated by the system when saved button is pressed. This information is stored in CMS database.

To edit or view these details, supervisor can click on ‘crew bio data’, then on search tab and select required crew id. After modifying editable fields click on save button to make the changes. Some fields are non-editable can be edited only through CMS admin user at CRIS.

The designations are co-related with Pay Band & Grade Pay. To view the pay band & grade pay enter designation and press ‘go’ button.

User can book a crew only if its crew id is active. Crew can be made inactive due to reasons like Super Annuation, Voluntary Retirement, Medical Retirement, Compulsory Retirement, Transfer, Promotion, Removal, Dismissal, Death, Permanent De-categorization, Resign, Others. Inactive crew ID does not appear in the CMS system to Supervisor/TNC. There is an option to make the crew temporarily inactive in cases like Temporary Transfer, Temporary Inactive, Drafted, Degraded; they can be made active in future.

In a lobby, there will be a unique crew name and father’s name pair. No two person’s in same lobby can have same father’s name.

5.6.1 Crew Bio-Data Others

In the ‘Others’ tab, crew’s particulars like Blood Group, Vision, Marital Status, Dependents, Family Planning, Identity Mark, Initial Medical Date, Unit Bill, Aadhaar No., RUID No., PAN No., Employee No., Employee Base ID, Bio Enable, Email Id,

Also Previous Promotion/Transfer History, Edit Last Promotion/Transfer Details, Family Member Details, Accident details, Awards and Punishments can be entered/modified/deleted.

5.6.2 Road Learning

In the “Road Learning” tab of biodata Crew LR is updated manually when a lobby is changed from NCMS to CMS Lobby, Also we can check LR of any crew in various routes between stations marked as LR point. The system also updates the dates automatically when a crew completes a journey on a particular route with CMS Booking.

Presently there are three types of LR which can be selected from Divisional Configuration Console for lobbies’ within the division. LR requirement will be configured by division for no. of trips required as per below Logic.

Period of absence from drive date LR Type I LR Type II LR Type III D N T D N T D N T 3 to 6 month à 1 0 1 1 1 2 1 0 1 6 month to 2 years à 2 0 2 2 1 3 2 0 2 2 years and above à 2 1 3 2 2 4 3 0 3

*D= Day Trip, N=Night Trip, T=Total Trips.

As soon as the user enters the Last Drive Date of a particular section of the route, Due Date for next drive is updated by system itself as per selected configuration type. Period of absence shall be calculated from last drive date. For LR total number of trips must be completed. Night run over and above the minimum requirement will be credited to day.

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. 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.

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.

Updation 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. .

For Type-I & Type-II division can select period to be considered for Night trip (Time From & Time TO) default time will be 1800 to 0600 & valid range 1700 to 0800). Also duration of running required for night is by default 1 min to max min as entered by user.

Type I – LR due date will be based on either of the run (day or night). And night run requirement will be there only if LR is overdue.

Type II – LR due date will be based on Day and night independently. Night run requirement will be there for all cases i.e LR is overdue or LR due. Exceptional Route where Night is not applicable even if lobby configures Night as Y, Same can be selected from Lobby Configuration console, More than one route can be selected & is applicable to the crew of that lobby, Night trip required will be treated as N & this will not be applicable to parallel routes.

Type III– LR due date will be based on only Day trip, Night trip will not be considered in any case.

5.6.3 Entry of Test and Training

When a supervisor enters Test and Training Details of a particular crew, the system automatically updates the next Due Date as per the type. For some specified training codes, system updates more than one Due Dates. Similarly for the crew training, in the crew bio-data, user can select ‘training’ tab and then enter date, station and details of test/training the crew has undergone. Due date for next test automatically populates thereafter.

5.6.4 Entry of Loco Competency

As soon as the supervisor enters last drive date for a particular loco type, system updates the next due date for that loco. The system also updates the dates automatically when a crew completes a journey on a particular Loco with CMS Booking.

5.6.5 Yard Learning

As soon as the supervisor enters last drive date for a particular Yard, system updates the next due date for that Yard. The system also updates the dates automatically when a crew completes a Shunting on a particular yard with CMS Booking.

5.6.6 Accepting Transferred Crew

Crew transferred from any other location can be accepted to our lobby with this form, User has to select the crew & the press the transfer tab. After that crew will start showing in Lobby Crew list at all the required places. Crew can also be rejected from this page if wrong crew is showing in list, that crew will again started reflecting in his original HQ,

5.7 Configure Rest Particulars

The rest types can be configured from the lobby configuration console. The user has to select the rest type from one of the below shown options.

a) These rests shall be given by the system itself as last per duty Hours information as available in the database. In case of outstation rest, the crew can opt for 6 Hrs rest.

b) The staff can, however, be called in breach of this limit (according to his rest) in cases of accidents or breakdowns. The supervisor has full power to call them. In such case the fetch crew all option is selected to display the under rest crew also getting highlighted in light grey.

5.8 Crew Gradation

A crew has to be graded by his monitoring LI mapped to his ID in CMS. The frequency of grading is different for different division. At present there are 6 types of crew gradation frequencies. Division configuration console user feeds the type of crew gradation & Counseling to be adopted within the division from one of the 6 types as mentioned below.

1. Each Inspector is nominated a set of crew which can be around 25 Pilots or 50 Shunters.

2. Each crew is graded A, B, or C.

3. At the time of bio data entry, Supervisor nominates the crew to Inspector.

4. Crew has to be monitored periodically as per the below mentioned periodicity.

5.9 Train Pulling Locations

Train pulling times are different for different lobbies. The lobby configuration console should configure the train pulling time to suite a Lobby requirement. A typical example of the data entry screen for Train pulling is shown below:-

The minimum pulling time is 15 min and the max pulling time is upto 1 Hr.

5.10 Coal Pilots

A new Module will be developed which will be visible to only those lobbies which are pre configured for coal pilot working. the master data for the coal pilots can be configured by the Configuration manager. It is recommended that user must come to CRIS to configure the coal pilots. While configuring the coal pilots the user must configure

· Base Lobby and the coal pilots siding with the standard IRCA codes.

· Bonus time between the base and the coal pilot sidings

· The bonus km’s between which the run has to be completed.

· SET to be defined instead of individual run

· SET can consist of one or more than one run

· Bonus km and bonus hrs will be applicable to SET

· TA will be made for coal pilot with SET to be indicated in route

· Sign ON and Sign OFF will be done at KIOSK with option to change the SET.

· After sign OFF flow will be directed to new manual entry (different from existing manual entry)

· In case crew does not sign OFF at kiosk same can also be handled through new manual entry. In this case sign OFF time will required to be filled.

· All runs will now be pre populated with set details with following changes permitted while saving

Opt for new set
Loco no/Type, Train No, for individual run
Arr. Dep. time for individual run

Mileage will be

sum of km for all runs if Sign ON to Sign OFF > Bonus time
sum of km for all run + Bonus km if sign ON to Sign OFF < Bonus time

Set consist of Run from 'base to siding', 'siding to siding', and 'siding to baseâ€™
First and last run are not part of SET

Manual for Coal pilot

When TA is of coal pilot Sign OFF on KOISK is directed automativaly to manual data entry
Separate button to be provided to add set (different from run add button)
Clicking on set add button will display all sets pertaining to base station filled as in current run
First run will be displayed as non editable and set detail run as editable column.
In case last station of set happens to be same as lobby then save is permitted else additional run has to be filled.
RRA, Accident , OSRA, Shunt count will be filled only once for a set

When FROM and TO are same and coal pilot set is selected, First run is part of set then these value will be part of first run even in set
Any run followed by set run (unless preceding run is also set run) will not be permitted for above values.

5.11 Suburban Module

Designed as per information given by lobby supervisor’s of WR and CR to CMS team visited Mumbai for two days. Deals with the all categories of crew (Motorman and guard) working on suburban trains.
Crew work on well defined set consists of one or more train working as well as waiting, halting or shunting duty.Proper rotation of crew on different sets. Auto generation of 24 Hrs. Set plan for next day working. Demand Register for future date duty change request given by crew. Crew movement Form for back data entry of sign on to signoff.
SRS document v 1.0 for suburban module

SUBURBAN_CrewBiodata
SUBURBAN_Set Details Prepration
SUBURBAN_crew booking
SUBURBAN_Demand_Register
SUBURBAN_Manual Crew Movment
SUBURBAN_Non Run
SUBURBAN_RunningAllowance
SUBURBAN_SignOn
SUBURBAN_SignOff
SUBURBAN-Circulars
SUBURBAN_Abnormality_Reporting
SUBURBAN_Loco Inspector
SUBURBAN-CrewSelfService

5.12 Sister Lobbies

Sister lobby concept is applicable where the user wants to serve call to Lobby “A” crew but they need to sign ON at Station “B”. Similarly on returning, the Crew Signs OFF at station “B” but he has to be made available at station A for further crew booking. For example lobby like Ghorpuri GPR can make a Train pulling location GPR – Mainline and PUNE – Mainline. When a GPR lobby makes a TA for GPR-mainline the crew can sign on at GPR with a call served from GPR while if the train pulling location is PUNE-Mainline then the crew can sign ON at PUNE for a call served from GPR lobby. On return back from outstation if GPR crew signs off at PUNE he shall be shown available at PUNE but the GPR supervisor has powers to make his HQ shifted from PUNE to GPR if it is felt that the next call serve for such crew shall be from GPR.

All such lobbies like GPR-PUNE, BSLX-BSL, BRCY-BRC are termed as sister lobbies by the CMS software.

The user has to come to CRIS with the information on the sister lobbies and get the changes introduced in the CMS database before he can actually use the any Lobby as sister lobby.

5.13 NCMS

NCMS implies non CMS lobby. Such Lobbies can go on line with the help of divisions own PC’s and start data entry for Routes, Shunter Yards, BIO data of crew, Train pulling times etc.
The crew of an NCMS lobby can sign OFF into the CMS system located at a regular CMS lobby directly if it has a valid crew ID. Such crew can become available as per standard norms and can be booked back to there respective Lobby HQ. Care should be taken that the PME, REFT and the traction particulars of the crew are complete and updated else he shall not be booked back from a CMS location.

6. Support via Email

6.1 Compose email:-

1. CMS software has capability to send a mail to one or many valid users within CMS network across the nation.

2. The module has capabilities to create users own custom Mailing List and interact with other users for custom mailings.

3. Count of number of “unread Mail” is displayed in the brackets which shall be refreshed, once the mail has been read and the user logs out.

4. The mail first comes to the Inbox.

5. The user can reply the mail by clicking on the Reply button.

6. He can forward the mail within the SLAM network.

7. He has the freedom to Send to and give a copy to the authority of his choice.

8. The mails once replied remain in the sent box.

9. User can send the mails to trash by clicking on the “-“sign.

10. Once in trash the mail remains there for some time and is erased by CRIS administrator at periodic set intervals.

11. You can send Mail to more than one users by differentiating the users IDs with colon “ :”

6.2 Address Book:-

1. There is an internal address book of all the user authorities who are authorized to us the email system

2. The software has capabilities to create users own custom list by clicking on the Add to My List.

3. Add List to mail can be use to add the sender to whom the mail is required to be sent.

6.3 SMS

CMS application provides a strong SMS support functionality to its users. This functionality is available at number 08860622020. The various functions are:-

1. Sending a group of CMS user SMS. The groups are

o Abnormality Group each type wise Track, Optg, S&T, CTLC, CPCR.

o Morning Position group - Loco, Traffic.

o Alert Group for Crew strength falling below a certain level.

o Others group.

2. Call server to crew and its acknowledgement.

3. Morning Crew for a lobby crew at various position in SMS.

4. Alert for crew value falling below a certain value.

5. Alert to a LI for his monitoring becoming due.

6. Birthday alerts to all the CMS staff whose number is configured into CMS system on their B’day.

7. Abnormality Alerts if the crew has reported an abnormality into CMS system to th group of mobile numbers configured into the system.

8. Abnormality closing alert by SMS to the CREW who lodged in the abnormality with remarks of the supervisor as well as who has closed the abnormality particulars.

9. SMS alert to crew that his rest has been modified to long rest by the supervisor.

10. Hardware instantaneous SMS to the user who lodges in a hardware complaint on his mobile phone.

11. Nearest hardware Service support center SMS alert regarding the SMS lodged in by CMS customer.

The mobile numbers are to be configured into the CMS system in the configuration console. Please ensure that the mobile numbers have been properly configured for getting proper results from the system.

6 Frequently Asked Questions

7.1. What is NCMS lobby and CMS lobby?

NCMS implies non CMS lobby. Such Lobbies can go on line with the help of divisions own PC’s and start data entry for Routes, Shunters Yards, BIO data of crew, Train pulling times etc. CMS lobby is where entire software and hardware of CRIS has been provided and the data entry required for the CMS working has been completed. Such lobbies shall be complete in itself for CMS software to work.

Once a NCMS lobby has been setup a NCMS crew can sign OFF directly at any CMS lobby and shall be made available at that CMS lobby. He can move back to a CMS lobby or a NCMS lobby on a valid TA.

7.2 How do I bring a NCMS lobby system on line?

You need a proper FOIS connection with a PC preferably with Mozilla fire fox installed on it, as default browser, at the Lobby desiring to upgrade as CMS lobby.

1. Obtain an IP address from CMS Control Center (C3) contact number 7217709646, 011-26886120,

011-24674160, Railway Number 54824.

2. Configure the following setting of the network in your TCP/IP settings

2.1. IP address as already circulated.

2.2. Subnet Mask 255.255.255.0

2.3. Default Gateway Shall be given by the Telecom department of Railways.

2.4. In case of problems while configuring your PC with the IP address, contact C3 for

voice support.

3. Ping the network by going to Start -> Run enters and press OK.

Short normal pinging	ping 10.60.200.168	If time< 75ms network is good
Continuous extensive regular pinging	ping 10.60.200.168 -t	If time< 75ms network is good
Short extensive pinging	ping 10.60.200.168 –l 1000	If time<170ms network is good
Continuous extensive regular pinging	ping 10.60.200.168 – l 1000 -t	If time<170ms network is good

4. Confirm the ping results to C3.

5. Enter address http:// 10.60.200.168/ and press enter. If the IBM, Webspher page appears

you have been connected to CRIS / CMS server.

6. Enter address http:// 10.60.200.168/CMSHELP to go to the CMS introduction and support

website. Read the instructions on the CMSHELP website for further action.

7. Obtain a letter from DRM of your division for nomination of one Lobby configuration

console user for CMS or the super user and come to CRIS for 2 day support training for

the super user with prior appointment. These super users shall be one per lobby and

shall come prepared for making routes and yards of their sections.

8. Configure the fire fox explorer as per the voice assistance of C3 for best result of CMS

software.

9. Open the fire fox from start -> program ->

10. Enter the following in the address bar http:// 10.60.200.168/CMS

11. Crew management system User Login screen shall open.

12. Enter User name and password as given by CRIS.

13. This will take you to CMS Lobby Configuration Console.

14. Consult you assigned CORE Implementer for further guidance within the CMS software.

15.

7.3 Do I need Antivirus software?

In case you are accessing the application using CRIS hardware in CMS mode, no Antivirus shall be needed. But in case Windows PC’s are being used by the users, then proper Antivirus software updated up to a current date shall be required. Also Acrobat reader shall be required for viewing the reports.

7.4 Mozilla fire fox settings required for use of CMS application:

The following shall be required.

· Uncheck Popup windows blocker.

· Enable Java

· Enable Java script.

· Connection setting Automatic without Proxy

7.5 Abbreviations Used in CMS

CMS uses abbreviations for various type of training. These abbreviations are as below:-

S.N	Non Run Code	Description	S.N	Non Run Code	Description
1	SIM3P	SIMULATOR TRG 3PH DR	50	SFCM	SAFETY CAMP
2	3PH	THREE PHASE TRAINING	51	GHC	GHAT SECTION COMMPETENCY
3	AIDT	ASST. INITIAL DSL TRANSPORT	52	CT	COMPETENCY TRIALS
4	AIET	ASST. INITIAL ELECT TRANSPORT	53	DARE	DAR ENQUIRY
5	AIFT	ASST. I DSL A/C TRANSPORT	54	DEQY	DEPARTMENTAL ENQUIRY
6	CDE	CONVERSION DSL TO ELECTRIC	55	DPEX	DEPARTMENTAL EXAMINATION
7	CED	CONVERSION ELECTRIC TO DSL	56	ENQR	ENQUIRY
8	DMU	DIESEL MULTIPLE UNIT	57	MTNG	MEETING
9	DRGPD	DRGP DIESEL	58	OPME	OTHER MEDICAL
10	DRGPE	DRGP ELECRTICAL	59	PDTR	PRIVATE DOCTOR TREATMENT
11	DRGPT	DRGP TRANSPORTATION	60	SPRT	SPORTS
12	EMU	ELECTRIC MULTIPLE UNIT	61	SHDT	SHED DUTY
13	MEMU	MAINLINE ELECTRIC MULTIPLE UNI	62	CPCR	CHIEF POWER CONTROLLER
14	PD	PROMOTION DSL	63	CTCC	CHIEF TRACTION CREW CONTROLLER
15	PDET	PROMOTION DSL ELEC TRANSPORT	64	CTLC	CHIEF TRACTION LOCO CONTROLLER
16	PDT	PROMOTION DSL TRANSPORT	65	PCR	POWER CONTROLLER
17	PE	PROMOTION ELECTRICAL	66	TCC	TRACTION CREW CONTROLLER
18	PET	PROMOTION ELEC TRANSPORT	67	TLC	TRACTION LOCO CONTROLLER
19	RDE	REFRESHER DSL/ELECTRICAL	68	OTHR	OTHER
20	RDET	REF DSL/ELECT/TRANSPORT	69	ABSEN	ABSENT
21	RDT	REFRESHER DSL/TRANSPORT	70	ARME	WAITING DUTY FOR ARME
22	REFD	REFRESHER DIESEL	71	LWP	LEAVE WITHOUT PAY
23	REFE	REFRESHER ELECTRICAL	72	MISC	MISCELLANEOUS
24	RET	REFRESHER ELECRICAL/TRANSPORT	73	NHW	AVAIL NATIONAL HOLIDAY
25	SIMD	SIMULATOR TRG DSL DR	74	NTB	NOT TO BOOK
26	SIME	SIMULATOR TRG ELEC DR	75	SNRUN	SYSTEM NONRUN
27	WDS4	WDS4 TRAINING	76	SUSP	SUSPENSION
28	AIT	ASST. INITIAL TRANSPORT	77	SYSRF	SYSTEM REFUSE
29	AID	ASST. INITIAL DSL	78	TJIN	JOINING TIME
30	AIE	ASST. INITIAL ELEC	79	TA	TERRITORIAL ARMY
31	HST	HIGH SPEED TRAINING	80	TAE	TERRITORIAL ARMY EMBODIMENT
32	DCLT	DC LOCO TRAINING	81	STDTO	STATIONARY DUTY WITHOUT NDA
33	RDCLT	REFRESHER DC LOCO TRAINING	82	STDTW	STATIONARY DUTY WITH NDA
34	ACDC	AC/DC TRAINING	83	SPENQ	SPARE FOR ENQUIRY
35	RACDC	REFRESHER AC/DC TRAINING	84	SPTRN	SPARE FOR TRAINING
36	REFMG	REFRESHER METER GUAGE	85	CCL	COMPENSATORY CASUAL LEAVE
37	REFNG	REFRESHER NARROW GUAGE	86	CL	CASUAL LEAVE
38	WDG4	WDG4 TRAINING	87	IOD	INJURED ON DUTY
39	WDP4	WDP4 TRAINING	88	LAP	LEAVE AVG PAY
40	FA	FIRST AID	89	LHAP	LEAVE HALF PAY
41	AIRB	AIR BRAKE	90	MNTL	MATERNITY LEAVE
42	UTRG	UNION TRAINING	91	PNTL	PATERNITY LEAVE
43	ASIG	AUTOMATIC SIGNALLING	92	PSICK	PME SICK
44	PME	PERIODICAL MEDICAL EXAM	93	SCL	SPECIAL CAUSAL LEAVE
45	PRSEL	PRE SELECTION TRAINING	94	SL	SICK LEAVE
46	PSY	PSYCHOLOGICAL TEST	95	SPPME	SPARE FOR PME
47	PT	PROMOTION TRANSPORTATION	96	CHCL	CHILD CARE LEAVE
48	REFSC	REFESHER TPT SAFETY CAMP	97	OTHR1	OTHER1
49	REFT	REFRESHER TRANSPORT	98	OTHR2	OTHER2