Madhav Pai

EMBARQ India

Bussing Bangalore:

From

Performance Management

to Improved Operations

Bangalore

Performance Indicators

Modal Shift

Mode Shift After Introduction of Big10

Private car

1%

Private 2-

wheeler

9%

Auto

3%

Regular Bus

87%

Boarding & Alighting: Route G2

Avg. Passenger Load - Route G2 - Both Directions

0

4

8

12

16

20

24

28

32

Brigad

e Roa

d Jn

.

Johnso

n Mar

ket

Anepalya

Adugodi

Adugodi P

olice

Qrts

Checkp

ost (

Foru

m)

St.Jo

hn's H

ospital

Madi

wal

a

Rupena

Agrah

ara

Bomm

anaha

lli

Garve

bhavi P

alya

Koodlu

Gat

e

Sing

asan

dra

Hosa R

aod

Konapp

ana

Agrah

ara

Info

sysC

ross

Info

sys

Parki

ng L

ot

BHEL C

ircle

Wip

ro G

ate

Bus Stop

Pas

sen

ger

s

Avera ge Boarding Average Al ighting

Bus Occupancy Variation: G2

Arrival Patterns: Route G9

Bus Arrivals @ Mekhri Circle - Route G9 - Towards CBD

6:00 AM

9:00 AM

12:00 PM

3:00 PM

6:00 PM

9:00 PM

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39

Bus Sequence

Arr

ival T

ime

0

60

120

180

240

300

Spre

ad

(m

inu

tes)

25/Oct/10 26/Oct/10 27/Oct/10 Sprea d

Travel Times

G1 G2 G6 G9

Total Trips Analysed 382 766 117 317

Avg. Time 60 60 65 54

Std. Deviation 9 10 12 9

< 50 min 54 119 7 127

50 - 60 min 165 305 37 123

60 - 70 min 108 212 43 44

70 - 80 min 51 110 17 23

> 80 min 4 20 13 0

Conclusions

Mode shift to BiG10 services: 12% (9% 2w, 1% Cars, 2% Auto)

Index Passenger KM (IPK): Passengers per bus km for all routes >= 4.0 indicates all routes are performing well.

Pass usage: high >50% on all four routes (55% for G2 & 63% for G6)

Trip Lengths: 40% of trips < 6km, Average ticket price 8-9 Rs.,

Pass trip length < Ticketed trip length

Boarding and alighting: Off-peak passenger loads are much lower than supply.

Arrival Patterns: Increasing buses on G2 will not result in increased passenger throughput.

will result in bunching

currently buses are not running full even during peak periods

Recommendations

More Data for Analysis

Rationalizing Services – Reduce down from 174 routes

Shorter Routes - For OD pairs with high demand

Buses for specfically for Peak Hour Trips

Crew Scheduling - To create spilt schedules to allow only peak

hour operations

Interchange Terminals

Periodic Data Collection – Using Staff

Service Planning – Route Rationalization

Crew Scheduling – Case Study SI99: Transmilenio Operator

Designing Terminals

Bussing Bangalore: Further Initiatives with BMTC

Current Operations Plan

1.Route Redundancy

2.Unmet demand for alternate

services

3.Poor Service During Peak

Hours

4.Poor Transfer Facilities

5.Lack of Reliability

165,000 Pax per Day

Existing System:

172 Routes

KBS

Existing System –

Point to Point

Integrated Network –

Hybrid: Trunk-and-Feeder +

Direct

Images: Nielsen, G. “Public Transport Network

Design”

Data Overview: OD Data

80%

KBS/KR 3 North G-3 South

G-3

KBS/KR South

Buses required – 289

KR

Market

KBS Brigade

Road

Legend

KR – 3: 32 kms

KBS – 3: 35 kms

KR – 3 – North:

KBS – 3 - North

3 - South

G – 3:

G – 3 – South

KBS – 3 – EC

Trunk Routes

Electronics

City

Attibele

Silk

Board

Feeders

Proposed feeders (#): 11

Network length: 89.6 km*

Proposed System:

89 Routes

8 Trunk

34 Feeder

47 Maintained

KBS

Field Data Collection

1 Day per arterial. 1 Arterial per month.

3 Types of Data CollectionBoarding & Alighting SurveyBus Occupancy SurveyPassenger Interviews

Each Survey 16 Hours of Data2 Shifts – 6 am to 2 pm & 2 pm to 10 pm

Total Team SizeBoarding & Alighting: 8Bus Occupancy: 16Passenger OD and Opinion: 6

Field Data Collection

Crew Scheduling – Case Study SI99, Bogota

0%

5%

10%

15%

20%

25%

30%

35%

40%

45%

Less than 40

hours Beetween 40 and

48 hours More that 12

hours

35%

42%

23%

Transmilenio Operator

Fleet – 130 buses

Only 25% of the drivers living near to where they start or end their work

35% of cases time for rest was driving a bus, going from one terminal to another

30% of cases time for rest was longer than three hours

Crew Scheduling – Case Study SI99, Bogota

Built linear programming

tools using “lingo” to

automate crew allocations – Lingo had limitation 15-

20 buses.

Eventually convinced

management to buy

commercial software “Goal Bus” – 1,500 USD

per year per bus.

USD 4 Million Savings

annually

0.0%

5.0%

10.0%

15.0%

20.0%

20

00

20

01

20

02

20

03

20

04

20

05

20

06

20

07

20

08

20

09

Estimated vs. Real Crew Costs

Crew Scheduling – Exercise for Bangalore

Two starting points - One at Brigade Road and one at

Electronic City.

Proposed frequencies -

28 Buses, 6991 kms, 384:43:15 hours of operation

From To Frecuency

06:25:00 07:40:00 00:08:00

07:40:00 18:40:00 00:05:00

18:40:00 22:45:00 00:08:00

Average St Dev Average St Dev H in Operation H Contracted Cost/day

48H Contracts 30 09:52:46 00:54:06 08:08:39 00:31:57

36H Contracs 26 05:47:35 00:22:12 05:47:35 00:22:12

Total 56 Driver/bus 1.77

48H Contracts 48 08:38:38 00:45:10 07:23:43 00:20:43

36H Contracs 6 05:55:45 00:14:50 05:55:45 00:14:50

Total 54 Driver/bus 1.88

420:00:00 1,138.30$

DriversSpread Steering

With BO

Without BO

394:56:45 396:00:00 1,145.39$

390:33:15

Terminal Design – Silk Board Junction

Terminal Design – Silk Board Junction

BUS KARO

Developing Concept for “Bus Karo: A Guidebook on Bus

Planning and Operations”

3 International Case Studies: London, Sao Paulo, Seoul

4 Indian Case Studies: Ahmedabad, Bangalore, Indore,

Mumbai

7 Common Factors for Good Bus Systems:

Planning, Support Infrastructure, Vehicles,

Technology, Contracting, Financial Analysis,

Monitoring and Evaluation

Peer Review: ITDP, C-STEP, CiSTUP

Bus Karo – Development and Writing

6 Workshops using Bus Karo

• April 2010 – Delhi

• January 2011 – Mumbai

• April 2011 – Goa

• May 2011 - Bangalore

• September 2011 – Bangalore

• Feb 2011 – Bangalore

150 Officials directly trained

35 cities

Bus Karo used for postgraduate training (CEPT, IIT-B, SPA, NIT Surat)

Bus Karo – Workshops

Built Capacity within BMTC around Big10 Performance

Analysis

Trained 50+ staff in techniques of data collection, service

monitoring and evaluation

• Survey Techniques

• Passenger Feedback Techniques

• Data Analysis

Trained staff currently being used to study and implement

BMTC initiatives (Bus Priority Lanes)

Deep Engagement with Bangalore: Better Monitoring for Better Service

Pillars of the Program

• Talking Transit – Workshop Series

• Learning Transit – Peer-to-Peer Learning

• Mentoring Transit – Implementing Pilot Projects

Cities of work - Bhubaneshwar, Delhi (Star Bus), Chennai,

Gulbarga, Hubli-Dharwad, Indore, Jaipur, Mysore,

Mumbai, Vishakapatnam

4th Pillar – Safe Transit – To be added soon

Bus Karo Plus

Delhi

Mumbai

Ahmedabad

SuratRajkot

Indore

Naya Raipur

Hubli - Dharwad

Bangalore

Jaipur

Cities of Work

Mysore

Bhubaneshwar

Vishakapattanam

Gulbarga

Chennai

Audited sections

Inspected sections

Ahmedabad BRT road safety audit: Study area

Ahmedabad BRT road safety audit: Pedestrian crossing

Ahmedabad BRT road safety audit: Pedestrian crossing

Ahmedabad BRT road safety audit: Pedestrian crossing

Ahmedabad BRT road safety audit: Pedestrian refuges

Ahmedabad BRT road safety audit: Lane marking

Ahmedabad BRT road safety audit: U turns

Thank You!