288 40521 Tender Documents

Final Report Roadmap for improving City Bus Systems in India
About Shakti Sustainable Energy Foundation:

Shakti Sustainable Energy Foundation works to strengthen the energy security of India by aiding the
design and implementation of policies that support energy efficiency, renewable energy and sustainable
mobility.
July 2016
Disclaimer: The views/analysis expressed in this report/document do not necessarily reflect the views
of Shakti Sustainable Energy Foundation. The Foundation also does not guarantee the accuracy of any
data included in this publication nor does it accept any responsibility for the consequences of its use.
*For Private circulation only
Page | i
Acknowledgement
Delhi Integrated Multi-Modal Transit Systems - DIMTS expresses its sincere thanks to the
Shakti Sustainable Energy Foundation (SSEF), for awarding the consultancy assignment for
the preparation of “Roadmap for improving City Bus Systems in India”.
The study team expresses its heartfelt thanks to Mr. Ravi Gadepalli, Program Manager
(Transport), SSEF; Ms. Shilpa Kharwal, Program Associate (Transport), SSEF and officials of
the SSEF for their support from time to time in carrying out the assignment.
Sincere thanks to Mr. Ashish Mishra – CIRT, Pune and Mr. A.K.Goyal – Chief General
Manager, Delhi Transport Corporation, Delhi; for their guidance and critical review during expert
review committee meetings in firming up the roadmap recommendations.
We acknowledge for the support and contributions extended by the Bangalore Metropolitan
Transport Corporation (BMTC), Karnataka State Road Transport Corporation (KSRTC),
Bhubaneshwar Puri Transport Services Ltd. (BPTSL), Dream Team Sahara, Calcutta State
Transport Corporation (CSTC), Calcutta Tramways Company (CTC), West Bengal Surface
Transport Corporation (WBSTC), Himachal Road Transport Corporation (HRTC), Raipur Nagar
Nigam Transport Limited, Amdavad Municipal Transport Service (AMTS), Ahmedabad Janmarg
Limited (AJL), Andhra Pradesh State Road Transport Corporation (APSRTC), Kanpur City
Transport Service Limited (KCTSL), Delhi Transport Corporation (DIMTS), AICTSL, Prasanna
Purple and Maharashtra State Road Transport Corporation (MSRTC) throughout this
endeavour.
Warm regards from the study team.
Page | ii
Table of Contents
ACKNOWLEDGEMENT ............................................................................................................................... II
TABLE OF CONTENTS .............................................................................................................................. III
LIST OF FIGURES .......................................................................................................................................V
LIST OF TABLES .........................................................................................................................................V
LIST OF ABBREVIATIONS .........................................................................................................................VI
EXECUTIVE SUMMARY .............................................................................................................................. 9
1. PROJECT BACKGROUND ........................................................................................................ 21
1.1 BACKGROUND ................................................................................................................ 21
1.2 NEED FOR THE PROJECT................................................................................................. 21
1.3 STUDY APPROACH & METHODOLOGY .............................................................................. 22
2. CITY SELECTION AND DATA COLLECTION PROCESS........................................................ 23
2.1 INTRODUCTION............................................................................................................... 23
2.2 CITY SELECTION PROCESS ............................................................................................. 23
2.3 DATA COLLECTION APPROACH ....................................................................................... 24
2.4 FORMATION OF EXPERT REVIEW COMMITTEE (ERC) ....................................................... 26
2.5 CONCLUSION ................................................................................................................. 26
3. CITY REPORT CARD ................................................................................................................ 27
3.1 INTRODUCTION............................................................................................................... 27
3.2 PRACTICES REVIEWED ................................................................................................... 27
3.3 CITY-WISE BUS OPERATIONAL CHARACTERISTICS ........................................................... 28
3.4 CITY-WISE REPORT CARDS ............................................................................................ 32
3.5 CONCLUSION ................................................................................................................. 55
4. INTERNATIONAL BEST PRACTICES ...................................................................................... 56
4.1 INTRODUCTION............................................................................................................... 56
4.2 EXISTING INTERNATIONAL BEST PRACTICES .................................................................... 56
4.3 SUMMARY OF KEY BEST PRACTICES AND LEARNINGS ...................................................... 59
4.4 CONCLUSION ................................................................................................................. 60
5. GAP ANALYSIS ......................................................................................................................... 61
5.1 INTRODUCTION............................................................................................................... 61
5.2 IDENTIFIED GAPS IN STRATEGIC TRANSPORT PLANNING .................................................. 61
5.3 TECHNOLOGY INTERVENTIONS IN BUS OPERATIONS AND GAP IDENTIFICATION .................. 62
5.4 EXISTING OPERATIONAL PROCESSES AND IDENTIFIED GAPS ............................................. 73
5.5 INSTITUTIONAL AND CONTRACTING STRUCTURE AND IDENTIFIED GAPS ............................. 80
5.6 FUNDING OPTIONS AND IDENTIFIED GAPS ....................................................................... 81
6. POLICY ROADMAP RECOMMENDATIONS ............................................................................ 82
6.1 INTRODUCTION............................................................................................................... 82
6.2 PREPARATORY W ORK TO BE DONE BY STUS/SPVS......................................................... 82
6.3 LIST OF MAJOR INTERVENTIONS ...................................................................................... 82
6.4 POLICY ROADMAP FOR STRATEGIC PT PLANNING............................................................ 84
6.5 ROADMAP FOR TECHNOLOGY INTERVENTIONS ................................................................. 87
Page | iii
6.6 ROADMAP FOR IMPROVING THE OPERATIONAL PROCESS ................................................. 98

6.7 ROADMAP FOR IMPROVING BUS TRANSPORT INFRASTRUCTURE ..................................... 109
6.8 ROADMAP FOR INSTITUTIONAL AND CONTRACTING FRAMEWORK .................................... 109
6.9 POLICY ROADMAP FOR FUNDING AND IMPLEMENTATION OF CITY BUS SERVICE ............... 112
7. PROPOSED NEW TOOLS FOR IMPROVING BUS SYSTEM EFFICIENCY ......................... 114
7.1 INTRODUCTION............................................................................................................. 114
7.2 PROJECT SHEET (PS) .................................................................................................. 114
8. CONCLUSIONS AND WAY FORWARD ................................................................................. 129
8.1 W AY FORWARD ........................................................................................................... 131
Page | iv
List of Figures
FIGURE 1-1: STUDY APPROACH & METHODOLOGY CHART .............................................................................. 22
FIGURE 2-1: PARAMETERS FOR CITY SELECTION............................................................................................ 23
FIGURE 2-2: SELECTED CITIES FOR COMPREHENSIVE STUDY ......................................................................... 24
FIGURE 3-1: PRACTICES REVIEWED WITHIN CITY BUS OPERATOR ................................................................... 27
FIGURE 3-2: CITY-WISE ROUTE DETAILS ......................................................................................................... 29
FIGURE 3-3: CITY-WISE VEHICLE UTILISATION ................................................................................................ 29
FIGURE 3-4: CITY-WISE EPK, CPK AND OPERATING RATIO ............................................................................ 30
FIGURE 6-1: LIST OF MAJOR INTERVENTIONS .................................................................................................. 84
FIGURE 7-1: VEHICLE AND CREW OPTIMIZATION TOOL .................................................................................. 119
FIGURE 7-2: TIME TABLE PREPARATION TOOL.............................................................................................. 120
FIGURE 7-3: ROUTE PLANNING TOOL............................................................................................................ 122
FIGURE 7-4: BUS MANAGEMENT SYSTEM WEB PAGE...................................................................................... 123
FIGURE 7-5: EXAMPLE OF GIS BASED ASSETS MANAGEMENT SYSTEM- LOCATION ASSETS .............................. 124
FIGURE 7-6: BUS MANAGEMENT SYSTEM WEB PAGE...................................................................................... 126
FIGURE 7-7: BUS FLEET ROUTE PLANNING SOFTWARE .................................................................................. 126
FIGURE 7-8: NEW JERSEY TRANSIT BUS ROUTE PLANNING ........................................................................... 127
FIGURE 7-9: EXAMPLE OF ROUTE COLOUR CODING SYSTEM – MARYLAND, U.S.A. ......................................... 128
FIGURE 7-10: EXAMPLE OF ROUTE NUMBERING - DOWNTOWN SALT LAKE MAP .............................................. 128
List of Tables
TABLE 0-1: SUMMARY OF OPERATIONAL AND FINANCIAL PERFORMANCE OF STUS ........................................... 10
TABLE 0-2: ACTION PLAN AND STAKEHOLDER RESPONSIBILITIES .................................................................... 20
TABLE 2-1: DEPARTMENTS AND OFFICIALS OF STUS AND SPVS CONTACTED................................................... 25
TABLE 3-1: CITY STUS AND PRIVATE OPERATORS ......................................................................................... 30
TABLE 4-1: CITY-WISE KEY AREA AND LEARNING ............................................................................................. 59
TABLE 4-2: CITY-WISE KEY AREA AND LEARNING ............................................................................................. 59
TABLE 5-1: GAP ASSESSMENT OF STRATEGIC TRANSPORT PLANNING ............................................................. 61
TABLE 5-2: GAP ASSESSMENT IN TECHNOLOGY DEPLOYMENT IN BUS OPERATIONS IN INDIA .............................. 62
TABLE 5-3: GAP ASSESSMENT IN OPERATIONAL PROCESSES OF CITY BUS SERVICES ........................................ 73
TABLE 5-4: GAP ASSESSMENT OF INSTITUTIONAL AND CONTRACTING STRUCTURE .......................................... 80
TABLE 5-5: GAP ASSESSMENT OF FUNDING OPTIONS ..................................................................................... 81
TABLE 6-1: STATUS OF STRATEGIC PT PLANNING STUDIES IN INDIA ................................................................ 84
TABLE 6-2: CITY CATEGORIES ....................................................................................................................... 85
TABLE 6-3: POLICY ROADMAP RECOMMENDATIONS FOR STRATEGIC TRANSPORT PLANNING ............................ 86
TABLE 6-4: POLICY ROADMAP FOR TECHNOLOGY INTERVENTIONS ................................................................... 89
TABLE 6-5: CURRENT STATUS IN DIFFERENT ORGANIZATIONS ........................................................................ 98
TABLE 6-6: POLICY ROADMAP FOR OPERATIONAL PROCESS .......................................................................... 100
TABLE 6-7: STATUS OF CONTRACTING STRUCTURE IN CITY BUS OPERATIONS IN INDIA .................................. 110
TABLE 6-8: POLICY ROADMAP FOR INSTITUTIONAL AND CONTRACTING REFORMS IN CITY BUS OPERATIONS ..... 111
TABLE 6-9: POLICY ROADMAP FOR FUNDING ................................................................................................ 112
TABLE 8-1: ACTION PLAN AND STAKEHOLDER RESPONSIBILITIES .................................................................. 131
Page | v
List of Abbreviations
AC Air Conditioner
ADB Asian Development Bank
AG Aktiengesellschaft (Corporation)
ÄICTSL Atal Indore City Transport Services Limited
AJL Ahmedabad Janmarg Limited
AMRUT Atal Mission for Rejuvenation and Urban Transformation
AMTS Ahmedabad Municipal Transport Service
APC Automatic Passenger Counting Systems
APSRTC Andhra Pradesh State Road Transport Corporation
ASRTU Association of State Road Transport Union
AVLS Automatic Vehicle Location system
BFMS Bus Fleet Management System
BMTC Bangalore Metropolitan Transport Corporation
BPTSL Bhubaneshwar Puri Transport Services Ltd
BQS Bus Queue Shelter
BRT Bus Rapid Transit system
CAN Controller Area Network
CCTV Closed Circuit Television
CDP Comprehensive Development Plan
CEO Chief Executive Officer
CEPT Centre for Environmental Planning and Technology University
CGM Chief General Manager
CIRT Central Institute of Road Transport
CMP Comprehensive Mobility Plan
CNG Compressed Natural Gas
CSTC Calcutta State Transport Corporation
CTC Calcutta Tramways Company
CTTS Comprehensive Traffic and Transportation Study
DIMTS Delhi Integrated Multimodal Transit system Limited
DOS Disk Operating System
DPR Detailed Project Report
DTC Delhi Transport Corporation
DTS Dream Team Sahara
DULT Directorate of Urban Land Transport
DVR Digital Video Recorder
EPB Earning per Bus
EPKM Earning per kilometer
ERC Expert Review Committee
ERP Enterprise resource planning
ETA Expected Time of Arrival
ETM Electronic Ticketing Machine
Page | vi
EWT Excess Waiting Time

FActls Finance and Accounting Information System
FIFO First In First Out
GDP Gross Domestic Product
GPS Global positioning system
GTFS General Transit Feed Specification
HO Head Office
HQ Head Quarter
HR Human Resources
HRM Human Resource Management system
HRTC Himachal Pradesh Road Transport Corporation
iBus Bus Communication and Information System
IIT Indian Institute of Technology
IPT Intermediate Public transport
ITS Intelligent Transport System
IVRS Interactive Voice Response System
JICA Japan International Cooperation Agency
JIT Just In Time
JnNURM Jawaharlal Nehru National Urban Renewal Mission
KCTSL Kanpur City Transport Service Limited
KCTSL Kanpur City Transport Service Ltd
KMB Kowloon Motor Bus Company
KPI Key Performance Indicator
KSRTC Karnataka State Road Transport Corporation
LED Light Emitting Diode
LIMs Log Sheet Issue Machines
LTA Land Transport Authority
MD Managing Director
MIS Management Information System
MoRTH Ministry of Road Transport and Highways
MoUD Ministry of Urban Development
MPS Minimum Performance Standards
MRTS Mass Rapid Transit system
MS Microsoft
MSRTC Maharashtra State Road Transport Corporation
NA Not Available
NFC Near-Field Communication
NGO Non-government organizations
OBD On-Bus Diagnostics
OD Origin Destination
OEM Original Equipment Manufacturer
OLTAS Online ticket accounting system
Page | vii
PA Public Address System

PIS Passenger information system
PM Post Meridiem
PMC Project management consultant
PMS Person Management System
PMU Project Management Unit
PPP Public Private Partnership
PT Public Transport
PTAL Public Transport Accessibility Level
PTV Planung Transport Verkehr AG
RFID Radio frequency identification
RFP Request for Proposal
RNNTL Raipur Nagar Nigam transport Limited
ROTA Return On Total Assets
ROW Right of Way
RTO Regional Transport Office
SMS Short Messages to be Sent
SOP Standard Operating Procedures
SPA School of Planning and Architecture
SPV Special Purpose Vehicle
STA State Transport Authority
StolnS Stores Inventory System
STU State Transport Undertakings
TOR Terms of Reference
UA Urban Agglomeration
VeMaS Vehicle Maintenance System
VGF Viability Gap Funding
WBSTC West Bengal Surface Transport Corporation
Page | viii
Executive Summary
With rapid urbanization, Indian cities are witnessing increased travel demand combined with
demand for faster, reliable and economical transport facilities. However, most of the existing
urban public transport systems in India are unable to meet this demand, thereby inducing
users to shift towards privatised motorised modes of transport like cars and two-wheelers for
their mobility needs.
The responsibility for urban development including urban transport rests with the State and
Local Governments. The State Transport Undertakings (STUs) continue to dominate the
road transport services for passenger mobility in providing inter-state, intercity services.
STUs also provide city transport services in few cities. On the other hand, few mega-cities
have exclusive city transport corporations or special purpose vehicle (SPVs) formed for city
bus operations. In smaller towns and cities, city buses are operated by unorganised/ un-
regulated private players.
It is only in the recent past that few cities have received dedicated urban buses through
JnNURM funding. Besides, city bus operations in most cities are financially unsustainable,
one of the main reasons for which is Government’s obligation to serving all sections of the
society and connecting most parts of the city on subsidised rates. It is important that the
passenger ridership of the city bus systems needs to be enhanced by providing faster,
reliable, comfortable and safe travel to its passengers.
Towards this objective, this project carried out the following activities:
 Review of existing operational, planning and management of bus operations
 Identified gaps in five intervention areas- strategic planning, operational practices,
technological deployment, contracting structure and funding
 Developed list of prioritized interventions for various classes of State Road Transport
Undertaking (STU)
The case cities for this study purpose were selected through a scientific manner. The 58
cities that procured and developed bus systems through funding support from JnNURM were
shortlisted in the initial phase. Secondary data for each city was collected and updated
through various sources like reports available in the public domain. Based on data analysis
and parameters like city characteristics, availability of public transport modes, population,
geographical location, bus fleet, progressiveness and multimodality the cities were
categorised into ten groups.
Out of these 10 groups, a total of 12 representative cities – namely Delhi, Ahmedabad,

Mysore, Bangalore, Raipur, Kolkata, Nashik, Indore, Bhubaneshwar, Shimla, Kanpur,
Vishakhapatnam – were selected for city level data collection and analysis of the current
processes and operations at organizational level. The data collection in these cities was
based on interviews with officials at the city bus service agency. Additionally an expert
review committee comprising of transportation experts in State Transport Undertaking
(STU), Special Purpose vehicle (SPV), Government departments and academics was
formed and discussions/meetings was initiated from the draft stage of the project.
Page | 9
City wise data regarding operational and financial statistics was collected from STUs/SPVs
such as fleet size, route details, staff details, revenue, expenditure and accident details and
a summary of the observations are as follows:
Table 0-1: Summary of Operational and financial performance of STUs
Parameters
Populati Fleet
Vehicle Revenue Expenditure
City City Bus Operator on (UA) Held Total
Utilization (Rs. Per (Rs. Per
in (Actu Routes
(Km/bus/day) km) km)
Millions al)
Amdabad Municipal
Transport Service 7.2 979 154 205 24.57 71.67
(AMTS)
Ahmedabad
Ahmedabad
Janmarg Limited 7.2 230 12 223 29.91 56.62
(AJL)
Bangalore
Metropolitan
Bangalore 9.5 6419 245 208 49.6 49.0
Transport
Corporation (BMTC)
Bhubaneshwar-Puri
Not Not
Bhubaneshwar Transport Services 0.9 185 9 170
indicated indicated
Ltd. (BPTSL)
Delhi Transport
16.7 4468 566 188 29.8 71.4
Corporation (DTC)
Cluster Buses (Delhi
Delhi Integrated
Multimodal Transit 16.7 1490 93 210 31.5 49.2
system Limited –
DIMTS)
Atal Indore City
CNG- 300, Not
Indore Transport Services 2.1 150 14 32.0
Midi - 190 indicated
Limited (ÄICTSL)
Kanpur City
Kanpur Transport Service 2.9 270 24 102** 19.5 22.7
Ltd (KCTSL)
Calcutta State
Transport 14.0 820 112 230 34.8 111.6
Corporation (CSTC)
West Bengal Surface
Transport
Kolkata 14.0 236 18 33.8 59.7
Corporation
(WBSTC) Ltd.
Calcutta Tramways
Co. (1978) (CTC) 14.0 456 76 206 21.8 59.4
Ltd.
Karnataka State
Road Transport
Mysore 0.9 445 40 228 36.0 44.0
Corporation
(KSRTC)
MSRTC
(Maharashtra State
Nashik 1.4 264 543 235 32.3 46.6
Road Transport
Corporation)
Page | 10
Parameters
Populati Fleet
City City Bus Operator Vehicle Revenue Expenditure
on (UA) Held Total
Utilization (Rs. Per (Rs. Per
in (Actu Routes
(Km/bus/day) km) km)
Millions al)
Raipur Nagar Nigam
Raipur transport Limited 1.1 100 11 200 17.8 14.4
(RNNTL)
Himachal Pradesh
Shimla Road Transport 0.17 169 245 98 36.0 53.3
Corporation
Andhra Pradesh
State Road
*
Vishakhapatnam Transport 1.7 654 200 298 23.4 29.4
Corporation
(APSRTC)
*covers operations in long distance suburban routes
**includes offloaded buses also
Source: DIMTS Survey (2016)
Observations:
 The fleet size increases with size of the city. However, cities like Kolkata,
Ahmedabad and Kanpur do not follow the trend. Based on the norms released by the
MoUD to estimate the bus requirement of a city based on its size, there is a shortfall
of more than 4000, 1000 and 800 buses respectively in these cities. Delhi also has a
shortfall of more than 4000 buses.
 Delhi has most number of routes, but the most standout case was of Nashik
(operated by MSRTC) which has 543 routes with 264 buses. This is mainly because
each bus has a minimum of 3 routes to serve.
Simultaneously, the best practices followed by other peers in different parts of the world
were reviewed. The best practices can lay down the foundation for Indian cities to initiate
reforms. Indian cities can learn the management practices and technology implementation
done in cities like Singapore, Hong Kong and London. Further, there are some other key
examples of best practices in different cities around the world. Based on the review of the
existing best practices in the world and their comparison with practices followed in city bus
operation in India, gaps were identified.
The existing gaps identified for each of the intervention area are as follows:
1) Gaps in strategic transport planning:

 Lack of city level integrated public transport planning
 Lack of PT route mapping and infrastructure
 Lack of focus on provisioning transport infrastructure
 Absence of accessibility based planning such as using indicators to define the
service delivery in terms of distance, cost waiting time etc.
2) Gaps in use of Information and Communication Technology (ICT)
 Absence or un-availability of periodically updated digital city maps
 Lack of maintenance of GPS devices installed in vehicles
Page | 11
 Collection of in-accurate data due to network issue and poor maintenance of the
devices
 Lack of integration of on-board computer systems available on new buses procured
under JnNURM with other systems in the buses
 Installation of GPS devices on a stand-alone basis, without driver consoles except in
Ahmedabad and Mysore
 Lack of two-way communication system in the buses.
 Absence of panic buttons and on-stop bus request buttons in buses
 Limited use of planning and scheduling systems to prepare timetables and duty
rosters for the crew and buses.
 Lack of automated systems for attendance and leave application. Currently, the
process followed is manual, and suffers from favoritism and mal-practices.
 No city has implemented Bus Fleet Management System or MIS / ERP system till
date
 No analysis or data analytics is done with the available data
3) Gaps in Operational Processes
 Use of local knowledge and judgement for route planning and rationalization instead
of scientific data.
 Non-optimal and inefficient operations due to adoption of manual systems using
parameters like journey speed and EPK for timetabling and schedule adjustments.
 Several cities have computerized some of their functions but in an isolated manner.
 The existing MIS system is outdated and requires major upgrades. In current times
when data is being made available from GPS/ETM on a disaggregated level, these
MIS systems require an overhaul to incorporate new data availabilities.
 Most of the cities are still struggling with maintenance due to non-availability of spare
parts and technical manpower. Breakdown analysis is not done to identify the
reasons of failure – Spare Parts, Driver or Workshop
 Stand-alone system for procurement (Least cost contracts system in use), inventory,
fuel and store consumption is used in the depot. There is no standard quality
monitoring procedure to check the material at the time of entry.
 Human resource department is setup only at HQ level. In smaller STUs (Nashik and
Shimla) and SPVs (Kanpur and Indore), there is no separate HR department to
manage these functions
4) Gaps in Institutional and Contracting framework
 Neglect of city bus operations as STUs that operate city bus services focus more on
the inter-city bus services. For operations, old fleets are used and quality of service is
poor, though they have domain experience
 Lack technical staff/knowledge in the ULBs that supervise city bus operations
 Lack of monitoring of service delivery in Net cost contracts for bus operations as
there is no risk of revenues to the ULBs. Private operators are interested in only
operating on profit making routes and therefore neglect several areas.
5) Gaps in funding
 In most cities, no regular fare revisions are carried out for various reasons.
Page | 12
 Money spent in providing concessions to various sections of users is not reimbursed

by the ULBs/State government agencies
 Buses operate on low profit routes
 ULBs have to rely on central funding for procurement of buses due to lack of
dedicated fund for public transport
 Commercial exploitation of assets such as terminals, BQS etc., is not aggressively
done by the STUs/ULBs.
Based on the gaps identified gaps in the five intervention areas (strategic planning,
technology interventions, processes, infrastructure, contracting framework and funding) and
the review of the available best practices, various recommendations and an indicative
roadmap is listed out for a period of next 10 years.
The general project studies which are required to carried out by STUs and SPVs before the
adoption of the recommended policies or which can be taken up along with implementation
of the recommendations are as follows:
 Business plan: - All SPVs and STUs shall prepare a business plan for the
organisation for minimum 10 years and maximum 20 years. The business plan can
have the future inflow of funds detailed out along with bus requirements, requirement
of new departments, new recruitments, hiring policy, fare revision mechanisms, and
bus procurement phasing plan
 Detailed Project Report (DPR) / Bus Modernisation Plan: Conduct a feasibility
study along with bus requirement and modernisation plan including ITS facilities,
infrastructures and funding requirements.
Roadmap Recommendations
The interventions suggested in the roadmap are divided into Short Term (0 – 2 years),
Medium Term (2 – 5 years) and Long Term (5 - 10 years). The cities are categorised into
progressive, moderately progressive and least progressive and accordingly suitable
recommendations and road map is worked out. The priority list of interventions and general
requirements of STUs and SPVs for efficient follow-up of the roadmap are also discussed in
the sections below.
1) Roadmap for Strategic Transport Planning

Short Term:
 Use recommendations from the Comprehensive Mobility Plan and other transport
plans prepared for the city while planning PT system
 Amend the City Master Plans to include proposals from Mobility plans/strategic plans
on allocation of depot space, multimodal transit centres, bus terminals etc.
 Prepare city level maps of all the public transport networks including IPT/MRTS etc.,
(if any)
Medium Term:
 Develop an integrated public transport route networks along with the interchange
nodes and economic nodes to help in the strategic planning and decision making
related to public transport provisioning
Page | 13
 Form separate business units / divisions, one for planning and another for operations
which are integrated within STUs/SPVs
 Modify the existing service level benchmarks (SLBs) with focus on overall mobility.
For example:
o Availability of PT modes within 500m/1000m of settlements
o Average waiting time not more than 10 min
o Frequency of buses 5 min during peak hour and 10 min during off-peak hours
etc.
Long term:
 Use Big Data and modelling for decision making
 Develop simple mapping tools to conduct PT accessibility analysis, plot O-D desire
patterns when modelling software are not used.
2) Roadmap for Technology Interventions
a) Vehicle Tracking
Short Term:
 Integrate the existing city map with layers like key destinations and other transport
infrastructure
 Improve GPS reliability and calibrate the systems as per the field conditions
Medium term:
 Install key components like panic button, driver console etc.
 Integrate new buses with OBD-II with the existing system and calibrate the system to
improve Expected Time of Arrival (ETA) of buses
Long Term:
 Explore the feasibility of installing driver behavior monitoring systems and if feasible,
create exception reporting and alerts system for deviation from the set benchmarks
like speed, route and schedule
b) Revenue Collection
Short Term:
 Use existing ETM infrastructure to introduce smart card in buses
 Introduce common mobility cards
Medium term:
 Study feasibility of restructuring the existing fare collection mechanism and introduce
card validators in the buses.
Long Term:
 Introduce new payment mechanism like NFC and wallet payment for ticketing
c) Passenger Information Systems
Short Term:
 Install CCTV cameras and surveillance systems in the fleet and terminals and
integrate the live feed with the operation control centre
Medium term:
 Install PIS network at key bus stops and terminals including railway stations and
airports). Then integrate the journey planner tool and create a mobile app providing
Page | 14
real-time information. In later stages, install PA system with internal PIS boards and
integrate all information channels to share traffic update, transport options and
shortest routes
Long Term:
 Develop lite version indigenous planning and scheduling system for automation of
timetabling of scheduling process
d) Fleet Management Systems
Short Term:
 Implement all modules of BFMS system for complete automation of HQ and all
depots
Medium term:
 Streamline the existing processes and use technical tools to automate key functions
such as maintenance, store & purchase, fuel, accounts and HR
 Implement biometric system for payroll and setup KPIs for each department and
functional areas
 Implement Wi-Fi and infotainment systems in all buses in-lieu of advertising rights
Long Term:
 Implement APC in selected routes on pilot basis to measure the increase in revenue
e) MIS and Data Analytics
Short Term:
 Set up separate divisions for MIS and Data Analytics
 Conduct capacity building of the existing manpower and recruit specialized staff to
conduct data analysis
Medium term:
 Use data to make decisions in the organization
Long Term:
 Use data for the planning of new routes and rationalization of existing routes
3) Roadmap for improving the operational process

a) Route Planning and Rationalization
Short Term:
 Compile ridership data in standard formats to estimate the demand
 Conduct passenger surveys and household surveys to assess the demand
 Digitize all bus routes and identify the overlapping routes to prepare simple network
Medium Term:
 Conduct scientific studies to analyze the passenger OD patterns for deciding
alignment and frequency of route
Long Term:
 Use transport planning and route optimization software for detailed analysis and
transport modelling tools such as PTV VISUM, TransCAD, Cube Voyager, EMME
etc., for demand assessment for new routes
 Make ETM data available in real time (online)
Page | 15
b) Time tabling
Short Term:
 Use GPS data to calculate the bus running time for different times of the day (peak
and off-peak hours), month and seasons in both directions
Medium Term:
 Use ETM data to create stop wise boarding profile and adjust schedule
Long Term:
 Introduce software to streamline processes as per the technology roadmap
c) Duty Roaster of Crew and Bus scheduling
Short Term:
 Prepare duty roasters for longer period (six months or more) after taking inputs from
the crew
Medium Term:
 Notify the crew about duty allocation through SMS a day before the duty and/or
provision for crew to accept/ decline duty allocated using SMS or IVRS
 Install Crew Management Kiosks at all depots for crew attendance (biometric) and
duty allocation
Long Term:
 Introduce software to streamline processes
d) Maintenance Practices
Short Term:
 Develop an application using MS-Excel or MS-Access to keep record of maintenance
schedules
 Group buses in smaller lots and introduce regular preventive maintenance schedules
– daily, weekly, monthly and yearly
 Strengthen the fleet maintenance activities by hiring technical manpower or
monitoring the performance of service provider
 Monitor key activities like engine oil consumption, tyre pressure, driver complaints,
repeated breakdown, and spare part consumption on daily basis
Medium Term:
 Create automated tools for daily analysis of maintenance activities, breakdowns,
incidents - bus-wise, driver-wise and route-wise
 Introduce special incentive schemes for workshops with lowest breakdown of
vehicles
 Create digital maintenance log-books for each vehicle to keep record of maintenance
activities
 Conduct capacity building of technical manpower on new technologies
Long Term:
 Set up training facilities for the technical manpower
 Implement Maintenance Management System – as part of the BFMS under
Technology Roadmap
Page | 16
e) Stores and Purchase

Short Term:
 Conduct procurements through rate contracts and e-tendering to ensure
transparency
 Follow ‘Hub and Spoke’ model of inventory management. Main store should be setup
at central location (central depot) and satellite stores in depots (divisional depot)
 Generate cost sheet of spare parts on the basis of cost per km to evaluate the
durability of the material
 Prepare weekly reports on spare parts on the basis of high and low consumption
 Computerize the store and inventory division and create digital record sheets for all
spare parts and oil tanks for receipt and issuance
Medium Term:
 Integrate with ERP system of bus manufacturer, suppliers and OEM (Original
Equipment Manufacturer) to place repeated purchase orders
 Introduce management concepts like JIT (Just in Time), FIFO (First in First Out) etc.
Long Term:
 Implement Maintenance Management System in all depots – as part of the BFMS
under Technology Roadmap
f) Human Resource
Short Term:
 Create organizational chart and define role and responsibilities of each department
 Integrate leave management system and biometric attendance with other functions
such as crew & bus scheduling, accounts and planning
Medium Term:
 Automate the payroll management system
 Create incentive policy for crew and workshop staff to improve productivity
 Set up training division for crew (drivers and conductors)
 Integrate leave management system and biometric attendance with other functions
 Provide driver skill training using ‘Driving Simulators’
Long Term:
 Implement BFMS as per technology roadmap
g) User Feedback System
Short Term:
 Upgrade the web-portal by adding bus operation details (routes, fare, buses) for
better user accessibility and add a separate user feedback section
Medium term:
 Develop mobile app to disseminate details on bus operations and receive commuter
feedback
 Setup toll-free Call Center for grievance redressal and send action taken report to
passengers through SMS
 Procure and install an integrated system to keep track of feedback/ suggestions
received from all sources
Page | 17
Long Term:
 Use automated systems to identify same feedback/ suggestions received from
different sources
h) MIS
Short Term:
 Prepare MIS report and table of existing information in readable formats
 Review existing MIS parameters to add new parameters and remove redundant
parameters
 Conduct capacity building of existing manpower and recruitment of specialized staff
to conduct data analysis
Medium term:
 Create lite application using Macros in MS-Excel or MS-Access to automate the
analysis of raw data
 Generate exception reports on all key parameters (schedule adherence, out-shedded
trips, missed trips, speed of buses etc.) and compare with past data on performance
 Generate revenue data on ridership, revenue collected, passengers carried etc., and
integrate with route planning
 Use operation data to improve timetables, bus schedules and network plan
Long Term:
 Implement data analysis and optimization as per technology roadmap
4) Roadmap for Improving Bus Transport Infrastructure

Short Term:
 Provide modern Bus Queue Shelter (BQS) on all major routes.
Medium Term:
 Make a strong case for the development authorities for inclusion of adequate space
for depots, terminals and changeovers during master plan preparation/amendment
Long Term:
 In larger cities and on major bus density corridor, demand for bus lanes for improving
operational efficiency of system. To start with, a corridor carrying more than 5000
persons per hour per direction by bus could be considered for this purpose
5) Roadmap for Institutional and Contracting Framework

Short Term:
 Form SPVs for city bus operations and contract the operations to private operators
preferably through Gross Cost Contracts. The SPV should have technical staff to
monitor operations based on KPIs agreed between both the parties. SPV should
strictly monitor the operations for provision of bonus for better operations and penalty
against non-adherence in the service contracts
 In case of cities with Net Cost Contracts, improve the contract by adding KPI to the
contract and provide premium/VGF to the operator on the basis of ridership and route
length
Page | 18
Medium term:
 Hire a PMC to assist the Transport Department/ULBs/STUs with technical support
and bid process management
 Test the Gross Cost Contracting options – Modify the contract type from net cost to
gross cost based on market review
Long Term:
 STUs operating the buses should shift their city bus operations through formation of
SPV and selection of operators based on Gross Cost Contract with KPIs/Hybrid
options
6) Roadmap for Funding Options

Short Term:
 The transport department/STA must allow bus operator to have certain routes with
inter-city operations to balance losses from city bus operations and also to
encourage private players to participate in tender process
 Seek funding from the Government of India and multi-lateral funding agencies
 Generate revenue from commercial development and place based dynamic
advertisement options
Medium Term:
 Initiate resource mobilization from CESS
Long Term:
 Introduce priced parking based on Public Transport Accessibility Level (PTAL) and
utilize the revenue generated for improvement of the system
Proposed new tools for improving bus systems efficiency
Based on the above recommendations, the following tools and toolkits are proposed to be
developed either by the Government, a NGO, or a commercial start-up to enable efficiency
enhancement in bus system in India:
 Development of ERP based dashboard for management,

 Vehicle and Crew optimization tool,
 Time table preparation tool,
 Route rationalization tool,
 Route planning tool,
 Dead kilometer optimization tool,
 GIS-based asset management system,
 Updation of MIS parameters for Bus agencies,
 Fare revision tool, and Bus management system,
 Toolkit / Guidelines for Route Planning,
 Toolkit / Guidelines for Route numbering / Color-code system.
The institutional responsibilities to implement the proposed recommendations lie with various
stakeholders, as provided in the table below:
Page | 19
Table 0-2: Action Plan and Stakeholder Responsibilities
Sl. Area of
Action Plan Major Stakeholder
No. Intervention
Strategic Periodic Amendment of PT Policy
 MoUD
1 Transport guidelines based on requirements
Planning Development of PT Master Plan / CMP  ULBs / City Government
Development of model document for
 MoUD / MoRTH
Technology Bus Modernisation Plan
2
Interventions Implementation of GPS, ETMs, CCTVs,
 STUs / SPVs / ULBs
PIS etc.
Development of Toolkit for process
 MoUD / MoRTH
modernization
Awareness campaigns on the policy
Improving roadmap recommendations with STUs  NGOs and Think-Tanks
3 Operational and SPVs
Process  NGOs in collaboration
Training and Workshop sessions with ASRTU / IIT / SPA /
CIRT / CEPT
Conducting Route Planning and route
 ULBs / STA
rationalization studies
Institutional
Review of existing HR Policy  Amendment by respective
and State Governments
4
Contracting Development and implementation of
 By CIRT / ASRTU
Framework Training Modules
Development of PT funding policy
 MoUD / MoRTH
Funding guidelines
5
Options Fare Revision Mechanisms and
 State Government
dedicated fund for PT
It is evident that all the recommendations would have to be implemented by respective STUs
and SPVs while other stakeholders provide a supportive role. The responsibility rests with
the STU/SPV to improve the city bus system for users as well as for the agency in terms of
operational and financial efficiency.
Page | 20
1. Project Background
1.1 Background
Indian cities have witnessed disproportionate growth of private vehicles (growth rate of 12%
per annum in the last two decades) and reduced share of public transport modes which are
often faced with issues such as inadequate route-network coverage, unreliable services,
inefficient operations and unavailability of fleet for operations, overcrowding during peak
hours, etc. Thus, it is critical to develop efficient and good quality public transport systems in
cities. There are several types of public transport modes available which can provide various
capacity levels, flexibilities to cover catchments under different cost implications.
Bus based public transport systems offer medium to high capacities to serve low to medium
trip lengths with low cost and high flexibilities; and are attractive to the Urban Local Bodies
(ULBs), Transport departments and State Transport Authorities (STA) for implementation.
Bus systems can also be used as feeder to rail based systems for first and last mile
connectivity.
To achieve a significant modal shift from private to public modes, the Government of India
has launched several schemes that encourage greater use of bus based public transport
system in cities. However, even after sustained efforts, the present status of city bus service
in India indicates that the issues still exist in most cities, in varying extents. Some of the key
issues faced in urban bus transportation system and by city bus operators are listed below:
Urban Bus Transport System City Bus Operator
• Traditional methods of bus operations, •Outdated / inadquate depot infrastructure

management and control for maintenance of bus fleet
• Inadequate Bus Fleet to meet demand •Outdated Depot management and
leading to low PT modal share (%) maintenance practices
• Lack of integration with other modes of •No scientific methodology to create / modify
transport (physical, network, fare, routes
institutional and information integration) •Revenue collection and reconciliation done
• Unreliable Service & Irregular Frequency manually with element of leakge on the part
• Poor Route Network Coverage & Inadequate of conductors as well as passengers
stoppages • Lack of financial resources for capital
• Lower willingness to pay investment
• Inadequate Fare Box Collection leads to no • Low penetration of technology in bus
Profitability & Viability operations management
• Ill maintained vehicles & Low customer • Shortage of trained manpower and
satisfaction resources
• Lack of integrated database for data
analytics and decision makin
1.2 Need for the project

The STUs running city bus operation continue to rely on traditional methods and old
concepts based on manual systems. These methods are highly dependent on personal
Page | 21
judgment and local knowledge, and use limited data feed from actual operations back to
making important decision on improving operations. This situation causes inefficient
operations, impacts commercial viability and results in poor level of service for users. This
reduces the lucrativeness of public transport system and its ability to cause mode shift from
private vehicles.
Considering this situation, Shakti Sustainable Energy Foundation (SSEF) has taken up an
initiative to identify a Roadmap for improving the city bus system in India. This project
identifies the most needed interventions for improvement of bus based public transport
systems in cities. For this, SSEF assigned the Consultancy Services and respective tasks to
M/s Delhi Integrated Multi Modal Transit System Limited, Delhi.
1.3 Study Approach & Methodology

The following methodology was adopted for the project:
Figure 1-1: Study Approach & Methodology Chart
In order to accomplish the above task, the following scope was adhered to:
 Determine a baseline of existing city bus systems in India including operations and
management practices.
 Developing a comprehensive list of interventions for cities to improve their systems
 Consultations with bus agencies for a detailed assessment of the current practices
and challenges in improving the interventions identified
 Shortlisting a feasible set of interventions in consultation with cities and experts
 Priority mapping of shortlisted interventions vis-à-vis the type of city bus system
 Constituting a review committee for feedback on the proposed priority interventions
 Developing a Policy roadmap for the overall improvement of city bus systems in India
Page | 22
2. City Selection and Data Collection Process

2.1 Introduction
In this chapter, the city selection criteria’s, selected cities and data collection process is
provided in detail. The agencies/organisations visited from each of the selected city and key
personal is also provided.
2.2 City Selection Process

JnNURM supported 58 cities were shortlisted and data such as population, public transport
data (such as number of buses, routes, type of buses etc., ITS facilities implemented for
operation) and multi-modality for all the cities were collected and updated through
secondary sources like reports available in the public domain. These cities were categorised
into various groups based on the city characteristics and characteristics of the city bus
system. These two parameters were further sub-categorised based on five indicators as
indicated in the figure below:
Figure 2-1: Parameters for City Selection
The five (5) indicators and their subgroups lead to around 400 numbers of different criteria
combinations into which the cities can be categorised. Out of these combinations only
realistic/feasible combinations were considered and analysed further.
Out of 10 feasible groups of cities identified, 12 cities representing various characteristics

and spreading across the country were selected and recommended for further analysis.
Page | 23
Figure 2-2: Selected Cities for Comprehensive Study
2.3 Data Collection Approach

The data collection was primarily based on Interviews with City bus service agency /
organization officials. The STUs of the selected cities were identified and the personal
interviews were done based on the prefixed survey questionnaire formats. Survey
Questionnaire has been prepared in such a way that recorded or published data is collected
as well as the internal processes of agency is determined and understood by a face to face
interview. The overall data collection approach followed for the study is as follow:-
The data collected from the above mentioned process were collated and analysed to
understand the process followed in operations under various functional heads of each STUs.
The departments contacted for collecting data for each city are summarised in Table 2-1.
Page | 24
Table 2-1: Departments and officials of STUs and SPVs contacted
State Transport Undertaking (STU)/ Key officials and departments

Sl. No. City
Special Purpose Vehicle (SPV) contacted
Kanpur City Transport Service Limited  Mr. Neeraj Saxena
1 Kanpur
(KCTSL) M.D- KCTSL
 Mr. Bishwajit Mishra
Bangalore Metropolitan Transport
2 Bengaluru Director – Information
Corporation
Technology
 Mr. B.C Ganganna Gowda
Karnataka State Road Transport
3 Mysore Chief Mechanical Engineer –
Corporation
Production
Bhubaneshwar Puri Transport Services  Mr. Krishan Kumar
4 Bhubaneshwar
Ltd. Commissioner, BPTSL
 Mr. Sudhansu Jena, CEO,
5 Bhubaneshwar Dream Team Sahara
DTS
Calcutta State Transport Corporation
6 Kolkata  Mr. N. S. Nigam, MD, CSTC
(CSTC)
 Mr. Nilanjan Shandilya, MD,
7 Kolkata Calcutta Tramways Company (CTC)
WBSTC and CTC
West Bengal Surface Transport  Mr. Nilanjan Shandilya, MD,
8 Kolkata
Corporation (WBSTC) WBSTC and CTC
 Mr. Raghubir Singh
9 Shimla Himachal Road Transport Corporation
CGM-Operations
 Mr. B.L Chandrakar
10 Raipur Raipur Nagar Nigam Transport Limited In-Charge Officer, Raipur
Nagar Nigam
 Mr. Arjab Shah
11 Ahmedabad Amdavad Municipal Transport Service (Additional Municipal
Commissioner)
 Mr. Deepak. V. Trivedi
12 Ahmedabad Ahmedabad Janmarg Limited (AJL) General Manager –
Operations
Andhra Pradesh State Road Transport  Mr. Sudesh Kumar
13 Vishakhapatnam
Corporation Regional Manager - APSRTC
 Mr. A. K. Goyal
14 Delhi Delhi Transport Corporation
CGM, DTC
15 Indore AICTSL  Officials of AICTSL
16 Indore Prasanna Purple  Depot Manager
 Mr. P.N Patil, R.E
 Mrs. Y.K. Joshi
17 Nashik MSRTC
Divisional Controller –
MSRTC, Nashik
Page | 25
2.4 Formation of Expert Review Committee (ERC)

As per project requirements, an expert review committee with eminent transportation experts
in all the fields like STU, SPV, Government departments and academics was formed and
discussions/meetings was initiated from draft stage of the project. The expert committee was
essential in orientation and also finalising the list of feasible interventions.
2.5 Conclusion
After visiting all the selected STUs and SPVs, data was collated and summarised to
understand the performance level of each of the city bus operator. The details of the
processes reviewed, analysis and city data is provided in the next chapter.
Page | 26
3. City Report Card

3.1 Introduction
In this chapter, a summary of the process and functioning of various STUs surveyed is
provided, along with analysis of general, operational and financial statistics. This has been
done to understand the performance level of each STU. Summary of the processes followed
in each of STUs visited is provided in the later sections.
3.2 Practices Reviewed

During field visit, discussions with senior and concerned officials of the STUs and SPVs
were done to understand the practices reviewed and data related to performance statistics
was also collected. The details of the practices reviewed are provided in the figure given
below:-
Figure 3-1: Practices Reviewed within City Bus Operator
The data was collected based on questionnaires was used to conduct comparative analysis
and also to prepare summary of the processes followed by STUs (provided as city report
cards).
Page | 27
3.3 City-wise Bus Operational Characteristics

General data regarding
operational and financial
statistics was collected
from STUs/SPVs such
as fleet size, route
details, staff details,
revenue, expenditure
and accident details
through data form I. A
summary of the
observations are as
follows:
 The fleet size

increases with
size of the city;
however, cities
like Kolkata,
Ahmedabad and Kanpur do not follow the trend.
 These cities also show a shortfall of more than 4000, 1000 and 800 buses
respectively. 1 Delhi also has a shortfall of more than 4000 buses as shown in the
figure.
Delhi has most
number of
routes, but the
most standout
case was of
Nashik
(operated by
MSRTC) which
has 543 routes
with 264 buses.
This is mainly
because each
bus has a
minimum 3
routes to serve.
These details are
provided in the figure below.
1
Based on the MoUD guidelines of minimum bus requirement against population of the cities
Page | 28
Figure 3-2: City-wise route details
 With respect to vehicle utilisation as shown in Figure 3-3, it is observed that

Vishakhapatnam has the highest 298 Km/bus/day) followed by Indore (245
Km/bus/day) and Nashik (235 Km/bus/day). The lower values was observed with
Shimla (98 km/bus/day) possibly due to the hilly terrain on which the buses operate
and lower operational hours.
Figure 3-3: City-wise Vehicle Utilisation
A study of the financial statistics of the cities indicates the following:
 The key indicator of financial performance is the bus operating ratio. This is the ratio
of total operating costs to revenue. It is estimated based on ratio of cost per kilometre
(CPK) to earnings per kilometre (EPK). Ratio of below 1 indicates profits and greater
than one indicate losses.
 Of the 12 cities, only Raipur performs with positive financials and Bangalore with
breakeven financial performance.
Page | 29
 All other cities incur huge losses such as Kolkata (2.62) followed by Delhi (1.99). This
is mainly due to pending fare revisions and increasing oil prices. The revenue,
expenditure and the operating ratio for all cities are provided in the figure provided.
Figure 3-4: City-wise EPK, CPK and Operating ratio
The contracting model of each city has different model:
Table 3-1: City STUs and Private Operators
City Authority / SPV / Public Operator Private Operator Model
Prasana Purple
Mobility Pvt. Ltd.,
Amdavad Municipal Transport Service (Municipal Shyama Shyam
Gross
Corporation) Services Centre,
Mateshwari Travels
Ahmedabad Pvt. Ltd.
Chartered
Automotive Pvt. Ltd.
Ahmedabad Janmarg Limited (SPV) Gross
Shree Maruti Travel
Pvt. Ltd.
Bangalore Bangalore Metropolitan Road Transport Corporation (STU) - -
Dream Team
Bhubaneshwar Bhubaneshwar-Puri Transport Services Limited (SPV) Net
Sahara (DTS)
Delhi Delhi Transport Corporation (STU) - -
Prasanna Purple
Net
Indore Atal Indore City Transport Pvt. Ltd. (SPV) Mobility Pvt. Ltd.
Gross
Time Travel Pvt. Ltd.
Kanpur Kanpur City Transport Services Limited (SPV) - -
Page | 30
City Authority / SPV / Public Operator Private Operator Model
Calcutta State Transport Corporation

Kolkata Calcutta Tramways Company - -
West Bengal Surface Transport Corporation (STU)
Mysore Karnataka State Road Transport Corporation (STU) - -
Nashik Maharashtra State Road Transport Corporation (STU) - -
Sri Durgamba
Raipur Raipur Nagar Nigam Transport Limited (SPV) Net
Transit Pvt Ltd.
Shimla Himachal Road Transport Corporation (STU) - -
Visakhapatnam Andhra State Road Transport Corporation (STU) - -
Page | 31
3.4 City-wise Report Cards

The city-wise report cards summarised from data form II, discussions and site visits are
provided below:-
3.4.1 City Report Card - Ahmedabad

CITY REPORT CARD - AHMEDABAD
Ahmedabad Municipal Transport Service (AMTS) / Ahmedabad Janmarg
Bus operations:
Limited (AJL)
Parameters Existing Conditions
Fleet Held Total Vehicle Revenue
Expenditure
Population (UA) (Actual) Routes Utilization (Rs. Per
(2011) (December (December (Km/bus/day) km) (2014-
(Rs. Per km)
(2014-15)
2015) 2015) (2014-15) 15)
Status
AMTS-979 154 205 24.47 66.59
7.2 millions
AJL – 230 12 223 - -
Route Planning - Traditional method of route planning Moderate

- Ahmedabad followed scientific approach to design the route
network based on scientific studies and used public transport
modelling tools - cube voyager software.
Route - CEPT University had conducted study to rationalize the routes for
Good
Rationalization both AMTC and AJL in the year 2014 utilizing passenger origin –
destination profiles and desire lines.
- The proposal was to introduce direction based trunk feeder route
system. However, the proposal was not implemented.
- In Ahmedabad, although timetable preparation is done manually,
speeds measured from ground are utilized for estimating travel
Time Tabling times. Moderate
- Also separate time tables are prepared for peak and off periods on
BRT routes.
- AMTS: Manual ticketing system – frequency adjustment is done
based on performance, speed, passenger loading etc.
Frequency
- AJL: Currently Electronic ticketing machines (ETMs) are offline, Moderate
Adjustment
so reports of ETM data is prepared manually and used for
adjustment of frequency of services periodically.
- Bus & Crew Scheduling Management is done by a manual
Duty Roster of process. The Duty Roster or ROTA is prepared manually on a
Crew and Bus daily basis and released in morning to staff. Poor
scheduling - Duty management of drivers and conductors is handled by the
duty clerk based on his personal memory.
Level of ITS
implementation
- AMTS: Manual ticketing system.
Ticketing
- AJL: Offline ETMs, Automatic Fare Collection system.
Passenger - AMTS: No Passenger information system.
Information - AJL: PIS boards, Audio Announcement system. Good
- AMTS: No GPS devices are installed in the buses.
Monitoring - AJL: GPS and two way communication systems are implemented
in buses. But AVLS is not utilized for further analysis.
Security and - AMTS: No CCTV provision in the buses.
Page | 32
Surveillance - AJL: CCTV cameras are installed in 22 buses.

- AMTS: Buses are procured by private operators and are
responsible for operation and maintenance.
Maintenance
- AJL: Buses are procured by the authority and private operators
Practices
are managing the operation and maintenance of the buses.
Preventive Maintenance is done - daily, monthly and docking.
- AMTS/ AJL: MIS section compiles all the key operation statistics
from different departments and prepares daily and monthly report.
The MIS at depot as well as HO level are being generated
manually.
MIS & Data - AMTS: Standard data analytics is performed based on GPS data
Good
Analytics available on various routes. Broad analysis is done of vehicle
breakdowns
- AJL: The detailed analysis is carried out for out shed trips, missed
trips, stop wise ridership, route wise revenue analysis, ridership
analysis and bunching analysis.
- AMTS: Follow e-tendering process based on L1 basis.
Stores and
- AJL: There is no computerized stores and purchase system Moderate
Purchase
installed.
Modern
- AMTS / AJL: Equipment are procured by the private operators.
Equipment
Other sources
- Commercial development at terminals and depots. Advertisement
of revenue Good
inside and outside buses
generation
Fare revision - No fare revision formula.
User Feedback - AJL: Complaint register at stations, Toll free number of call
Good
system center, Facebook, Twitter.
Human
Resource
Management
Leave Moderate
- Manual leave management system is available.
Management
Attendance - Biometric system is used for marking attendance.
Page | 33
3.4.2 City Report Card - Bangalore

CITY REPORT CARD - BANGALORE
Bus operations: Bangalore Metropolitan Transport Corporation (BMTC)
Expenditure
(2011) (December (December
(Rs. Per km) Status
(Km/bus/day) km) (2014- (2014-15)
2015) 2015) (2014-15) 15)
9.5 millions 6419 245 208.9 49.61 49.00
2
Route Planning Traditional method of route planning Moderate
- Rationalization/ simplification of routes has been done scientifically

to some extent from passenger origin destination data, demand
Route and local knowledge.
Good
Rationalization - EMBARQ/ DULT have carried out rationalization of routes in
Bangalore. A system of direction oriented route has been
implemented, called Big 10.
- Time table optimization is done based on GPS recorded travel
time in peak and off peak hours. Time table and Crew optimization
Time Tabling is initiated on pilot basis using Lumiplan optimization software. Good
- Lumiplan uses GPS speed data in timetables for assessing realistic
travel time in peak and off peak periods.
- Broadly based on EPKM (Earning per kilometre) data, overall
Frequency route ridership and missed trips extracted from MIS.
Good
Adjustment - In future, frequency adjustment is likely to be based on ETM data,
looking into stop wise boarding and alighting profiles.
- Bus & Crew Scheduling Management is done manually.

Duty Roster of - The Duty Roster or ROTA is prepared manually on a daily basis
Crew and Bus and released in morning to staff. Duty management of drivers and Poor
scheduling conductors is handled by the duty clerk based on his personal
memory.
Level of ITS
implementation
- ETMs are used in most the buses now. BMTC has launched Smart
Ticketing mobility card in partnership with Axis Bank and it will be launched
for public in near future.
Passenger
- PIS inside buses and at terminals are implemented. Good
Information
- GPS and two way communication systems are implemented in
Monitoring
buses. But not utilized for further analysis, or monitoring.
Security and
- CCTV cameras are installed in 500 buses.
Surveillance
Maintenance - Preventive Maintenance is done - daily, monthly and scheduled
Good
Practices docking.
2
Based on judgment and local knowledge of major city generators, accessibility of various areas, public requests
and request made by local political leaders.
Page | 34
- BMTC plans to utilize detailed data analytics for optimization of

operations. Some analysis modules to be included are Revenue,
MIS & Data Cost, Routes, Load factor, Fleet utilization, Crew efficiency,
Good
Analytics Operational efficiency analysis etc.
- MIS section compiles all the key operation statistics from different
departments and prepares daily and monthly reports manually.
- Central Store inventory management system is fully computerized
Stores and
with e-tendering. However the depot inventory module is in pilot Good
Purchase
stage in one depot.
Modern - Automatic washing is used but traditional equipment for
Moderate
Equipment maintenance.
Other sources
- Commercial development at terminals and depots, Advertisement
of revenue Good
inside and outside buses.
generation
Fare revision - Revision done based on oil prices and staff salary revision. Good
- BMTC use multiple channels for User feedback. It has setup a toll
User Feedback
free helpline through call centre, provided e-mail address; establish Good
system
a website, facebook account and mobile application.
Human
Resource
Management
Leave Good
- Automatic leave management system is available.
Management
Page | 35
3.4.3 City Report Card - Bhubaneshwar

CITY REPORT CARD - BHUBANESHWAR
Bus operations: Bhubaneshwar-Puri Transport Services Ltd. (BPTSL)
Expenditure
(2011) (March (December
(Rs. Per km)
(Km/bus/day) km) (2014-15) Status
2016) 2015) (2014-15) (2014-15)
9 city
0.9 millions 185 170 Not Not
routes
(2011) indicated indicated
- BPTSL has adopted routes suggested in mobility plan prepared
for the city, to which modifications are implemented based on local
knowledge of major city generators, and accessibility of various
Route Planning Moderate
areas, public requests and request made by local political leaders.
- There is no standard system for analysing any passenger demand
profiles by conducting scientific surveys.
Route
- ETM data is reviewed to rationalize routes. Moderate
Rationalization
- Time tabling is done manually, but not followed strictly. The
Time Tabling Moderate
operator tweaks the services based on demand levels.
- Frequency adjustment is done manually and Electronic ticketing
Frequency
machines (ETMs) are offline, so reports of ETM data is prepared Moderate
Adjustment
manually and used for adjustment of frequency of services.
Duty Roster of process in Bhubaneshwar.
Crew and Bus - The Duty Roster or ROTA is prepared manually on a daily basis Poor
scheduling and released in morning to staff. Leave management system is
handled as per Govt. laws.
- GPS is installed in buses, but feeds are not used for tracking or
travel time estimation. Vehicle Tracking was initially done, but later
Level of ITS
discontinued.
implementation
- Few buses, especially those deployed on intercity routes, have
CCTV cameras fitted in them. ETMs are introduced in all buses.
Ticketing - Offline ETMs are fully implemented
Passenger Poor
- PIS boards are not installed currently.
Information
Monitoring - GPS is not installed currently.
Security and
- CCTVs are not installed currently.
Surveillance
- BPTSL is doing Preventive maintenance – daily, monthly and
docking (3 months).
- The maintenance processes and records are done manually at
Maintenance
present. Maintenance was responsibility of the vehicle Moderate
Practices
manufacturer. All repair and maintenance inventory is done
manually and no software is used for the purpose. Instead, log
books and registers are maintained.
Page | 36
- MIS reports at depot level are being generated manually and later
data entry done through computers by the statistical department.
- The statistician in the Head Office prepares daily, monthly and
yearly operational reports for the management to review. Weekly
reports are generated, based on requirements of the
MIS & Data
management. Moderate
Analytics
- Data analysis is done by statistical department (in house) based
on ETMs data, route ridership and ticket sold, operation and
maintenance cost, customer feedback and local knowledge
and then performance report are generated to review the route-
wise performance in terms of earnings and operational efficiency.
- Rate contract procurement process is done at the central office
level.
Stores and - The request for purchase is sent from the divisional level to the
Moderate
Purchase central office and tendering process is done manually on the
basis of rate contract by the central office. The store inventory is
done manually at the depot / divisional level.
Modern
- Standard depot equipment are being used.
Equipment
Other sources - Advertisement inside and outside buses. The revenue sharing
of revenue model is that 20% share has to be given to BPTSL, while the rest
generation is retained by the operator (DTS).
- Customer feedback can be submitted using Email, Website,
User Feedback
Mobile SMS and Telephone. Moderate
system
- Feedback complaint tracking redressed is done by these systems.
Human
Resource
Management
Leave Poor
Management
Attendance - Bio-metric are used.
Page | 37
3.4.4 City Report Card - Delhi

CITY REPORT CARD - DELHI
Delhi Transport Corporation (DTC) – Public Operator
Bus operations:
Delhi Integrated Multimodal Transit system Limited (DIMTS) – Cluster Buses
Vehicle Revenue
Fleet Held Total Expenditure
Population (UA) Utilization (Rs. Per
(Actual) Routes (Rs. Per km)
(Km/bus/day) km) (2014- (2014-15)
(2015-16) 15)
29.8 (non 71.4 (non Status
DTC – 4468 566 188
AC, city AC, city
22 millions (March 2016) services services
(2011) only) only)
Cluster- 1490 93 31.5
(March 2016) (March 2016)
210 49.24
- DTC: The operator adopts Traditional method of route planning

which is based on origin destination of route, operational feasibility
and alignment, identification of designated bus stops, assessing route
Route Planning length data by physical survey. Moderate
- Cluster: The agency adopts Scientific method of route planning or
evaluation process for operation. There are 657 registered routes
identified for operation under the cluster scheme.
- DTC: Rationalization of routes has been done scientifically, based
on Route rationalization study commissioned by Transport
Department, Government of NCT of Delhi in which extensive surveys
were done and route mapping and analysis was done in Cube
Route Voyager software. Modifications to routes are done also based on
Good
Rationalization public requests. Cluster buses are operated on congruent alignment
with that followed by DTC.
- DIMTS carries out periodic survey to obtain public feedback and
suggestions pertaining to cluster services. Route performance is
monitored on weekly basis.
- DTC: The duty operational plan is based on flat average running
time per km during peak and off peak hours. The time table is fixed
without taking in to account the actual travel demand on the
route.
- Cluster: Currently time tabling is prepared manually, but
implementation of differential scheduling is in progress.
- DTC: Adjustments are done based on review of performance of a
route and passenger feedback.
Frequency
- Cluster: This is presently done broadly based on passenger Moderate
Adjustment
demand or route ridership (ground data) through Automatic
Vehicle Location System software (AVL).
- DTC: Route & Crew Scheduling Management is done by a manual
process across all the depots of DTC. The Duty Roster is prepared
Duty Roster of manually on a daily basis and released everyday around 4:00 PM for
Crew and Bus the next day. Moderate
scheduling - Cluster: Duty allocation of a bus on a particular route is done on the
AVL system. Drivers and conductors are issued memos and waybills
only after reporting to the depot and biometric verification.
Level of ITS
implementation
- DTC: Manual preprinted tickets are being used. Currently, ETM has Moderate
Ticketing been introduced on pilot basis.
- Cluster: Online ETMs are used in all buses, with the provision of fall
Page | 38
back on manual preprinted tickets in case of any issue with ETM.

Passenger
- DTC / Cluster: LED display boards inside buses (DTC, DIMTS)
Information
- DTC: Monitoring through GPS devices is under progress.
Monitoring - Cluster: Monitoring of operations is done through GPS based AVL
systems.
Security and - DTC: CCTV has been implemented in 200 buses
Surveillance - Cluster: CCTVs are not installed in the buses.
- DTC: DTC has outsourced the maintenance and repairs of JnNURM
buses to the manufacturers – Tata Motors Limited and Ashok Leyland
Limited. The bus-wise logs of kms and maintenance work is
computerized with daily check list of due buses earmarked for
Maintenance
preventive maintenance in sync with preventive maintenance Moderate
Practices
schedules as laid down by vehicle manufacturers.
- Cluster: Maintenance of buses is done by concessionaires. Annual
Maintenance Contract (AMCs) is done by vehicle manufacturer in
some cases.
- DTC: Route wise EPK and EPB and route wise average no of
passengers reports are developed manually for monitoring of
productivity of crew and operations planning at depot and corporate
MIS & Data
level. There is no data analytics reported except using MIS reports for Moderate
Analytics
making decisions on route performance.
- Cluster: Daily operation statistics are prepared and monitored
through scientific methods.
- DTC: Materials are procured through Lowest cost contract (L1) at the
Stores and central office level.
Moderate
Purchase - Cluster: Stores and purchase management is done by
concessionaire or vehicle manufacturer.
Modern
- DIMTS: Modern equipment’s are used by the private operators.
Equipment
Other sources
of revenue - Cluster: Display of advertisement on Cluster buses is in progress.
generation
- Fares are decided by the Transport Department, applicable both in
Fare revision
DTC and Cluster services.
User Feedback - DTC: Call center and Website
Moderate
system - Cluster: Mobile app, OCC, Mail, Letters, Feedback forms on website
Human
Resource
Management
Leave Moderate
- Cluster: Concessionaire/ Man power agency (Conductor)
Management
- DTC: Presently both biometric and manual systems exist.
Attendance
- Cluster: Biometric attendance system is being used.
Page | 39
3.4.5 City Report Card - Indore

CITY REPORT CARD - INDORE
Bus operations: Atal Indore City Transport Services Limited (ÄICTSL)
Fleet Held Total Vehicle Revenu Expenditur
Population (UA) (Actual) Routes Utilization e (Rs. e (Rs. Per
(2011) (December (December (Km/bus/day) Per km) km) (2014- Status
2015) 2015) (2014-15) (2014-15) 15)
CNG - 300 Not
2.17 millions 150 14 32
Midi – 190 indicated
- The city bus route network system has been planned and designed
in a scientific manner. Direction oriented Hub and Spoke
Route Planning pattern of routing has been adopted. Moderate
- Also AICTSL undertakes passenger loadings in deciding the routes
apart from the traditional method of route planning.
- Rationalization/simplification of routes has been done
Route
scientifically based on passenger origin destination, demand and Moderate
Rationalization
local knowledge and using public transport modelling tool.
- Time tabling is done manually based on the expected passenger

loadings in the peak, normal and off peak hours.
- This is presently done broadly based on EPKM (Earning per

Frequency
kilometre) data and route ridership and cancelled trips extracted Moderate
Adjustment
from MIS.
- In the current process, Route & Crew Scheduling Management is
Duty Roster of done by a manual process. The Duty Roster is prepared manually
Crew and Bus on a daily basis for the next day. Moderate
scheduling - Daily earning report and monthly route wise performance reports
are prepared and used in bus scheduling.
Level of ITS
implementation
Ticketing - Offline ETMs are fully implemented.
Passenger
- PIS inside buses are implemented. Moderate
Information
Monitoring - GPS are implemented in buses.
Security and
- CCTVs are installed in BRT buses at present.
Surveillance
- City buses operation is operated on Net Cost model. The buses
are procured and maintained by the operators.
Maintenance - BRT buses are owned by AICTSL and operated by private
Moderate
Practices operator under Gross Cost Model. Maintenance is being carried
out by the private bus operators and buses are having Annual
Maintenance Record (AMCs) with the bus manufacturer.
- Currently, the MIS is being generated manually and digitalized by
the operator for the MIS purpose in which data is fed from the
ETMs and GPS devices.
MIS & Data
- AICTSL is currently carrying out the data analytics for the Moderate
Analytics
reconciliation of payments to be made to the private bus operators
and other performance reports as mentioned above through a
technology vendor Ärya Omnitalk
Page | 40
- A separate store and purchase room is there at the bus depots,

Stores and
which are used for the replacement of the bus parts. Stores and Poor
Purchase
purchase records are computerized.
Modern
- Equipment are procured by the private operators.
Equipment
Other sources
of revenue - Only farebox collection.
generation
User Feedback - Customer feedback can be submitted using Toll free helpline
Moderate
system through call centre, email, website, Facebook, Mobile app
Human
Resource
Management
Leave Moderate
- Manual leave management system is available
Management
Page | 41
3.4.6 City Report Card - Kanpur

CITY REPORT CARD - KANPUR
Bus operations: Kanpur City Transport Service Ltd (KCTSL)
Fleet Held Total Vehicle Revenue Expenditure
Population (UA) (Actual) Routes Utilization (Rs. Per (Rs. Per
(2011) (December (December (Km/bus/day) Status
km) (2014- km) (2014-
2015) 2015) (2014-15) 15) 15)
2.9 millions 270 24 102 19.5 22.78
- KCTSL adopts Traditional method of route planning. There is no

Route Planning standard system for analysing any passenger demand profiles by Moderate
conducting scientific surveys.
- No periodic route rationalization study is carried out to improve the
Route existing network.
Moderate
Rationalization - New routes are evaluated based on political influence or public
demand.
- Time tabling is manually done based upon origin destination
Time Tabling route length, passenger demand, road condition, average Moderate
speed, layover time and number of buses.
- Frequency adjustment is done manually and Electronic ticketing
Frequency machines (ETMs) are offline, so reports of ETM data is prepared
Moderate
Adjustment manually and used for adjustment of frequency of services
periodically.
Duty Roster of - Bus & Crew Scheduling Management is done by a manual process
Crew and Bus in Kanpur. The Duty Roster or ROTA is prepared manually on a Poor
scheduling daily basis and released in morning to staff.
Level of ITS - Not implemented ITS facilities in buses. Only ETMs are introduced
implementation on all buses.
passenger
Information Poor
Security and
Surveillance
- KCTSL carries out Preventive maintenance as per manufacturing
schedules. The maintenance processes and records are done
manually at present. Repair & Maintenance activities are out
sourced to a service provider.
Maintenance
- Software are under development. Fuel management is maintained Moderate
Practices
by software. The data of earned and missed km are fed into
software, developed in house by service provider, which
automatically updates driver wise, bus wise earned km and fuel
average achieved.
- MIS at depot as well as Head Office level are being generated

MIS & Data
manually and later data entry done through computers by the Moderate
Analytics
statistical department.
Page | 42

level by service provider. Limited Tender is done for day today
Stores and urgent requirements to be procured from local market.
Moderate
Purchase - Service provider has in place a software based inventory control
system. Quality control management is done manually and visually
respectively. They do not have material testing facility.
Modern
Equipment
Other sources
generation
User Feedback
- No customer feedback system is available.
system
Human
Resource
Management
Leave Poor
Management
Attendance - Manual system to record attendance.
Page | 43
3.4.7 City Report Card - Kolkata

CITY REPORT CARD - KOLKATA
Calcutta State Transport Corporation (CSTC) / West Bengal Surface
Bus operations: Transport Corporation (WBSTC) Ltd. / Calcutta Tramways Co. (1978) (CTC)
Ltd.
Fleet Held Total Vehicle Revenue Expenditure
(Actual) Routes Utilization (Rs. Per (Rs. Per
Population (UA)
(December (Decembe (Km/bus/day) km) (2014- km) (2014-
2015) r 2015) (2014-15) 15) 15)
CSTC - 820 112 230 34.87 111.67 Status
14 millions
(2011) CTC - 456 76 206 21.83 59.4
WBSTC –
18 - 33.87 59.76
236
- CSTC, CTC and WBSTC adopt Traditional method of route

Route Planning Moderate
planning.
Route - In the absence of any travel data, existing routes are evaluated
Moderate
Rationalization based on public demand.
- CSTC: Time tabling is computerized using a spreadsheet tool is

developed in Excel based on number of vehicles to be put,
Time Tabling average speed that can be achieved depending upon traffic Moderate
congestion and number of stops, halt time at the destination.
- Time tables are revised whenever required (approx. twice a year).
Frequency
- There is no scientific method of frequency adjustment.
Adjustment
- CSTC: Through Online Ticket Accounting System
Duty Roster of
- CTC / WBSTC: Crew and bus scheduling is done by manual
Crew and Bus
process.
scheduling
Level of ITS
implementation
- CSTC: Introduction of ETMs is in progress (60% complete) . Online
Ticketing Advanced Ticket reservation system for long distance services
- CTC/ WBSTC: Manual, pre-printed tickets are used
- CSTC: Route information are available on the website
Passenger
- CTC: Route information are available on the website Moderate
Information
- WBSTC: Website is under preparation
- CSTC: In progress
Monitoring - CTC: Done manually
- WBSTC: GPS are implemented in buses.
Security and
- CSTC/ CTC/ WBSTC: CCTV cameras are installed in Volvo bus
Surveillance
- CSTC/ CTC: Both Preventive and Corrective maintenance is done
daily and after completion of 20 thousand km periodicity.
Maintenance
- WBSTC: Both Preventive and Corrective maintenance is done Moderate
Practices
with weekly, monthly, yearly and Km based as per manufacturers
recommendations.
Page | 44
- CSTC: Compilation and MIS report generation is done at the

Central Statistical Section, which compiles data generated in
different depots.
MIS & Data
- CTC: The MIS at depot level are being generated through Moderate
Analytics
softwares, which are later submitted to the Head Office. The depot
level systems are not connected to the central system.
- WBSTC: MIS reports are prepared manually.
- CSTC: Materials are procured through open and limited tenders
as well as rate contracts at the central office level. The request for
purchase is sent from the divisional level to the central office and
tendering process is done through e-tenders also manually by the
central office. The store inventory is done by software (Central
store and purchase system) at the depot / divisional level and
quality control management is done through visual and lab
testing of equipment.
Stores and
- WBSTC: Materials are procured through Rate contract and Moderate
Purchase
Limited Contract at the central office level. The request for
purchase is sent from the divisional level to the central office and
tendering process is done through e-tenders also manually by the
central office. Inventory Management is done manually at depot
level only and and quality control management is done through
visual and lab testing of equipment.
- There is no software for Fuel management system in WBSTC but in
CSTC Fuel management system is software based.
Modern
- No modern equipment are used, except ETMs.
Equipment
Other sources
generation
Fare revision - As decided by State Government
- CSTC: Through website, Emails, Posts, Social media, Toll free
User Feedback helpline
Moderate
system - CTC: Through website, Emails, Posts
- WBSTC: Emails, Posts, toll free helpline number
Human
Resource
Management
- CSTC: Software Poor
Leave
- CTC: Software
Management
- WBSTC: Manual
Attendance - CSTC/ CTC / WBSTC: Biometric
Page | 45
3.4.8 City Report Card - Mysore

CITY REPORT CARD - MYSORE
Bus operations: Karnataka State Road Transport Corporation (KSRTC)
Expenditure
Population (UA) (Actual) Routes Utilization (Rs. Per Status
(2011) (December (December (Km/bus/day) km) (2014-
(Rs. Per km)
(2014-15)
2015) 2015) (2014-15) 15)
0.9 millions 445 40 228 36 44
Route Planning - Traditional method of route planning. Moderate
- Scientific approach to design the route network.

Route
- Have attempted to rationalize bus routes based on scientific Good
Rationalization
studies and public transport modelling with Cube Voyager.
- Timetable optimization is done using GPS recorded travel time in

Time Tabling peak and off peak hours. Lumiplan software has been used for Good
timetable preparation.
- ETM data is taken from depot for adjustment of frequency of

Frequency services periodically by 6-monthly review.
Good
Adjustment - ETM data is analysed and used for route adjustment.
- Automatic scheduling is also done by Mysore.
- Bus & Crew Scheduling Management done manually. The Duty
Duty Roster of Roster or ROTA is prepared manually on a daily basis and
Crew and Bus released in morning to staff. Poor
scheduling - Duty management of drivers/conductors is handled by the duty
clerk based on his personal memory.
Level of ITS
implementation
Passenger
- PIS inside buses and at terminals are implemented. Good
Information
- GPS and two way communication systems are implemented in
Monitoring
buses.
Security and
Surveillance
Maintenance - Preventive Maintenance is done - daily, monthly and scheduled
Practices docking.
- MIS section compiles all the key operation statistics from different
departments and prepares daily and monthly report. MIS reports
are generated using data entries in depots.
MIS & Data
- Data analysis is done manually based on timetable deviation, Moderate
Analytics
driver wise analysis, real time feedback, local knowledge, GPS
km, ITS data etc. MIS analysis for trend etc. is done in Excel and
then sent to higher authorities.
- Central Store inventory management system is fully computerized

Stores and
with e-tendering. However the depot inventory module is in pilot Good
Purchase
stage in one depot.
Modern
Equipment
Page | 46
Other sources
- Commercial development at terminals and depots, Advertisement
of revenue Good
inside and outside buses.
generation
User Feedback - KSRTC has good passenger feedback systems which consist of
Good
system following: Web Portal, SMS alerts, IVRS.
Human
Resource
Management
Leave Moderate
- Automatic leave management system is available.
Management
Page | 47
3.4.9 City Report Card - Nashik

CITY REPORT CARD - NASHIK
Bus operations: MSRTC (Maharashtra State Road Transport Corporation)
Expenditure
(Rs. Per km) Status
(Km/bus/day) km) (2014-15)
2015) 2015) (2014-15) (2014-15)
1.48 millions 264 543 235 32.38 46.60
- Traditional method of route planning. There is no standard

Route Planning system for analysing any passenger demand profiles by Moderate

Route
existing network. In the absence of any travel data, existing routes Moderate
Rationalization
are evaluated based on political influence or public demand.
- Time tabling is done manually, based on assumption of an
average running time, layover time and dwell times.
Time Tabling - The travel times are estimated based on field surveys using Moderate
manual methods. The timetables are updated once in a year
(during month of June).
- Frequency adjustment is done manually and it is need based.
Frequency Currently Electronic ticketing machines (ETMs) are offline, so
Moderate
Adjustment reports of ETM data are prepared manually and used for
adjustment of frequency of services.
Duty Roster of process in Nashik. The Duty Roster or ROTA is prepared manually
Crew and Bus on a daily basis and released in morning to staff. Poor
scheduling - Duty management of drivers and conductors is handled by the
duty clerk based on his personal memory.
Level of ITS - MSRTC does not have any immediate plans to implement the ITS
implementation facilities in buses. Only ETMs are introduced in all buses.
Passenger
Information Poor
Security and
Surveillance
- Preventive maintenance is done with three periodicity; daily,
monthly and docking (3 months).
Maintenance
- All repair and maintenance inventory is done manually and no Moderate
Practices
software is used for this purpose. Instead, log books and registers
are maintained.
- Currently, MIS at depot as well as divisional level is generated
manually and later data entry done through computers by the
MIS & Data statistical department.
Moderate
Analytics - Data analysis is done by statistical department (in house) and
performance reports are generated to review the route-wise
performance in terms of earnings and operational efficiency.
Page | 48

level. The request for purchase is sent from the divisional level to
the central office and tendering process is done on the basis of
Stores and
rate contract (through e-tenders) by the central office. Moderate
Purchase
- The store inventory is done manually at the depot / divisional level
and quality control management is done through visual and lab
Modern
Equipment
Other sources
generation
- Customer feedback can be submitted using Email, Website, Post
User Feedback
and Telephone. Moderate
system
- Feedback complaint tracking redressed system is manual.
Human
Resource
Management
Leave Poor
Management
Attendance - Manual system for attendance
Page | 49
3.4.10 City Report Card - Raipur

CITY REPORT CARD - RAIPUR
Bus operations: Raipur Nagar Nigam transport Limited (RNNTL)
Expenditure
(Rs. Per km) Status
(Km/bus/day) km) (2014-15)
2015) 2015) (2014-15) (2014-15)
1.12 millions 100 11 200 17.85 14.44
- RNNTL adopts Traditional method of route planning. There is no


Route
existing network. In the absence of any travel data, existing routes Moderate
Rationalization
are evaluated based on political influence or public demand.
Time Tabling - Time tabling is done manually but at centralized level. Poor
- Frequency adjustment is done manually and ETM data is
downloaded after completion of shift. Based on the information
from the ETM for few days, which is analysed to understand the
Frequency
demand for each route through which the frequency of buses is Moderate
Adjustment
modified.
- Frequency is fixed based on demand as high frequency and low
frequency bus routes.
process in Raipur. The Duty Roster or ROTA is prepared
manually on a daily basis and released in morning to staff.
Duty Roster of
- Crew scheduling is done at centralized level (operator’s office) on
Crew and Bus Poor
weekly basis and based on arrival times of conductor and drivers.
scheduling
- The ETMs are handed over to the conductor along with the vehicle
number and route on which to be operated by the operations
manager.
Level of ITS
implementation
- Offline ETMs are fully implemented. Smart card based ticket
Ticketing
system was launched on pilot basis.
passenger Moderate
- PIS inside buses are implemented.
Information
Security and
Surveillance
- RNNTL is done Preventive maintenance. Repair & Maintenance
activities are out sourced to vehicle manufacturer.
Maintenance
- Operations and Maintenance contract was a part of the bus Moderate
Practices
procurement from the manufacturer as these buses were procured
as part of the JnNURM.
- MIS is being generated manually and a spreadsheet tool is
developed by the operator for the MIS purpose in which data is fed
MIS & Data from the ETMs.
Moderate
Analytics - Data analysis is done based on ETMs data, GPS devices data,
route ridership and ticket sold, operation and maintenance
cost, customer feedback and local knowledge and then
Page | 50
performance report are generated to review the route-wise

Stores and - RNNTL are using manual system to manage the stores and
Poor
Purchase purchase.
Modern
- Equipment are procured by the private operators.
Equipment
Other sources
of revenue - Advertisement inside and outside buses and bus terminals. Good
generation
User Feedback
system
Human
Resource
Management
Leave Poor
Management
Page | 51
3.4.11 City Report Card - Shimla

CITY REPORT CARD - SHIMLA
Bus operations: Himachal Pradesh Road Transport Corporation (HRTC)
Expenditure
(2011) (December (December (Km/bus/day)
(Rs. Per km) Status
km) (2014- (2014-15)
2015) 2015) (2014-15) 15)
0.17millions 169 245 98 36.07 53.32
- HRTC adopts Traditional method of route planning. There is no

Route existing network.
Moderate
Rationalization - In the absence of any travel data, existing routes are evaluated
based on political influence or public demand.
- Time tabling is done manually by Regional Transport Office
Time Tabling Poor
(RTO)
Frequency downloaded after completion of shift. Based on the information
Moderate
Adjustment from the ETM for few days, is analysed to understand the demand
for each route through which the frequency of buses is modified.
Duty Roster of - Bus & Crew Scheduling Management is done by a manual process
Crew and Bus in Shimla. The Duty Roster or ROTA is prepared manually on a Poor
scheduling daily basis and released in morning to staff.
Level of ITS
implementation
Passenger
Information
Security and
Surveillance
- Himachal Pradesh City Transport bus stands Management &
Development authority (HPCTBSMDA) carries out Preventive
Maintenance maintenance with weekly periodicity.
Moderate
Practices - Repair & Maintenance activities are done in-house by Himachal
Road Transport Corporation which is entrusted operation of city
buses, on weekly basis at depot level.
- MIS is being generated manually and a spreadsheet tool is
developed by the operator for the MIS purpose in which data is fed
from the ETMs.
MIS & Data - Data analysis is done based on ETMs data, GPS devices data,
Moderate
Analytics route ridership and ticket sold, operation and maintenance
cost, customer feedback and local knowledge and then
performance report are generated to review the route-wise
- All three procurement process, Open tenders, Limited tenders
Stores and and Rate Contract are done at the central office level by service
Moderate
Purchase provider.
- The request for purchase is sent from the divisional level to the
Page | 52
central office and tendering process is done on the basis of rate

contract (through e-tenders) by the central office. The store
inventory is done by software at the depot / divisional level and
quality control management is done through visual and lab
Modern
Equipment
Other sources
generation
User Feedback
system
Human
Resource
Management
Leave Poor
Management
Page | 53
3.4.12 City Report Card - Vishakhapatnam

CITY REPORT CARD - VISHAKHAPATNAM
Bus operations: Andhra Pradesh State Road Transport Corporation (APSRTC)
Expenditure
(Rs. Per km) Status
(Km/bus/day) km) (2014-15)
2015) 2015) (2014-15) (2014-15)
1.7millions 654 200 298 23.47 29.4
- APSRTC adopts Traditional method of route planning. There is

Route Planning no standard system for analysing any passenger demand profiles Moderate
by conducting scientific surveys.
- Route rationalization or improvement of existing services and
starting of services on a new alignment is initially proposed by the
Route Depot manager based on various inputs such as public demand
Moderate
Rationalization and physical survey.
- The same is reviewed and approved by the Regional Manger
before implementation.
- Time tabling is done manually, based on assumption of an
average speed of 20 kmph (3 minutes per km) for ordinary
services and 24 kmph (2.5 minutes per km) for express services.
The timetables are updated on the website.
- Frequency of Time table is changed based on passenger need or
demand
downloaded after completion of shift.
Frequency
- Information from the ETM for few days is analysed to understand Moderate
Adjustment
the demand for each route through which the frequency of buses is
modified.
- Online ticket accounting system (OLTAS) is used for automatic
Duty Roster of allocation and information to staff. The system sends the duty
Crew and Bus information in advance through SMS to the crew. Good
scheduling - The crew can also confirm or decline the duty through SMS. Duty
sheets are printed through computers for the staff
Level of ITS
implementation
Passenger
Information
Security and - CCTVs are installed currently in low floor buses (Tata Marco Polo)
Surveillance and Volvo buses.
- APSRTC carries out Preventive maintenance with daily, weekly,
KM based and Yearly periodicity.
Maintenance
- Vehicle Maintenance System (VeMaS) software is used for Moderate
Practices
maintenance of buses. There is no software for Fuel management
system. Standard practices as common in all STUs are followed.
- Outputs of ETMs and other ITS software like AVLS, VeMaS,
StolnS, OLTAS, FActls, and LIMs etc from each depot is
MIS & Data manually compiled at the Regional Office, which is later sent to
Moderate
Analytics Zonal level.
- Data analysis is done based on ETMs data, GPS devices data,
customer feedback and local knowledge and then performance
Page | 54
report are generated to review the route-wise performance in terms

of earnings and operational efficiency.
- ASRTU Rate Contract is done at the central office level. The
request for purchase is sent from the divisional level to the central
office and tendering process is done on the basis of rate contract
Stores and
(through e-tenders) by the central office. Moderate
Purchase
- The store inventory is done by StolnS software at the depot /
divisional level and quality control management is done through
visual and lab testing of equipment.
Modern
Equipment
Other sources
generation
User Feedback - Customer feedback can be submitted using Call centre, Toll free
Moderate
system number, Emails, Website, Post, Written, SMS and WhatsApp
Human
Resource - HRM is maintained by Person Management System (PMS)
Management
Leave Moderate
- Software based system is developed for leave management.
Management
3.5 Conclusion
After analysing the operational characteristics of each STUs in 12 cities, the operational
process, ITS deployment and contracting structure is compared with the international best
practices. In the next chapter, international best practices followed worldwide for each of the
operational characteristics and ITS deployment is provided.
Page | 55
4. International Best Practices
4.1 Introduction
Government of India is keen to revive all loss making public bus operators and also to open
up the sector for the private players. As highlighted above, some of the bus operators are
following good practices, which can be adopted by their peers.
It is equally important to understand the best practices followed by other peers in different
parts of the world. These best practices can lay down the foundation for Indian cities to setup
reform. Indian cities can learn the management practices and technology implementation
done in cities like Singapore, Hong Kong and London. Further, there are some other key
examples of best practices in different cities around the world. In this chapter, a brief of the
best practices followed worldwide for city bus operations are provided.
4.2 Existing International Best Practices

Strategic Transport Planning
It is important to involve customer feedback in the planning stage. TfL London is operating
700 bus routes in the city and around 15% to20% bus routes are revised every year. TfL
reviews the routes thoroughly to increase the patronage and efficiency. The authority also
solicits feedback from public, user advocacy group (TravelWatch) and other stakeholders.
The consultation process helps the authority to understand local opinion about the proposed
changes to a number of bus routes. The communication is sent to registered Oyster Card
holders who use local routes in the area through email. The questionnaire for customer
feedback from the public users consists of 13 questions (10 general and 3 specific).
Further, the route network should be simple and understandable. For example, Barcelona
modified its route network based on orthogonal grid scheme – vertical, horizontal and
diagonal routes. Similarly, Seoul designed 4 new types of routes with color coding – Trunk
Lines (Blue), Feeder Lines (Green), Circular Lines (Yellow) and Wide Area Lines (Red).
LTA Singapore has recently introduced on-demand bus service based on crowdsourcing
principle. The authority has launched a mobile app – Beeline. The commuters can indicate
and suggest Origin, Destination and Arrival time at destination using this app. The authority
analyses the crowd-sourced data with existing transport data to identify popular routes. In
case of sufficient demand, the route is launched and the customer can do the booking to
reserve the seat using the same app.
Technological improvement in Bus Operations
Technology plays a key role is public transport operation. It is important for all stakeholders
– authority, operator, employee and commuters. KMB Hong Kong has implemented vehicle
and crew scheduling to automate the process. The scheduling engine uses algorithms to
create cost-saving vehicle and crew schedules, as well as multi-day rosters. Scheduling
system is integrated with vehicle maintenance system and human resource system to take
Page | 56
automatic inputs related to availability of buses and staff members. Similarly, START
ROMAGNA in Ravenna (Italy) adopted Intelligent Garage Solution to optimized preventive
and predictive maintenance.
It is equally important to have vehicle monitoring and fare collection system. TfL London
introduced implemented bus communication and information system (iBus) to install
equipment in 8,500 buses, 90 depots and 42 service control centres. The system records
kms operated on bus routes by the operators. The information is used to calculate kms and
reliability performance payments to the bus operators, as well as, public performance
statistics. Further, it helps to monitor key KPIs - kms operated; percentage of schedule
operated and excess wait time. The same information is used to share information with
passengers using Web, SMS, 2500 signs and supports over 60 smartphone apps.
London also has integrated fare solution known as Oyster Card. Similarly, Hong Kong has
equally good fare collection system - Octopus card, a rechargeable contactless stored value
smart card used to transfer electronic payments in online or offline systems. The commuters
can travel in any modes of public transport using this card. The card is also used for
payment at convenience stores, supermarkets, fast-food restaurants, on-street parking
meters, car parks, and other point-of-sale applications such as service stations and vending
machines.
Improving the Operational processes
Bus route planning and modification is backbone of any bus system. The good route
network increases the coverage of bus service, as well as, patronage. KMB, Hong Kong is
one of the best examples of bus route planning and modification. The operator conducted
the route audit and followed ‘area approach’ network restricting approach. The entire route
network was reviewed using transport planning software packages. Some key measures
taken included straighten circuitous routings to enable faster and more direct services,
introduce express routes, and integration of bus routes using interchanges by following “Hub
and Spoke” model.
Most of the bus operators in India are facing two key challenges:
a) Availability of bus depots,and,

b) Poor maintenance facilities.
KMG Hong Kong can be good learning case for depot management and maintenance
practices. Owing to space shortage, the operator constructed multi-level depots to increase
the capacity. All these depots are 2 stories (Ground + First Floor + Rooftop). Ground area is
mainly used for fuelling, washing and maintenance of buses. First Floor and Rooftop are
used for the parking of the buses. Rooftop is also used for training of drivers in the day time.
KMB categorized depot size as the depot capacity to carry out maintenance of the buses,
rather than parking of the buses. The company has devised a system to ensure that the
buses are maintained at centralized locations and parking of the buses can be done at
satellite depot and bus terminal.
Page | 57
Technology tools are generating tons of data on every hour basis for transport companies.
These data can be used to draw meaningful conclusion and improve decision making. TfL
London uses data analytics to reach a much deeper understanding of customer behaviour
and provide better and more efficient services to meet customers' needs. The authority is
doing ‘Journey Mapping’, ‘Bunching Prediction’ and other analysis using vehicle location and
ticketing data.
Likewise, Sao Paulo is using data analysis to estimate the passenger occupancy in the
vehicles. The take data mostly from commuter transit cards - the bus card, the subway card
and use algorithms to infer information about how commuters and the transportation flow are
behaving. The authority does not require huge investment in hardware and other
infrastructure.
Institutional and Contracting Framework
To increase the participation of private players, it is important to design good contracting

model to create win-win scenario. Singapore also introduced quality based gross cost
system for bus contracting. All buses and bus infrastructures are owned by the authority,
and the operator is paid fees to operate the services. Evaluation of the tender was done
using Analytic Hierarchial process. Tender documents are evaluated in two aspects: Quality
and Financial cost. However, the emphasis was given to quality score over the financial.
Similarly, TfL London introduced Quality Incentive Contracts in the year 2000 to increase
the participation of private players. This is Gross Cost Contract, where operators submit bids
based on total operating cost of a route plus profit margins. Under this model, all buses and
infrastructure is owned by the bus operator. TfL specifies and monitors Minimum
Performance Standards (MPS) as per the service contract. Operators get a bonus of 1.5% of
the annual contract price for every 0.1 minute improvement in Excess Waiting Time (EWT)
above a set baseline standard, up to 15%. This helps to ensure the quality and reliability of
bus service.
Funding Options for city bus operations
One of key issues faced by the bus operators in India is low fares. In the absence of
automatic fare revision mechanism, the operators are dependent on political approval.
Bangalore has managed to devise a fare revision formula. However, the operator still cannot
raise the fare. Singapore has one of the best fare revision mechanisms as fare review is
done by independent authority – Public Transport Council. The fare adjustment is done with
respect to change in consumer price index, wage index and energy index. The authority
follows the principle of affordability, i.e. fare level should be affordable for consumer.
Similarly, Hong Kong has good mechanism to revise public transport fare. The fares of
franchised buses are determined by the Chief Executive in Council (CE-in-Council). Fare is
calculated on the basis of change in cost, forecast of future fares, and public acceptability
and affordability. If the bus operator achieved rate of return of 9.7% or more, the same is
shared between operator and passengers.
Page | 58
4.3 Summary of Key Best Practices and Learnings

As stated above, the learning from key cities has been summarized below:
Table 4-1: City-wise key area and learning
Singapore Hong Kong London

 Crowdsourcing of bus  Fare Collection System  Route Rationalization
routes  Route Planning and Time-  Bus Communication and
 Innovative approach to tabling Information System
promote PPP  Vehicle and Crew
 Tendering process and
 Regulatory Environment Scheduling
KPI monitoring
 Travel Demand  Multi-level Depot and
Management Maintenance Practices  Use of Data Analytics and
Customer information
 Driver Training
 Customer Listening
Program
In addition to above mentioned cities, the following are best practices followed in other cities
around the world:
Table 4-2: City-wise key area and learning
Key Area Division City (Country) Learning
Route Redesigning the route

Barcelona (Spain)
Rationalization network
Strategic
Transport Planning
Route Seoul (South
Categorizing bus routes
Rationalization Korea)
Dresden (un)coupling bus

Technology
(Germany) articulations
Technology
Interventions
Technology Energy Strategy and
Lyon (France)
Auxiliaries
Rio de Janeiro Building network of BRT

Route Planning
(Brazil) System
Maintenance
Ravenna (Italy) Intelligent Garage System
Improving Practices
operational Data Analytics Urumqi (China) Analysing Travel Patterns
processes Partnership with Urban
Data Analytics Sao Paulo (Brazil)
Engine
Operations and Redesigning PT
Madrid (Spain)
Planning Interchanges
Page | 59
Key Area Division City (Country) Learning

Customer Customer friendly Bus
Nantes (France)
Information Network
Customer Using Open data for
Madrid (Spain)
Information information
Institutional &
Contracting Driver Training Madrid (Spain) Driver Assistance System
framework
Dusseldorf Fare setting and adjustment
Funding Fare Revision
(Germany) practices
4.4 Conclusion
Based on the review of the existing practices in the world, the best operational practices are
compared with the practices being followed in city bus operations in Indian cities to identify
the existing gaps. The existing practices followed in India, best practices worldwide and the
identified gaps are provided in the next chapter.
Page | 60
5. Gap Analysis
5.1 Introduction
In this chapter, a comparison of the city-wide performance in various areas against the best and available practices has been done to
understand the gaps in city bus operations in India. Based on the identified gap areas, a Roadmap is recommended for each of the parameters
which are discussed in the later chapters:-
5.2 Identified Gaps in Strategic Transport Planning

The existing planning practices followed in India, identified gap areas in strategic transport planning related to public transport planning and
best practices followed for the same are as provided in the table below:-
Table 5-1: Gap Assessment of Strategic Transport Planning
Sl City Level International Best

Existing Practices Gap Analysis
No. Parameters Practices
 Master Plans  Lack of city level integrated public  Los Angeles: in Los
o Provides hierarchy to road networks transport planning which identifies Angeles Metro group
o parking facilities and mass rapid transit need of various systems such as looks after the public
systems bus routes, IPT routes, transport provisions
Strategic o Allocate suitable spaces for terminal, interchanges and terminals for and prepares short
Public depots, BQS, changeover etc. developing integrated public and long range
1 Transport  CDPs: transport system transportation plans
Planning at o The CDPs rarely adopt a scientific  Lack of PT route mapping and along with Bicycle
City level approach to assess transportation needs infrastructure (depot space, master plan. All
o Provides requirement of buses and their terminals etc.) to facilitate requirements for city
related funding requirements based on integrated planning bus operations along
crude assessment  Lack of focus on provisioning all PT routes are
 Comprehensive Mobility Plans transport infrastructure (such as detailed out in this
Page | 61

oOptimizes mobility patterns of people and depot space, terminals etc.) in the Master Plan.
goods with focus on PT, NMVs and Master Plan. At present done on
pedestrians the basis of crude assumptions
o Provides a recognized and effective platform (based on population)
for integrating land use and transport  Accessibility based planning such
planning as using indicators to define the
 CTTS: service delivery in terms of
o Focuses on vehicle flows, distance, cost waiting time etc., is
o CTTS does not develop scenarios not used
5.3 Technology Interventions in Bus Operations and Gap Identification

The below table provides the different technologies available globally for improving the efficiency of the public transport. This is then compared
with the technological deployment in Indian cities for bus operations and gaps has been assessed. The identified gap assessment is provided
below:-
Table 5-2: Gap Assessment in technology deployment in bus operations in India
Components Existing Technologies Gap Analysis International Examples

 Digital city maps are not available  London – The city has
 GIS Map of cities with minimum or are not updated on periodic created digital map with
scale of 1:2000 and accuracy +/- 5 basis all key infrastructure
metres  Lack of updated layers of other and landmarks
 Digital route map of bus routes, transports infrastructure like  Cities like Hong Kong,
bus stops, road inventory (depot, railway, metro and other modes Singapore, Seoul etc
terminal etc), landmark locations  Lack of updated layers of key have fully digital map of
and layers of metro and railways destinations and landmarks in the city bus routes and
GIS (Geographical Information network and stations in the city city, along with future development other key landmark
Page | 62

System) plan
Vehicle Tracking System
 GPS devices with GPRS  Vehicles are fitted with GPS  London – The
connection and latency of 10 devices but the maintenance of the authority has installed
seconds to send real-time location devices are poor GPS devices in all the
 Devices have inbuilt antenna and  The data accuracy is an issue buses, called iBus
battery storage to operate when owing to network issue and system
the vehicles are turned off maintenance of the device  Cities like Singapore,
 Vehicle location data helps to Seoul, and Madrid
monitor tracking of buses and have installed GPS in
GPS (Global Positioning generate alerts in case of any all the buses
System) deviation from standard
parameters
 The control centre is the beating  The control centres installed in a  London – The
heart of a public transport provider. few cities are not fully functional, authority has setup
Vehicle tracking system without restricting the monitoring and Surface Transport and
operation control centre cannot tracking of buses Traffic Operation
work efficiently  Only Ahmedabad, Bangalore, Centre to monitor
 Vehicles are monitored, deviations Delhi, Indore and Mysore has fully buses
to the timetable are recognized, functional control centre to monitor
necessary dispatching measures over-speeding, route diverting and
are executed and drivers are service delay owing to some
supported incidents
Operation Control Centre  The control centre consists of
screens to display vehicle location,
data centre and specialized staff
Page | 63

 On-board computer integrated with  On-board computer available on  London, Singapore,
other on-board elements new buses procured under Seoul, and Madrid
(passenger displays, CCTV, traffic JnNURM but not integrated with have made on-board
signal priority, PA system, other systems in the buses computers mandatory
passenger counting, etc.)  Only Ahmedabad and Mysore use on buses
 Allow voice announcement for on-board computer system with
passengers about approaching vehicle tracking device
stops
On Board Computer  Interfaces with CAN network and
PIS Board in the buses
 Helps automate Driver & Bus  GPS devices are installed on a  London, Singapore,
Service Login. There is no stand-alone basis, without driver Hong Kong, Seoul, and
requirement to make entry in the consoles except Ahmedabad and Madrid have installed
backend to connect bus detail with Mysore driver console in the
GPS  The duty entry system is manual, buses to automate the
 Helps exchange messages with i.e. allocating bus and drivers on process
Control Centre in real time. The the route and trip
control centre can send message
related to advance or delays. Can
Driver Console
raise alarms in case of any
violation
 In such systems, hardware is used  No hardware is used to monitor the  Lyon – The operator
to monitor driver performance in drivers’ behaviour in real-time like has installed Driver
real time including speed, sharp turn, acceleration etc. Assistance system in
acceleration/ breaking, engine  Training is provided to drivers for the buses to monitor
idling, fast turns etc. better fuel efficiency (Vizag) and driver behaviour and
 The control centre can review low accident driving but there is no fuel consumption in
drivers performance in real time hardware to evaluate the real-time
Driver Behaviour Monitoring  There is option to install display improvements
unit indicating the driving
Page | 64

behaviour in relation to defined
threshold values in front of driver
 There is no two-way  Cities including
 Audio Interface Equipment communication system in the buses London, Singapore,
(microphone/speaker) for voice and normally instructions are given Seoul, Madrid etc have
communications between control to drivers using mobile phone or two-way
centre, dispatchers and driver after the duty communication system
 Helps control centre to exchange  Only Ahmedabad, Bangalore in the buses to speak
message with the driver in case of (Volvo) and Mysore has installed with drivers
any emergency, road block or two-way communication system in
Two-way Communication deviation and vice versa the buses
 Panic buttons installed in the  No city has installed panic button in  Istanbul - The Istanbul
buses for passengers to send the buses yet. On-stop bus request Electric Tram and
distress message to control room buttons are also not working in any Tunnel Company
in case of emergency cities (IETT), the city’s public
 Button is integrated with GPS  Ministry of Road Transport & bus authority installed
system to send the location of the Highway (MoRTH) has issued panic buttons on their
bus to control centre directive to install the same in all buses. The IETT centre
 In some cases, panic buttons are public transport vehicle would alert the security
connected with CCTV camera and forces and a company
centre receives live footage inside official would arrive on
Panic Button the bus panic button is pressed the scene once they
receive the panic
signals.
Ticketing & Fare Collection
System
Page | 65

 ETMs are used to print tickets for  Most of the cities are using offline  N.A.
the passenger. There are two ticketing machines only and store
types of ETM machines - Offline data in the depot system at the end
vs. online. In Offline ETM, the data of the trip, except Delhi and
is stored in the machine and Bangalore
downloaded in the night at depot.  No centralized server is used to
In Online ETM, the data is send to store ticketing data to do passenger
backend in real-time. OD analysis and crew performance
 ETMs help digitise records and can
generate reports. They can be
used to issue group ticket and
ETM (Electronic Ticketing
passes. Some machines also have
Machines)
card readers. Lastly, they can help
to collect OD data of the users and
demand patterns
 Off-board ticketing, similar to  Only Ahmedabad has implemented  Trans-Milenio, the BRT
metros, improves boarding time. the same. Technology does not systems of Bogota,
The commuters can check-in and work at full efficiency and require Colombia uses fare
check- out using fare cards or upgrading gates
journey tokens; reduces revenue
leakage and manpower required to
collect the revenue. The system is
used for closed stations at BRT
Fare Gate Validator Corridor.
Page | 66

 Ticket vending machines automate  No city has installed ticket vending  The BRT system of
ticket purchase. Can be used at machines to promote off-board Taichung in Taiwan
stations or placed at bus stops for ticketing for buses. The system can used ticket vending
issuing off-boarding ticket be used for cities with BRT machines
 Ticket vending machines are being operation like Ahmedabad and
used widely now to reduce the Indore
boarding time
Ticket Vending Machines
 For open bus-stops, validators are  No city has installed or experiment  Cities including
installed in the buses to validate with card validators in the buses London, Hong Kong,
the mobility card but requires high owing to heavy passenger load Singapore etc. has
penetration of smart cards as  The same can be explore with installed card readers
single journey passengers need to single tapping option or can use in the buses (near
pay cash or get single journey existing ETM machines to read the driver’s area) to read
RFID ticket card passengers’ card
 Normally, they are used for fixed
fare rather than distance based
Card Validators fare as tap-in and tap-out is
difficult. However, validation at the
entry and exit point give accurate
OD data
 Smart cards store information to  No city has implemented mobility  London – The
process monetary transactions and card system for bus transport authority has
card holder’s details for security except Ahmedabad BRT only. introduced ‘Oyster’
purposes. There are two Further, the integration of different card – a multi-modal
categories of smart cards - A modes of transport in city is no smart card for payment
single purpose transit pass and an done yet in all modes
electronic purse (e‐purse) card  No integrated fare has been  Hong Kong – The
 The smart card can be used for proposed for the city, i.e. the different operators
Page | 67

Mobility Card Multimodal transportation ticketing commuters can take any modes to formed the organization
or Integrated Transport e-ticketing, complete the journey to introduce ‘Octopus’
combining all modes on a single card in the city
ticket
 CCTV and surveillance system  Most cities do not have CCTV  Cities including
monitor the passengers inside the cameras in the buses. Some cities London, Singapore,
bus, either locally in DVR or in has installed CCTV partially; ex – Madrid etc. have CCTV
real-time to the control room for Bangalore (500), Mysore (10), in the buses and
live monitoring Ahmedabad (22), Shimla (169) and monitor the bus in real-
 The cameras can also record the Raipur (100) time
demand of service in real-time  The buses procured under
through rush inside buses and JnNURM-II will be equipped with
used for any post-accident analysis CCTV cameras but the integration
CCTV and Surveillance System will be challenge owing to poor
supporting infrastructure
Passenger Information System
 Information display boards are  Most of the cities have not able to  London – The
installed at key locations like bus install passenger display boards at authority has installed
terminal and stops. PIS boards are key locations passenger information
equipped with GPRS or Wifi to  Mysore and Ahmedabad are board at bus stops
receive data from the data server currently using PIS boards at bus
 Boards display the expected time stop to display next bus
of arrival (ETA) of the next buses. information. Delhi has installed
Boards are also installed inside display boards at bus stops but
Display Boards buses for next approaching stop these are not fully functional owing
information to lack of GPS in DTC buses
Page | 68

 Touch Screen Kiosks serve as an  No city has invested in information  London – The
interactive medium for information kiosks for bus transport, except authority has installed
services at key locations like bus Bangalore touch screen at bus
terminal and are integrated with  Coordination among different stops and inside the
the operator web portal, for agencies is also a critical challenge buses to allow
dissemination of information about to find space for the same commuters to explore
its services bus routes and
 The Kiosks are available 24x7 and timetable
provide route information, journey
Information Kiosks planner and other details about the
city
 Journey planner apps are an  Most of the cities does not have  Madrid – The authority
efficient tool to provide information journey planner application and follows an open data
to commuters. Commuters can add mobile app to disseminate policy and allows third-
O/D points to find out the various information to public party apps to show bus
trip options and integrated with  Delhi has created a real-time information
vehicle tracking system for real- journey planner and mobile app for
time information buses but the system does not
 Most of the authorities are using have DTC buses details. Bangalore
open data policy which allows to and other cities are still in the
Journey Planner and Mobile transition phase
integrate the real-time bus
App
information with third-party app
Page | 69

 Software modules are available for  A few cities like Mysore and  Hong Kong – The
planning timetables, which help to Mumbai use planning and operator has
optimize deployment and scheduling system to prepare introduced the system
management of vehicles and timetables and duty rosters for the to automate bus and
drivers – from creating rosters to crew and buses crew schedule
transferring data for payroll  In most cities, timetables and duty
accounting rosters are created manually and
 Similarly, the vehicle deployment leads to under-utilisation of assets
process ensures high availability of and manpower. Similarly, leave
the vehicles and preventive and application process is manual, and
Planning & Scheduling System corrective maintenance schedules suffers from favouritism and mal-
practices
 No city has implemented Bus Fleet  Hong Kong – The
 BFMS increase efficiency in
Management System or MIS / ERP operator is using ERP
operation and management of
system till date based system to
depot infrastructure, bus service
 Some organizations have integrate all depot
efficiency and other resources by
developed in-house systems to operators
integrating all core operations –
manage internal operations.
Planning, Scheduling, Crew,
Bangalore, Mysore and Vizag, use
Maintenance, Store & Purchase,
isolated systems for fuel and store
Fuel, Account, HR etc.
management.
Bus Fleet Management System  It works like ERP for transport
 Other cities are struggling to define
(BFMS) organization and automate the all
the basic processes and operation
manual process
management system
Page | 70

 WiFi systems are provided in bus  No bus transport has implemented  N.A.
systems allow passengers to utilise WiFi facility at bus station and
their journey time and enhance inside the buses. Delhi and
service experience and at bus Bangalore are planning to install
stations or terminals, as well as, on the same in the city buses
long distance buses. Some cities  Some of inter-city buses has
use this facility to improve implemented basic WiFi and
customer service. Infotainment system in the buses
 Similarly, the operators are
WiFi and Infotainment System installing infotainment system to
provide free entertainment
contents
 APC systems use sensors to  No city has implemented passenger  Norway – APC
determine the number of counting system in India yet. This is systems are used in
passengers boarding/de-boarding also due to high patronage in the cities like Oslo and
the buses, thus determining the buses Akershus in Norway
occupancy level of passengers in  In the absence of APC, it is difficult  Los Angeles: it is also
the buses in real-time and reduce to find out the occupancy level in used in Los Angeles
Automatic Passenger revenue leakage. the buses at given time County Metropolitan
Counting Systems (APC) Transportation
Authority buses
 OBD systems help capture vehicle  The average age of the current  N.A.
health information related to fleets in Indian cities ranges from 2
electrical system, safety, engine to 11 years. Hence, most of these
and transmission. buses do not have any OBD
 The system also monitors the systems
functioning of ITS components  Buses under JnNURM-II mandate
OBD-II. Some cities are procuring
On-Bus Diagnostics (OBD) new buses with these systems
Page | 71

 Data analytics can be used to  Only Ahmedabad, Delhi and  London – The
understand systems and make Mysore are using data analytics authority is extensively
decision to improve service software to analyse vehicle tracking using data analytics
delivery. For example, ticketing and ticketing data tools for ‘Journey
data can provide information  Most of the cities are not using any Mapping’ and
related to demand and used for data analysis tools to review the ‘Bunching Prediction’
service optimization. raw data and do not have
 Similarly bus arrival, time spent at specialized manpower to carry out
stops, unexpected delays, these tasks
Data Analysis and passenger numbers etc, are a
Optimization valuable asset that help identify
inefficiencies in vehicle and staff
deployment, as well as, potential
routing improvements
Page | 72
5.4 Existing Operational Processes and identified gaps

The existing bus operational process followed in India and identified gap areas in city bus operations as compared to best practices regarding
key process are provided in the table below:-
Table 5-3: Gap Assessment in operational processes of city bus services
Sl International Best
Process Existing Practices Gap Analysis
No. Practices
 Planning of new routes, change in  The authorities do not analyse the  London – The
alignment or route extension is based OD data of users and authority revised 15-
on local knowledge, ground survey to boarding/alighting data at each 20% of its routes every
assess adequate right of way (ROW) point regularly to understand the year. Besides data
on road, parking space at nodes, demand pattern analytics, the authority
feasibility of taking a turn for vehicles  High demand routes are not followed consultation
inter-alia with catchment area connected through direct or process with the public
 In the absence of travel data, new express service  Hong Kong – The
routes are based on destination  There is no crowdsourcing options operator followed ‘Area
concept instead of direction based which allow commuters to submit Approach’ to review
Route Planning and approach. New routes are also route suggestions the entire network of a
1 based on political influence or public  Vehicle requirements are not particular district,
Rationalisation
demand assessed based on the demand rather than
 No periodic route rationalization study and expected ridership of each performance of
are done to improve the existing route individual routes
network. In most cities, routes are  The authority do not conduct the  Barcelona - The city
evaluated only on EPK (Earning per consultation process to collect has introduced a new
km). For low earning routes, feedback from the existing and bus network based on
authorities shift the buses to prospective commuters in the an orthogonal grid
profitable routes particular areas scheme – Vertical,
 Ahmedabad, Indore and Mysore  Route planning is not done using Horizontal and
follow scientific approach to design software packages like PTV Diagonal Routes
the route network. Similarly, Delhi VISUM, TransCAD, Cube
Page | 73
No. Practices
and Mysore have tried to rationalize Voyager, EMME etc.
bus routes based on scientific studies
and transport modelling with Cube
Voyager software
 Timetables are prepared for different  No pattern/ profile of travel time or  Hong Kong – The
routes based on average speed, i.e. demand data is used for optimum operator introduced
static timetable. The scheduler duty planning of a route based on differential timetable
calculates numbers of duties for each differential scheduling of time with above 90%
route based on distance and average table, which is based on travel time reliability, along with
speed. Each trip is allocated equal analysis of GPS data clock faced
time irrespective of time of the day  Route categorization is done on frequencies (e.g. 15,
and demand of passengers the basis of EPK rather than 20 and 30 minutes
2 Timetabling  In Ahmedabad, although timetable ridership and expected potential intervals)
preparation is done manually, speeds  Same timetables are used for peak  Seoul – The authority
measured from ground are utilised for and non-peak hours trip without used Bus Management
estimating travel times for peak and considering the journey time System to identify
off periods on BRT routes optimal bus operation
 In Mysore, time table optimization is intervals during peak
done based on GPS recorded travel and non-peak hours
time in peak and off hours using
Lumiplan software.
 Bus & Crew Scheduling Management  Scheduling is not done  Hong Kong – The
is done manually in most cities. The scientifically to allocate the buses operator introduced
Duty Roster or ROTA is prepared on the routes, based on available Bus Scheduling and
Duty Roster of Crew manually on a daily basis and fleet. There are delay at the time of Planning System to
3
and Bus scheduling released in morning to the staff. Duty outshedding owing to non- automate crew and
management of drivers and availability of buses owing to lack bus scheduling
conductors is handled by a duty clerk of integration
based on his memory.  Crew schedule are not prepared
Page | 74
No. Practices
 Any deviations from the ROTA (for and disseminated in advance. In
example, change in driver, conductor, some STUs, the duty roaster are
etc.), is noted by the out-shedder in changed on daily basis
the sub-yard register and  No software is used to prepare
subsequently updated in the daily crew duty roaster to allocate the
Duty Register by the record-keeper resources based on availability
 Due to manual system, last moment and statutory laws. The crew
changes are very high, resulting in scheduling is important to ensure
delay in outshedding of buses that good drivers are used
 In Vishakhapatnam, Online ticket optimally
accounting system (OLTAS) is used  Owing to manual system, the
for allocation and information to staff operator needs extra float for
through SMS. The crew can driver / conductor / bus for the
confirm/decline the duty through outshedding of the buses
SMS. Duty sheets are printed through
computers
 Buses while operating require three  The preventive maintenance work  Hong Kong – The
types of maintenance – (a) is planned and carried out based operator followed ‘Hub
Preventive, (b) Maintenance for on the kms travelled. Odometers of and Spoke’
defects developed on route and the buses are working properly in maintenance model,
reported by drivers after coming back most of the cities. The kms are i.e. developing main
to the depot, and (c) Maintenance of estimated based on daily operation depots as maintenance
Maintenance defects that lead to breakdown and idle run hub
4
Practices  Maintenance records are kept  Except few STUs, most of the
manually through registers. In most of cities are still struggling with
STUs, odometers of the buses maintenance due to non-
malfunction and kms are recorded on availability of spare parts and
the basis of daily schedule operation technical manpower
and maintained by adding schedule  Bus logbook are not maintained
and idle kms
Page | 75
No. Practices
 In workshops, mechanics fills the properly or updated regularly to
defect card mentioning the problem in monitor the key activities
vehicle. After submission of defect performed
card, indent is generated by the store  Breakdown analysis is not done to
and after entering details in bin card, identify the reasons of failure –
the items are issued. The ledger Spare Parts, Driver or Workshop
section maintains vehicle wise details  Tyre management is a challenge
of expenditure as it is difficult to maintain the
 Tyre Management is also a manual health card of each tyre in the
process. A tyre card is maintained depot
and managed for every tyre which
keeps the record of mileage and
Resoling / Retreading history of every
tyre
 The documents and records
pertaining to Fuel Management are
also manual. In some STUs, the
fuelling stations are setup by oil
companies which manage the
delivery and inventory of diesel.
Mysore has implemented advance
filling and dispensing system using
RFID.
 Most STUs use manual systems to  Stand-alone system for  Ravenna (Italy) – The
manage the store and purchase. The procurement (e-tendering), operator introduced
items are issued to depot store based inventory, fuel and store automated system to
5 Store and Purchase on manual demands raised by them. consumption is used in the depot manage the
The purchase orders are created  There is no standard quality maintenance tasks and
manually monitoring procedure to check the introduce the concept
 The department manages all the material at the time of entry of ‘Predictive
Page | 76
No. Practices
aspects of procurement cycle i.e.  There is also problem of obsolete Maintenance’
Inventory Stock Management, parts as the spare parts is stored
Purchase Order Processing, for buses which are out of active
Receipt/Issuance of Material from fleet
Central Store, Payment Processing,  Owing to manual system, new
Local Purchase and Issue of Items in management techniques like JIT
the depots with no visibility to HO. (Just in Time), FIFO (First in First
The key challenge is exchange of Out) cannot be followed
information among departments.  The selection of vendor is done
 A proforma is sent by the Central based on lowest cost of items
Store to depot on periodic basis. The instead of cost per km on actual
depots send their demand for all consumption of item, except
items based on last year’s Mysore
consumption after deducting the  The manual system is used for fuel
stock-in-hand dispensing and filling which can
 The Purchase Assistant prepares the lead to pilferage and waster
agenda by making comparative list
(by using the ASRTU rate contracts
and tender rates kept in files) of
approved available source
 The material is received at the
Central Store. The store keeper
records all materials received in a
ledger. The material is issued to
depots as per their demand every
week and issued to workshop staff on
the basis of requisition slip and the
entry is done in the register at depot
level. The consumption of all spare
parts is recorded in the separate
Page | 77
No. Practices
register to maintain the inventory list.
 The recruitment of quality manpower  Human resource department is  Hong Kong – The
is one of the key challenges for setup only at HQ level, which is operator has installed
STUs. There is shortage of responsible for recruitment, ERP system to
manpower in most of the organization training and deployment of the automate different
and existing manpower is not skilled manpower. However, there is no departments including
with latest technology resources at depot level Human Resource and
 Attendance and leave records are  In smaller STUs (Nashik and Finance. HR System is
managed manually at depot level. Shimla) and SPVs (Kanpur and integrated with crew
The officer compiles all the records at Indore), there is no separate HR scheduling system
the end of the month and the records department to manage these
are sent to HQ for the compilation functions
 In bigger STUs, the recruitment is  The roles and responsibilities of
6 Human resources managed centrally through HQ. The each role are not clearly defined
depot requires to send requisition for and no written SOPs are available
manpower. After the approval, the for the staff
recruitment process is started. For
SPVs, the recruitment process is
governed as per government policy.
The department needs to send
request to state government or STUs
for put staff on deputation
 In Bangalore and Mysore, kiosk-
based Leave Management System is
installed to sanction leaves of crew
and maintenance staff
 Passengers can submit their  In developed cities, the commuters  Singapore – The
7 User Feedback feedback / suggestions / complaints can use various channels including authority has a mobile
though complaint book available in toll number, website, email, social app to get route
Page | 78
No. Practices
the buses. Further, they can write to media channels (Facebook, suggestions from users
the operator or authority Twitters etc.) to submit their  Hong Kong – The
 In some STUs, toll-free call centre is feedback to the authority or operator has
setup to receive passengers’ operators ‘Customer Listening
complaints. Some other modes  Automated incident number or Program’ for customer
include email, website and mobile track number is not generated for feedback
app registering the complaints  London – A
 Social media channels like Facebook Commuter Group -
and Twitters regularly suggestions TravelWatch has been
from passengers created to give regular
feedback to authority
 San Francisco -
Commuters can rate
their journey
experience
 MIS compiles all the key operation  MIS executives use old techniques  London – The
statistics from different departments and software to manage and authority has
and prepares daily and monthly compile data. Data analysis is not introduced iBus system
reports used to understand trends to collect operational
 The reports are prepared on daily  Most decisions are taken on data
basis and the monthly report is judgmental basis without any  Sao Paulo – The
8 MIS
prepared for the top management for scientific backing authority uses data
the review from GPS/Cards/
Counters etc to
determine public
transport occupancy
levels
Page | 79
5.5 Institutional and Contracting Structure and Identified Gaps

The existing practices followed in India, identified gap areas in city bus operations and best practices regarding institutional and contracting
structure are as follows:-
Table 5-4: Gap Assessment of Institutional and Contracting Structure
Sl City Level
Existing Practices Gap Analysis International Best Practices
No. Parameters
 In most cities, the operations  City Bus operations are presently carried out by  London – TfL introduced
are done by the STU directly STUs directly or by Municipal Corporations (without Quality Incentive
with few of the maintenance or without a Special Purpose vehicle (SPV)) Contracts in 2000 based
and security outsourced. No through Net Cost Contract and Gross Cost on Gross Cost Model.
Contract or legal binding Contracts. Major issues are: The capital investment is
with the private operators o The STUs that operates city bus services have done by the operator
are involved and city bus more focus on the inter-city bus services
Institutional operations are done by neglecting the city bus operations. For  Singapore – LTA has
and divisional / zonal offices. operations, old fleets are used and quality of adopted new modified
1  For bus operations and service is poor, though they have domain contracting model in
Contracting
Reform maintenance of fleet, private experience 2015, where capital
sector participation has o The ULBs that supervise the city bus operations investment will be done
been explored by local lack technical staff/knowledge in bus operations by LTA and will pay
urban bodies - Municipal o With Net cost contract as there is no risk of management fee to the
corporations by forming revenues to the ULBs, strict monitoring of service operator
SPVs through either the delivery is not done. Private operators is
Gross Cost or Net Cost interested in only profit making routes and
contracting models neglect several areas
 Strict monitoring of KPIs required
Page | 80
5.6 Funding Options and Identified Gaps

The existing practices followed in India, identified gap areas in city bus operations and best practices regarding institutional and contracting
structure are as follows:-
Table 5-5: Gap Assessment of Funding Options

 Most of the states have At present, city bus operations are loss making for  Proximity tax
negligible funds allocated various reasons including:-  Employers tax
for STUs o In most cities, no regular fare revisions are  Cross-utility Funding
 One of the main sources of carried out for various reasons. This results in
revenue is fare box lower fare box revenues even when ridership
revenue increases
 Few cities also uses their o Money spent in providing concessions to
infrastructure such as various sections of users is not reimbursed
terminal space, BQS and o Buses operate on low profit routes
buses for advertisements  ULBs have to rely on central funding for
Funding  Few cities have developed procurement of buses due to lack of dedicated fund
1 commercial spaces at bus for public transport
Options
terminals on PPP basis  Commercial exploitation of assets such as
terminals, BQS etc., is not aggressively done by the
STUs/ULBs
o In few cities revenue is generated from
advertisements
o In-vehicle advertisement occurs in most the
places but in the terminal area and few cities
generate revenue at BQS
 Till date no city generates revenue from the parking
 Few STU’s are providing rental/ lease for
commercial/ office spaces in the terminal area
Page | 81
6. Policy Roadmap Recommendations

6.1 Introduction
Having identified gaps and available best practices policy roadmap for strategic planning, in
this chapter technology interventions, processes, infrastructure, contracting structure and
funding are listed out based on categorisation of cities as progressive, moderately
progressive and least progressive. The priority list of interventions and general requirements
of STUs and SPVs for efficient follow-up of the policy Roadmap are also discussed in the
sections below.
6.2 Preparatory Work to be done by STUs/SPVs

The general project studies, which are required to carried out by STUs and SPVs before the
adoption of the recommended policies or which can be taken up along with implementation
of the recommendations are as follows:-
 Business plan: - All SPVs and STUs shall prepare a business plan for minimum 10
years and maximum 20 years. The business plan can have the future inflow of funds
detailed out along with bus requirements, requirement of new departments, new
recruitments, hiring policy with roles and responsibilities for each positions, fare revision
mechanisms, funding and bus procurement phasing plan.
 Detailed Project Report (DPR) / Bus Modernisation Plan: a feasibility study along with
requirement of buses and modernisation plan with implementation of ITS facilities,
infrastructures and funding requirements and sources to be prepared.
6.3 List of major interventions

The order of initiation of policy roadmap by the STUs/SPVs is provided in the figure given
below. The basic requirement to bring about change in process and their requirements are
listed in priority order.
Page | 82
Page | 83
Figure 6-1: List of major interventions
6.4 Policy Roadmap for Strategic PT Planning
6.4.1 Status of Strategic PT Planning studies in India

In most of the cities, some planning documents are prepared. The status of availability of
strategic public transport planning report is provided in the table provided below:-
Table 6-1: Status of Strategic PT Planning studies in India
Maste CTTP
Cities CDP CMP Others Studies
r Plan s
(Implementation of BRTs in Bangalore,
Bangalore    Implementation of Sub-urban Rail system for
Bangalore, Bangalore Mobility Indicators study)
Mysore,    
Ahmedabad,   (Integrated Mobility Plan, Ahmedabad)
Delhi    
Kolkata,    (Citizen's report on Air quality and Urban

Mobility, Kolkata)
Vishakhapatn
   (Urban Transport requirements, Andhra
am Pradesh) 
Bhubaneswar    (Feasibility studies for Metro rail, Mono Rail
and Light rail systems) 
(Level of service classification for Urban
Heterogeneous Traffic: a case study of Kanpur
Kanpur    Metropolis, Citizen's report on Air quality and
Urban Mobility) 
Shimla    
Page | 84
Maste CTTP
Cities CDP CMP Others Studies
r Plan s
(Detailed Project report for Bus funding
under JnNURM, Capacity Building for Urban
Development Project- Rapid Base line
Raipur   assessment- Raipur city, Sustainable mobility
plan for Naya Raipur, Short Term Traffic and Long
Term Traffic and
Transportation Plan Raipur - Ongoing) 
Nashik   (Nashik Rapid Mass Transport Feasibility
study, ) 
(Comprehensive Reporting Of Traffic
 Management System With
Indore   (On- Planning & Execution Of Bus Rapid Transit
going) Network
In Indore City (M.P), India) 
On the basis of the above chart, the cities are grouped into three categories as given below:
Table 6-2: City Categories
Category “A” Category “B & C”

(Progressive) (Moderate Progressive)
Delhi Raipur
Ahmedabad Nashik
Indore Kanpur
Mysore Shimla
Bangalore
Visakhapatnam
Bhubaneshwar
Kolkata
Category A – The cities have CMPs, Transport Demand Forecast Study, Route
rationalisation studies, prepared that includes proposals related public transport provisions
and future routes. These cities should also have city-wide PT route map
Category B – The cities have conducted traffic studies and have basic understanding of the
travel characteristics (prepared CTTS) and Master Plans.
Category C – In these cities, no traffic studies has been conducted and only CDPs are
prepared.
Page | 85
6.4.2 Roadmap Recommendations for Strategic Transport Planning

Policy Roadmap for strategic transport planning are as follows:-
Table 6-3: Policy Roadmap Recommendations for Strategic Transport Planning
Sl City Level Short term Medium Term Long Term

Existing Gap Areas
No. Parameters (Upto 2 Year) (2 – 5 years) (5 - 10 years)
 Lack of city level integrated Category ‘A’ Cities
Category ‘A’ Cities
public transport planning  Use CMP recommendations in Category ‘A’ Cities
 Lack of PT route mapping planning PT system  Development of an
 Amend the City Master Integrated traffic data
 Little focus on provisioning  An integrated public transport route Plan with proposals from centre
transport infrastructure networks along with the interchange Mobility plans/strategic
(depot space, terminals etc.) nodes and economic nodes to be plans to allocate space  Use of Big Data and
in the Master Plan developed in each city prepared that for depot, multimodal modelling for decision
helps in the strategic planning and transit centres, Bus making
 Accessibility based planning
such as using indicators to
decision making related to public terminal etc.  Develop simple mapping
transport provisioning tools to carry out PT
define the service delivery in  Monitor and evaluate
Strategic Public terms of distance, cost  Modify existing service level SLBs and modify routes accessibility analysis, plot
waiting time etc., is not used benchmarks (SLBs) with focus on based on assessments/ O-D desire patterns when
Transport
1 overall mobility. For ex – periodic PT surveys modelling software not
Planning at City used.
level o PT availability within  Develop of multimodal
500m/1000m of settlements transit centres Category ‘B & C’ Cities
o Average waiting not more than  Implement city bus
Category ‘B & C’ Cities
10 min services and routes,
o Frequency of buses 5 min during  Strategic public transport multimodal transit centres,
peak hour and 10 min during off- plan to be prepared under depots etc., based on the
peak hours etc. the supervision of strategic plan proposals
Category ‘B & C’ Cities ULBs/STUs and route
modification/new route  Monitor SLBs through
 Prepare City level maps of all the periodic surveys and
requirement be refined
public transport networks – all the modify routes based on
accordingly.
cities should map all the PT routes assessment studies
including IPT/MRTS (if any)
Page | 86
6.5 Roadmap for Technology Interventions
6.5.1 Status of ITS in City Bus Transport

Most of Indian cities are still in the transition phase. Some cities have already implemented
ITS system and trying to optimize the service. On the other hand, some of the cities are still
trying to implement the system. While many cities still lack technology required to enhance
the bus service.
Vehicle
Planning Tracking
Ticketing MIS / ERP Analysing
and and
Cities and Fare System and
Scheduling / Operation
Management (BFMS) Optimizing
Despatching Control
Centre
Ahmedabad ×   × 
Bangalore In process   × 
Bhubaneshwar × ×  × ×
Delhi ×  (35%)  (35%) × ×
Indore ×   × ×
Kanpur × ×  (34%) × ×
Kolkata × × × × ×
Mysore In process   × 
Nashik ×   × ×
Raipur ×  (37%)  × ×
Shimla ×   × ×
Visakhapatnam   (75%)   (Partial) ×
On the basis of above chart, we can categorize these cities in three groups as given below:
Category A – The cities has implemented vehicle tracking and fare collection system. The
cities are using ERP and Data analysis tool. Further, the cities are taking advance measures
to adopt new technologies.
Category B – The cities are implementing ITS components and are looking to stabilize the
system.
Category C –These cities still have a long way to go as the basic systems are not fully
functional. The cities are struggling to maintain the basis bus service.
Page | 87
All cities require to improve he infrastructure and resources. However, the level of
development is different in each city and would require intervention at different level.
Category “A” Category “B” Category “C”

(Highly Progressive) (Moderate Progressive) (Low Progressive)
Bhubaneshwar
Ahmedabadi, Bangalore Kanpur
Nashik
Delhi Indore
Raipur
Mysore Kolkata Shimla
Visakhapatnam
Page | 88
6.5.2 Roadmap Recommendations for Technology Interventions

The following Roadmap is proposed for cities to upgrade bus transport in the cities.
Table 6-4: Policy Roadmap for technology interventions
Sl City Level Short Term Medium Term Long Term

Key Gap Areas
No. Parameters (First 2 Years) (3-5 Years) (6-10 Years)
 Good quality city GIS map Category “A” Category “A” Category “A” and “B”
are not available with city
 Integrate existing city map  Improve the map and  Improve the map based on
administration
with other layers like key integrate with other service change in city profile
 Lack of updated city destinations and other like para-transit
information and route Category “C”
transport infrastructure Category “B”
network  Integrate existing city map
 Lack of integration with other Category “B”
 Integrate existing city map with other layers like key
1 GIS Mapping agencies like transport,  Improve existing city map by with other layers like key destinations and other
housing etc. plotting all bus routes and destinations and other transport infrastructure
infrastructure – bus stops, transport infrastructure
depot etc. Category “C”
Category “C”
 Improve existing city map by
 Create city transport map plotting all bus routes and
with all road inventory and infrastructure – bus stops,
transport infrastructure like depot etc.
bus stops and terminal
 Low cost GPS devices with Category “A” Category “A” Category “A”, “B” & “C”
less reliability are not
Vehicle Tracking  Improve GPS reliability and  Install advanced  Integrate new buses with
available
calibrate the system as per components like driver OBD-II and with the existing
2
System and  Absence of central control the field condition behaviour monitoring system system
Operation centre to monitor the buses
 Install other key components Category “B”
Control Centre  Basic GPS are provided but like panic button, driver
without key components like console etc.  Calibrate system to improve
driver console, two-way Expected Time of Arrival
 Create exception
communication etc (ETA) of buses
Page | 89

Key Gap Areas
 Non-availability of reporting/alerts system for  Explore the feasibility for the
manpower and infrastructure the deviation from installation of driver
to allocate buses before the benchmarks like speed, behaviour monitoring system
starting of the shift route and schedule  Create exception report and
 No key technical reports Category “B” alerts system for the
related to bus tracking are deviation from the set
generated  Set up/operationalize the benchmarks like speed,
control centre to monitor route and schedule
buses
Category “C”
 Install of key components
like panic button, driver  Improve the GPS tracking
console, two-way system by maintaining the
communication etc. hardware infrastructure
Category “C”  Do Capacity building to use
the available information for
 Install GPS with driver better planning and
console in all buses and monitoring
calibrate system to match
ground conditions
 Set up/operationalize the
control centre to monitor
buses
 Install of key components
like panic button, driver
console, two-way
communication etc.
 ETM machines used are not Category “A” Category “A” Category “A”
Ticketing and dynamic and basic offline
 Use existing ETM  integrate common mobility  Introduce new payment
3 Fare ETM machines are being
infrastructure and introduce card with other services mechanism like NFC and
Management used for the service
smart card in the buses  Install card validators in the wallet payment for fare
 Absence of Smart cards in
 Introduce Common mobility buses to reduce the use of collection
the buses and integration
card single journey tickets
Page | 90

Key Gap Areas
with other modes of  Conduct feasibility study for  Introduce off-board ticketing Category “B” and “C”
transport restructuring of existing fare like gates and ticket vending
 Install card validators in the
 High issuance of single mechanism and to introduce machines in the closed
buses to reduce the use of
journey ticket is leading to card validators in the buses system
single journey tickets
revenue leakage Category “B” Category “B” and “C”  Introduce off-board ticketing
 Do Transition from offline  Introduce common mobility like gates and ticket vending
ticketing machines to online card which is integrated with machines in the closed
ETMs in all the buses other modes and other system
 Introduce smart card for the service like department
commuters in the buses stores
Category “C”  Make commuters use smart
card to reduce single
 Procure online ETM journey ticket
machines for the city bus  Conduct feasibility study for
service restructuring of existing fare
 Introduce smart card for the mechanism and to introduce
commuters in the buses card validators in the buses
 Set up data centre or using
cloud technology to store the
data
 Do capacity building for the
staff for using ticketing
machines
 Non-availability of funds to Category “A” Category “A”

meet capital and operating
 Install CCTV cameras in  Install CCTV cameras and
CCTV and cost of the system
pilot buses either in offline or surveillance system in the
4 Surveillance  Streaming of content is online mode to improve the fleet and terminal --
System delayed / stopped due to service monitoring  Integrate live feed with the
observed lower bandwidth
 Integrate CCTV cameras operation control centre
available in the newly Category “B” and “C”
procure buses under
Page | 91

Key Gap Areas
JnNURM-II  Install CCTV cameras in the
 Evaluate accident / incident buses and at bus terminal
and crew productivity based  Integrate live feed with the
on new system operation control centre
Category “B” and “C”
 Conduct feasibility study to
install CCTV in old buses
and integrate cameras in
new buses
 Non-availability of GPS Category “A” Category “A” Category “A”

devices in the vehicle
 Expand PIS network at key  Integrate with payment  Integrate all information
 Non-availability of raw data bus stops and terminal gateway to allow people to channels to share traffic
to calculate ETA of the (including railway and book ticket through mobile update, transport options
buses airport) app and shortest route
 No investment in the  Integrate journey planner  Integrate passenger
passenger information Category “B” and “C”
tool and creation of mobile feedback system in the
system owing to lack of fund app with real-time mobile app to receive  Integrate seat availability
 Lack of supporting information customer feedback and expected journey time
Passenger infrastructure like modern features
 Adopt open data policy and  Set up information kiosks at
5 Information bus stops or terminal facility  Set up information kiosks at
integrate real-time bus the bus stops or inside the
System location buses the bus stops or inside the
 Install PA system with  Create social media account buses
internal PIS boards (twitter etc.) to share latest  Integrate with payment
updates with commuters gateway to allow people to
 Integrate seat availability book ticket through mobile
 Install PIS boards at key bus and expected journey time app
stops in the city features
 Introduce PIS with mobile
app application
 Adopt open data policy  Expand PIS network at key
(including GTFS standard) bus stops and terminal
Page | 92

Key Gap Areas
and integrate with third-  Integrate journey planner
party transport app tool and creation of mobile
app with real-time
information
 Integrate passenger
feedback system in the
mobile app to receive
customer feedback
 Install PA system with
internal PIS
 Lack of investment by STUs Category “A” Category “A” Category “A”
in transit modules for time-
 Evaluate existing scheduling  Implement shortlisted  Implement planning and
tabling and scheduling
and planning system in the system for planning and scheduling system for the
 Available international market (Xerox, Trapeze, scheduling full network
software’s are very costly - Giro etc.)  Implement schedule Category “B” and “C”
Only international packages
 Develop lite version for optimization module by
are available which charge
indigenous planning and using available assets and  Set up biometric system and
on the basis of per bus per kiosks for drivers and
scheduling system for manpower for the network
month conductors to print duty
automation of timetabling of  Set up biometric system and
Planning and  Flexible work schedule is scheduling process roaster
kiosks for drivers and
6 restricted due to Motor  Integrate the system with
Scheduling  Implement leave conductors to print duty
Transport Workers Act 1961 other system for further
management kiosks and roster
 Lack of specialized network optimization
SMS based facility for  Integrate system with other
manpower available to drivers attendance system for further network
implement the technology
Category “B” optimization
 Evaluate and improve
 Process mapping for reliability and on-time
existing bus and crew performance of existing
scheduling practices route network
 Computerize existing  Create express route and
manual process for control shorter service during peak
centre, dispatching and
Page | 93

Key Gap Areas
printed memo hours
 Implement leave Category “B” and “C”
management kiosks and
SMS based facility for  Implement “lite” version of
drivers for attendance planning and scheduling
system for the preparation of
Category “C”
timetable, crew schedule
 Review and adopt best and duty roster
practices followed by other  Conduct feasibility study to
STUs (A and B) implement the advance
 Train manpower for route version of planning and
and service planning scheduling system for the
 Computerize existing organization (the
manual process for control organization should have at
centre, dispatch and printed least 500 buses and more
memo than 5 depots)
 Create express routes and
shorter service during peak
hours
 Lack of funds available to Category “A” and “B” Category “A” and “B” Category “A” and “B”
implement BFMS system as
 Create SOP documents to  Prepare System  Implement all modules of
it will require
streamline key activities – Requirement and bid BFMS system for complete
computerization of all the
Depot, Maintenance, Store document for the automation of HQ and all
department
Bus Fleet & Purchase, Fuel, Ticketing, procurement of the system depots
 Lack of trained manpower to
7 Management Account and Human  Select the bidder (Trapeze,
define the system Resources
System (BFMS) INIT AG, IVU Traffic
requirement and Category “C”
 Process mapping to Technologies AG, Lumiplan
implementation
 Inability to migrate database
implement BFMS system and any other)  Do Capacity building of
 Streamline existing process  Do Capacity building of internal manpower for the
of DOS-based system
and use of technology tools internal manpower for the transition and recruitment of
 Absence of standard to automate key functions transition and recruitment of
operating procedure (SOP) specialized manpower
 Implement biometric system specialized manpower  Evaluate and Implement of
Page | 94

Key Gap Areas
in the organization for payroll  Implement BFMS system to BFMS system (Trapeze,
 Lack of will for change in  Setup KPIs for each automate the key process – Giro Inc., INIT AG, IVU
management for department and functional Depot, Maintenance, Store Traffic Technologies AG, Vix
implementation of BFMS in area & purchase and fuel Technologies, Lumiplan,
the organization Category “C” Category “C” Goal System and any other)
to automate the operation
 Process mapping of all  Create SOP documents to
depot activities - Depot, streamline all key activities –
Maintenance, Store & Depot, Maintenance, Store
Purchase, Fuel, Ticketing, & Purchase, Fuel, Ticketing,
Account and HR Account and Human
 Do Capacity building and Resources
computerization of the  Process mapping to
existing process implement BFMS system to
 Implement biometric system automate the operation
for staff payroll management  Prepare System
Requirement and bid
document for the
procurement of the system
 Set up KPIs for the
performance of each
department and functional
area
 Lack of funds available to Category “A”, “B” and “C” Category “A”, “B” and “C”
implement Wifi and
 Float EoI to find potential  Implement wifi and
WiFi and infotainment system in the
bidders to implement the infotainment system in all
buses and at bus stations
8 Infotainment solution buses in-lieu of advertising
 Low advertising potential is --
System  Implement wifi and rights
found in smaller cities
infotainment system in
buses in-lieu of advertising
on pilot basis
Page | 95

Key Gap Areas
 Inability to calculate the Category “A” Category “A”

benefit of the system –
 Conduct feasibility study to  In case of significant
Investment Vs. Revenue
increase revenue by improvement in revenue
realization
reducing leakage and realisation, the system can
 Lack of funds available for investment be roll out for the fleet
the investment in these
 Implement APC on pilot
system
basis to measure the
Automatic  Lack of will and resistance increase in revenue Category “B” and “C”
Passenger from the staff for
9  Improve service planning  Implement APC in selected
Counting implementation of these --
based on boarding and routes on pilot basis to
Systems (APC) measures
alighting pattern at each bus measure the increase in
stop revenue
Category “B” and “C”  In case of significant
improvement in revenue
 Study cost benefit analysis realisation, the system can
of implementation of APC – be roll out for the fleet
Investment Vs. Increase in
revenue (5%, 10%, 20% or
more)
 The system cannot be Category “A”, “B” and “C” Category “A”, “B” and “C”
implemented in old buses
 Study feasibility to integrate  Use OBD data to monitor
On-Bus owing to non-availability of
OBD system with other and evaluate the health of
10 Diagnostics hardware
system like vehicle tracking, the vehicles --
System (OBD)  Procurement of new buses control centre etc.
is very slow owing to non-
 Integrate vehicle sensors
renewal of NURM
and emergency response
system
11 Data Analysis  Lack of availability of Category “A” Category “A” Category “A”, “B” and “C”
accurate raw data for the
Page | 96

Key Gap Areas
and Optimizing vehicle location, passenger  Set up separate division for  Use operational data to  Decision making process
boarding and alighting, load MIS and Data Analytics improve timetable, route should be data-driven in the
factor, passenger  Do capacity building of network, crew deployment organization
 Lack of trained manpower to existing manpower and and vehicle utilisation  Evaluation of service
carry out the job recruit specialized staff to  Use ticketing data to delivery performance based
conduct data analysis improve the route network, on data
 Calibrate raw data to service coverage and load  Use of data for the planning
improve accuracy level factor of new routes and
 Share key insights with  Use maintenance data to rationalization of existing
management evaluate performance of routes
Category “B” and “C” buses, vehicle health,
breakdown analysis
 Install GPS and ticketing  Use driver behaviour data to
devices to collect the raw conduct customized training
data program for fuel efficiency
 Prepare MIS report and and incentive systems
tabling of information in  Cost analysis of all
readable formats incidents, and potential
 Recruitment of specialized measures to increase the
manpower for data service quality and revenue
management and analysis Category “B” and “C”
 Setup separate division for
MIS/ Data Analytics
 Calibration of raw data to
improve the accuracy level
by using analytical tools
 Use operation, ticketing,
maintenance and driver
behaviour data to improve
the service quality
Page | 97
6.6 Roadmap for Improving the Operational Process

The following is the current status of systematic process followed in different cities:
Table 6-5: Current Status in Different Organizations
Route Planning Duty Roaster of

Time Maintenance Store and Human User
City & Crew and Bus MIS
Tabling Practices Purchase resources Feedback
Rationalisation scheduling
Bangalore Average Average Average Good Good Average Good Average
Mysore Good Good Average Good Good Good Good Good
Ahmedabad
Poor Poor Average Average Average Poor Poor Average
(City)
Ahmedabad
Good Good Good Average Average Average Good Average
(BRT)
Delhi
Poor Poor Poor Good Good Average Poor Poor
(Public)
Delhi
Good Poor Average Good Good Good Good Good
(Cluster)
Kolkata Poor Poor Average Average Average Average Poor Poor
Vishakhapatnam Good Good Good Good Good Good Average Good
Bhubaneshwar Average Poor Poor Poor Poor Poor Poor Average
Kanpur Poor Poor Poor Average Average Poor Poor Poor
Shimla Poor Poor Poor Average Average Poor Poor Poor
Raipur Poor Poor Poor Average Average Poor Poor Average
Nashik Poor Poor Poor Average Average Average Average Average
Indore Good Average Average Average Average Poor Good Average
On the basis of above table, we can be categorized the cities as follows:

(Highly Progressive) (Moderate Progressive) (Low Progressive)
Mysore Indore Bhubaneshwar
Visakhapatnam Nashik Raipur
Ahmedabad (BRT) Kanpur
Delhi (Cluster) Kolkata
Bangalore Shimla
Category A – The cities have developed good system to manage the task and is using
technology to improve the system, as well as, utilizing data received to optimize their
services. Some of the cities have developed independent software for crew rosters, vehicle
maintenance, inventory management, etc but there is no integration between these systems
Page | 98
Category B – The cities are in transition phase and are using modern practices to improve
the functional areas
Category C – In these cities, different processes are primarily done manually and
inconsistently. There has been no major initiative to improve the existing practices to bring
efficiency
Page | 99
6.6.1 Roadmap for Improving the Operational Processes

The following policy roadmap is proposed for improving the operational processes.
Table 6-6: Policy Roadmap for operational process
Sl Short Term Medium Term Long Term

Parameters Key Gap Areas
no. (First 2 Years) (3-5 Years) (6-10 Years)
 Lack of standard Category “A” and “B” Category “A” and “B” Category “A” and “B”
procedure to introduce
 Conduct Scientific studies  Categorize services into  Create integrated transport
new routes
to analyse OD pattern of AC premium services, plan with bus routes
o Based on local passengers for deciding Express services, etc.
knowledge of trip alignment and frequency of  Nomenclature of routes to Category “C”
generator nodes route be done in a scientific
o Destination based,  Integrate crowdsourcing manner so that it reflects  Create and strengthen
and not direction application with website Origin and Destination of separate Route Planning
oriented and mobile app to get routes  Use transport planning and
 Lack of scientific route suggestions from the  Create and strengthen route optimization software
planning or analysis public separate Route Planning for detailed analysis –
Route Planning
1 and
based on OD matrix and  Passenger feedback to be team transport modelling tools
line load reviewed in conjunction such as PTV VISUM,
Rationalisation  Use transport planning and
 Limited Market and necessary route optimization software
TransCAD, Cube Voyager,
segmentation: modifications to be done EMME etc. to be used for
for detailed analysis –
introduction of Express demand assessment for
transport modelling tools
Services, Premium Category ‘C’ Cities new routes
such as PTV VISUM,
services, etc TransCAD, Cube Voyager,
 Compile ridership data in
 Nomenclature of route is standard format to EMME etc. to be used for
not reflective of Origin estimate the demand demand assessment for
and Destination new routes
 Conduct passenger
 No periodic review and surveys and household
rationalization of routes surveys to assess the Categories “C”
 Overlaps with other demand  Integrate crowdsourcing
Page | 100

routes and transport  Digitize all bus routes and application with website
systems such as metro finding out the overlapping and mobile app to get
 Routes are evaluated with other routes to suggestions from the
primarily by its average prepare simple network public
EPK and not by service  Strengthen of route  ETM data should be
level to commuters planning team available in real time
(online)
 Average speed on the Category “A” Category “A” Category “A”, “B” and “C”
network is used. Static  Use of GPS data to  Implement Planning and  Implement Planning and
schedules are prepared calculate running time for Scheduling Module as per Scheduling Module as per
based on distance and different times of the day Technology Roadmap Technology Roadmap
speed throughout the (peak and off-peak hours),
day, irrespective of time month and seasons in both
of day and passenger directions Category “B” and “C”
demand  Use GPS data to assess
 Use of ETM data to basis
 Timetables are prepared of stop wise boarding running times for different
manually without using profile to adjust schedule times of the day (peak and
any network optimization off peak hours), month and
2 Timetabling tools  Introduce software to seasons in both directions
streamline process as per
 Scheduling is done on the Technology Roadmap  Prepare differential
basis of EPK timetable for peak and off-
peak hours based on
Category “B” and “C” analysis of GPS and ETM
 Different schedules (static) data
for peak and off-peak
hours should be prepared
initially, based on average
speed in different time
slots; and also for both
directions
Page | 101

 Duty roster is prepared Category “A” and “B” Category “A” and “B” Category “A”, “B” and “C”
manually on daily basis  Crew Management Kiosks  Use Advanced algorithm  Implement Planning and
and released in morning to be installed at all based system to prepare Scheduling Module as per
 Due to manual system, depots, wherein crew duty memo for crew Technology Roadmap
last moment changes are attendance (biometric) can including changeover
high, which results in be done. He gets notified between shifts
delay in outshedding. of duty allocated  Implement Planning and
 Additional reserve of  Introduce software to Scheduling Module as per
drivers and conductors streamline process as per Technology Roadmap
have to be maintained Technology Roadmap
Duty Roaster of Category “C”
3 Crew and Bus Category “C”
 Crew Management Kiosks
scheduling  Prepare duty roasters for to be installed at all
longer period (six months depots, wherein crew
or more) after taking inputs attendance (biometric) can
from the crew be done. He gets notified
 Notification of duty of duty allocated to him
allocation to be sent to there itself
crew through SMS a day
before the duty and/or
provision for crew to
accept/ decline duty
allocated using SMS or
IVRS
 Preventive maintenance Category “A” Category “A” Category “A”, “B” and “C”
is done on the basis of  Introduce regular  Implement Maintenance  Implement Maintenance
Maintenance recorded kms, rather than preventive maintenance Management System – as Management System – as
4 actual odometer reading
Practices schedules – daily, weekly, part of the BFMS under part of the BFMS under
 In the absence of monthly and yearly Technology Roadmap Technology Roadmap
automated notifications,  Use of simple IT  Do Capacity building of  Set up training facility for
Page | 102

chances are that applications instead of technical manpower to the technical manpower
maintenance may be manual recording to update them with new
missed generate notifications for technology
 Maintenance records are maintenance
maintained manually and  Create automated tools to Category “B” and “C”
it is difficult to check do daily analysis of
vehicle history maintenance activities,  Create automated tools to
breakdowns, incidents and do daily analysis of
 Separate records are maintenance activities,
maintained for key - Bus-wise, Driver-wise
and route-wise breakdowns, incidents and
aggregates like engine, - Bus-wise, Driver-wise
transmission, tyre, battery  Introduce special incentive and route-wise
etc. scheme for workshop for
lowest breakdown of  Implement Maintenance
vehicle Management System – as
part of the BFMS under
 Creategital maintenance Technology Roadmap
log-book for each vehicle
to keep record of all  Do Capacity building of
maintenance related technical manpower to
activities update them with new
technology

 Development of small
application using MS-excel
or Access to keep the
record of all maintenance
schedule
 Grouping of buses in
smaller lots and Introduce
regular preventive
maintenance schedules –
daily, weekly, monthly and
Page | 103

yearly
 Strengthen maintenance
activities by hiring
technical manpower or
monitor the performance of
service provider
 Monitor key activities on
daily basis – engine oil
consumption, Tyre
pressure, drivers
complaints, repeated
breakdown, and spare
part consumption
 Vendor selection or Category “A” Category “A” Category “A”

procurement process is  Procurement must be done  Implement BFMS as per  Implement Maintenance
not standardized. through rate contract and Technology Roadmap Management System in all
Contracts are usually e-tendering to ensure depots – as part of the
awarded on L-1 basis  Integrate ERP system of
transparency bus manufacturer, BFMS under Technology
 Procurement process is  Automate spare parts suppliers and OEM Roadmap
time consuming – storage and inventory (Original Equipment
approval is needed from using software application Manufacturer) to place
Stores and central, zonal levels, etc. Category “C”
5 to record the entry and repeated purchase order
Purchase  Integrate ERP system of
 Quality checks of issue of all spare parts  Introduce management
materials and correct bus manufacturer,
 Storage of items (filters concept like JIT (Just in suppliers and OEM
practices of handling / etc.) in separate boxes as Time), FIFO (First in First
storing them may not be (Original Equipment
per the maintenance Out) etc. Manufacturer)
known by local schedule
manufacturers  Introduce management
 Create digital record sheet Category “B” and “C” concept like JIT (Just in
 Bulk inventory is not of all spare parts and oil
 Automate spare parts Time), FIFO (First in First
possible – tie up with tanks for receipt and
storage and inventory Out) etc.
Original Equipment
Page | 104

Manufacturer (OEM) is issuance using software application  Implement Maintenance
needed for Just-In-Time  Generate cost sheet of to record the entry and Management System in all
(JIT) delivery spare parts on the basis of issue of all spare parts depots – as part of the
cost per km to evaluate the  Storage of items in BFMS under Technology
durability of the material separate boxes as per the Roadmap
maintenance schedule
Category “B” and “C”  Create digital record sheet
of all spare parts and oil
 Following up ‘Hub and tanks for receipt and
Spoke’ model of inventory issuance
management. Main store
should be setup at central
location and satellite stores
in depots
 Generate cost sheet of
spare parts on the basis of
cost per km to evaluate the
durability of the material
 Weekly reports on spare
parts on the basis of high
and low consumption
 Computerise store and
inventory division. Creating
digital record sheet of all
spare parts and oil tanks
for receipt and issuance
 Lack of written roles and Category “A” Category “A” Category “A”, “B” and “C”
6 Human Resource responsibilities of staff  Create organization chart,  Implement BFMS as per  Implement BFMS as per
member and defining role and Technology Roadmap Technology Roadmap
Page | 105

 Lack of standardized responsibilities of each
procedures or SOPs department Category “B” and “C”
 Recruitment process is  Integrate leave  Set up training division for
generally slow and lack of management system and crew (drivers and
independence biometric attendance with conductors)
other functions
 Implement BFMS as per
 Automate payroll Technology Roadmap
management system
 Create incentive policy for
crew and workshop staff to
improve productivity
 Set up training division for
crew (drivers and
conductors)

 Create organization chart,
and defining role and
responsibilities of each
department
 Do Gap analysis to find out
the required manpower to
carry out the essential
tasks
 Create of incentive policy
for crew and workshop
staff to improve
productivity
Page | 106

 Limited options available Category “A”, “B” and “C” Category “A”, “B” and “C” Category “A”, “B” and “C”
to raise issues to  Upgrade web-portal by  Procurement and  Implement Passenger
concerned officials adding all operation details installation of an Information System as per
 Records are maintained (routes, fare, buses) for integrated system to keep Technology Roadmap
manually with limited better accessibility and track of feedback/
facility to do analysis user feedback section suggestions received from
 Difficult to keep track of  Develop mobile app to all sources
User Feedback
7
System complaints received and disseminate details and to  Automate system to
action taken receive commuters’ identify same feedback/
feedback suggestions received from
 Setup toll-free Call Center different sources
and generation of tracking
number to send action
taken report to passengers
through SMS
 Records are maintained Category “A” Category “A” Category “A”, “B” and “C”
manually and data is  Review Existing MIS  Use operation data to  Implement Data Analysis
entered in the compute r parameters and add new improve timetable, bus and Optimization as per
 Information is compiled parameters and deduct schedule and network plan Technology Roadmap
related to - Manual redundant  Implement Data Analysis
records of vehicle  Do Capacity building of and Optimization as per
performance, route existing manpower and Technology Roadmap
8 MIS performance, etc. recruitment of specialized
 Monitoring is not done staff to conduct data
analysis Category “B” and “C”
centrally
 Create lite application  Create lite application
 Parameters are outdated
and aggregated for using Macros in MS-Excel using Macros in MS-Excel
or Ms-Access to automate or Ms-Access to automate
several critical items and
the analysis of raw data the analysis of raw data
need updation.
received from vehicle
 Generate exception
Page | 107

reports on all key tracking and ticketing
parameters (schedule machines
adherence, outshedded
trips, missed trips, speed
of buses etc.) and
comparison with past data
 Generate revenue data on
ridership, revenue
collected, passengers
carried etc., and integrate
with route planning

 Prepare MIS report and
tabling of existing
information in readable
formats
 Do Capacity building of
existing manpower and
recruitment of specialized
staff
 Use ETM data to analyse
OD pattern of passengers
Page | 108
6.7 Roadmap for Improving Bus Transport Infrastructure
For efficient operation of bus system in various cities, the following recommendations are
made related by transport infrastructure provisions and equipment’s:
(a) Modern Bus Queue Shelter (BQS) to be provided on all major routes. Delhi
provides a good example of using advertisement space for funding good BQS which
could be adopted by various cities.
(b) Non availability of adequate depot space is a major issue in various cities. It is
therefore recommended that bus agency make a strong representation to
development authorities during master plan preparation/modification to include
adequate space for depots, terminals and changeovers. A norm of about 25 buses
per acres could be considered for allocating depot space in city.
(c) In larger cities, and major bus density corridor, bus agency shall also represent for
having bus lanes for improving operational efficiency of system. A corridor carrying
more than 5000 persons per hour per direction by bus could be considered for this
purpose to start with.
(d) Most of the cities must adopt for modernization of their existing depot, adding
equipment like automatic washing facility, Leave applying Kiosk, Smart Card based
fuel pumps (for fuel management functions), biometrics for attendance and
surveillance system in depot premise.
All above recommendations are relevant for short term implementation.
6.8 Roadmap for Institutional and Contracting Framework
6.8.1 Status of Contracting Structure in City Bus Operations in India

In most of the cities, the city bus operations are done by STUs which are incurring huge
losses from operations of city buses. Few Indian cities have tried net cost contract and gross
cost contract with modifications. The status of operations and structure are summarised in
the table provided below:-
Page | 109
Table 6-7: Status of Contracting Structure in City Bus Operations in India
On the basis of the above chart, the cities are grouped into three groups as given below:

(Highly Progressive) (Moderately Progressive) (Low Progressive)
Delhi (Cluster) Bangalore Kanpur
Ahmedabad Mysore Nashik
Indore Visakhapatnam Kolkata
Bhubaneshwar Shimla
Raipur
Category A – The cities have implemented Gross Cost Contract with or without monitoring
and if Net Cost Contract is adopted, have modified to provide VGF or premium to the
Operator.
Category B – The cities that followed Net Cost Contract or operated by STU directly which
has capability to operate large fleet and have better operational efficiency.
Category C – In these cities, the city bus operations re done by STU directly that incur large
losses and does not have full capability.
Page | 110
6.8.2 Roadmap for Institutional and Contracting framework in city bus operations
Table 6-8: Policy Roadmap for Institutional and Contracting reforms in city bus operations

Existing Gap Areas
No. Parameters (Upto 2 Year) (2 – 5 year) (5 - 10 year)
 STUs focus on the inter- Category ‘A & B’ Cities Category ‘A & B’ Category ‘A, B & C’
city bus services  In terms of institutional structure, Cities Cities
neglecting the city bus formation of SPV for city bus operations  Testing of Gross  The STUs operating
operations. For contracting the operations to private cost options - the buses must shift
operations, old fleets are player through Gross cost contract is Modification of their city bus
used and quality of service preferred - the SPV to have technical staff contract type from operations through
is poor, though they have to monitor operations based on KPIs net cost to gross formation of SPV and
domain experience agreed between the both parties. Strict cost based on selection of operators
 ULBs lacks technical monitoring to be done by the SPV with market review based on Gross Cost
staff/knowledge skills in provision of bonus for better operations Contract with
bus operations and penalty against non-adherence in the KPI/Hybrid options
service contracts Category ‘C’ Cities
 With Net cost contract,
Institutional and  In case of cities with Net Cost Contract,  City bus operation
strict monitoring of service
1 Contracting improve the contract by adding KPI to the to be by Gross Cost
delivery is not done.
Reform contract and providing premium/VGF to Contract with KPI
Private operators
interested only on profit the operator on the basis of ridership and  Hiring of PMC
making routes and route length studies Consultants
neglecting large areas  Hiring of PMC consultants to assist
 Though Gross Cost Transport Department/ULBs/STUs with
Contract is the better technical support and bid process
option, strict monitoring of management
KPI is key for its success Category ‘C’ Cities
 Strengthen the technical departments
through training to all key operational and
administration staff along with
computerization
Page | 111
6.9 Policy Roadmap for Funding and Implementation of City Bus Service
Policy Roadmap recommendations for funding are as follows:-
Table 6-9: Policy Roadmap for funding

Existing Gap Areas
 Fare revisions not carried Category ‘A, B & C’ Cities Category ‘A, B & C’ Cities Category ‘A, B & C’ Cities
out regularly with direct  More aggressive outlook  Cess in the form of Green  Proximity Tax - Property tax
implication on lower fare advertisement revenue by Tax revision based on proximity
box revenues increasing adopting place based  Introducing PT cess on to public transport
ridership increasing. dynamic advertisement petrol and diesel  Employers tax – tax on
 Money spent in providing options employment
 Revenue from congestion
various concessions not  Revenue from parking charging by ULBs can be  Cross-utility financing
reimbursed charges at terminals and utilized for PT improvement
 Operations on low profit stations can be utilized for - congestion charging can
routes o PT development be imposed on heavy
/operations in city – one commercial vehicles
 ULBs rely on central
funding for bus Commercial entering the CBD during
1 Funding Options procurement due to lack of development at peak hours
terminals should be
dedicated PT fund  Funding sought from central
developed on PPP basis
 Commercial exploitation of and multi-lateral agencies -
(on lease) AMRUT and from
assets such as terminals, o Initiation of resource
BQS etc., are not JICA/WB/ADB
mobilization from
aggressively done by the CESS
STUs and ULBs.
 Cess on one time tax being
o In few cities revenue is levied on motorized vehicles
generating form the
advertisement.  Cites can integrate various
o In vehicle other revenue to city bus
advertisement is operations as under
happening in most the o If SPV is formed with
Page | 112

Existing Gap Areas
places but in the municipal corporation,
terminal area and at the Adv. Revenue, revenue
BQS few cities are from parking, terminals
generating revenue. etc., can be utilized for
 Till the date no city is improving/subsidizing
generating revenue from bus service
the parking area. o If STU is operating, Adv.
Revenue from buses
 Few STU’s are providing and commercial
rental/ lease for development at
commercial/ office spaces terminals can be utilized
in the terminal area. for bus service
 Nowhere PPP model is improvement
developed to have a real  Allow bus operator to have
estate model in the air certain routes with inter-city
space of the terminal area. operations to balance losses
from city bus operations; to
encourage private players to
participate in tender process
 Introduce priced parking
based on PTAL and
revenue generated to be
used for improvement of PT
Page | 113
7. Proposed New Tools for Improving Bus System Efficiency

7.1 Introduction
Based on the recommendations made in the earlier chapter, various tools and toolkits are
proposed in this chapter which could be developed either by the Government, an NGO, or by
any commercial start-up to enable efficiency enhancement in bus system in India. Brief
information of these proposals is included which is refered as ‘project sheets’ and provided
below. The selected areas are as follows:
i. Development of ERP based dashboard for management

ii. Vehicle and Crew optimization tool
iii. Time table preparation tool
iv. Route rationalization tool
v. Route planning tool
vi. Dead kilometer optimization tool
vii. GIS-based asset management system
viii. Updation of MIS parameters for Bus agencies
ix. Fare revision tool
x. Bus management system
xi. Toolkit / Guidelines for Route Planning
xii. Toolkit / Guidelines for Route numbering / Colour-code system
The details of each are provided in the sections below as project sheets with project ID.
7.2 Project Sheet (PS)
7.2.1 PS1: Development of ERP based dashboard for management

An Enterprise resource planning system (ERP) based dashboard for each of the
management functions shall be developed. The main functions that shall be integrated with
ERP as shown in the figure given below:-
Page | 114
The proposed ERP system will have multiple dashboards which will display the key health of
system under various functions, as follows:
Dash board for Depot Manager

The dashboard for Depot Manager shall have the various data made available as shown in
below figures. The outputs may be in the form of pie-charts, line graphs, bar charts etc.
The system may have following components for Depot manager in the Dashboard:-
Page | 115
Dashboard for Maintenance Manager
The dashboard
for Maintenance
Manager shall
have the various
outputs made
available for
performance
review of
maintenance
function as shown below in figures. The outputs may be in the form of pie-charts, line
graphs, bar charts etc.
The ERP may have the following

components associated with the dashboard:-
Page | 116
Dashboard for HR Manager
The dashboard for Human Resource

Manager shall have the following outputs
made available through ERP:-
Dashboard for finance & Accounts Team
The dashboard for F&A Manager shall have

the following outputs made available through
ERP:-
Dashboard for Traffic Manager
The dashboard for Traffic Manager shall

have the following outputs made
available through ERP. The outputs may
be in the form of pie-charts, line graphs,
bar charts etc. as shown.
Page | 117
The system may have following

components for Traffic manager in
the Dashboard
Page | 118
7.2.2 PS2: Vehicle and Crew optimisation tool

Presently duty rosters are prepared manually in most of the agencies. This could create lack
of optimization of vehicles and staff in bus agencies where large number of vehicles and
staff are handled. While there are “off the shelf” software available, these are costly, complex
and lack customization of local labour laws/condition.
It is therefore important to develop a very simple crew optimization tool which can assign
crew duties automatically within constrain of number of vehicles and labour laws (rest time,
maximum number of duty hours etc.). This tool will greatly help bus agencies in
modernization of their existing system and is depicted below.
Figure 7-1: Vehicle and crew Optimization Tool
Page | 119
7.2.3 PS3: Time Table Preparation Tool

Presently time tables are prepared manually based on the average speed of network and for
limited number of time segments due to complex number of combinations involved.
The purpose is to automate this process with an indigenously developed simple tool which
could be handled by bus agencies. Available proprietary software are very costly and very
complex for handling Indian requirement.
The proposed system will have following modules:
1) Line data preparation module: In this module section-wise/direction-wise journey

speeds of all routes will be inputted either by GPS feed or through route survey
2) Time segmentation Module: this module will define time segmentation of peak/ off-
peak/ early morning/ late night/ weekdays/ weekends/ monthly etc. This could either
be done by judgment or using historical ticketing data of ETM or ticket records.
3) Frequency calculations and vehicle requirement module: In this module, the system
will access travel time data and ticketing data for deciding bus frequency and number
of buses in order to meet travel demand and maintain minimum frequency levels
Figure 7-2: Time Table Preparation Tool
Time table module: Based on above analysis of fleet and time segmentation, this module will
generate time tables (stop-wise) for various periods and for various routes
Frequency Refinement Module: Auto generated timetables could be checked by supervisors

in this module and refinement/ revisions could be done.
Page | 120
7.2.4 PS4: Route Rationalisation Tool

There has been a need for a simple route rationalization tool for assisting bus agencies.
Presently, it is done through judgment and local
knowledge with limited data and scientific analysis
The proposed system will have following elements:
1) Integrated Route Mapping tool for services

overlap analysis: This tool will map all the
existing routes of buses, mini buses, Gramin
Sewa, metro, monorail and any other public
transport systems in the city. This will facilitate in
 Route overlaps analysis and rationalization
 Simplifying and integrating public transport system
2) Route Efficiency analysis Module: This module

will have data of route-wise/segment-wise/time-
wise ridership data and earning per Km data,
occupancy data, bunching data etc. This will
facilitate identification of efficient and inefficient
routes
3) Optional Module – Trip Desire line plotter: This

module (as optional) can assist cities to plot
passenger desire lines and assist bus agencies to
match route profile and passenger demand.
Page | 121
7.2.5 PS5: Route Planning Tool

Most cities lack route planning tools which analyse public transport demand and accessibility
of public transport on a city level. Route planning can be done using transport planning
software’s such as VISUM, CUBE, EMME etc., however these can be too complicated for
bus agencies lacking specialised personnel. It is therefore recommended that a simple
solution be developed on which the city transport network can be plotted and information can
be superimposed to determine the need for new routes through Passenger desires lines,
Trip generation nodes, Passenger accumulation (based on shortest paths) on routes and
accessible/inaccessible areas of public transport based on isochrones.
The proposed system will have following elements, as depicted in the schematic below:
1) Network Module: This module holds details of transport network and major economic
nodes
2) Demand Module: This module will hold data on transport demand
3) Analysis Module: which analyses data to determine the demand area, services deficit
area and potential new routes
Figure 7-3: Route planning tool
Page | 122
7.2.6 PS6: Dead Kilometre Optimisation Tool

At present, allocation of routes to depot is done purely on the basis of judgment. No analysis
of dead-km is done to determine optimum solution of route allocation of buses to depot or
identification of suitable depot space with respect to route network. The proposed tool will
help cities determine optimum depot locations or route allocation if depots already exist in
city.
Development of this tool will require an operation research based optimization algorithm
which can calculate dead–km on assigning various bus routes to various depots or locating
various depots at various places with reference to the bus routes structure.
7.2.7 PS7: GIS based Asset Management System

Bus agencies hold several assets such as bus queue shelters, PIS boards, stop sign boards,
advertisement panels, land for depot, terminals etc. However record of these assets is kept
by manual method which is not the best system for asset management.
We recommend that
agencies develop a GIS
based asset management
tool which will house
information on:-
 Location of asset
 Type of asset
 Conditions and life
of asset
 Other details
This tool will help in
maintaining proper records
of assets as well as
developing up-gradation/
replacement plans for their
asset for each agency
Figure 7-4: Bus management system web page
Page | 123
Figure 7-5: example of GIS based assets management system- Location assets
Page | 124
7.2.8 PS8: Updation of MIS Parameters for Bus Agencies

The MIS systems adopted by many cities are old and not much work has been done to
upgrade it periodically or making it dynamic to suit the changing needs of organisations.
Some of the issues in the existing MIS systems are:
 It captures operators efficiency parameters but does not capture public services
delivery parameters such as crowding, wait times, accessibility etc.
 Rapid changes observed in last few years through use of technology (such as GPS,
ETM etc.,); various indicators could be analysed at more disaggregated level for
decision making.
 There is need to add certain new parameters and remove certain redundant
parameters for modernization of MIS system as per present needs.
7.2.9 PS9: Fare Revision tool

There is a need for developing a standard tool for fare revisions which takes into account;
capital cost, operation cost and increase in key inputs on a regular (ex – yearly) basis.
The tool will be based on mathematical procedures in which the user can input key
parameters and get fare revision every year. This tool will help agencies to scientifically
represent need for periodic revision of bus fare taking into account of various relevant
parameters in transparent manner.
7.2.10 PS10: Bus Management System

(Performance monitoring tool of contracting)
Many cities are moving towards adopting gross cost contract where concessionaire payment
is made based on agreed key performance indicators. Currently, except DIMTS, most of
agencies do it based on manual/ semi-automatic methods which are not efficient enough
and not sustainable with increasing operations.
Thus, there is need to develop a standard tool which could monitors “key performance
indicators” based on data collected by GPS/ETM/MIS system of bus agency and make
recommendations of
 Concessionaire payment
 Penalties (with details of deviation)
 Bonuses (with areas of good performance)
 Comparison of concessionaire performance.
Page | 125
Figure 7-6: Bus management system web page
7.2.11 PS11: Toolkit / Guidelines for Bus Route Planning

Present bus route planning is done mainly based on local knowledge and judgements by bus
agencies. Due to the lack of any guidance in this area, most of the agencies rely on
knowledge of staff to deliver these functions.
Therefore, it is recommended that a toolkit of route planning be created which can provide
various methods of route planning considering various levels of data analysis. This toolkit on
one hand shall recommend “Rapid Assessment technique” while on other hand it can also
provide detail methods driven by large data & modern software.
Figure 7-7: Bus fleet route planning software
Page | 126
Figure 7-8: New Jersey Transit Bus route planning
Page | 127
7.2.12 PS12: Toolkit / Guidelines for Route numbering / Colour-code system

Bus route numbering systems in most of the cities are developed on an ad-hoc basis. In the
small cities with limited service, it does not make much difference; however in medium to
large cities, a logical route numbering systems and differential colour code of services would
help users to differentiate various routes and improve user’s convenience.
It is therefore recommended that a toolkit could be developed in which various principles of

route numbering / colour system could be explained. This toolkit will be helpful for cities to
reorganize bus numbering and colouring system.
Figure 7-9: Example of Route colour coding system – Maryland, U.S.A.
Figure 7-10: Example of Route numbering - Downtown Salt Lake map
Page | 128
8. Conclusions and Way Forward

Various cities in India were grouped into categories based on city characteristics, viz.,
population, geographical location, multimodal availability and characteristics of city bus
system, viz., city bus fleet size, progressiveness of the bus transport system in order to
carry out baseline analysis of the urban bus system of the cities.
A total of 12 representative cities – namely Ahmedabad, Bangalore, Bhubaneshwar, Delhi,

Indore, Kanpur, Kolkata, Mysore, Nashik, Raipur, Shimla, Vishakhapatnam – were selected
for city level data collection to study the organizational processes and prevailing practices.
The data collected and the findings from these cities on existing processes are provided in
the report.
The study observed the following:
a) Ahmedabad, Bangalore, Delhi (cluster system), Indore, Mysore and Vishakhapatnam

have elements of progressive approach in operations management and public
service delivery.
b) Rest of the cities, viz., Bhubaneshwar, Delhi (STU), Kanpur, Kolkata, Nashik, Raipur
and Shimla follow traditional and suboptimal processes in operations management
and public service delivery.
The areas of deficit in existing systems have been identified and compared with examples
from other countries, where large scale reforms in road based public transport systems
have been implemented, in order to formulate benchmarks for each area.
Both national and international practices have been studied to present best cases for
various functions to optimize bus planning, operations and management system.
Further, based on discussions with stakeholders, a detailed activity wise Roadmap (short
term, medium term and long term) has been prepared for adoption and implementation of
best practices in respective cities.
The summary of findings/activities is listed below:-
1) Route Planning and Rationalization is being done using local knowledge,

requirements and judgment. This process needs to be strengthened by incorporating
scientific data and simple tools to assist bus agencies in scientific planning.
2) Timetabling and schedule adjustments are manually done in most cities using
parameters like flat average journey speed, both in peak and non-peak hours, and
average route EPK which result in suboptimal and inefficient operations. A simple
timetabling tool has been proposed to be developed for Indian conditions to offset the
high cost and complexity of available international software.
3) Several cities have computerized some of their functions, although in an isolated
manner. A serious need has been observed to develop an Integrated Enterprise
Resource Planning (ERP) at the organizational level to improve efficiency and to build
an integrated data source. The proposed ERP system will have various modules such
Page | 129
as Operations, Maintenance, Accounts & Payments, HR etc., with multiple dashboards

for each organizational unit to monitor performance of their operations. This is explained
in detail in the project sheet section.
4) The existing MIS system is outdated and requires major upgrades. In current times
when data is being made available from GPS/ETM on a disaggregated level, these MIS
systems require an overhaul to incorporate new data yielded by GPS/ETM. The existing
MIS system also needs to be reviewed on performance monitoring parameters which
are primarily designed from the operator’s perspective and completely ignores the user
perspective. The modernization of MIS system has been proposed as part of
recommendations and detailed in the project sheet section.
5) On the technology front, a Roadmap has been presented in the report. Most cities have
GPS & ETM capabilities (or are in the process of procuring them). The first challenge
is to adapt these systems to existing operations and then look for second generation
technological reforms. There is a need to develop simple optimization/data analytics
tools and connect all this information to the proposed ERP module so that all data
collected from GPS/ETM applications can be used for operations/monitoring of systems.
6) Agencies can collect useful data using crowd sourcing by adding option to user to
suggest routes and other elements at their website/mobile app. This data will be
valuable for planning new routes and making adjustments to existing routes, to provide
demand responsive and dependable service to passengers while reducing travel
time/cost in comparison to private modes.
7) Some agencies could also consider adding modern devices such as Automatic
Washing, Leave Kiosks, Smart Card enabled fuel pumps, Biometrics based attendance
and Depot surveillance system which will help them improve efficiency.
8) Review of institutional arrangement indicates that city bus operations are run by
STUs, municipal corporations or SPVs. In case of STU run operation, except some
cases (BMTC, Mysore), largely it is observed that STUs pay less attention to city
operation as their main focus is on intercity operations, although STUs are the most
experienced in handling operations. Municipal corporations have inadequate capacity to
run bus services and consequently experience challenges. SPVs mainly work on an
outsourced model and are able to manage operation though they also face challenges
due to lack of experience of this sector. In terms of contracting options, gross cost, net
cost and some form of hybrid options have been observed for managing bus operations.
The advantages/disadvantages and experiences of bus agencies and operators has
been recorded to recommend suitable option on above areas. Based on various
analysis and interviews, it has been found that SPV run bus service with gross cost
contracting (strongly driven by KPI) is the preferred mode. However, in the present form
it will require some moderations as suggested below:
a. SPVs require capacity building by imparting training to staff with sector
knowledge. At the very least a Public Transport Planner, Bus operations and
monitoring expert and ITS expert should be inducted for dynamic planning and
monitoring functions.
Page | 130
b. In Gross Cost model, KPI shall link incentives for operators for passenger
carried so that the crew is more attentive toward public service delivery and
enhances the level of service of the public transport system
9) While many of bus agencies planning to adopt gross cost in the future, many others
are likely to continue to with existing Net Cost system. In such case, more emphasis is
needed on KPI-based monitoring and introduction of cross subsidization model for rural/
unviable routes for operators. Indore presents a very interesting example under this
model. In all cases capacity building of staff is key issue which shall be resolved by
setting up technical PMU ( preferably through PPP route) by which bus agency can
have access to specialized manpower for enhancing their bus operations, adopting new
software’s and techniques and installation of new technologies.
10) Funding is major issue for most bus companies, as bus operation is not self-sustained,
if considered for providing good service to cities as several of routes in less populated
areas and off peak hours run with low occupancies. Consultants view is that following
options could be considered by cities:
a. A public transport cess could be considered on diesel/petrol which can fund public
transport subsidy.
b. Revenue from advertisement and parking should be utilized for filling this gap
c. In certain cases, revenue from developing commercial spaces at terminal &
depots could be considered.
d. In some states, premium collected from intercity operations on long routes can be
used to subsidize city bus service. This model is successfully working in Indore
city.
11) A tool for standardization of fare revision mechanism has been suggested to facilitate
automatic revision of bus fares (upward/downward) based on key input parameters in
transparent manner as being done by government for petrol/diesel prices.
12) There are several other suggestions made to modernize bus system by adopting
modern practices of route numbering and bus colouring which could be considered by
cities
8.1 Way Forward

The roadmap recommendations and their actions plans are to be taken up by various
stakeholders in implementing and the responsibilities with stakeholders/institutions are as
provided in the table below:
Table 8-1: Action Plan and Stakeholder Responsibilities
Sl. Area of
No. Intervention
Periodic Amendment of PT Policy
Strategic  MoUD
guidelines based on requirements
1 Transport
Development of PT Master Plan /
Planning  ULBs / City Government
CMP
Page | 131
Sl. Area of
No. Intervention
Development of model document for
 MoUD / MoRTH
Technology Bus Modernisation Plan
2
Interventions Implementation of GPS, ETMs,
 STUs / SPVs / ULBs
CCTVs, PIS etc.
Development of Toolkit for process
 MoUD / MoRTH
modernization
Awareness campaigns on the policy
Improving roadmap recommendations with STUs  NGOs and Think-Tanks
3 Operational and SPVs
Process  NGOs in collaboration
Training and Workshop sessions with ASRTU / IIT / SPA /
CIRT / CEPT
Conducting Route Planning and route
 ULBs / STA
rationalization studies
Institutional and Review of existing HR Policy  Amendment by respective
State Governments
4 Contracting
Development and implementation of
Framework  By CIRT / ASRTU
Training Modules
Development of PT funding policy
 MoUD / MoRTH
Funding guidelines
5
Options Fare Revision Mechanisms and
 State Government
dedicated fund for PT
It is also evident that all the recommendations would have to be implemented by respective
STUs and SPVs while other stakeholders provide a supportive role. The responsibility rests
with the STU/SPV to improve the city bus system for users as well as for the agency in terms
of operational and financial efficiency with the policy roadmap.
Page | 132
Ani
nit
iat
ivesuppor
tedby:
ShaktiSust
ainabl
eEnergyFoundati
on
TheCapit
alCourt(
4thFl
oor)
Muni
rkaPhaseII
I,NewDel
hi110067,I
ndi
a
Pr
ojectConsul
tant
:
Del
hiInt
ergratedMulti-ModalTr ansi
tSyst em Li
mi ted
Fir
stFl
oor,ISBT,Kashmer eGate,Delhi-110006,India
Ph:011-43090100 Fax:(011)23860966
Websi
te:htt
p:/
/www.dimts.
in/
,mailusat:inf
o@dimt s.i
n

288 40521 Tender Documents

Uploaded by

Copyright:

288 40521 Tender Documents

Uploaded by

Document Information

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

288 40521 Tender Documents

Uploaded by

Copyright:

Final Report Roadmap for improving City Bus Systems in India

About Shakti Sustainable Energy Foundation:

*For Private circulation only

Warm regards from the study team.

6.6 ROADMAP FOR IMPROVING THE OPERATIONAL PROCESS ................................................. 98

EWT Excess Waiting Time

PA Public Address System

Out of these 10 groups, a total of 12 representative cities – namely Delhi, Ahmedabad,

Table 0-1: Summary of Operational and financial performance of STUs

1) Gaps in strategic transport planning:

 Money spent in providing concessions to various sections of users is not reimbursed

1) Roadmap for Strategic Transport Planning

3) Roadmap for improving the operational process

e) Stores and Purchase

4) Roadmap for Improving Bus Transport Infrastructure

5) Roadmap for Institutional and Contracting Framework

6) Roadmap for Funding Options

 Development of ERP based dashboard for management,

Table 0-2: Action Plan and Stakeholder Responsibilities

Urban Bus Transport System City Bus Operator

• Traditional methods of bus operations, •Outdated / inadquate depot infrastructure

1.2 Need for the project

1.3 Study Approach & Methodology

Figure 1-1: Study Approach & Methodology Chart

2. City Selection and Data Collection Process

2.2 City Selection Process

Figure 2-1: Parameters for City Selection

Out of 10 feasible groups of cities identified, 12 cities representing various characteristics

Figure 2-2: Selected Cities for Comprehensive Study

2.3 Data Collection Approach

Table 2-1: Departments and officials of STUs and SPVs contacted

State Transport Undertaking (STU)/ Key officials and departments

2.4 Formation of Expert Review Committee (ERC)

3. City Report Card

3.2 Practices Reviewed

Figure 3-1: Practices Reviewed within City Bus Operator

3.3 City-wise Bus Operational Characteristics

 The fleet size

Figure 3-2: City-wise route details

 With respect to vehicle utilisation as shown in Figure 3-3, it is observed that

Figure 3-3: City-wise Vehicle Utilisation

A study of the financial statistics of the cities indicates the following:

Figure 3-4: City-wise EPK, CPK and Operating ratio

The contracting model of each city has different model:

Table 3-1: City STUs and Private Operators

City Authority / SPV / Public Operator Private Operator Model

Bangalore Bangalore Metropolitan Road Transport Corporation (STU) - -

Delhi Delhi Transport Corporation (STU) - -

Kanpur Kanpur City Transport Services Limited (SPV) - -

City Authority / SPV / Public Operator Private Operator Model

Calcutta State Transport Corporation

Mysore Karnataka State Road Transport Corporation (STU) - -

Nashik Maharashtra State Road Transport Corporation (STU) - -

Shimla Himachal Road Transport Corporation (STU) - -

Visakhapatnam Andhra State Road Transport Corporation (STU) - -

3.4 City-wise Report Cards

3.4.1 City Report Card - Ahmedabad

Route Planning - Traditional method of route planning Moderate

Surveillance - AJL: CCTV cameras are installed in 22 buses.

3.4.2 City Report Card - Bangalore

- Rationalization/ simplification of routes has been done scientifically

- Bus & Crew Scheduling Management is done manually.

- BMTC plans to utilize detailed data analytics for optimization of

3.4.3 City Report Card - Bhubaneshwar