Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Railway Ticket Issuing System (Online)


Published on

The software solution implements a Railway Ticket Issuing System (RTIS) for the Sri Lanka Railways Department (SLRD). The solution allows to overcome the extreme human intervention to the current ticket issuance process. The proposed system will be an automated system so that SLRD will be able to manage their ticketing transaction efficiently.

Team Members:
Rashmika Nawaratne
Malinga Perera
Rumal Perera
Chaamini Mangaleswaran
Dilaj Perera

Published in: Technology, Travel

Railway Ticket Issuing System (Online)

  1. 1. solutions done right
  2. 2. Vision The software solution implements a Railway Ticket Issuing System (RTIS) for the Sri Lanka Railways Department (SLRD). The solution allows to overcome the extreme human intervention to the current ticket issuance process. The proposed system will be an automated system so that SLRD will be able to manage their ticketing transaction efficiently.Slide 2
  3. 3. Problem Domain • Purchasing railway tickets without traveling to the station • Delay of the prevailing manual ticket issuing procedure • Difficulty of monitoring the performance of railway counter staff • Invalid ticketsSlide 3
  4. 4. Automated Ticket Issuing System (ATIS) ATIS is a complete solution for issuing railway tickets. It provides resolutions for all the mentioned problems. The ATIS consists of a network of Automated Ticket Issuing Machine(ATIM)s and a web based solution.Slide 4
  5. 5. Automated Ticket Issuing System The ATIS is envisioned to Purchasing tickets The ATIS will have a major enable railway ticket issuance online via theto manage data data center Lanka Gate Via the SLRD website about the tickets. Major Country Portal and from the Via the LGCP SLRD website with Credit Card railway stations and the From ATIM s Hand held Barcodeare After or Mobil based payments. major data center Readers making payments, passengers connected through a high can determine the validity of Validating tickets will be provided an image of the the ticket. Once that is speed network a railway purchased ticket. It contains a Use of Bar Code Readers ticket is scanned, the SLRD. implemented by status of barcode and passengers are the ticket willtake update incopy supposed to be a printed thedisaster recovery center is A system. of that. Sharing data established in order to minimize system failures due The ATIM accepts Sri Lankan Through a High Speed to loss of data. currency notes and issues a bar Network code contained tickets.Slide 5
  6. 6. Main features • Credit card or mobile based payment • Enables purchasing railway tickets from any place • 24x7 available ticketing • Enables centralized control for monitoring and auditingSlide 6
  7. 7. Main features • High speed ticket issuance • High Reliability • User friendly GUI • Quick responseSlide 7
  8. 8. User Friendly GUI Starting window Select Destination Date of Departure Select Dep. Time Num of Passengers Select Preferred Train Select the Class Transaction Detail Payments Successful PaymentSlide 8
  9. 9. Project Stakeholders Internal Stakeholders • Railway Station Staff • Railway Conductors • Railway Department Administration • System Engineers • Railway PassengersSlide 9
  10. 10. Project Stakeholders External Stakeholders • ICTA • Sri Lanka Government • Mobile Service Providers • Banks • Internet Service ProvidersSlide 10
  11. 11. Agile Unified ProcessSlide 11
  12. 12. Agile Unified Process Change Requirements of StakeholdersSlide 12
  13. 13. System Architecture Disaster Recovery System SLRD Website Lanka Gate Main Data-store VPN Automatic Ticket Issuing MachineSlide 13
  14. 14. Slide 14
  15. 15. Agile Unified Process Major PhasesSlide 15
  16. 16. Major Phases and Milestones Phase 1 -Planning and Designing Cost and Estimate Acceptance 20/09/11 Finalization of Technical Architecture and Infrastructure Design 23/10/11 Completion of Online Ticket Issuing Web Service design in SLRD website via 18/11/11 LankaGate Country Portal Completion of Railway Ticket and ATIM designs 15/11/11 Phase 2 – Developing / Building Establishment of State-of-Art Data Centre in Western Province 1/11/11 Connecting SLDR Data Centre with Lankan Government Network 25/11/11 Connecting Major Railway Stations with State-of-Art Data Centre by a High Speed 5/01/12 Network Installation of ATIM and all necessary hardware in Major Railway Stations 28/01/12Slide 16
  17. 17. •Termination of contract after expected successful outcome Major Phases and Milestones Phase 3 – Validating Training all Railway Conductors regarding the operation of Handheld Barcode 5/03/12 Readers and staff regarding the overall new system Establishment of DRC (Disaster Recovery Centre ),manned 24/7,365 days 22/02/12 5/04/12 Completion of Successful Test runs Phase 4 – Deployment Launching the online ticket issuing services with proper public awareness 8/04/12 Phase 5 – Evaluating 15/6/12 Completion of Post Implementation Review Updating and Required correction 25/7/12 Termination of contract after expected successful outcome 30/7/12Slide 17
  18. 18. High level Timeline Major Phases No Name Start Finish Sep-Nov Dec-Feb Mar-May June - Aug 1 Planning and Designing 1/09/11 15/11/11 2 Developing / Building 18/10/11 29/01/12 3 Validating 5/01/12 5/04/12 4 Deployment 8/04/12 25/7/12 5 Evaluating 12/4/12 30/7/12Slide 18
  19. 19. High Level Timeline Major MilestonesSlide 19
  20. 20. Main Project Roles 1 Project Manager 2 Project Sponsor 3 Project Team Members 4 Project Administrator or Co-ordinator 5 Systems Developer System Administrator 6Slide 20
  21. 21. Project Manager Responsibilities Managing and leading the project team. Recruiting project staff and consultants. Managing co-ordination of the partners and working groups engaged in project work. Detailed project planning and control including: Templates Developing and maintaining a detailed project plan.Slide 21
  22. 22. Project Sponsor Responsibilities Championing the project and raising awareness at senior level. Approving strategies, implementation plan, project scope and milestones. Resolving strategic and policy issues. Driving and managing change through the organization. Templates project goals with other Prioritizing ongoing projects. Communicating with other key organizational representatives.Slide 22
  23. 23. Project Team Members Responsibilities Provide functional expertise in an administrative process Work with users to ensure the project meets business needs Documentation and analysis of current and future processes/systems Identification and mapping of information needs Templates Defining requirements for reporting and interfacing User trainingSlide 23
  24. 24. System Administrator Responsibilities Management and support of the various environments. Network operating systems management and support. Database management and support. Back-up and disaster recovery measures. Contributing to technical strategy, policy and procedure. Templates Development and operation of technical testing programmes. Production of technical documentation to agreed quality standards.Slide 24
  25. 25. Systems Developer Responsibilities Working with the Project Manager on definition of development requirements and priorities. Data Migration. Interfaces with other systems. Reporting configuration and deployment. Set up and maintenance of security rights and access permissions. Contributing to technical strategy, policy and procedure. Templates operation of technical testing Development and programmes. Production of technical documentation to agreed quality standards. Reporting on progress/issues to management and users.Slide 25
  26. 26. Documentation Planning and designing Developing/Building The Project Proposal Business Process Improvement The Project Charter Business Requirements Specification Business Case Business Requirements Register Benefits Plan Options Analysis Change Management Plan Implementation Plan Project Budget Project Business Continuity Plan Project PlanSlide 26
  27. 27. Documentation Validating / Deployment Evaluating PIR Questionnaire Test Plan Post-Implementation Review Training Strategy Project Closure ReportSlide 27
  28. 28. Communication We will be connected with you till the successful ending, because we know that success depends on it. Status Reports 1 Monthly Target: Students, day-to-day railway uses. All stakeholders Entire Project Team. Team Meetings Purpose: To gain stakeholders on progress Update input from plans (tasks, review detailed special of the project. and action items). groups and keep them abreast of the assignments, Project’s status. Frequency: Monthlyfor entire team. Weekly 2 Weekly Method: Distribute electronically and post Frequency: As required. Meething via web Method: Presentation/Discussion Periodic Demos and Target Presentations 3 As RequiredSlide 28
  29. 29. There Are Risks But we have smart solutions ✓ 1 Loss to project of key staff. Identifyon User Requirements Focus alternative resources Ensure training staff ✓ 2 Significant changes in user requirements Check that the user Make sure scheduledare Ensure for that senior outages. Revised business processes in case offrom are aware of the involvedatunexpected project. management startfully requirements are project. captureconstructing user spec. start of of before absence. Investigate whether investigated and agreed project, its relative importance, Best people withprocedures, Review training appropriate ✓ 3 Changes in priorities of of senior management. Changes in priorities senior management. extraits progress. and resources authority to knowledge and could either before specification enhance. ✓ 4 Poor capture of full User requirements. be involved or shadow any decide on requirements work dependent on a single ✓ 5 Inadequate training – too little too late member of staff. Ensure complete records of work are ✓ 6 Poor business processes available at any point. ✓ 7 Loss of power, internet at key eventsSlide 29
  30. 30. User Acceptance Guidelines Because we know that user rejection is the last thing you want. Learnability How we are going to test that Any staff member who intends to use the We will allow few stuff members(after 1 1 system should be able to use this after 1 2 hour training) and passengers(average day of training. passengers without any training) to use Any passenger should be able to use the the system for couple of hours and system only with the on system tour observe them. They should be able to conducted on demand by the system. learn and use it with low number of errors. System should use instinctive approach for all the user interfaces. Cancel button should be colored red. Back and forward buttons should be at lower left and right corners and colored blue. OK/Commit buttons should be Green.Slide 30
  31. 31. There are MORE!!! Just to ensure that customer is satisfied!!! System should be working with a maximum downtime of ✓ 10mins per week. ✓ System should respond within 5 seconds to every interaction. User manual should be available for the train department ✓ staff. System should show whether the machine is working or out ✓ of order from a green and a red indicating light. If a critical error was found, it should immediately notify the ✓ main station. ✓ Each ATIM and System Administrator PC will act as a client. Should have separate server controlled by the railway ✓ department.Slide 31
  32. 32. THANK YOU!