120 likes | 709 Views
CREW MANAGEMENT SYSTEM. CRIS & FOIS. OBJECTIVES & SCOPE. Maintain inventory of all Crews including position of home crew at out stations Scheduling and assignment of Crew to trains Monitoring road learning, training,RC,etc Scheduling periodic rest Modernization of Calls process
E N D
CREW MANAGEMENT SYSTEM CRIS & FOIS
OBJECTIVES & SCOPE • Maintain inventory of all Crews including position of home crew at out stations • Scheduling and assignment of Crew to trains • Monitoring road learning, training,RC,etc • Scheduling periodic rest • Modernization of Calls process • Crew productivity(hrs worked, km earned) • HOER • paperless lobby • To link all activity points • A tool for saving OT, Km all. • cover- lobby, CCC, dvn office , control office ,Zonal Rly. CONTD.--
OBJECTIVE contd… • Cover functions of all actors at above places. • Booking of Crew on links. • Booking of Crew for shunting duty • Driver monitoring by LI • Grading of Crew by LI • Employees self service • Essential information available on rail net • Allowance calculation • Circulars availability • Reports
FEATURES • Central server • Biometric and touch screen based Sign on/off • Paperless lobby • SMS for call on • Browser based application • Using FOIS network/COA • Server level messaging service with FOIS/COA/COIS -Updating train arrival/departure times at Crew booking - updating Crew particulars in FOIS contd--
FEATURES contd…. • Working offline for Short duration in case of network disconnection, working and updating with central server later on connection. • LINUX OS, Oracle or DB2 for data base • Expandable up to 2500/3500 nodes • Driver knowledge evaluation quiz. • Real time data entry • IVRS & BA ? Not confirmed. • Calculation of benefit have not yet been done.
COST ESTIMATE • Detailed estimate of Rs 38.16 crores sanction by Railway Board. This includes 2.75 crores for establishment etc. of FOIS organization. • 302 locations of integrated lobbies to be covered.
Implementation strategy • System development for freight, coaching, shunting & EMU services by the end of May 06. • June 2006 central server deployment & implementation on one division with biometrics,SMS & railnet connectivity. • July 06 functional testing of the application • March 2007 at all the locations.
ISSUES • Integration of lobbies • Lack of infrastructure & manpower • Wide variation in practices posing probs in customisation of appl • Incorporation of features already available on cms running on rlys
PRESENTAION ON CREW MANAGEMNT BEING DEVELOPED BY CRIS. Status on date: Manual /auto Problem areas of manual and attempt of tackling these problem areas by exiting. What we are going to achieve with new system? Why cant we achieve that through the existing auto system by up gradation/integration thereof. Objective and scope and features (whether this includes all such features of existing ones. If not what is plan. Issues in development of application and implementation in the field target time.
Existing vs New system applications Features, scope , objectives simplification of booking process Modernization of call process Cost Variation in practices (customization vs universalization). Equipment existing Integration of existing with new Status on date vs future Upgradation vs new? Architecture Capacity Browser based vs client server based Oracle replication
Development of applications- Integration with FOIS/COIS/COA Variation in practices Lab testing Field testing Train and changes during timelines Frequent quarries/replies Audit /reliability Data entry FOIS time
Implementation Integration of lobbies. Finalisation of locations Ownership(I&C) of lobby Training Infrastructure -RH/training facility/sparing of staff/gap between training and implementation/OCC/backup for 6 hrs vs cutoff Site Implementation team FOIS time 30 max month with 24 min. need 45 officers