ITS and MIS for Middle Managers

This document contains the following 6 deliverables

1. Delivery Presentation

2. Trainer Manual

3. Participant Manual

4. Pre-Training Questionnaire

5. Post-Training Questionnaire

6. Group Activity

ITS and MIS for Middle Managers

P resentation title[To edit, c lick View > Slide Master > Slide Master]

©2019 Deloitte Shared Services India LLP 1

Delivery Presentation

EFFICIENT AND SUSTAINABLE CITY BUS SERVICES PROJECT (INDIA)EFFICIENT AND SUSTAINABLE CITY BUS SERVICES PROJECT (INDIA)

ITS AND MIS FOR MIDDLE MANAGERS

MINISTRY OF HOUSING AND URBAN AFFAIRS, GOVERNMENT OF INDIA

Consultancy Services for Design and Development of Training Programme for City Transport Professionals

December 2020

2

Preface

The Efficient and Sustainable City Bus Services (ESCBS) project was introduced to improve the efficiency and attractiveness of city bus

transport in India. ESCBS project has three major components, which includes, National Capacity Building (NCB); Regulatory, Institutional

and Fiscal Analysis; and City Demonstration. This engagement falls under the purview of the NCB component of the ESCBS project. The

objective of this engagement is to design and develop training programme for city transport professionals, and involves undertaking pilot

testing, implementation, evaluation, and suitable modification of the training programme.

As a part of this engagement, eight training areas have been identified and prioritized by the Ministry of Housing and Urban Affairs

(MoHUA).

Policy Advocacy for

Senior Managers

Outsourcing for Senior

Managers

Monitoring and

Evaluation for Senior

Managers

Network Planning for

Middle Managers

Operations Planning for

Middle Managers

Outsourcing for Middle

Managers

Bus Operations for

Middle Managers

ITS and MIS for Middle

Managers

1 2 3 4

5 6 7 8

For each training area, a total of three modules have been prepared:

A. Participant’s Notes: Detailed reference notes containing links to more readings to be circulated before trainings.

B. Trainer’s Notes: Detailed notes for trainer’s reference containing focus points, questions for discussion, etc.

C. Delivery PPT: Brief presentation containing infographics, videos, group activities, etc. to be displayed on screen.

3

This training material on “ITS and MIS” provides guidance on Information Technology, Intelligent Transport Systems &

Management Information Systems, and the relationship amongst them; insight into ITS design (technology, platform, data

requirement & allied support) and role of non-ITS in ITS. This also covers ITS applications in 07 sub modules viz. fleet

management, ticketing management, passenger information system (PIS), maintenance management system & fueling

management, inventory management, and manpower management. The module also provides lessons learned from cities

and best practices for better understanding.

These ITS & MIS will aid commuters in getting real-time information of buses and make cashless transactions while for

operators it helps in identifying passenger demand, easy cash transaction & revenue reconciliation, optimum utilization of

fleet & manpower, effective planning preventive maintenance, shift and duty allocation of staff, inventory management, and

meeting the growing demands of passengers. Further, this module will help in gathering information for performance

monitoring.

About the Module

4

Learning Objectives

ITS use in PT System is mainly directed to fulfil the needs of stakeholders, namely the

Authority/Government, users, service providers, and the society.

• Access to accurate information helps in taking faster and quicker decisions.

• ITS enables authority to make public transport more intelligent.

• Monitor compliance with the obligations set out in the concession agreement, revenue & cost account and is a useful

business intelligence tool.

• Extended use of ITS enhances the capability of management of Traffic & Transport System.

Authority/Government:

• ITS makes public transport more attractive and a convenient option for travel.

• Improving real time data generation and Travel Advisory Systems (TAS).

• Efficient, easy to understand and responsive data compilation, analysis and communication system based MIS, mainly

wrt users.

• ITS offers users with multiple fare transaction options such as mobile, card, and wallet and aids in making quick and

transparent transactions.

User related ITS and MIS objectives to target:

5

Learning Objectives



• Enhanced managerial control with minimum effort.

• ITS enables service providers to track & take faster decisions resulting in improved on-time operations and compliance of

agreement.

• In the event of an alert/emergency, ITS offers a holistic view and facilitates decision makers in normalizing the situation.

Service provider:

• In the city, mobility being the key need, ITS puts forth bus transport as a smarter mobility option before the society.

• Travel requirements of the society can be better addressed by using ITS.

• ITS ensures compliance of public transport services offered to the society.

Society:

6

Table of Contents

Introduction

A. Defining IT, ITS and MIS

B. Overview of ITS

C. Objectives of ITS and MIS

D. Why ITS is required (Commuter, Operator and Authority’s perspective)

E. Relation between IT, ITS and MIS

F. Attributes of productive output information

G. Management Information Systems: A tool

H. Overview of ITS and MIS Technology Framework

I. Benefits of ITS and MIS (Operator, Commuter, and Authority)

J. City Bus Transport using ITS

K. Limitations and Cautions of ITS Technology

L. Systematic Implementation ITS Program

M. ITS technology and platform

N. ITS allied support

O. Support required for ITS

P. Case study: Mysore

1

7

Table of Contents

Automatic Fare

Collection System

A. ITS technology and architecture

B. Electronic ticketing machine

C. Smart cards

D. Open loop vs Closed loop card

E. Smart cards - PMPML

F. Case study: Surat

G. Digital wallets and E-wallets

H. Case study: APSRTC

I. Case study: Surat

J. Revenue reconciliation

3

Fleet Management

Systems

A. Overview

B. ITS technology

C. ITS architecture

D. Case study: Mysore

E. Case study: Surat

F. Events: expo, fairs and festivals

G. Case study: PMPML

H. Case study: Surat

I. Driver console with Vehicle Health Monitoring System

J. ITS in Management of Incident

K. Application of ITS in Operations Management

L. Case study: APSRTC

2

8

Table of Contents

ITS Project in MysoreA. Project outcomes

B. Lessons learned5

Key ConsiderationsA. Guidelines for ITS and MIS implementation

B. Key takeaways6

Passenger Information

Systems

A. Insight into Passenger Information System (PIS)

B. ITS technology

C. ITS architecture


E. Case study: NMMT

F. Case study: DIMTS

G. Case study: Sitilink Surat

H. Application of PIS: BMTC Video

4

9

Introduction

Defining IT, ITS and MIS

Q1. What is IT, ITS, and MIS?

Q2. How does ITS help?

Q3. How will MIS help?

Q4. What must middle managers know before going for ITS?

1. Introduction

2. Fleet Management Systems

3. Automatic Fare Collection System

4. Passenger Information Systems

5. ITS Project in Mysore

6. Key Considerations

Defining IT, ITS and MISA

Overview of ITS and MISB

Objectives of ITS and MISC

Why ITS is required?D

Relation between IT, ITS and MISE

Productive output informationF

MIS: A toolG

ITS and MIS Technology FrameworkH

Benefits of ITS and MISI

City Bus Transport using ITSJ

Limitations and Cautions of ITSK

Systematic ImplementationL

ITS technology and platformM

ITS allied supportN

Support required for ITSO

Case Study - MysoreP

10

Introduction

ITS and MIS Manual

Ministry of Housing and Urban Affairs (MoHUA) has developed a manual for Planning,

Designing, Implementing and Evaluating ITS and MIS Projects for Urban Bus Systems.

Analysis of international best practices and

professional literature devoted to ITS and MIS.

Detailed learnings, challenges faced in

implementing ITS and the benefits realized after the adoption of ITS/MIS form the Mysuru Bengaluru,

Indore, Pune etc. included.

Manual contains guidance, cautions, examples of ITS / MIS projects based on the

best experience in India and elsewhere.

Detailed guidance on preparing ConOps, FRS,

Defining Technical Solution, Identification of Business Model, Cost Estimates and Selection of SI included.

Sample User Requirements, Functional Requirements, Formats and Templates, Model RFP and Guidance

Notes are also incorporated.

Complete framework provided for ITS and MIS

solutions that can be implemented effectively and efficient in timely manner for

smooth Bus Operations.

The focus is given on assessing needs for

ITS/MIS, set up the goals and objectives for the

system and review existing business processes ahead of developing what ITS and/ or

MIS will do.

Salient Features of the Manual

Emphasis is given on need and perspective of ITS for

Commuter, Operator and PT Agency.

For detailed information refer to Manual for Planning, Designing, Implementing and Evaluating ITS and MIS Projects for Urban Bus System on MoHUA’s website.

1. Introduction












MIS: A toolG







ITS allied supportN



11

Introduction

Overview of ITS THIS is being

considered

1. Introduction












MIS: A toolG







ITS allied supportN



12

Introduction

Objectives of ITS and MIS

Eff icient EconomicalReliable

OPERATOR

SafeInformation Accessible Convenient

PassengersPASSENGER

Access Timely & Directly Decision making

AUTHORITY

ENHANCING THE PUBLIC TRANSPORT EXPERIENCE

1. Introduction












MIS: A toolG







ITS allied supportN



13

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

Why ITS is required – Commuters’ perspective

When is the bus going to

come???


come???

Which bus should I take to reach my destination???


When should I reach the bus stop to

take my bus??


take my bus??

Is the next stop my

destination?

Is the next stop my

destination?

Automatic Fare Collection, Integrated fare payment options

available ???


available ???

14

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

Why ITS is required – Operator’s perspective

Where are the buses??Where are

the buses??

Have any of the buses missed

any stops?


any stops?

Is any of the bus over-speeding?

Has there been any accident?



Are all the buses operating as per

schedule?

Are there any breakdowns?


schedule?


How the route is performing w.r.t revenue,

ridership etc., ?


ridership etc., ?

15

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

Why ITS is required – Authority’s perspective

Ensure operator will achieve optimum

utilization of resources – buses, drivers &

conductors



conductors

How to monitor compliance

obligations set out in the concession

agreement, revenue & cost account etc




Base for Monitoring & Evaluation of PT and need for intervention

(if any)


(if any)

Are Passengers being charged legal

fare and is the transaction - fair &

transparent.



transparent.

How to make sure commuters are getting to real-time info. such as fare ETA/ETD, next

bus stop etc.,


bus stop etc.,

For seamless travel how to integrate - 1) services

2) fare payment options between multiple operator/ different modes of transport.



16

Introduction

Benefits of ITS and MIS: Case study of Mysore

1. Introduction












MIS: A toolG







ITS allied supportN



17

Data Processing & Storage

Generation of Input Data

Output Information

Generation

IT

ITS

Management Information System

Introduction

Relation: Between IT, ITS and MIS

1. Introduction












MIS: A toolG







ITS allied supportN



18

Introduction

Relation: Generation of input data

Storing of raw data in Database Server/concern server

ITS Server

Technical systems & hardware required for ITS application:

• Automatic vehicle location

• Electronic fare collection

• Driver’s console incl. driver monitoring, vehicle health monitoring

• in-vehicle data hub & processor

• Surveillance equipment

• PIS, communication, etc. for generation & transfer of raw data

ITS Technologies

1. Introduction












MIS: A toolG







ITS allied supportN



19

Introduction

Relation: Data input, Processing and Output information including MIS

Example

Input Data

• Tracking of bus• Revenue earning• Fuel consumption

01

ITS Server, Data collection, storage &

processing

• Processing of data usingmathematical,statistical, GIS andother application tools

• Storage of processedinformation

02

Output Information incl. MIS

• Real-time Information to the passengers

• Driver monitoring • Earning per kms

03

1. Introduction












MIS: A toolG







ITS allied supportN



20

Introduction

Attributes of productive output information

Determine

usefulness of

output information

Quality

Completeness

Relevance Timely

1. Introduction












MIS: A toolG







ITS allied supportN



21

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

Management Information System: A Tool

Operational Performance Indicators

Capacity

•Fleet Size

•Buses on-Road

•Buses of f -Road

•Bus Utilization per

day

•Staf f ratio per bus

Serviceability

• Scheduled kms v s

Ef f ective kms

• Ef f ective kms vs

cancelled kms

• Total Passenger

kms

• Load f actor per bus

/ per route

• Passengers carried

per bus per day

Reliability

• Trips scheduled v s

Trips cancelled

• Regularity and

punctuality

• Adherence to

operational

discipline (rash

driv ing, stops

skipping, route

dev iations, crew

behav iour)

• Breakdowns

recorded f or ev ery

10,000 kms

Safety

• Accidents recorded

per 100,000 kms

• Number of f atal

accidents recorded

• Number of non f atal

accidents recorded

• Number of

complaints receiv ed

f rom passengers on

crew behav iour,

rash driv ing, stops

skipping, route

dev iations

Financial Performance Indicators

For detailed information refer: 1. World Bank: Hand book on Passenger Transport ITS toolkit2. SUTP report: Manual for Planning, Designing, Implementing and Evaluating ITS and MIS Projects

Notes for Trainer

Elaborate the above point

Operational Cost

• Personnel Cost

• Material Cost

• Operating Cost Per Effective Kilometer (CPKM)

Revenue

• Traffic Revenue

• Non-Traffic Revenue

• Subsidy re-imbursement

• Fare concessions re-imbursement

• Total earnings per bus per day or per km

Performance Ratios

• Total Cost per bus per day (on road)

• Percentage return on capital invested

• Schedules earning more than total cost

• Schedules with earnings higher than variable cost but lower than total cost

• Schedules earning less than variable cost

• Operating cost per passenger km

22

Introduction


Support the top

level officers in taking decision

Information support

for Decision-Making

Assist in taking day–to-day operative decision to

achieve the service output


Generation of

Bus operations generate revenue transactions and data on

utilization, kilometers, schedule adherence, route-wise, time of the day etc., which get recorded daily.

Transaction Processing

using IT & ITS


1. Introduction












MIS: A toolG







ITS allied supportN



23

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

Overview of ITS & MIS Technology Frame work

Priority for various ITS components should be decided by the PT Agency,

based on its needs. However, vehicle tracking system and fare collection

system are basic systems which should be implemented first by a PT Agency.

System

Architecture

System

Architecture

Communication

Architecture

Communication

Architecture

Data ModelsData Models

IntegrationIntegration StandardsStandards

ITS / MIS TECHNOLOGY FRAMEWORK

24

Introduction

Benefits of ITS and MIS

Authority

Operator

User

1. Introduction












MIS: A toolG







ITS allied supportN



25

Introduction

Benefits of ITS and MIS: Case study of Hubballi-Dharwad

1. Introduction












MIS: A toolG







ITS allied supportN



26

Introduction

City Bus Transport using ITS

ITS PROGRAM IMPLEMENTED IN

• Mysore (KSRTC)

• Bengaluru (BMTC)

• Delhi (DTC & Cluster buses)

• Mumbai (BEST, NMMT, Mira

Bhayandar etc)

• Bhopal

• Hubli Dharwad (BRT)

• Ahmedabad (Janmarg BRT)

• Indore (BRT)

• Naya Raipur (BRT)

• Pune (BRT)

• Hyderabad (TSRTC)

• Chandigarh

• Jaipur (JCTCL)

• Kolkata (CSTC)

1. Introduction












MIS: A toolG







ITS allied supportN



27

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

City Bus Transport using ITS - After implementation experiences

Mysore• Increase in ridership by 15%

• Vehicle utilization increased from 247.5

km to 251.7 km.

• Increase in Crew utilization from 66.3 km

per employee to 68.2 km per employee

• Improvement in Operational discipline

Indore• Increase in ridership by 19%

• Decrease by 70% for over-speeding

and 90% for route deviations.

• Increase in average trip length 20%

(5 km to 7 km) per completed trip

• Increase in earning per kilometre

from INR. 62/- per km to INR. 90/-

per km

28

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

City Bus Transport using ITS – Key Learning during implementation

S.No. PROJECT PHASE KEY LEARNING

1 Project

Conceptualization

and Design

• Lack of in-house capacity to understand and conceptualize ITS/ MIS

technology

• Challenges in drafting requirements – ‘one size fits all’ approach

• Lack of availability of proper documented guidelines for planning

and implementing ITS initiatives for Indian cities

2 Project

Procurement

• Difficulty in attracting good SIs – High risk, ambiguity in scope, PQ

conditions not in line with project scope/ value, stringent SLAs

• Long and drawn out bidding process with multiple iterations

3 Project

Implementation

• Lack of in-house capacity to review/approve deliverables

• Ambiguity in scope leads to change requests/ disputes

• Lack of readiness on part of authority – site, buses, power, users

etc.

• Acceptance criteria not clearly laid down

• Resistance to change at various levels of the organization

• Instance of sabotages to ITS equipment installed on buses

• Lack of experience on part of the SI in implementing ITS projects

for large fleet size

• Long duration to achieve stabilization of the ITS initiatives

4 Operations and

Maintenance

• Vendor lock-in and inability to scale up beyond the terms agreed in

the RFP

• Inadequate support provided by the SI during the maintenance

• Integration with 3rd party/external systems

29

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

City Bus Transport using ITS - Reasons for failure

To know the challenges and solution to overcome refer: 1. World Bank: Hand book on Passenger Transport ITS toolkit2. SUTP report: Manual for Planning, Designing, Implementing and Evaluating ITS and MIS Projects

Improper definition of goals and objectives

Improper need assessment

Improper listing of the user or functional requirements

Unsuitable selection of business model

Improper selection of technologies / Closed architecture

Ticketing products not designed based on market requirements

Poor Controlling, Monitoring and Project Management

Use of nonpractical approach and techniques (over sizing/under sizing)

Below par quality of service providers

SI not following a structured, well-defined process for planning, design and implementation of its projects

Lack of support facilities at the end of the implementation agency

Inadequate readiness of environment

30

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction

Limitations & cautions of ITS Technology

1First define the ITS objectives in terms of the organization's requirements and

outcomes and then examine the appropriateness of an ITS/MIS led approach.

Benefits from ITS / MIS are realized over a medium to long term. Avoid

unnecessary expectations on benefits from ITS/MIS are not built up.2

Co-operation and willingness on part of the different stakeholders to use the ITS / MIS is the most critical aspect for it to succeed.

3

There is every possibility that the PT Agencies may face stiff resistance to change

for ITS/MIS system on part of the users of the system.4

Intelligent Transport Systems will not mend a broken or poorly organized urban

passenger transport system.5


31

1. Introduction












MIS: A toolG







ITS allied supportN



Introduction


6 ITS / MIS initiatives need financial support to sustain and deliver the results.

PT Agencies should plan for financing the ITS / MIS projects throughout their

project life-cycle and accordingly should plan for the required financing.7

8There might not have any direct and immediate financial return from the ITS/MIS and they are not cheap to implement either.


32

Introduction

Systematic implementation ITS program

An ITS project is not just a technology project but is a solution for transforming the business processes.

1. Introduction












MIS: A toolG







ITS allied supportN



Guidance Public Transport Function

ITS Application ITS Technology

33

1. Introduction












MIS: A toolG







ITS allied supportN



Systematic implementation ITS program – Guidance – Planning of IT Program


WORKING NOTES AND HIGH LEVEL COST ESTIMATES

1.Need Assessment

2.Stakeholder Identification

3.Setting of Goals and Objectives

4.Identification of Functions and

Services

5.Identification of Users of ITS / MIS

6.User Requirements Preparation

7.Development of Scope of ITS / MIS

Project

8.Preparation of Project Plan

Introduction

34

1. Introduction












MIS: A toolG







ITS allied supportN



Business

and Service

Context

Planning

Service Delivery

Operational Support

Business Intelligence

& Compliance

Systematic implementation ITS program – PT Functions which ITS can support

Introduction

35

Introduction

Systematic implementation ITS program– Overview of ITS Application & Technology

1. Introduction












MIS: A toolG







ITS allied supportN



Bus vehicle Tracking Device

Driver Management Console

In-bus CCTV surveillance

At Station Display Unit

In-Vehicle Display Unit

Mobile App PIS

QR Code based ticketing

Contactless Ticketing

Electronic Ticketing System


ITS Application

and Technology

Fleet Management System

AFCSPIS

36

ITS technology and platform

PLATFORM

1. System Architecture

2. Communication Architecture

3. Data Modal

4. Interface

5. Standard

Crucial points Decisive points

Technology

1. System / sub-system

2. Location

3. Technology type

4. Role

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



37

ITS Allied Support: Infrastructure (Data Center - Servers)

Types of Servers Purpose

Data File Server Communication server

Database Server Database server

Application Server a. Web server

b. GIS server

c. PIS Server with support of streaming Server

(for advt.)

d. SMS

e. Reporting server / MIS

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



38

Support required for ITS – at control room, in buses and at bus stops & stations

Support for ITS

Fire safety

Uninterrupted power supply

Cooling system

Security

Fiber/wifi

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



39

Case study: Mysore (ITS Master Plan)

Source: Mysore City Transport Division of KSRTC

Having ITS that conforms to International Standards in providingefficient operation for Mysore City.Vision

Objective

Concept of ITS

Strategy

Strategic Agenda

Target Level: Improve Operation Management by use of GPS.

Strategy Level: To provide efficient, clean, and safe solution/services.

Action Level: Implement GPS based Tracking, Monitoring & PIS.

Bus information


Electronic Payment

Environment, Safety & Security

Centralized Data Center for ITS

Improved Transport

Efficiency & Productivity

Tracking, data acquisition &

transmission of data

Better mobility &

accessibility

Reduced energy use

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



40

Case study: Mysore (Project Scope - solution view)

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



41

Case study: Mysore (Project phases)

Planning

Design and Build

Procurement

Implementation

Testing & Operationsprogram Mgmt.

Regular Review

Risk Mgmt.

Quality Mgmt.

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



42

Case study: Mysore (Project Scope - sub-components view)


Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



43

Case study: Mysore (Infrastructure - data center, command and control center)

• Servers: all configured in cluster mode (fault tolerance)

• Internet connectivity: 5 Mbps x 2 (redundancy)

• Higher capacity UPS: 2 x 20 KVA online UPS

• Higher capacity DG set: 85 KVA Diesel Generator

• Air conditioners

Data Center

• High-end video wall in Control Room

• Dispatcher Workstations

• Access Control

Command and Control Center

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



44

Case study: Mysore (Project commissioning)


Data Center Central Control Station Video Wall (CCS)

PIS Display Board PIS Display Board (LED) In-Bus Display (LED)

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



45

Case study: Mysore (Team Structure)


KSRTC operations & maintenance team

CMC Mgmt

KSRTC Mgmt

Representative

KSRTC operations team

CMC Onsite Operations

Mgr

Data center team

Network Engg.

Server Engg.

Desktop & PIS Engg.

Software & Application

Support Engg

In bus equipment team

Bannimantapa depot

Kuvempungara depot

Satgalli depot

Helpdesk & dispatchers

team

EMS alertsMonitoring Team (Shared team)

Introduction

1. Introduction












MIS: A toolG







ITS allied supportN



46

Introduction

Key Learning from ITS Technology Implementation: Mysore City

1

ITS Domain- Initially hired consultants & implementation partners had inadequate

ITS domain skill. Subsequently, the contract was terminated which resulted in

time lag till another consultant and implementation partners could be hired on

account of scope of work finalization. Later the contract was awarded to M/s. TCS.

Difficulty in mapping business processes with the technology - Lack of availability

of Functional Requirement Specification for each system as required for the

business process led to:

• Changes in design even during the implementation stage.

• Increase in work of synchronization of daily operational changes with system

requirements.

2

Implementation challenges included:

• Installation time increased due availability of buses at night only.

• ITS technology compatibility issues with older buses.

• Bus shelter – non-standard design, no power supply, security of ITS

equipment.

• Approval of type & size of regional language font for PIS.

• Availability of wireless network signals for communication devices.

3

The project was expected to be completed in 3 years but was completed in 6years. The reasons were:

1. Introduction












MIS: A toolG







ITS allied supportN



47

Introduction

5

Contract challenges:

• Lack of flexibility (in contract) to deal with field realities and changes.

• Ambiguity in RFP – Technical/System vs. functional requirement conflicts. E.g.,

LED boards, UPS need etc.

• Non-clarity on GIS scope, back-up power requirement etc.

Business data challenges:

• Geo-fencing shelter-less bus stops.

• Aligning documented (route) data with field data.6

Commuters & other challenge:

• Setting clear expectations from ITS solution.

• Effective promotions & communications of ITS with its benefits.

• Getting timely approvals and support from various local authorities such

hospitals, tourist spots, railways, for deploying the PIS display boards.

8

Competency building challenge: lack of ITS domain knowledge such that training

was imparted starting from depot.7

4

Lack of information on:

• Actual number of bus stops – it was initially informed that there were less than

400 bus stops when actually there were 2400 approximately. This led to project

delay by almost 7-8months.

• Battery performance of each bus (input & output current)- make & type wise.


1. Introduction












MIS: A toolG







ITS allied supportN



48

Time allocation:

• Completing the Chart–

40 minutes

• Presentation of the

Chart – 15 minutes

(each group)

Group Activity

1. Introduction












MIS: A toolG







ITS allied supportN



49


Questions for Audience

Q1. What are the essentials for middle managers in ITS applications in

fleet management?

Q2. In fleet management, what areas need to be focused upon?

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE

Events: expo, fairs and festivalsF

Case study: PMPMLG

Case study: SuratH

Driver console with VHMSI

ITS in management of incidentJ

Case study: APSRTCL

Application of ITS in OMK

50


Overview

FMS

Dynamic Rescheduling

7

Emergency Mgmt.

6

Driver Standard

Compliance

5

Service Contract

Compliance

4

Schedule Adherence

3Route

Condition Monitoring 2

Automatic Vehicle

Monitoring

1

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


For deeper reforms refer: 1. World Bank: Hand book on Passenger Transport ITS toolkit2. SUTP report: Manual for Planning, Designing, Implementing and Evaluating ITS and MIS Projects

51


ITS Technology

AVM

Driver console

with VHMS

Camera

FDAS

Emergency Button

GIS Layer

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


52


ITS Architecture

Emergency

Breakdown

Report Accident

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


53


Case study: Mysore (Managing bus operations)


Tracking

Route Setting

VMU Management

MIS Reports

Administration

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


54


Case study: Surat (ITS for route service monitoring)

Route Service Line Route Map View

Source: Lumiplan

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


55


Events: Expo, Fairs and Festivals

Challenges?

How can MIS data help?

Management of fleet for operations of buses

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


56


Case study: PMPML (Review of performance)

Source: PPT by CMD, PMPML

The Fleet Management System helps to know the performance, such as (1) average no. of

buses/day on the road (2) daily passenger per bus.

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


57


Case study: Sitilink Surat (ITS for service contract monitoring)

Source: Lumiplan

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


58


Driver console with Vehicle Health Monitoring System

Vehicle health monitoring system (VHMS)

Communication aid for driver

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


59


ITS in Management of Incident

• Fire incidence

• Breakdown

• Emergency

button

• Cameras

• Data storage

ITS application module in Incident management comprises of

the following

• Incidence - Fire incidence, Breakdown

• Emergency button

• Cameras & data storage

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


60


Application of ITS in Operations Management - Video

Source: Hik Vision

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


61


Application of ITS in Operations Management - Video

Source: BMTC

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


62


Case study: APSRTC (ITS enabled incident management - FMS)

Source: APSRTC

1. Introduction






OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCL


63

Automatic Fare Collection System


Q1. What must middle managers know before going for ITS in

Automatic Fare Collection System?

Q2. What are the cashless options available in automatic fare

collection system supported by ITS?

1. Introduction






ITS technology and architectureA

Electronic ticketing machineB

Smart cardsC

Open loop vs Closed loop cardsD

Smart cards - PMPMLE

Case study: SuratF

Digital wallets and E-walletsG

Case study: APSRTCH

Case study: SuratI

Revenue reconciliationJ

64


ITS technology and architecture

Cash Cashless

Ticketing options shall address the requirements of customers

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI



65


Electronic ticketing machine

Click to

play Video

• Safe & Efficient

• Multi-purpose

• Real-time information transfer and report generation1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


66


Smart cards

Source: Concept note on CMC by NCPI

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


67


Smart cards

• No upfront cost is involved.

• Payment is per transaction basis.

Smart Card Benefits

• National Common Mobility

Card (NCMC), also known

as One Nation One Card, is an

inter-operable transport card

conceived by the MoHUA of

the GoI. It was launched on 04

March 2019.

NCMC

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


68


Open loop smart card Vs. Closed loop smart card

Concern Open-loop Smart Card Closed-loop Smart Card

CustomerFriendly

Customers can use the same card for Metroand Bus travel in all cities and states.

Customers need to buy different cards fordifferent public transport systems withinthe city & state.

Convenience Customers can use their bank-issued NCMCcard for fare payment rather than waiting ina queue for card/token/ticket issuance.

Customers may require to stand in queuefor card issuance, top-up, etc.

Loyalty Points Loyalty Points consumers may benefit frompartner banks' loyalty/reward points, asprovided with Debit and Credit cards.

No such provision. Any such loyalty anddiscount is a cost to the Public TransportOperators.

MinimumInfrastructure

Public Transport Operators can minimizetheir cost of maintenance of infrastructureand workforce for card issuance, top-up,card replacement, and refunds, as multiplepartner banks can issue open-loop card.

Each Public Transport Operators need tobear significant expenses for maintenanceof infrastructure and workforce for cardissuance, top-up, card replacement, andrefunds.

Negotiating Power

As open-loop acceptance devices are basedon open interoperable standards, there aremultiple vendors available for paymentacceptance devices, which provides anopportunity for cost and servicenegotiations.

Closed-loop cards may be of proprietarystandards, leading to vendor lock-in forsubsequent purchase and renewals ofacceptance devices.

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


69


Open loop smart card Vs. Closed loop smart card


No vendor lock-in

Open standards based payment acceptancedevices provides the freedom of subsequentpurchase and renewals of devices.

Proprietary standards may lead tovendor lock-in for subsequentpurchase and renewals of acceptancedevice.

Ease of Implementation

Well standardized payment acceptance devicesand availability of multiple vendors provides easeof implementation. Payments related scope ofwork to be taken care of by the partner bank andhence PTOs may focus on their key activities.

PTOs need to evaluate multipleproprietary specifications leading todifficulty in implementation.

Fast Deployment Due to similar implementation process, bestpractices and reference implementationguidelines, there will be standardizedprocurement practices and RFPs. Thisconsiderably expedites deployment of digitalpayments in Public Transport Operators.

Each deployment will have specificrequirements and each PublicTransport Operator requireconsiderable expertise for selection ofan appropriate solution.

Retail acceptance

NCMC open-loop card offers acceptance at all the existing retail PoS devices.

Closed-loop cards can only beaccepted within their operatingenvironments.

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


70


Smart cards: PMPML

EarlierSmart card

Conventional Pass Smart card

Purchase of smart card – website & point of sale / counter.1

Efficiency improvement.2

Reduction in inventory & stocking of materials.3

Multiple use of card - Additional revenue for PMPML when used for other payments.4

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


71


Case study: Surat

BRTS Station ETM with POS

Surat Money Card

Turnstile with Fare gate Validator

City Bus Pole Validator

Source: Lumiplan

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


72


Digital wallets and E-wallets

• Card details are saved in wallets to enable card-less transactions.

• Money remains in user's bank account or credit card.

• Example - Masterpass, Google Wallet, Apple's Passbook.

Digital Wallets

• Money is pre-loaded in the wallets for card-less transactions.

• Money moves from user's account to either a merchant’s current account or an escrow

account.

• Example - Paytm Wallet, Freecharge Wallet, Mobikwik.

E-Wallets

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


73


Case study: APSRTC (Mobile applications)

✓ Packed with e-Wallet

✓ Easy tool for Ticket Booking

✓ Easy tool for Ticket Cancellation

✓ Packed with Live Tracking

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


74


Case study: Surat (Ridership and revenue)

Source: Lumiplan

Top/Last 5 Stops and Route –Ridership and Revenue Hour basis Ridership and Revenue

Day basis ridership and revenue

1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


75


Revenue reconciliation

Ticket sales consolidation

Ticket validation conciliation

Communications


1. Introduction








Smart cardsC



Case study: SuratF


Case study: APSRTCH

Case study: SuratI


76

Passenger Information System


Q1. What information do passengers require to plan the journey,

during the journey, and at bus stop/station to board the right bus?

Q2. What must middle managers know before going for ITS in

passenger information system?

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF

Case study: Sitilink SuratG

Application of PIS: BMTCH

77


Insight into Passenger Information System (PIS)

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



Plan the journey

During journey

At bus stop/station


78


ITS Technology

Source: Lumiplan

Bus AVMLED Route Destination board

outsideLED Route Destination board

inside

Public Announcement System -Audio Server GIS Layer

Voice announcement system

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



79


ITS Technology

Bus Stop – LED display board, LCD Monitor

Bus Station – DOOH – Digital out off House

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



80


ITS Architecture


1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



81


Case study: Mysore


1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



82


Case study: NMMT (Mobile applications)

Source: ppt on “Integrated Intelligent Transport System (IITS) in Navi Mumbai” by NMMT source internet

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



83



Overall Features

• Real-time bus information

• Reminder for bus arrival

• Travel information sharing WhatsApp and SMS

• Real-time availability of seats in buses

Ease of Travelling

• E-ticketing through mobile app

• Smart card recharge through mobile app

• Online pass approval through app

• Safe travel through SOS service

Ticket & Pass Booking, & Safety

• Feedback system for users

• Monitoring system from Control center

• Announcement to commuters on latest offerings

• Document approval for availing pass

Ease of Management

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



84



Features

Users can see Real-time information of bus arrival and departure.1

Users can see nearby bus stops along with walking time.2

Users can see the last stop of the running bus.3

Users can set alarm to remind him/her to reach bus stop.4

Users can set favorite/frequent routes from a bus stop as per the travel requirement. 5

Users are able share their travelling details with any one through WhatsApp & SMS.6

Users can see latest announcements by NMMT.7

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



85



Landing PageStops Near your

location

Information of all runningbuses (In

green) as wellas Scheduled

buses (in blue)

Real-time arrivalof 46 route

number bus inAPMC Market

Bus Stop

Share yourtraveling details

w ith yourfriends/relatives to

take them on-board in the same

bus


1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



86


Case study: DIMTS (Mobile applications)

Poochh-O by DIMTS Mob App for commuters

Source: ppt on “Integrated Transport Operations Management Systems” by DIMTS

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



87


Case study: Sitilink Surat (Mobile applications and M-ticketing)

Source: Lumiplan

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



88


Case study: Sitilink Surat (Integration with google maps)

Integrate Public Transport information with Google Maps

Source: Lumiplan

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



89


Application of PIS: BMTC Video

Source: BMTC

1. Introduction






Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



90

ITS Project in Mysore city

Mysore ITS Project Outcomes: Video

1. Introduction






Project OutcomesA

Lessons LearntB

91


ITS Project in Mysore City: Lessons learned

1. Introduction






Project OutcomesA

Lessons LearntB

1










requirements.

2





equipment.



3


92



1. Introduction






Project OutcomesA

Lessons LearntB

5














8



4






93

1. Introduction






Guidelines for ImplementationA

Key TakeawaysB

Key Considerations

Guidelines for ITS & MIS implementation

Based on in-house capacity and availability of workforce exclusively for the job,

involves PMC through planning, procurement and implementation. The Authority must

understand that the need to hire a PMC is that it shall make up for the lack of in-

house capacity and works as an extension of the Authority (And not another

contract). Alternatively, preference can be given to pragmatic project manager/s, as

adviser, who are experienced in technology know-how, have expertise about

processes, and are well versed with Indian operating scenario.

1

For given finance/funding what can be the best output viz., few modules of ITS with

excellent technology or all modules with adequate technology?

Set the priority and go with few modules with excellent technology first and add

modules as and when ready. Total capex/opex depends on no. of buses, routes,

schedules & bus stops, all of which needs to be viewed within the framework of

priority and available finance. Generally priority may be given to:

1. Automated vehicle monitoring system with scheduling of buses.

2. Passenger Information System.

3. Automated Fare Collection System.

2

94

1. Introduction







Key TakeawaysB

Key Considerations


According to the type of application/system, compile necessary basic information such

as:

• List of bus stops with names, shelter/without shelter, request stops, etc.

• List of buses - type & make wise, age wise etc.

• Bus-wise information on battery output & input voltage.

• Routes, schedules, staff etc.

3

ITS design process will start - Planning, Design & Build, Procurement, Testing &

Operation, and Implementation. In the process, the consultant will develop FRS

[Functional Requirement Specification] & SRS [System Requirement Specification].

Say, for PIS:

• FRS includes - size of LED display board for each bus stop/station according to no.

of passengers, route , language font type & size etc.

• SRS includes - size of LED bulb, input & output current, glow life in hours, no. of

lines/rack/strips, UPS requirements etc.

4

95

1. Introduction







Key TakeawaysB

Key Considerations


Data Storage – data storage costs have reduced drastically, plus private cloud has

been put in place and NIC also offers excellent options. Thus, according to the

requirement, data can be stored. As per IT Law, 90 days data needs to be stored.

5

Training needs to be imparted continuously to all stakeholders in order to yield

maximum benefit from the system. For upgrading skills, vertical interaction program,

workshops, and group exercises may be thought of.

6

Best option 1) Server vs. cloud, 2) capex vs. opex model and 3) totally outsource/

part outsourcing?

It is better to move to cloud for its scalability & easy maintenance, plus the SLA

[Service Level Agreement] are taken care of by the provider. Options such as part

outsourcing may be explored in cases where data and assets are owned by the

corporation but ITS operations and maintenance is outsourced.

7

96

1. Introduction







Key TakeawaysB

Key Considerations


Information systems can be hard to develop and put into service – a few city

transport operators initially started operating buses fitted with vehicle tracking

system thinking the system will give information of bus halt at bus stops. However, no

information was received. When investigated, it was found that buses performed their

routine activities without any deviation. The attributed reason was no proper geo-

fencing to map bus stops, so it could not detect the stops.

Solution – Middle level managers can play a vital role in finding true cases as they are

well-versed with business processes.

8

AIS 140 speaks of ITS requirement for public transport vehicle operation focusing on

few areas in ITS such as Automatic Vehicle Monitoring System, Emergency Panic

Button oriented towards the safety of passengers. But for other systems, multiple

options are available.

Middle managers play a decisive role during ITS implementation especially in business

process validation, and also after commissioning.

9

97

1. Introduction







Key TakeawaysB

Key Considerations

Key Takeaways

1ITS objectives in terms of the organization's requirements and outcomes should

be defined first before examining the appropriateness of an ITS/MIS led approach.

Define key business drivers for decision making.2

Identify sources of funding for initiatives such as capital fund, operative fund or

combination of funds from Central, State, ULB or a combination; single year or

multi-year availability.3

Intelligent Transport Systems are effective when there is a willingness to change

organizational and operational procedures to take advantage of opportunities

being created.4

It is essential to understand that Intelligent Transport Systems will not mend a

broken or poorly organized urban passenger transport system; ITS can only act to

enhance one that is already reasonably effective.5

Intelligent Transport Systems are usually not cheap to implement, and they might

not have a direct financial return. ITS may help in assisting many aspects of the

business, such as enhancing the system's usability, customer retention, or

increase ridership.

6

98

1. Introduction







Key TakeawaysB

Key Considerations

Key Takeaways

7

Irrespective of technological changes/upgrades, the functional requirements

should spell out the deliverables from each sub-system, and technical

specifications must emphasize interfacing, regulatory/compliance, security

requirements, etc.

PMC shall be engaged right from the planning stage to procurement, installation,

and commissioning stage. The consultant shall make a plan, estimate the budget,

analyze the financial viability, prepare the specifications beforehand, and ensure

its implementation.

8

Role & responsibility shall be clearly defined for Purchaser and Supplier and shall

have a mechanism in place for dispute resolution in the contract.9

Intelligent Transport Systems have a recurring cost of operation and maintenance,

which may be quite significant. Unless there is an ability, commitment, and

capacity, the ITS program should not be implemented.10

Like in other procurement processes, in ITS procurement also there is a risk of

capturing the process by its potential suppliers. To counter this, ITS Toolkit is a

valuable resource.12

11Carrying out data intelligence for better understanding of commuters

requirements and services provided.

99

1. Introduction







Key TakeawaysB

Key Considerations

Key Takeaways

Electronic fare collection may prove to be an Intelligent Transport Systems with

the highest financial return. Any success in this domain could both act as a

technical platform and provide funding support for future programs. Use the Public

Transport Fares Toolkit for further advice.

13

On stabilization of the project, the project implementing agency will need to take

up a Public Outreach program. Value additions to the project like Mobile Apps,

Open Data Policy to be developed and deployed for an enriched experience.14

Results will be visible only when operational procedures are changed and

applications are refined thereafter. Many cities have only been able to take full

advantage of ITS in their second or third implementation programs.15

100

Thank You !

Time for discussion

101

Reference table

A. 9

B. 10

C. 11

D. 12-15

E. 16-18

F. 19

G. 20-21

H. 22

I. 23-24

J. 25-28

K. 29-30

L. 31-34

M. -

N. 35

O. 36

P. 37

Q. 38-47

A. 11-13

B. 14

C. 15

D. 16-19

E. 20-22

F. 23

G. 24-25

H. 26

I. 27-28

J. 29-32

K. 33-34

L. 35-38

M. 39

N. 40-42

O. 43-44

P. 45

Q. 46-54

A. 9

B. -

C. 10

D. 11-14

E. 15-17

F. 18

G. 19

H. 20

I. 21-22

J. 23-26

K. 27-28

L. 29-32

M. 33

N. 34-36

O. 37-38

P. 39

Q. 40-49

Delivery

PPT

Trainer

manual

Participant

Manual

A. 48-49

B. 50

C. 51

D. 52

A. 55-56

B. 57-58

C. 59

D. 60

A. 50

B. 51

C. 52

D. 53

Introduction


B. Overview of ITS


D. Why ITS is required





I. Benefits of ITS and MIS




M. Understanding ITS and Non-ITS

N. ITS technology and platform

O. ITS allied support

P. Support required for ITS

Q. Case study: Mysore

1

Fleet Management

Systems

A. Overview

B. ITS technology

C. ITS architecture


2

102

Reference table

E. 53

F. 54

G. 55

H. 56

I. 57

J. 58

K. 59-61

E. 61

F. 62

G. 63

H. 64

I. 65

J. 66

K. 67

E. 54

F. 55

G. 56

H. 57

I. 58

J. 59

K. 60-61

Delivery

PPT

Trainer

manual

Participant

Manual

A. 62-63

B. 64

C. -

D. 65-66

E. 67-68

F. 69

G. 70

H. 71

I. 72

J. 73

K. 74

A. 68-69

B. 70

C. 71

D. 72-74

E. 75

F. 76-77

G. 78-80

H. 81

I. 82

J. 83

K. 84-85

A. 62

B. 63

C. 64

D. 65-67

E. 68

F. 69

G. 70-72

H. 73

I. 74

J. 75

K. 76-78

Fleet Management

Systems







K. Case study: APSRTC

2

Automatic Fare

Collection System



C. Automatic daily pass vending machine

D. Smart cards

E. Common mobility cards


G. E-wallets

H. Digital wallets and E-wallets

I. Case study: APSRTC

J. Case study: Surat

K. Revenue reconciliation

3

103

Reference table

A. 75-76

B. 77-78

C. 79

D. 80

E. 81-84

F. 85

G. 86-88

A. 86-87

B. 88-89

C. 90

D. 91

E. 92-94

F. 95

G. 96-97

A. 79

B. 80-81

C. 82

D. 83

E. 84-86

F. 87

G. 88-90

Delivery

PPT

Trainer

manual

Participant

Manual

A. -

B. -

C. -

D. -

E. -

F. -

G. -

H. -

I. -

A. 98-99

B. 100

C. 101

D. 102-103

E. 104

F. 105

G. 106

H. 107

I. 108

A. 91

B. 92

C. 93

D. 94-95

E. 96

F. 97

G. 98

H. 99

I. 100

Passenger

Information

Systems


B. ITS technology

C. ITS architecture


E. Case study: NMMT



4

Preventive

Maintenance

Management

Systems

A. Operation – Maintenance interface

B. Overview

C. Preventive maintenance schedules

D. Planning of fleet for preventive maintenance using IT

E. Preventive maintenance schedules

F. Creation of Bus Master File

G. Overview on Fuel Management System

H. Input – Use of ITS and MIS in Fuel MS

I. Output – Use of ITS and MIS in Fuel MS

5

Inventory

Management

Systems

A. Need for inventory management

B. Database: Creation for individual items

C. Requisition slip and Issue slip

6

A. -

B. -

C. -

A. 109-110

B. 111

C. 112

A. 101

B. 102

C. 103

104

Reference table

A. -

B. -

C. -

A. 113-114

B. 115

C. 116-117

A. 104

B. 105

C. 106-108

Delivery

PPT

Trainer

manual

Participant

Manual

A. 89

B. 90-91

A. 118

B. 119-120

A. 109

B. 110-111

A. 92-95

B. 96-98

A. 121-124

B. 125-127

A. 112-115

B. 116-118

Workforce

Management

Systems

A. Need for workforce management systems

B. Leave management systems

C. Crew management systems

7

ITS Project in

Mysore

A. Project outcomes

B. Lessons learned8


B. Key takeaways9

105

Bibliography• http://urbanmobilityindia.in/Upload/Conference/cffba672-c8a8-4faa-a1cd-749da6e6ef85.pdf

• https://ppiaf.org/sites/ppiaf.org/files/documents/toolkits/UrbanBusToolkit/assets/1/1d/1d.html

• https://www.ssatp.org/sites/ssatp/files/publications/Toolkits/ITS%20Toolkit%20content/assets/files/ITS_Toolkit_Han

dbook.pdf)

• https://www.ssatp.org/sites/ssatp/files/publications/Toolkits/Fares%20Toolkit%20content/fare-collection-

procedures/revenue-protection-processes.html

• Concept note on Common Mobility Card

• http://www.arthapedia.in/index.php?title=Digital_/_Electronic_Wallet_(e-wallet)

• https://virtocommerce.com/glossary/what-is-inventory-management

• https://blogs.worldbank.org/transport/one-bus-away-how-unbundling-bus-provision-operation-can-support-bus-

modernization-programs

• https://ops.fhwa.dot.gov/publications/fhwaop04010/chapter12.htm

• Concept note on CMC by NCPI

• https://www.guru99.com/mis-definition.html

• https://www.scdlpune.com/role-and-use-management-information-system-mis-airlines-aviation-industry.html

• https://www.atlassian.com/blog/jira-software/server-vs-data-center-whats-right

• https://www.slideshare.net/navas0001/electronic-ticketing-machine-etm

• Knowledge exchange workshop, building on the experience from SUTP - ppt of Shri A Sen Gupta

• Manual for Planning, Designing, Implementing and Evaluating ITS and MIS Projects – ppt by DIMTS



Trainer Manual

1

December 2020December 2020




TRAINER’S NOTES – ITS AND MIS FOR MIDDLE MANAGERSTRAINER’S NOTES – ITS AND MIS FOR MIDDLE MANAGERS

2

PrefaceThe Efficient and Sustainable City Bus Services (ESCBS) project was introduced to improve the efficiency and attractiveness of city

bus transport in India. ESCBS project has three major components, which includes, National Capacity Building (NCB); Regulatory,

Institutional and Fiscal Analysis; and City Demonstration. This engagement falls under the purview of the NCB component of the

ESCBS project. The objective of this engagement is to design and develop training programme for city transport professionals, and

involves undertaking pilot testing, implementation, evaluation, and suitable modification of the training programme.


(MoHUA).

Policy Advocacy for

Senior Managers


Managers

Monitoring and


Managers


Middle Managers


Middle Managers


Managers

Bus Operations for

Middle Managers


Managers

1 2 3 4

5 6 7 8





3

About the Module

It is strongly recommended that the trainer's manual is referred to before the training session.





management, inventory management, and manpower management. The module also provides lessons learned from cities and

best practices for better understanding.


operators it helps in identifying passenger demand, easy cash transaction & revenue reconciliation, optimum utilization of fleet

& manpower, effective planning preventive maintenance, shift and duty allocation of staff, inventory management, and meeting

the growing demands of passengers. Further, this module will help in gathering information for performance monitoring.

4

Learning Objectives












wrt users.

• ITS offers users with multiple fare trabsaction options such as mobile, card, and wallet and aids in making quick and



5

Learning Objectives





agreement.


Service provider:




Society:

6

Note for Trainers

Questionnaire, 20 min

Tea Break, 30 min

Discussion, 30 min

Group Activity, 100 min

Content Dissemination,

180 min

Lunch, 60 min

Session BreakupTotal 7 hours (420 min)

Key points for Trainers

✓ The trainers shall make sincere efforts to make the

training session interactive.

✓ The trainers shall adhere to the time given for a particular

module. Some time for discussions should be kept aside at

the end of the session.

✓ The trainers are requested to circulate the pre and post

training questionnaire at the beginning of the training

session.

✓ A group activity has been planned for each training

session. The trainers are requested to circulate the same

as per the power point presentation (Delivery

presentation).

✓ It is recommended that the trainer refers to the module-

wise notes. They provide the objective of that module,

along with notes and questions for discussion during the

training session.

Part 1 Part 2Lunch

10:00 AM to 1:00 PM

1:00 PM to 2:00 PM

2:00 PM to 5:00 PM

Tea break 1 Tea break 2

Structure of the training

7

Note for TrainersChallenges

A. Indian urban public transport (PT) w.r.t ITS & MIS can be categorized into three categories (1) having no ITS & MIS (2)

minimal/part module supporting front end activities viz., ticketing management system (3) full fledge ITS & MIS system in

place. Unfortunately, most urban PT agencies fall either in the first or second category, and very few are in the third

category. However, in all the 3 types, one thing is common, i.e., middle-level officers play a very crucial role and are well

versed with:

Conventional practices in fleet management, ticket collection, MIS, passenger information system, planning & operation of public

transport.

B. However, middle-level officers in the first 2 categories lack in the following facets:

1. Understanding IT, ITS & MIS, role & benefits of ITS and MIS.

2. What best can be obtained under each module viz., PIS, ticketing management system, etc.

3. What are the pitfalls?

C. Competence of middle-level officer’s w.r.t implementation of ITS & MIS - (a) type & years of experience (b) qualification

and (c) inclination to look from various perspectives.

Work-related to ITS & MIS starting from processing of tender incl. hiring of the consultant is assigned to an officers/team who has multi-

disciplinary experience in various areas and has no background of IT (or) having IT background with less exposure to public transport

workings. About PT, these officers lack knowledge of what citizens expectations are. Even they face problems, e.g., for a given set of

technical requirement of hardware components, identifying component which is a value for money.

Way forward

A. & B. Given the above condition, it is a pre-requisite to start with brief information on ITS & MIS, overview & insight into ITS design, current

trends/practices, understanding various modules with the support of case studies, and lessons learned from ITS project implemented in

Mysore city.

C. Often consultant is hired for the assignment; however, final decisions have to be taken by the PT agency viz., scope of work, available

options in the market vs. requirements, allocation of fund & financial position, which are the best options for the given set of condition 1)

server vs. cloud, 2) capex vs. opex model and 3) total outsource/part outsourcing.

The knowledge of middle-level officers needs to be raised to ensure that they assist their seniors in implementing ITS & MIS.

8

Table of Contents

Introduction


B. Overview of ITS


D. Why ITS is required (Commuter, Operator and Authority’s perspective)





I. Benefits of ITS and MIS (Operator, Commuter, and Authority)









1

Fleet Management

Systems

A. Overview

B. ITS technology

C. ITS architecture




2

9

Table of Contents


Systems


B. ITS technology

C. ITS architecture


E. Case study: NMMT



4

Automatic Fare Collection

System




D. Smart cards



G. E-wallets





3

Fleet Management

Systems






2

10

Table of Contents

Workforce Management

Systems

A. Need for workforce management systems and benefits thereof



7

Inventory Management

Systems




6


B. Lessons learned8

Preventive Maintenance

Management Systems


B. Overview




F. Creation of Bus Master File and updating bus-wise spare parts consumption


H. Input – Use of ITS and MIS in fuel management systems

I. Output – Use of ITS and MIS in fuel management systems

5


B. Key takeaways9

11

Introduction

Notes for Trainer

General Information on the Session

Approximately 20 min.

Module Objective

The objective of the module is to:

• Define the relationship between IT, ITS, and MIS;

• Familiarize the audience with the method of data processing;

• Understand the importance of information and identify relevant information;

• Understand that Management Information System is a tool;

• Understand the benefits of ITS systems;

• Understand the difference between ITS and Non-ITS systems and how they are facilitating

function to each other;

• Familiarize the audience with the components of ITS technology and concise guidance on

implementation. Understand ITS platform with focus on integrating old & new technology

and communication required thereof. Besides, the abstract of the decisive point is covered.

• Provide insights into infrastructure requirements and roles & responsibility of the team,

i.e., consulting & operating team.

• Case study is used to elucidate the above information.

Module Notes

This module defines and distinguishes between IT, ITS, and MIS. It also provides an overview

of how raw data is transformed into information. What are the characteristics of productive

data and how MIS can be a decision-making tool. Furthermore, the module describes the

benefits of ITS systems for operator, commuter, and the authority.

In addition, this module also clarifies the difference between ITS & Non-ITS, develops

familiarity on technology, platform, data requirement, and allied support.

1. Introduction




5. Preventive Maintenance Management

6. Inventory Management Systems

7. Workforce Management Systems








MIS: A toolG






12

Introduction


IT (Information Technology) refers to the use of computer storage, network and

other physical devices, data center infrastructure (power, cooling system, server,

storage sub-system, etc.) and process to create, process, store, secure, and exchange all

forms of electronic data.





Intelligent Transport Systems (ITS) are a suite of public transport planning, operations

management, and customer service applications that are enabled by advanced information

& communication technologies. They act to enhance the effectiveness, efficiency, and

usability of public transport services provided to benefit public transport authority,

operators, and passengers.

ITS involves customized, situation-specific applications to address specific functions.







MIS (Management Information System) is a system that uses IT, tracks business

processes (via multiple on-line systems & applications associated with ITS), and has the

provision for recording, storage, and processing data to produce information. This

information helps to make crucial decisions.

The above information is also one of the primary sources of input for defining Key

Performance Indicators (KPIs) of Monitoring & Evaluation (M&E).







1. Introduction














MIS: A toolG






13

Introduction

ITS and MIS Manual




















MIS will do.





1. Introduction














MIS: A toolG






14

Time allocation:

• Completing the Chart

– 40 minutes

• Presentation of the

Chart – 15 minutes

(each group)

Group Activity

Notes for Trainer:

Participants are from different cities and often more than one participant report from the same city, so

following is a prerequisite:

1. Formation of groups –

a) It is ideal to have a group of size of 04-06 participants; based on no. of participants, estimate

how many groups are required.

b) Identify the team leaders (voluntarily) for the groups and inform the other participants to join

the team leader. Ensure to create heterogeneous groups.

2. Now allot the group activity sheet.

3. On completion of group activity by each team, inform the participants to share the challenges they are

facing and what are the current practices they are following.

1. Introduction














MIS: A toolG






15

Introduction

Overview of ITS THIS is being

considered

Notes for Trainer

The system architecture (as shown), conceptually represents interactions between elements of each user

system and the system as a whole. Out of the whole, the transit management is being considered.

1. Introduction














MIS: A toolG






16

Introduction



OPERATOR


PassengersPASSENGER


AUTHORITY


Notes for Trainer

Passengers-can access real-time public transport information with multiple options for boarding points,

routes (subject to availability), etc., and plan the trip conveniently. ITS also supports faster, safer &

transparent fare transaction. For the operator, ITS & MIS is an enabler to provide efficient, reliable, and

economical service. For the authority, accurate processed information is easily accessible on a timely basis

facilitating decision making.

1. Introduction














MIS: A toolG






17

1. Introduction














MIS: A toolG






Introduction



come???


come???




take my bus??


take my bus??

Is the next stop my

destination?

Is the next stop my

destination?


available ???


available ???

Notes for Trainer


18

Notes for Trainer


1. Introduction














MIS: A toolG






Introduction



the buses??


any stops?


any stops?






schedule?



schedule?



ridership etc., ?


ridership etc., ?

19

1. Introduction














MIS: A toolG






Introduction




conductors



conductors








(if any)


(if any)



transparent.



transparent.


bus stop etc.,


bus stop etc.,





Notes for Trainer


20

Introduction

Case study of Mysore (Video)

1. Introduction














MIS: A toolG






Notes for Trainer

Play the video and summarize the benefit

21

Data Processing &

Storage

Generation of Input

Data

Output Information

Generation incl.

IT

ITS


Introduction


1. Introduction














MIS: A toolG






Notes for Trainer

Notes for this slide are given in the next 3 slides.

22

Introduction


ITS Server

ITS

Technologies

Storing of raw data in Database Server / concern server

Technical systems & hardware required for ITS application

• Automatic vehicle location (GPS – Global Position System onboard),

• Electronic fare collection (ETVM- Electronic Ticket Vending machine compatible with

multi-medium payment systems and complete GPS/GPRS connectivity),

• Driver’s console including driver monitoring, Vehicle Health Diagnostic System (VHDS)

and monitoring, emergency alert switch, reversing camera,

• In-vehicle data hub & processor,

• Surveillance equipment (CCTV cameras),

• Passenger Information System (PIS) (duly synchronized Audio-Video system for the

benefit of pax, onboard & Off-board, including PwDs [Persons with Disabilities]),

• Communication system,

etc. for generation & transfer of raw data.

1. Introduction














MIS: A toolG






23

Introduction


•Tracking of bus

•Revenue earning

•Way bill data

•Fuel consumption

•Surveillance Data

Input data

•Processing of data usingmathematical, statistical, GISand other application tools

•Storage of processedinformation

ITS Server

Data collection, storage & processing •Real-Time Information to the

Passengers – on-board & Off-board

•Driving Behavior monitoring

•Route behavior Monitoring

•Vehicle productivity, bus loading,

•Earning per kms


Example Example

Raw data streaming to an ITS server makes sense only when it is organized into reports (information) by analyzing them through purpose-built software tools.

Facts/raw data collected from bus operations which are received at ITS server form's "input

data” – an unorganized heap or dump. Information is then derived from this random

collection by organizing it for a specific use or purpose. The outline of the difference

between "input data" & "output information / MIS" is illustrated below:1. Introduction














MIS: A toolG






24

Introduction


Determine

usefulness of

output

information

Quality

Completeness

Relevance Timely

Attributes / Characteristics

Quality Accuracy and reliabilityof available informationaffects the quality ofdecisions thatmanagers make usingthe information.

Timeliness Availability of real-timeinformation reflectingcurrent conditionsfacilitates managers inmaking precisedecisions.

Completeness Complete informationallows managers toconsider all relevantfactors when makingdecisions.

Relevance Having informationspecific to a situationassists managers inaddressing criticaldecisions.

1. Introduction














MIS: A toolG






25

Introduction


Operational Performance Indicators

Capacity

•Fleet Size

•Buses on-Road

•Buses of f -Road

•Bus Utilization per

day

•Staf f ratio per bus

Serviceability

• Scheduled kms v s

Ef f ective kms

• Ef f ective kms vs

cancelled kms

• Total Passenger

kms

• Load f actor per bus

/ per route

• Passengers carried

per bus per day

Reliability

• Trips scheduled v s

Trips cancelled

• Regularity and

punctuality

• Adherence to

operational

discipline (rash

driv ing, stops

skipping, route

dev iations, crew

behav iour)

• Breakdowns

recorded f or ev ery

10,000 kms

Safety

• Accidents recorded

per 100,000 kms

• Number of f atal

accidents recorded

• Number of non f atal

accidents recorded

• Number of

complaints receiv ed

f rom passengers on

crew behav iour,

rash driv ing, stops

skipping, route

dev iations

Financial Performance Indicators


Notes for Trainer


1. Introduction














MIS: A toolG






Operational Cost

• Personnel Cost

• Material Cost

• Operating Cost Per Effective Kilometer (CPKM)

Revenue

• Traffic Revenue

• Non-Traffic Revenue

• Subsidy re-imbursement

• Fare concessions re-imbursement

• Total earnings per bus per day or per km

Performance Ratios

• Total Cost per bus per day (on road)

• Percentage return on capital invested

• Schedules earning more than total cost

• Schedules with earnings higher than variable cost but lower than total cost

• Schedules earning less than variable cost

• Operating cost per passenger km

26

Introduction


1. Measuring actual performance against measurable goals /outcomes wrt (KPIs).2. Review of actual performance against benchmarked KPIs output which are organized appropriately for

ease of appreciation and quick action at different levels of management.3. Taking corrective action.

Better insight into public transport,

meeting commuting needs, operator’s

performance, and interventions required

(if any) thereof.

Improving the decision-making quality: Correctinformation becomesavailable quickly to themanagers from a goodMIS which they can usefor making data baseddecisions. This improvesthe quality of decisions.

Provides connectivity: MISprovides betterconnectivity with all thedepots. In turn facilitatingeffective decision-making.

Aids passengers in makingdecisions by providing real-time passenger information.



Support top-level

officers in taking decision

Information support

For quick and focused Decision-Making

Management Information System Reports appropriate

for action at different levels of

management

Generation of


using IT & ITS



1. Introduction














MIS: A toolG






27

1. Introduction








Understanding ITS and Non-ITSM

ITS technology and platformN

ITS allied supportO

Support required for ITSP

Case Study - MysoreQ


MIS: A toolG






Introduction


Notes for trainer: Explain the above and emphasis on caution “Priority for various

ITS components should be decided by the PT Agency, based on its needs.

However, vehicle tracking system and fare collection system are basic

systems which should be implemented first by a PT Agency”

System

Architecture

System

Architecture

Communication

Architecture

Communication

Architecture




28

Introduction

Benefits of ITS and MIS: Authority

Authority

Operator

User

Notes for Trainer

User: ITS makes public transport more attractive, convenient, time saving, and safe for the user.

Operator - ITS enhances efficiency and revenue & expenses records.

Authority: ITS ensures that smarter & safer public transport is offered, oversee management of

operations, and revenue account and is a useful business intelligence tool.

1. Introduction










ITS allied supportO




MIS: A toolG






29

Introduction

Benefits of ITS and MIS: Case study of Hubballi-Dharwad (Video)

1. Introduction










ITS allied supportO




MIS: A toolG






Notes for Trainer:

Play the video and highlight on the

point such as ITS systems incorporated

by Hubballi-Dharwad BRTS includes:

Notes for Trainer:

1. AVLS: Automatic Vehicle Location System

2. AFCS: Automatic Fare Collection System

3. VPS: Vehicle Planning and Scheduling

4. PIS: Passenger Information System

5. IMS: Incident Management System

30

Introduction



• Mysore (KSRTC)• Bengaluru (BMTC)• Delhi (DTC & Cluster buses)• Mumbai (BEST, NMMT, Mira

Bhayandar etc)• Bhopal• Hubli Dharwad (BRT)• Ahmedabad (Janmarg BRT)• Indore (BRT)• Naya Raipur (BRT)• Pune (BRT)• Hyderabad (TSRTC)• Chandigarh• Jaipur (JCTCL)• Kolkata (CSTC)

Notes for Trainer:

Elaborate the above.

Emphasis on the point that this technology is not

a new in India. But one needs to understand

that An ITS project is not just a technology

project but is a solution for transforming

the business processes.

1. Introduction










ITS allied supportO




MIS: A toolG






31

Notes for trainer: Explain the above

1. Introduction










ITS allied supportO




MIS: A toolG






Introduction




km to 251.7 km.











per km

32

1. Introduction










ITS allied supportO




MIS: A toolG






Introduction



1 Project

Conceptualization

and Design


technology


• Lack of availability of proper documented guidelines for planning and

implementing ITS initiatives for Indian cities

2 Project

Procurement




3 Project

Implementation



• Lack of readiness on part of authority: site, buses, power, users, etc.




• Lack of experience on part of the SI in implementing ITS projects for

large fleet size


4 Operations and

Maintenance

• Vendor lock-in & inability to scale up beyond the terms agreed in RFP




33

1. Introduction










ITS allied supportO




MIS: A toolG






Introduction















34

1. Introduction










ITS allied supportO




MIS: A toolG






Introduction







3







35

Introduction


1. Introduction










ITS allied supportO




MIS: A toolG












36

1. Introduction










ITS allied supportO




MIS: A toolG






Introduction





Guidance – Intended to guide the stake holders in a structured way (viz., Planning, Design, Implementation

& Evaluation in order to determine what the ITS is required to do, and how this fits within the broader

corporate service, operations and management strategy. How system & technology will be embedded in the

organization. Followed by implementation & evaluation.

Public Transport Function – It is intended to identify the priority areas for development of urban passenger

transport system, and whether there are ITS applications can assist in that process

ITS Application – The ITS Applications describes what the ITS does and how it does it.

ITS Technology – The ITS Technologies consist of a wide range of physical devices, their embedded

software, and their means of communication. They are the means of implementing the ITS Applications.

Notes for Trainer: Elaborate the following:

ITS applications includes PIS, Fleet Mgmt and Automatic Fare Collection System and the supporting are ITS technologies. In the subsequent slide we will be discussing more on application wise technologies.

37

1. Introduction










ITS allied supportO




MIS: A toolG









1.Need Assessment




Services




Project


Introduction

38

1. Introduction










ITS allied supportO




MIS: A toolG






Business and

Service Context• General service

characteristics• Public transport funding

and cost recovery• Economic regulation• Role of public and private

sectors• Institutional framework• Public transport

restructuring

Planning

• Network and modal planning

• Service planning and specification

• Service contracting and management

• Fares policy and practice

• External communications

• Multi-modal integration

Service Delivery• Vehicle and crew scheduling• Preparation of vehicles for duty• Performance of service delivery• Crew Management• Service Quality Management• Management of incidents• Farescollection• Traveler information• Security and customer services

Operational Support• Demand management• Public transport priorities• Operations control center• Systems payment management• Vehicle and Infrastructure

maintenance• Inventory management• Fleet Management• Environmental program• Operator management• Human resource and development• ICT and ITS system support


& Compliance

• Legal and service compliance• Financial accounting and reporting• Consumption monitoring• Incident analysis


Introduction

39

1. Introduction










ITS allied supportO




MIS: A toolG






Introduction







Mobile App PIS





ITS Application

and Technology


AFCSPIS

40

Introduction

Understanding ITS and Non-ITS

Notes for Trainer – ITS Design (Understanding ITS and Non-ITS)

Without Non-ITS system, no ITS system can be implemented.

When ITS systems are implemented, Non-ITS system often receive many input data from ITS systems (viz., kms run per trip or day, route / conductor wise revenue with transaction records, vehicle health,

MIS etc.).

In some cases, the Non-ITS function can also provide baseline data for ITS systems (viz., Service Scheduling - allotment of crew based on the availability status, number of fit vehicles that can be

provided for operations).

ITS Systems (Core Functions) Non-ITS Systems (Facilitated Functions)

Operations Management including need-based dynamic scheduling of services; Automatic

Vehicle Tracking

Bus and Crew scheduling and performance monitoring, and overall Management

Route and Driving behavior monitoring--Driverconsole

Leave Management, grievance handling, and wage administration

Security and safety against Fire hazards Vehicle maintenance scheduling, monitoring and control; Defect analysis and PM schedules up-

gradation

Passenger Information system – On-board & Off-board including for PwDS

Fuel consumption monitoring

Electronic Fare Collection System complete with on-line way-bill transfer, revenue leakage

prevention assistance

MIS

1. Introduction










ITS allied supportO




MIS: A toolG






41

Introduction


ITS Technology

Technology should be analysed from four perspectives:

• System/sub-system: Functions performed by the ITS system, e.g., Operations Management, Fare

Collection, Surveillance, and PIS.

• Location: Where is the technology located, e.g., on vehicles, at the control center, at bus-stops

processor, communications device, and data storage units.

• Technology type: Nature of the device e.g., customer-facing equipment, sensors, data processor,

communications device, and data storage units.

• Role: Generate data (e.g., sensor), process data (e.g., card leader), display (e.g., at-stop information

display), analyse data (e.g., dispatch support), and optimize resources (e.g., scheduling).

Many devices have multiple embedded components and they may perform multiple functions. For example,

a suitable GPS enabled mobile phone may now be sufficient to support AVM functions, while previously it

would have required a radio, a GPS unit, a driver interface/console, and an integrating processor. Similarly,

individual devices may now perform multiple functions, or a suitable combination of two devices where

shared processing may eliminate need for a third device.

Notes for Trainer – ITS Design (ITS technology and platform) – Crucial points

1. Technology is just one component of an ITS project. Organizational structure and operating procedures

are equally important, and all three must be taken into consideration in designing.

2. Technology choices and specifications should not be made until they are fully understood as to what

the ITS is required to do. Issues such as choice of communication or vendor preference should not be

allowed to predetermine design outcomes.

3. Procurement should focus on outcomes rather than on devices.

4. Implementation is a significant task which must be planned and resourced correctly. Adequate time

must be allowed for testing, installation, and commissioning.

1. Introduction










ITS allied supportO




MIS: A toolG






42

Introduction


ITS Platform

An ITS system consists of many inter-connected devices, software, and information. At a minimum, they

need to be able to connect and exchange information. ITS systems and sub-systems may need to perform

the tasks together.

ITS “Platform” concept elements are:

• System Architecture: Mapping all ITS systems and relate them with each other.

• Communication Architecture: defines how the systems and devices communicate with each other, and

what information is to be exchanged.

• Data Model: Consistency in defining the data to be used so that data generated by the system / sub-

system will be in standard/common form.

• Interfaces: Defines the physical connectivity between devices and protocols used for information

exchange.

• Standards: For ensuring that both Vendors and Clients develop hardware and software in a common way,

usually based on international industry consensus.

The ITS deployment team will determine appropriate platform elements. Ideally, it is expected to select

international norms that reflect industry practice and relevant elements of such norms.

Notes for Trainer – ITS Design (ITS technology and platform) – Decisive points

The data requirements fall under the following broad categories:

• Background data, configuration data, and daily assignment data.

• Real-time of event/transaction-specific data that the ITS requires when performing a specific function.

• Data which the ITS system should pass to devices, both for immediate and downstream use.

1. Introduction










ITS allied supportO




MIS: A toolG






43

Introduction

ITS technology and platform: Wireless communication technology network

General PacketRadio Service(GPRS).Download speedup to 114Kbps.

2G

High-Speed Packet

Access (HSPA).

Download speed of

up to 168Mbps.

4G

High-SpeedDownlink PacketAccess (HSDPA).Download speed ofup to 14Mbps.

3G

Introduction of 3G network madevideo calling and seamlessstreaming of video possible.

Long Term Evolution

(LTE).

Download speed of

up to 299.6Mbps

4G

LTE is a 4G network that

supports faster

communication and HD

video streaming.

To date, most of the urban transport network in India uses GPRS, which is 2G wirelesscommunication technology.

In the upcoming projects, ensure to include hardware configuration compatible with highercommunication technology.

1. Introduction










ITS allied supportO




MIS: A toolG






44

Introduction

ITS Allied Support: Infrastructure, back-office, human

Occasionally, an ITS system may be free-standing or plugged into existing ITS systems

without any other requirements. However, most ITS systems are not independent, and they

require supporting infrastructure and back-office support. In this backdrop, three particular

aspects needs to be considered:

• The ITS system may need to share some aspects of the IT platform of the host

organization (e.g., servers, communication, operating systems). Therefore, platform

capacity may need to be increased along with purchase of additional user licenses.

• The ITS system may need to interface with the existing administrative and/or

management IT systems. Therefore, system software amendments may be needed.

• The ITS systems may also need non-ITS supporting technology, including

communications, servers, back-office PCs, printers, office software, and security

software.

• Human Resources – For smooth functioning of ITS, it is essential to define the role of the

consulting team (ITS consultant) and the operational team (urban transport operator)

after commissioning of the ITS project during the contracting period.

These requirements need to be identified, specified, and budgeted for, as part of the ITS

system design and planning.

1. Introduction










ITS allied supportO




MIS: A toolG






45

Introduction






b. GIS server

c. PIS Server with support of streaming Server (for

advt.)

d. SMS


Size of the memory allocated to the server for a given purpose shall be based on expected

load that is likely to come, that is:

1. How many operator's teams in multiples, separated geographically will be accessed

simultaneously (if any)?

2. How many commuters concurrently are expected to access and (or) can be given access?

3. Size suggested for smooth running of application tools including GIS.

4. Provisions for future upgrades (if any).

1. Introduction










ITS allied supportO




MIS: A toolG






46

Introduction

Data Center

Fire safety


Cooling system

Security

Fiber/wifi

Support required for ITS – at control room and in buses, bus stops & stations

1. Introduction










ITS allied supportO




MIS: A toolG






47

Introduction



Having Intelligent Transport System (ITS) that conforms to international standards &supports the transport agency in providing efficient operation & management ofTransportation System for Mysore City.

Vision

Objective

Concept of ITS

Strategy

Strategic Agenda

Target Level: Improve Operation & Management of Intelligent Transport System by use of

GPS, GPRS, and data center for dissemination of information for transport management.

Strategy Level: To provide efficient, clean, safe, and commuter-friendly solutions.

Action Level: Implement GPS based vehicle tracking & monitoring system, and passenger

information system.

Transport Management

Bus Information


Electronic Payment



Improved Transport Efficiency & Productivity.

Tracking, data acquisition, and transmission of data for improved Road Traffic Management & Security.

Better services mobility & access to commuters.

Reduced energy use, emissions & noise.

1. Introduction










ITS allied supportO




MIS: A toolG






48

Introduction


➢ Components

• AVL

• Real-time PIS

(ETA/ETD)

• In-bus display

• CCC

• MIS reports

• EMS

• Training

• SMS & IVRS

• Fleet Management

• Commuter portal

➢ Scope

• 500 buses

• 167 display boards at

bus stops

• 2400 + bus stops

• 6 terminals


1. Introduction










ITS allied supportO




MIS: A toolG






49

Introduction



• Kick-off meeting• Site Survey• Route Survey• Bus Stop Survey• Site Plan Sign-

off• SRS• Project Plan• Implementation

Plan• Reviews &

Iterations• Finalize

• Power calculations• CCS room design• Communication,

database sizing• S/w specifications• H/w specifications• Design document

for VMU and PIS• Test plans for VMU,

PIS & SFAT• ETA algorithm• EMS• S/w Development &

customization

• FAT for custom hardware (VMU and PIS)

• Software FAT• Procurement of off-

the-shelf and custom hardware

• Software procurement

• Deliveries for full system

• Full system hardware installation

• Full system software installation

• ITS application configuration

• Training• System integration• POP & WIR• System acceptance• Rollout

Implementation

Testing & Operations

Procurement Planning Design & Build

Programme Mgmt.

Regular Review

Risk Mgmt.

Quality Mgmt.

1. Introduction










ITS allied supportO




MIS: A toolG






50

Introduction



Notes for trainer:Elaborate the above.

1. Introduction










ITS allied supportO




MIS: A toolG






51

Introduction



Data Center

• Servers – all configured in cluster mode (fault tolerance)

• Communication

• GIS

• ITS Application

• SMS/IVRS Applications

• PIS Display Board Applications

• Network & Firewall components

• Web application -(website – http://mitra.ksrtc)

• Internet connectivity 5 Mbps x 2 (redundancy)

• Higher capacity UPS - 2 x 20 KVA online UPS for failover

• Higher capacity DG set - 85 KVA Diesel Generator Backup


Command & Control Center



• Access Control


1. Introduction










ITS allied supportO




MIS: A toolG






52

Introduction






1. Introduction










ITS allied supportO




MIS: A toolG






53

Introduction

Case study: Mysore (Team structure)

KSRTC Mgmt

Representative


CMC Onsite Operations Mgr

Data center team

Network Engg.

Server Engg.

Desktop & PIS Engg.


Support Engg

In bus equipment team

Bannimantapa depot

Kuvempungara depot

Satgalli depot


team

EMS alerts

Monitoring Team

(Shared team)


KSRTC Operational Team

• DC

• DTO

• DME

• ITS in charge

• Depot Managers

• Assistant Works supervisors

• Assistant Traffic Superintendent / Traffic Inspector (ATS /ATI)

Key Roles of Operations Managers

1. Own complete operations

• Conduct review meeting

• Issue & escalations management

• Implementation & maintain SOP

• Monitor & control Service Level Assistance

2. Dispatchers/ Helpdesk

• Monitor & track buses through ITS

application

• Engage crew through audio mechanism

• Answer queries

• Schedule & Route

• Ticketing Management

• EMS alert monitoring

Capacity development –

➢ Exposure to KSRTC officers and staff for handling project

management professionally.

➢ Instructions manual for crew and staff.


CMC Mgmt

Notes for trainer:Elaborate the contents in the box

above & on the left.

1. Introduction










ITS allied supportO




MIS: A toolG






54

Introduction


1










requirements.

2





equipment.



3

The project was expected to be completed in 3 years but was completed in 6 years. Thereasons were:

Notes for Trainer:Explain the lessons learnt from the ITS project in Mysore city.Focus on the point that the project was expected to be completed in 3 years, but it took 6 years for actual completion.

1. Introduction










ITS allied supportO




MIS: A toolG






55

Introduction

5














8



4







1. Introduction










ITS allied supportO




MIS: A toolG






56


Notes for Trainer



Module Objective


• Understand the ITS technology and architecture of Fleet Management System.

• Understand various subsystem in the fleet management system wherein ITS can enhanceefficiency.

• Familiarize the audience with the role of ITS in fleet management system, what & how itdoes to improve efficiency.

• Output of fleet management systems is expounded with the help of case studies.

Module Notes

This module recognizes the role of ITS in system & subsystem; its focus is on how it can getefficacy in the conventional practices of fleet management. It also focuses on the "need tochange”, which is supported by a Case Study.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

57

Fleet Management System (FMS)

Overview

The subsystem in FMS is elaborated in the module on "bus operation." Types of MIS

reports and use in monitoring of services is also covered in the same module.

In this module, emphasis is on covering the ITS application aspect without repetition of

contents.

FMS


7

Emergency Mgmt.

6

Driver Standard

Compliance

5

Service Contract

Compliance

4

Schedule Adherence

3Route


Automatic Vehicle

Monitoring

1

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

58


ITS Technology

FDAS

Emergency Button

GIS Layer

AVM

Driver console

with VHMS

Camera

Notes for trainer:Notes on this slide are elaborated on

the next slide.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

59


ITS Technology

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

Notes for Trainer

• AVM - As per AIS 140: ITS requirement for public transport vehicle operation. The AVM shall be capable

of obtaining position information using Global Navigation Satellite System (GNSS). GNSS receiver

specifications are as follows:

• Device shall be capable for operating in L and/or S band and include support for NAVIC/IRNSS

(Indian Regional Navigation Satellite System) for devices installed on or after 1st April, 2018.

• Device shall support GAGAN, the Indian SBAS (Satellite Based Augmentation System).

• Device shall have a position accuracy of minimum 2.5 m CEP or 6 m 2DRMS.

• Device shall have an acquisition sensitivity of minimum (-) 148 dBm.

• Device shall have tracking sensitivity of minimum (-) 165 dBm.

• Device shall have an internal antenna, however, in case of integrated systems with

vehicle/aftermarket OEM approved kits, if the fitment location prevents the internal antenna from

functioning, external antenna shall be provided.

• Device shall have an internal back-up battery to support 4 hours of normal operations (to be

tested for positional record transmission at a frequency of 60 sec).

• Device shall be designed to operate between 8VDC and 32VDC using vehicle battery input voltage

range 12/24Volts..

• Emergency Panic Button – preferably to be used by commuters in case of emergency; duly

supported by cameras.

• GIS layer for mapping.

• FDAS – Fire detection & alarm system.

• VHMS – Vehicle health monitoring system.

60


ITS Architecture

Emergency

Breakdown

Report Accident

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

Notes for Trainer

The information on the location of the bus is tracked & sent to the server

through the Automatic Vehicle Monitoring (AVM) System which forms the

input for the concerned module. On receipt of processed information on

incidence, CCC follows the SOP laid down under incident management which

strives to cut down on the disruption that is likely to extend to other routes.

61



1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

Tracking

MISReports

Administration


• Dynamic status reports – GIS map tracking

• Scheduled replay

• Line Diagram

• Alerts monitoring

Route Settings

• Add, delete, cancel trips

• Reschedule trips

• Reason for breakdowns

• Create and upload files to VMU required for

scheduling

VMU Management

VMU ID configurations

GSM/GPRS Parameters

VMU health check

Send command messages to VMU

Generate various MIS reports

TC/KSRTC Supervisors can analyze and enhance operational efficiencies

Reports are downloadable in different formats

User creations and management

Role-based access

Master data management

Alert configurations

62




Source: Lumiplan

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

63



1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

Challenges:

1. The volume of commuters increases during these occasions.

2. Often such occurrence takes place over multiple days and passenger movement (arrival and

departure) happens throughout the entire duration.

3. Passenger demand cannot be managed with daily scheduled operation.

4. Bus parking capacity at the venue is often unknown.

5. Hence, special arrangements for catering to this extra load have to be made with utmost care and

precision.

MIS data

• Previous year's performance –

ridership trends, no. of trips

per day, no. of vehicles used,

no. of crews required, the

requirement of other staff, etc.

• Trends over the last two

years – increasing/decreasing

in correlation with adjoining

public holidays/off day.

• Based on past MIS data, trend

analysis is carried out to

quantify the total number of

buses required, considering

holidays, weekends, and

weather forecasting.

Management of fleet for operation of buses

1. For a major part of the operations, fleet from the nearest

depot is taken to avoid dead kms. and losses.

2. In case of shortfalls, based on MIS data on fleet strength ofother nearby depots, instruction is given for supplying spare

buses with the crew to the venue/temporary bus stand.

3. In case of an unprecedented increase in passenger demand,

at any point in time, leading to demand for extra buses, ITS

plays a crucial role by using the vehicle tracking solution.Under this, CCC tracks the buses in special operations and

other scheduled buses (nearby vicinity) with an expected

time of arrival at the stand. Based on this, CCC takes a call

to:

a) either wait for the arrival of special operations buses or,

b) instruct bus drivers who are in the nearby vicinity for re-

routing scheduled bus/buses to cater to the rising demand

with due consideration to no. of passengers on board.

64






1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

Notes for Trainer:

ITS offers a continuous real-time view of performance tracking.

65



Source: Lumiplan

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

Notes for Trainer

The report is generated automatically and can be accessed on the ITS dashboard

from the Manager’s mobile or laptop any time.

66



Note for Trainer: Electronic Control Unit (ECU) - embedded system in automotive electronics that controls

one or more of the electrical systems or subsystems in a vehicle. It is like a brain, Vehicle CAN (Controller

Area Network) - is a robust vehicle bus standard designed to allow microcontrollers and devices to

communicate with each other in applications without a host computer. It is like a nervous system.

Driver console comprises of the following:

• Vehicle health monitoring system (VHMS).

• Communication aid for the driver.

Communication aid for Driver

Each time the driver accelerates or brakes sharply or over speeds; CCCrecords the information and flashes a warning to the driver on the driver’s

console. For example, in case of over speeding, it flashes "Go Slow," as

shown in the picture.

Communications to the crew are also passed through the console.


More than 100 parameters are loaded in VHMS for monitoring vehicle health. ECUpresent in the vehicle sends information to SCU "Signal Control Unit" through

vehicle CAN. The SCU, which is enabled with GPRS/latest communication

technology, communicates the information to CCC. The ITS server at CCC

processes the data, i.e., coding & decoding, and as per the severity set in SOP,

the information is escalated. The information sent to the officer is mostly in the

form of an SMS. An illustration of the SMS is provided on the right.

The detailed information can also be made available through Wi-Fi or OTA (over the air), etc. This

information is essential for non-ITS system, especially for carrying out preventative maintenance of the

vehicle.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

67



Notes to trainer: In FDAS picture, zones 1, 2 & 3 are areas demarcated by OEMs in the Engine

compartment.

ITS application module in Incident management comprises of the following:

• Incidence - Fire incidence, Breakdown.

• Emergency button.

• Cameras & data storage.

Cameras & data storage

The purpose of on-board cameras is as follows:

• For enhancing the safety & security of passengers and luggage on board

• Assistance to driver especially while reversing.

• In case of incidence, data from DVR can be extracted for further investigation.

• Data can be the transferred via. Wi-Fi or OTA or through other communication. Theduration for which the data can be stored in DVR is a function of the size of the data

and the capacity of DVR.

A potential area of fire hazard is the engine compartment against which Fire Detectionand Alarm System (FDAS) & Fire Detection and Suppression Systems (FDSS) are

present in the bus. In case of a fire incidence, in the engine compartment, the FDAS (as

shown in the picture) triggers the alarm in the bus and also sends communication toCCC. To avert the loss of life & property, CCC responds as per the laid down SOP.

Meanwhile, the driver, through the passenger announcement system, intimatespassengers to de-board the bus.

Emergency Button

When the emergency button is pressed by passenger/crew to indicate safety/panicsituation caused by human or natural disaster or vehicle incidence, etc., the SCU

communicates the information to CCC. The ITS server at CCC process the information

and acts upon it as per the severity set in SOP. The concerned officer gets the

information in the form of SMS and even a telephonic call.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

68



Source: APSRTCNote for Trainers: The report is generated automatically and can be accessed on

the ITS dashboard from the Manager’s mobile or laptop any time.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

69


Notes for Trainer



Module Objective


• Educate participants about ITS technology & architecture required for ticketingmanagement system.

• Understand various cashless options which can be implemented in public transport.

• Upgrade the conventional way of ticketing management by adopting latest technologiesavailable. Ways in which ITS supports’ in implementation with the help of a case study.

• Improved decision-making - Extending ITS information generated to other allied systemsand their confluence with available data leads to the collection of information, based onwhich correct & fast decision/s can be taken.

Module Notes

This module, recognizes the role of ITS in system & subsystem and concentrates on:

• How ITS can increase the efficiency of existing ticketing management system.

• Cashless, transparent, and fast transactions.

• Generating information viz, ridership vs. revenue.

Case studies support the deliverables.

1. Introduction











Automatic daily pass vending machineC

Smart cardsD

Common mobility cardsE

Case study: SuratF

E-walletsG

Digital wallets and E-walletsH

Case study: APSRTCI

Case study: SuratJ

Revenue reconciliationK

70



Notes for Trainer: IT enables ease ofAccounting and saving of Time, for usersas well as for conductor, operator etc.

Notes for Trainer: Integration of all cash & cashlesstravel, and reconciliation of total revenue earnedencompasses ticketing system management.

Electronic Ticketing Machine

Pass System

Card System

M Ticketing

Digital Wallet

E-Wallet

Pole validator

Gate Validator

Ticketing options shall address all the requirements of the customers

Cash Cashless

Server & payment gateway

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


71



Instructor: Earlier, bus & route information were updated by the exclusive team of dispatcher and issue of ETMs

was done separately. Now optimization of workforce and improvement in efficiency is obtained by issuing IT enabled

ETM. As soon as ETM is issued to the conductor, the information of bus & route get updated in other allied system

including route information on bus. Duplication of work is removed.

Electronic Ticketing Machine (ETM) Master data pertaining to unit fare charges for adult/child and luggage,

concessions, route, and bus service are uploaded on the ETM. Once the configuration is over, the ETM is ready for use

during the journey.

Reports generated:

1. Ticket Details – no. of tickets issued to Adults, Child, etc.

2. Validation of Pass viz., through ETM for Students, Elected Representatives, specially

abled and Freedom Fighters etc.. and report generated thereof.

3. Payment made through ETM towards Bus Stand Fee, Tollgate Fee and Bridge Fee

and report generated thereof .

4. Revenue Collection Report.

5. Status Report.

Multipurpose: Enables the conductor to issue tickets/passes/card.

Information Generation: Information on revenue collection is made available in real-

time by transmitting the transaction data to the back-end server through wireless

connectivity.

Safe & Efficient:

• ETMs usage is possible only through a combination of PIN and password. It

facilitates downloading of updated route or fare information through wired or

wireless connection.

• Efficient reconciliation of revenue – less time is required for settlement at the Cash

Counter.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


72


Automatic daily pass vending machine

One of the main attractions of a vending machine is its low maintenance cost, which lowers the overheads,

and occupies less space, simple in operation and is portable. Unlike the ticketing counters, there are no staff

requirements, which means the authority does not have to deal with staff cost, allied leave, etc., and a

machine will happily work 24 hours a day, 365 days a year.

CIRT had undertaken a study on the "impact of daily pass on revenue" in case of discontinuation due to resale

of preprinted daily pass by the passengers. After the study, it was recommended not to discontinue the day

pass; however, should make provision for photographs to avoid resale of a daily pass.

The machine has a user-friendly touch

screen, and software. Passengers can

select preferred languages viz,

English/Hindi/ local language for

communication.

The machine provides commuters with

the facility to buy a daily pass and avoid

long queues at the counter. Passengers

have to select the pass option followed by

getting a picture clicked and finally

payment processing.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


73


Smart cards


1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


Note for Trainers: Schematic map of automatic fare collections system. The trainer may elaborate the same.

74


Smart cards

• The Smart Card must be compatible with

“National Common Mobility Card”

specifications.

• Testing of read & write of Smart Card with

ETMs is a prerequisite.

• Coding for reading real card is also required.

• RBI clearance is essential.

Benefits –

• No upfront costs are involved.


1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ



CustomerFriendly

Customers can use the same card for Metroand Bus travel in all the cities and states.




Loyalty Points Loyalty Points Consumers may benefit frompartner banks' loyalty/reward points, asprovided with Debit and Credit cards




Each Public Transport Operators needs tobear significant expenses for maintenanceof infrastructure and workforce for cardissuance, top-up, card replacement, andrefunds.

75


Smart cards

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ



Negotiating Power

As Open-loop acceptance devices are based on open interoperable standards, there are multiple vendors available for payment acceptance devices, which provides an opportunity for cost and service negotiation.

Closed-loop cards may be of proprietary standards, leading to vendor lock-in for subsequent purchase and renewals of acceptance devices.

No vendor lock in

Open standards based payment acceptance devices provides the freedom for subsequent purchase and renewals of devices.

Proprietary standards may lead to vendor lock-in for subsequent purchase and renewals of acceptance device


Well standardized payment acceptance devices and availability of multiple vendors provides ease of implementation. Payments related scope of work to be taken care of by the partner bank and hence PTOs may focus on their key activities.

PTOs need to evaluate multiple proprietary specifications leading to difficulty in implementation.

Fast Deployment

Due to similar implementation process, best practices, and reference implementation guidelines, there will be standardized procurement practices, and RFPs. This considerably expedites the deployment of digital payments in Public Transport Operators.

Each deployment will have specific requirements and each Public Transport Operators requires considerable expertise for the selection of an appropriate solution

Retail acceptance


Closed-loop cards can only be accepted within their operating environments.

76


Common Mobility Cards (CMC)

National Common Mobility Card (NCMC), also known as One

Nation One Card, is an inter-operable transport card conceived

by the Ministry of Housing and Urban Affairs (MoHUA) of

the Government of India (GoI). It was launched on 04 March

2019.

The transport card enables the user to pay for travel, toll duties,

retail shopping, and withdraw money. It is enabled through the

Rupay card mechanism. The NCMC card is issuable as a prepaid,

debit, or credit RuPay card from partnered banks such as

the State Bank of India, Punjab National Bank, and others.

The NCMC is an indigenously made product, and is a part of the ”Make In India” project. It was first

conceptualised in 2006 as part of the National Urban Transport Policy (NUTP).

The card has dual interface (contact & contactless) and is interoperable. Thus, it provides solutions to low

value payments for various segments e.g., Transit, Smart cities, Toll, Parking, and other low value merchant

payments in addition to the normal day-to-day retail payments. These specifications supports not only

payment products but also transit applications like passes & government applications such as social security,

driving license, Id/access card etc.

The urban development ministry tasked the National Payments Corporation of India (NPCI) with

management, clearing and settlement of payments, simulating cards and terminals, and maintenance of

network. Bharat Electronics Limited (BEL) has created the reader prototype.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


77


Case study: Surat



Surat Money Card


Source: Lumiplan

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


78


Case study: Surat

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


Note for Trainers:

1. ETM with POS [Point of Sale]: POS offers functionality to conduct activities like issuing

smart card, QR code based paper tickets, topping up smart cards and handling customer

queries related to ticketing. POS has the ability of ticket issuing/cancelling/refunding/

adjusting etc. POS devise reads and writes from all the fare media as defined in the

business rules.

2. Turnstile Type Automatic Gates with ticket validators: Automatic Gates are equipped with

acceptance infrastructure capable of reading and authenticating all types of fare media.

The acceptance infrastructure shall interface with the gates for communicating the access

controls.

3. Bus Pole Validator - For on-board transaction pole validators are used.

4. Money Card - Cashless smart card technology in transportation as well as in retail areas.

79


E-wallets

Operational Mechanism:

Under mobile or electronic wallets, the individual pre-loads cash in the e-wallet and uses it to make payments

or transfers. Money is loaded either electronically (using a computer/mobile) through a credit card or bank

account, or physically by handing over cash to a local merchant (point of sale [POS]) or at the ATM counters.

What is required is an internet connection and a mobile /computer. With the technology in place, mobile-

based operations through e-wallets have become a mode for financial inclusion.

There are charges for mobile / e-wallet, which includes registration fees and cash loading charges(above a

limit) towards payment companies/service providers. These charges are at times higher than those for

internet banking. However, the main advantage of e-wallet is that while shopping online, the customer stands

to benefit from the concessions/ offers from the payment companies in the form of cash-backs, etc.

Benefits of e-wallets

The use of debit cards requires access to the designated point of sales and ATM counters. However, in the

case of e-wallets, money moves along with the holder, and he can access it from an instrument held in his

hand – his mobile or computer, giving much flexibility for the account holder. Further, e-wallets avoid the

dangers associated with card thefts.

For those who stay far away from ATM/bank branches, as in rural areas, money is still accessible to them at

the click of a button. In case of any requirement for physical cash, they just need to go to the nearby banking

correspondent or a local merchant who can double up like an ATM. Thus, e-wallet comes handy for those who

do not have a bank account, net banking, or credit card, especially those who may otherwise be ineligible for

receiving them. At present, services are not generally designed to handle significant payments. The use of e-

wallets help in moving away from a cash-based economy. In the process, all the transactions get accounted

for in the economy,which helps in reducing size of the parallel economy.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


80


Types of e-wallets permitted in India

As per the Reserve Bank of India, there are three kinds of e-wallets in India: closed, semi-closed, and open.

Closed e-wallets: The company/entity issues wallets for facilitating purchase of goods and services sold by

them (or) in other words, money stored in these wallets cannot be used for transactions with any other

company. These wallets/instruments do not permit cash withdrawal or redemption. Closed wallets are online

accounts, where money gets credited in case of a refund on account of a cancellation or return of a product or

service. Some companies even earn interest on these deposits.

As these instruments do not facilitate payments & settlement for third party services, issuance and

operationalization of such wallets are not classified as payment systems. Hence, RBI approval is not required

for issuing them. e.g., companies like Flipkart.com, Makemytrip.com, Bookmyshow.com, etc.. issue closed

wallets to their consumers.

Semi-Closed e-wallets: These wallets can be used to transact online and offline, including buying goods and

services, financial services, payment of fees, premiums, etc., through/to merchants, which have a specific

contract with the issuer to accept the payment instruments. These wallets do not permit cash withdrawal or

redemption by the holder. An RBI approval is required to start and operate a semi-closed wallet.

Since these wallets are handled by non-banking agencies (banks and non-banking financial agencies cannot

issue semi-closed wallets), they are required to deposit this money in an escrow account with a partner bank.

Interest on these deposits depends on the agreement between the payment company and the bank. Wallets

for amounts up to Rs.10,000/- can be created under this category by accepting minimum details of the

customer, provided the amount outstanding at any point in time does not exceed INR 10,000/- and the total

value of reloads during any given month also does not exceed INR 10,000/-. Amount up to INR 50,000/- can

be created in wallets by accepting any 'officially valid document' which is compliant with anti-money

laundering rules. E.g., Paytm Wallet, Freecharge Wallet, Citrus, Oxygen, etc.

E-wallets

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


81


Wallets amounting up to INR 10,000/- can be created under this category by accepting minimum details of

the customer, provided the amount outstanding at any point of time does not exceed INR 10,000/- and the

total value of reloads during any given month also does not exceed INR 10,000/-. Amount up to INR 50,000/-

can be created in wallets by accepting any ‘officially valid document’ which is compliant with anti-money

laundering rules. Amount up to INR 1,00,000/- can be created by with full Know Your Client norms (KYC) and

can be reloaded. Example:

1. Paytm Wallet,

2. Freecharge Wallet,

3. Citrus,

4. Oxygen

5. AirTel Money, which is used for making payments for a range of services like money transfer from Airtel

Money to another bank account or any other Airtel Money Wallet or paying select utility bills is an example

of Semi Closed E Wallet

Open e-wallets: Open Wallets can only be issued by banks or in partnerships with banks. These wallets can

be used to perform all the transactions of a semi-closed wallets plus withdraw cash at ATMs or banks and

transfer funds. However, cash withdrawal at POS is permitted only up to a limit of INR 1000/- per day subject

to the same conditions as applicable on debit cards (for cash withdrawal at POS). Example:

1. M-Pesa is an open wallet run by Vodafone in partnership with ICICI Bank.

2. Axis Bank’s e-Wallet Card’, can used for making payments on sites that accept Visa cards, with a minimum

limit of INR 10, and a maximum limit of INR 50,000, and a validity of 48 hours.

3. Pay Zapp by HDFC Bank, etc.. are few open wallets in India.

E-wallets

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


82



1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


Digital Wallet E-Wallet

Card details are saved in the wallets which

enables card-less transactions.

Money is preloaded in the wallets to transact

card-less.

Money remains in user's bank account or

credit card.

Money moves from user's account to either a

merchant’s current account or an escrow

account.

Example - Masterpass, Google Wallet, Apple's

Passbook.

Example - Paytm Wallet, Freecharge Wallet,

Mobikwik.

83







1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


84


Case study: Surat (Ridership and revenue)Source: Lumiplan

Top/Last 5 Stops and Route – Ridership and Revenue Hour basis Ridership and Revenue


1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


Note for Trainer:

• Explain overview of AFCS.

• Information from AFCS helps the management to know where we are – w.r.t no. of passengers carried,

revenue collected, top/ last 05 performing & non performing routes etc.

85



An urban passenger transport system often has multiple revenue sources, ranging from on-vehicle sales

to quantified subsidy payments, and multiple beneficiaries of those revenues, ranging from the

operators to the public authority. Robust procedures are required so that all revenues are accounted for and

reconciled before making payments to them. The reconciliation process may be manual or computerized in

traditional fare collection systems, but can be automated through a clearinghouse in electronic systems. The

latter has advantages in terms of accuracy, security, and speed.

Ticket sales consolidation: Consolidation of sales revenues varies in complexity depending on the scale of

activities and the range of revenue sources. It is simplest among owner-drivers who only collect their

revenues and most complex where the fares collection system may involve several operators with their

collections accruing from on-board sales by crew, sales from automated vending machines in various

locations, and off-system agents, and internet-based sales channels. Allied to the sale method is the creation

of robust audit trails that routinely tracks revenues from these sources through to the collated deposits in the

banking system so that the movements are fully captured and evidenced. This process also enables primary

data to be collected on revenue sources and allocations for inclusion within the routine management

information system.

Ticket validation conciliation: Validation of travel documents is essential in verifying that legitimate travel

is being undertaken and that the validated travel value has been correctly deducted from the tickets/passes,

and correctly recorded. The validation processes may be complex, where several operators are involved. It

may arise from on-board validation by the crew [either manually or by a machine] or on-vehicle or off-

system free-standing validators. The purpose of conducting validation is to identify the vehicle, route, and

operator involved in the travel undertaken and the cost of that travel. This information is then used as

routine management information data on travel activities and revenue allocation purposes. It can also be

used for verification of payments related to travel undertaken by concessionary pass holders. Allied to the

validation method is the creation of robust audit trails that routinely track the correct allocation of revenues

accrued to various service providers.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


86



Communications: Manual revenue collection systems [that is, those incapable of electronic data transfer]

generate clerical or computerized control systems to verify if revenue management processes have been

reconciled. They also enable identification of any variations for investigation and correction. Complex fares

systems and those systems with many crew, vehicles, operators, and locations require significant manual

input to validate that systems are functioning as planned. Such systems are prone to human error, and may

also be targeted for fraud. Electronic fare collection systems are inherently more accurate and secure but

involve transmission of large volumes of data. Data transfer from a vehicle to its operating base or centralagency can be achieved in real-time with mobile radio communication, or at the end of the duty by physical

data transfer or local communication. However, the volume of stop-based transactions is generally far higher

than on a single vehicle, and data transfer to the central agency then usually requires fixed links such as

high-capacity copper or fiber-optic cable. Consolidation at depot level requires even higher communication

capacity for the central agency, and this will require fiber-optic cable.

Revenue reconciliation: In simple terms, revenue reconciliation is the balance of sales generated to fares

validated over any given period. There are various ways in which travel is sold to passengers, various ways in

which passengers validate their ticket products for travel, and then various ways in which these activities are

communicated to the fares system operator. These have been described in the preceding sub-sections. On ascale of complexity, traditional fare collection systems generate more manual recordings and require a series

of individual inputs, each of which requires reconciliation. In case of any variation, an investigation needs to

be undertaken until reconciliation is established. These processes are time-consuming and prone to human

error or fraud but most can be computerized after the initial data entry.

However, modern electronic fare collection systems lend themselves to automated revenue reconciliationmechanisms which is managed through a clearinghouse that is provided either by the fare collection agency

or the system integrator on its behalf. The financial clearing system has to be robust and accurate and

trusted by all affected parties. This function, and its software capability are central to the successful

implementation of an electronic fare collection system. In either case, the revenue reconciliation process

should enable an array of analytical reports to be generated at any time, place, product and class, series so

that an overview of activity levels can be established. These analytical tools require computerized systems,

and cannot be replicated cost-effectively in the manual revenue management systems.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


87


Notes for Trainer

General Information on the SessionApproximately 20 min.

Questions:Q1. What information do the passengers require to plan the journey, during the journey, andat bus stop/station to board the right bus?Q2. What must middle managers know before going for ITS in passenger information system?

Module ObjectiveThe objective of the module is to:

• Realize essential information required for planning trips from passenger’s perspective.

• Understand latest trends in passenger information system viz., DOOH - Digital out offHouse, LCD monitor, information of ‘number of commuters on-board’ to off-boardpassengers on their mobile, provisions of setting alert for time of departure from home etc.

• Outline the ITS architecture required to support PIS for maximum outreach.

• Case studies (including video) are used to support the above objectives and for elaborationon ITS application in PIS.

Cross reference - Major challenges in implementation of PIS is covered in management ofoperation under “Bus Operations Module”.

Module Notes

This module, recognizes the role of ITS in system & subsystem and concentrates on:

• How ITS can increase the efficiency of existing ticketing management system.

• Cashless, transparent, and fast transactions.

• Generating information viz., ridership vs. revenue.

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


88



1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


Passengers require the following information to plan the journey:

1. Real-time information like route-wise arrival & departure of buses.

2. Type of service (A/c, Ordinary/Express etc.).

3. Approximate travel time for reaching the alighting point.

4. No. of passengers on board, whether to board the bus or wait for the next bus.

5. Next bus on the same route.

6. Fare for the trip, options for cashless transactions.

7. Information on alternatives options at the alighting point, for reaching to the destination.

8. General advice on disruptions en-route (if any).

Passengers require the following information during the journey:

➢ Route and trip details at the start of the trip– start time, likely trip duration.

➢ En-route stops – current stop and next stop at every halt to facilitate alighting.

➢ Connecting routes/modes/transfer characteristics/timings etc. at transfer locations.

➢ Last mile connectivity details at arrival stations at the end of a trip.

➢ Crew details to record feedback on their behavior.

➢ In-journey information is required for all pax including Persons with Disabilities (PwD) through –audio-video pre-

recorded synchronized announcements/displays on-board.

Passengers require following information at BQS to board the right bus:

✓ Route map and operating time table.

✓ Route no. and route destination, of arriving bus.

✓ Arriving Bus category – AC, express, ordinary, limited stop along with tariffs, if possible.

✓ Information as audio- video synchronized announcement/displays as bus stops – particularly useful for PwDs to

enable them to board the right bus without any other help.

89


ITS Technology

Source: Lumiplan



inside



1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


90


ITS Technology



1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


Note for Trainers:

• Explain the above technology.

• DOOH – this is a new technology in which energy consumption is less and PPP models may be

implemented. The screens are eye catchy.

91


ITS Architecture


Streaming server aids in providing advertisement between the updates of real-time passenger information system.

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


92


Case study: Mysore


➢ Components

• AVL

• Real-time PIS (ETA/ETD)

• In-bus display

• CCS

• MIS reports

• EMS

• Training

• SMS & IVRS

• Commuter portal

➢ Scope

• 500 buses


bus stops


• 6 terminals

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


93



1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


Objective

• Promote intelligent travel to commuters.

• Reduce waiting time of commuters.

• Provide safe & quality travel.

• Journey planner for commuters.

• Feedback mechanism for citizens.

• Real-time bus arrival reminder.

Overall Features

Source: ppt on “Integrated Intelligent Transport System (IITS) in Navi

Mumbai” by NMMT source internet

Ease

of

Travellin

g

Tic

ket

&Pass

Bookin

g&

Safe

ty

Ease

of

Managem

ent

Real-time bus

information

Reminder of bus

arrival

Travel information

sharing vis WhatsApp

and SMS

Real-time availability

of seats in buses

E-ticketing through

mobile app

Smart card recharge

through mobile app

Online pass approval

through app

Safe travel through

SOS service

Feedback system of

User

Monitoring system

from Control center

Announcement to

commuters on latest

offerings

Document approval

for availing pass

94




1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF

Case study: Sitilink SuratG Users can see Real-time

information on bus arrival

and departure

Users can see nearby bus stops

along with walking time

Users can see the last stop of the running

bus

Users can set the alarm to

remind him/her to reach bus

stop

Users can set favorite/frequent routes from a bus stop as per the

travel requirement

Users can share their traveling

details with anyone through WhatsApp

& SMS

User can see the latest

announcements made by NMMT

Features

2 3 4 5 6 71

95




1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF



location

Information about all

running buses(In green) as

well asScheduled

buses (in blue)


number bus inAPMC Market Bus

Stop

Share yourtravelling detailsw ith your friends/ relatives to takethem on-board in

the same bus

96


Case study: DIMTS (Mobile applications)Poochh-O by DIMTS Mob App for commuters


1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


Note for Trainers:

• Elaborate the workings of the app.

• This is one of the few apps which gives advance information on possiblity of getting a seat in the bus.

97



Sitilink mobile application offers citizens a medium

to plan their journey in an efficient way. Surat

Sitilink application provides multiple options listed as

below:

▪ Journey Planners

▪ M-ticketing

▪ Route and Stops Information

▪ Route Map

SMC Department vehicle application is developed

for real-time vehicle tracking and reporting. It is also

used for initiating operator billing based on AVLS

Data.

Sitilink Supervisor application is developed for

Sitilink operations.

Source: Lumiplan

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


98




Source: Lumiplan

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


99

Preventive Maintenance Management Systems

Notes for Trainer



Module Objective

For breakdown free operation of buses, it is a pre-requisite to have a fleet that has undergonepreventative maintenance as per the schedule. So, the objective of this module are to:

• Elucidate types of preventive maintenance schedule with the basis for scheduling.

• How confluence of IT & ITS aids in decision-making.

• Understand the usage of IT in fuel management systems.

Module Notes

After highlighting the types of maintenance practice, the IT-based systems concentrate oncreating master data with IT architecture supporting the extraction of input from ITS basedsystem (example- information on kms run by each bus). The confluence of such informationleads to increased efficiency in:

• Scheduling preventative maintenance activity without affecting the operation.

• MIS report generated aids in evaluation of performance .

1. Introduction









Operation-Maintenance InterfaceA

OverviewB

Preventive maintenance schedulesC

Planning of fleet using ITD

Preventive maintenance schedulesE

Creation of Bus Master FileF

Fuel Management Systems (Overview)G

Input – Use of ITS and MIS in FMSH

Output – Use of ITS and MIS in FMSI

100


Operation – Maintenance Interface

1. Introduction










OverviewB








Operation Maintenance

Fleet required for Day-to-day operations

Events fairs, & festivals

and

Availability of spare buses

Workforce availability for

Day-today operations


and

Extra crew available, if any

Intake of fleet Capacity of the depot /

workshop

Buses (if any) lagging

behind schedule due to

various reasons

and

Availability of spare parts

for subject maintenance

Workforce availabilityAgainst each type of

maintenance

and

Extra staff that can be

made available, if any

101


Overview

Preventive maintenance is defined as a service undertaken by technicians to maintain the bus

in a satisfactory operating condition in order to avoid breakdowns and major operational

failures. Maintenance standards play a significant role in defining vehicle operating costs,

levels of safety and reliability, and pollution. Preventative Maintenance is a decisive factor for

smooth functioning of an effective bus system. The benefits of preventative maintenance are

as under:

• Prevent mechanical failures with a target of zero breakdowns during service provisioning.

• Reduction in emissions.

• Improving fuel efficiency thereby resulting in a reduction of fuel costs.

• Comfort, convenience & safety is prioritized through preventative maintenance.

• The service life of buses are improved.

• Preventative maintenance is less expensive compared to breakdown maintenance which

improves service reliability.

• It also improves safety by reducing the incidence of failure of safety-critical components

such as brakes, tires, and steering mechanisms.

• It helps in anticipating and initiating repairs.

1. Introduction










OverviewB








102


Preventive maintenance schedules

Generally preventive maintenance is set out on the following guidelines:

1. Manufacturer’s warranty requirements / recommendations.

2. Usually conducted at fixed intervals and at intervals as per legal requirements.

3. Criteria is merely borrowed from other transport agencies.

Based on the above criteria, preventative maintenance schedule is streamlined as illustrated

below:

Maintenance Schedule Preventative Maintenance Schedule for Activity

Schedule 1 Daily Maintenance Time-based

Schedule 2 Fortnightly Maintenance Time-based

Schedule 3 Quarterly Maintenance Time-based (or) Kms. based (or) as per OEM’s

recommendation whichever is earlier

Schedule 4 Annual Maintenance Time-based (or) Kms. based (or) as per OEM’s


• In addition to the above, accidental & heavy repair work is also to be carried out though

they are not part of preventative maintenance.

A broad checklist of activities that need to be carried out as per the above schedules are given

in the participants manual.

IT plays a crucial role in tracking (w.r.t due date, date of maintenance completed & kms.

covered) and execution (send alerts to the concern officers) of explicit activities in each

schedule.

1. Introduction










OverviewB








103


Planning of fleet for preventive maintenance using ITIllustration

1. In Urban transport, it is expected that maximum buses are to be kept on-road during the day

to meet passenger’s demand with only a few buses remaining in the depot which are due for

quarterly or annual maintenance or in need of heavy repairs.

2. The maintenance management software aids in quantifying total load for schedule-wise

maintenance activity. The table below illustrates schedule-wise workload shown for a depot:

Depot Total fleet

available

Schedules to

be operated

Schedule 1 Schedule 2 Schedule 3 Schedule 4

01 100 90 90 8 1 1

3. Shift-wise load is to be segregated based on the following info:

a. Time required to complete the scheduled activity.

b. Request from the fleet management team for want of any specific bus to be taken on

priority.

c. Availability of spare parts, as required, for carrying preventive maintenance activity for

the bus.

d. Generally, for urban transport, it is recommended to plan the shift which is dynamic

based on incoming bus flow. However, bare min. no. of buses, i.e., at least 2-3 vehicles

shall be made available before starting the shift for optimum utilization of the

workforce.

e. Non-core activities shall be outsourced, for example, cleaning & mopping of buses, tire

pressure check, tire puncture removal, driver for moving the bus within the depot etc..

Accordingly, in-house workforce requirement will reduce on account of such

outsourcing.

1. Introduction










OverviewB








104


Planning of fleet for preventive maintenance using ITIllustration

Preventative Maintenance Schedule No. of buses Shift Artisan Helper

Schedule 1 90 1700hrs to 0200hrs &

2200hrs to 0630hrs

14 14


2200hrs to 0630hrs

04 04


0800hrs to 1700hrs

10 10

Schedule 4 1

Heavy Repairs & Oil Change 1700hrs to 0200hrs &

2200hrs to 0630hrs

3 3

Low KMPL vehicle attending & fuel performance monitoring

1700hrs to 0200hrs &

2200hrs to 0630hrs

2 2

Vehicle Examiner In-line with operations 2 2

tires preparation 1700hrs to 0200hrs &

2200hrs to 0630hrs

2 2

Depot Stores 0900hrs to 1800hrs &

0800hrs to 1700hrs

- 2

Battery & Electrical maintenance 1700hrs to 0200hrs &

2200hrs to 0630hrs

2 2

HSD oil top-up 1700hrs to 0200hrs &

2200hrs to 0630hrs

- 2

Body Fitter, Welder & Painter 0900hrs to 1800hrs &

0800hrs to 1700hrs

3

42 43

Table below outlines shift-wise estimated workforce required to complete the scheduled maintenance activities for depot 01 having fleet of 100 buses.

1. Introduction










OverviewB








105



Snapshot shows buses due for schedule 2, 3 & 4 of preventive maintenance.

1. Introduction










OverviewB








106


Creation of Bus Master File and updating bus wise spare parts consumption

The snapshot gives vehicle related information such as the make, capacity, engine horse power, engine & chassis no..

The snapshot gives information on bus-wise material used. This information is useful in maintenance management.

1. Introduction










OverviewB








107


Overview on Fuel Management System

IT application in fuel management ranges from receipt of fuel at the depot to consumption offuel by vehicle and recording the same.

Source: ppt of Dr K N Ingalgi, BMTC

1. Introduction










OverviewB








108


Input - Use of ITS and MIS in Fuel Management Systems

It is the format in which vehicle-wise fuel issue record is maintained. This information can be used as an input for MIS of the fuel management system.

1. Introduction










OverviewB








109


Output - Use of ITS and MIS in fuel management systems

The MIS Report Generated includes:

• Daily Fuel Consumption Statement

• Depot-wise HSD Statement

• Daily KMPL Statements

• Master Statements

• Monthly HSD Inventory Statement

• Vehicle-wise KMPL Statement-Daily

• Individual Vehicle-wise Statement

• Low KMPL Vehicle Statement Daily

• Model-wise Vehicles KMPL Statement

• Vehicles-wise ABC KMPL Analysis System

• Driver-wise KMPL Statement- Daily

• Low KMPL Driver Statement - Daily

ITS Application – Sample Report


1. Introduction










OverviewB








110

Inventory Management Systems

Notes for Trainer



Module Objective

The objectives of this module are to:

• Provide information on IT enabled Inventory Management Systems.

• Using IT, create database & master list, to reduce the investment in inventory & to re-orderat an appropriate time.

• Ensure less vehicle downtime, especially on reason “for want of spares.”

Module Notes

The module covers the need for inventory management wherein use of IT aids in the followingways:

• Precisely assess the order quantity (based on past consumption trend) and predicts the re-order point.

• Controls investment in inventory.

• IT makes it possible to manage the inventory effectively by tracking the item in demandfor availability in any other unit/s.

1. Introduction









Need for inventory managementA

Database: Creation of individual itemB

Requisition slip and Issue slipC

111


Need for Inventory Management

1. Introduction












Status of

availability

Effective use of

Capital

Reduction in

risk of loss


It gives a clear picture of the

constant flow of materials into

and out of the existing

inventory.

The reports on inventory helps

understand the stock position &

how to address demand;

triggers are sent at the right

time to recoupment/replenish.

The activity will aid in

investment control and planning

of maintenance orientated

operations.

The inventory management can

help in improving the demand

forecasting by analyzing data

trends from the past data. This

minimizes holding and handling

costs, reduces the investment,

and eases cash flows.

112


Database: Creation for individual items

The image is a format, in which the store department collects detailed information about the part as a database.

The snapshot shows the master list for some of items whose detailed information is collected.

1. Introduction












113


Requisition slip and Issue slip

The depot sends the requisition slip to stores department. On the same day, the store issues the required items, as available with them.

1. Introduction












114

Workforce Management Systems

Notes for Trainer



Module Objective

The objective of this module is to provide insights into Workforce Management Systems. Themodule describes IT initiatives, which include leave management & crew management.

Module Notes

The module covers the following topics:

1. Leave management systems – provides benefits, processes, and features of leavemanagement systems along with the screenshots for applying for a leave.

2. Crew management systems – provides features and benefits of crew managementsystems along with the design framework.

1. Introduction









Need for Workforce managementA

Leave management systemB

Crew management systemC

115


Need for Workforce Management Systems and benefits thereof

1. Introduction












For a public transport, management of workforce plays a very crucial ro le and has significant impact both on

operations as well as maintenance functions. The use of IT, has improved the efficiency of workforce planning

& management.

IT initiatives in workforce management are broadly classified into following subsystem:

1. Leave management system

2. Crew management system

Benefits of Leave Management systems

• Builds confidence within the staff that the system is notdriven by humans and follows all rules and regulations.

• Easy to use;

• Touch Screen Kiosk is similar to ATM.

• Audio instructions in local language for the employee

to navigate to the next step.

• In-built Printer to give leave application

acknowledgement.

• SMS confirmation of leave sanction or rejection

decision.

• Secured;

• Biometric authentication to allow employee access

system.

• Since the data is stored in a centralized server, so is

secured/no tempering of information at the local level.

Since the data of leave application is received in aconsolidated form, for unit head it becomes easier to take a

decision for grant of leave thereby enabling better planning

of crew allocation which earlier was very tedious.

Benefits of Crew Management

System

• Crew will get the duties as per rules

without any human element involved.

• No chance of partiality by the

authorities in case of duty allocation.

• Information of allocated duty is sent

via SMS.

• Since the data is stored in a

centralized server, it is secured and no

tempering of information at the local

level is possible.

• Portal for generating rosters i.e., Duty

Allocation chart and various reports

depending on designation of the crew

and with combination as well.

• The unit head, have to focus only on making provision for last minute non-

availability of crew.

116


Leave Management Systems

Not

GrantedGranted

Source: Vritti Solutions Limited

1. Introduction












117


Crew management systems

Design of crew management system

Screenshot of front view in which the crew is expected to log in using password or bio-metrics and select the depot


1. Introduction












118


Crew management systems


Roster block creation Duty allocation

In this module, roaster blocks are created and accordingly crew duties are assigned.

Example: In the above snapshot, Block 1 comprises of 06 crew duty daily, so a roaster block

of 07 crew duty is created to take care of weekly offs. The detailed duty allocation is shown in

the snapshot “Duty allocation.”

1. Introduction












119



1. Introduction









Project OutcomesA

Lessons learnedB

120


1










requirements.

2





equipment.



3



1. Introduction









Project OutcomesA

Lessons learnedB

121


5














8




4





• Battery performance of each bus (input & output current)- make & type wise.1. Introduction









Project OutcomesA

Lessons learnedB

122

Key Considerations


1. Introduction










Key TakeawaysB








1










2

123


as:





3




Say, for PIS:





4

1. Introduction










Key TakeawaysB

Key Considerations


124




5




6


part outsourcing?





7

1. Introduction










Key TakeawaysB

Key Considerations


125









8







9

1. Introduction










Key TakeawaysB

Key Considerations


126


be defined first.







being created.4







increase ridership.

6

1. Introduction










Key TakeawaysB

Key Considerations

Key Takeaways

127

7




requirements, etc.




its implementation.

8











1. Introduction










Key TakeawaysB

Key Considerations

Key Takeaways

128





13


up a Public Outreach Programme. Value additions to the project like Mobile Apps,





1. Introduction










Key TakeawaysB

Key Considerations

Key Takeaways

129

Thank You !

Time for discussion

130

Reference table

A. 9

B. 10

C. 11

D. 12-15

E. 16-18

F. 19

G. 20-21

H. 22

I. 23-24

J. 25-28

K. 29-30

L. 31-34

M. -

N. 35

O. 36

P. 37

Q. 38-47

A. 11-13

B. 14

C. 15

D. 16-19

E. 20-22

F. 23

G. 24-25

H. 26

I. 27-28

J. 29-32

K. 33-34

L. 35-38

M. 39

N. 40-42

O. 43-44

P. 45

Q. 46-54

A. 9

B. -

C. 10

D. 11-14

E. 15-17

F. 18

G. 19

H. 20

I. 21-22

J. 23-26

K. 27-28

L. 29-32

M. 33

N. 34-36

O. 37-38

P. 39

Q. 40-49

Delivery

PPT

Trainer

manual

Participant

Manual

A. 48-49

B. 50

C. 51

D. 52

A. 55-56

B. 57-58

C. 59

D. 60

A. 50

B. 51

C. 52

D. 53

Introduction


B. Overview of ITS
















1

Fleet Management

Systems

A. Overview

B. ITS technology

C. ITS architecture


2

131

Reference table

E. 53

F. 54

G. 55

H. 56

I. 57

J. 58

K. 59-61

E. 61

F. 62

G. 63

H. 64

I. 65

J. 66

K. 67

E. 54

F. 55

G. 56

H. 57

I. 58

J. 59

K. 60-61

Delivery

PPT

Trainer

manual

Participant

Manual

A. 62-63

B. 64

C. -

D. 65-66

E. 67-68

F. 69

G. 70

H. 71

I. 72

J. 73

K. 74

A. 68-69

B. 70

C. 71

D. 72-74

E. 75

F. 76-77

G. 78-80

H. 81

I. 82

J. 83

K. 84-85

A. 62

B. 63

C. 64

D. 65-67

E. 68

F. 69

G. 70-72

H. 73

I. 74

J. 75

K. 76-78

Fleet Management

Systems








2

Automatic Fare

Collection System




D. Smart cards



G. E-wallets





3

132

Reference table

A. 75-76

B. 77-78

C. 79

D. 80

E. 81-84

F. 85

G. 86-88

A. 86-87

B. 88-89

C. 90

D. 91

E. 92-94

F. 95

G. 96-97

A. 79

B. 80-81

C. 82

D. 83

E. 84-86

F. 87

G. 88-90

Delivery

PPT

Trainer

manual

Participant

Manual

A. -

B. -

C. -

D. -

E. -

F. -

G. -

H. -

I. -

A. 98-99

B. 100

C. 101

D. 102-103

E. 104

F. 105

G. 106

H. 107

I. 108

A. 91

B. 92

C. 93

D. 94-95

E. 96

F. 97

G. 98

H. 99

I. 100

Passenger

Information

Systems


B. ITS technology

C. ITS architecture


E. Case study: NMMT



4

Preventive

Maintenance

Management

Systems


B. Overview








5

Inventory

Management

Systems




6

A. -

B. -

C. -

A. 109-110

B. 111

C. 112

A. 101

B. 102

C. 103

133

Reference table

A. -

B. -

C. -

A. 113-114

B. 115

C. 116-117

A. 104

B. 105

C. 106-108

Delivery

PPT

Trainer

manual

Participant

Manual

A. 89

B. 90-91

A. 118

B. 119-120

A. 109

B. 110-111

A. 92-95

B. 96-98

A. 121-124

B. 125-127

A. 112-115

B. 116-118

Workforce

Management

Systems




7

ITS Project in

Mysore

A. Project outcomes

B. Lessons learned8


B. Key takeaways9

134




dbook.pdf)


















Participant Manual

1

December 2020December 2020




PARTICIPANT’S NOTES – ITS AND MIS FOR MIDDLE MANAGERSPARTICIPANT’S NOTES – ITS AND MIS FOR MIDDLE MANAGERS

2

PrefaceThe Efficient and Sustainable City Bus Services (ESCBS) project was introduced to improve the efficiency and attractiveness of city

bus transport in India. ESCBS project has three major components, which includes, National Capacity Building (NCB); Regulatory,

Institutional and Fiscal Analysis; and City Demonstration. This engagement falls under the purview of the NCB component of the

ESCBS project. The objective of this engagement is to design and develop training programme for city transport professionals, and

involves undertaking pilot testing, implementation, evaluation, and suitable modification of the training programme.


(MoHUA).

Policy Advocacy for

Senior Managers


Managers

Monitoring and


Managers


Middle Managers


Middle Managers


Managers

Bus Operations for

Middle Managers


Managers

1 2 3 4

5 6 7 8





3

About the Module

It is strongly recommended that participant’s manual is referred to prior to the training session.





management, inventory management, and manpower management. The module also provides lessons learned from cities and

best practices for better understanding.


operators it helps in identifying passenger demand, easy cash transaction & revenue reconciliation, optimum utilization of fleet

& manpower, effective planning preventive maintenance, shift and duty allocation of staff, inventory management, and meeting

the growing demands of passengers. Further, this module will help in gathering information for performance monitoring.

4

Learning Objectives












wrt users.

• ITS offers users with multiple fare trabsaction options such as mobile, card, and wallet and aids in making quick and



5

Learning Objectives





agreement.


Service provider:




Society:

6

Table of Contents

Introduction


B. Objectives of ITS and MIS

C. Why ITS is required (Commuter, Operator and Authority’s perspective)

D. Relation between IT, ITS and MIS

E. Attributes of productive output information

F. Management Information Systems: A tool

G. Overview of ITS and MIS Technology Framework

H. Benefits of ITS and MIS (Operator, Commuter, and Authority)

I. City Bus Transport using ITS

J. Limitations and Cautions of ITS Technology

K. Systematic Implementation ITS Program

L. Understanding ITS and Non-ITS

M. ITS technology and platform

N. ITS allied support

O. Support required for ITS

P. Case study: Mysore

1

Fleet Management

Systems

A. Overview

B. ITS technology

C. ITS architecture




2

7

Table of Contents


Systems


B. ITS technology

C. ITS architecture


E. Case study: NMMT



4

Automatic Fare Collection

System




D. Smart cards



G. E-wallets





3

Fleet Management

Systems






2

8

Table of Contents

Workforce Management

Systems

A. Need for workforce management systems and benefits thereof



7

Inventory Management

Systems




6


B. Lessons learned8

Preventive Maintenance

Management Systems


B. Overview




F. Creation of Bus Master File and updating bus-wise spare parts consumption


H. Input – Use of ITS and MIS in fuel management systems

I. Output – Use of ITS and MIS in fuel management systems

5


B. Key takeaways9

9

Introduction


1. Introduction









Objectives of ITS and MISB

Why ITS is required?C

Relation between IT, ITS and MISD

Productive output informationE

MIS: A toolF

































ITS and MIS Technology FrameworkG

Benefits of ITS and MISH

City Bus Transport using ITSI

Limitations and Cautions of ITSJ

Systematic ImplementationK


10

Introduction

ITS and MIS Manual

1. Introduction













MIS: A toolF


























MIS will do.





11

Introduction


OPERATOR


PassengersPASSENGER



AUTHORITY


1. Introduction













MIS: A toolF







12

Introduction



come???


come???




take my bus??


take my bus??

Is the next stop my

destination?

Is the next stop my

destination?


available ???


available ???

1. Introduction













MIS: A toolF







13

Introduction



the buses??


any stops?


any stops?






schedule?



schedule?



ridership etc., ?


ridership etc., ?

1. Introduction













MIS: A toolF







14

Introduction




conductors



conductors








(if any)


(if any)



transparent.



transparent.


bus stop etc.,


bus stop etc.,





1. Introduction













MIS: A toolF







15

Introduction

Case study of Mysore (Video)

1. Introduction













MIS: A toolF







16

Data Processing &

Storage

Generation of Input

Data

Output Information

Generation incl.

IT

ITS


Introduction


1. Introduction













MIS: A toolF







17

Introduction


ITS Server

ITS

Technologies

Storing of raw data in Database Server / concern server

Technical systems & hardware required for ITS application

• Automatic vehicle location (GPS – Global Position System onboard),

• Electronic fare collection (ETVM- Electronic Ticket Vending machine compatible with

multi-medium payment systems and complete GPS/GPRS connectivity),

• Driver’s console including driver monitoring, Vehicle Health Diagnostic System (VHDS)

and monitoring, emergency alert switch, reversing camera,

• In-vehicle data hub & processor,

• Surveillance equipment (CCTV cameras),

• Passenger Information System (PIS) (duly synchronized Audio-Video system for the

benefit of pax, onboard & Off-board, including PwDs [Persons with Disabilities]),

• Communication system,

etc. for generation & transfer of raw data.

1. Introduction













MIS: A toolF







18

Introduction


•Tracking of bus

•Revenue earning

•Way bill data

•Fuel consumption

•Surveillance Data

Input data

•Processing of data usingmathematical, statistical, GIS,and other application tools

•Storage of processedinformation

ITS Server

Data collection, storage & processing •Real-time Information to the

Passengers – on-board & Off-board

•Driving Behavior monitoring

•Route behavior Monitoring

•Vehicle productivity, bus loading,

•Earning per kms


Example Example

Raw data streaming to an ITS server makes sense only when it is organized into reports (information) by analyzing them through purpose-built software tools.

Facts/raw data collected from bus operations which are received at ITS server form's "input

data” – an unorganized heap or dump. Information is then derived from this random

collection by organizing it for a specific use or purpose. The outline of the difference

between "input data" & "output information / MIS" is illustrated below:1. Introduction













MIS: A toolF







19

Introduction


Determine

usefulness of

output

information

Quality

Completeness

Relevance Timely

Attributes / Characteristics

Quality Accuracy and reliabilityof available informationaffects the quality ofdecisions thatmanagers make usingthe information.

Timeliness Availability of real-timeinformation reflectingcurrent conditionsfacilitates managers inmaking precisedecisions.

Completeness Complete informationallows managers toconsider all relevantfactors when makingdecisions.

Relevance Having informationspecific to a situationassists managers inaddressing criticaldecisions.

1. Introduction













MIS: A toolF







20

Introduction


1. Measuring actual performance against measurable goals /outcomes wrt (KPIs).2. Review of actual performance against benchmarked KPIs output which are organized appropriately for

ease of appreciation and quick action at different levels of management.3. Taking corrective action.

Better insight into public transport,

meeting commuting needs, operator’s

performance, and interventions required

(if any) thereof.

Improving the decision-making quality: Correctinformation becomesavailable quickly to themanagers from a good MISwhich they can use formaking data baseddecisions. This improves thequality of decisions.

Provides connectivity:MIS provides betterconnectivity with all thedepots. In turn facilitatingeffective decision-making.

Aids passengers in makingdecisions by providing real-time passenger information.



Support top-level

officers in taking decision

Information support

For quick and focused Decision-Making

Management Information System Reports appropriate

for action at different levels of

management

Generation of


using IT & ITS



1. Introduction













MIS: A toolF







21

Introduction


Priority for various ITS components should be decided by the PT Agency,

based on its needs. However, vehicle tracking system and fare collection

system are basic systems which should be implemented first by a PT Agency.

System

Architecture

System

Architecture

Communication

Architecture

Communication

Architecture




1. Introduction








Understanding ITS and Non-ITSL


ITS allied supportN




MIS: A toolF






22

Introduction

Benefits of ITS and MIS: Authority

Authority

Operator

User

User: ITS makes public transport more attractive, convenient, time saving, and safe for the user.

Operator - ITS enhances efficiency and revenue & expenses records.

Authority: ITS ensures that smarter & safer public transport is offered, oversee management of

operations, and revenue account and is a useful business intelligence tool.

1. Introduction










ITS allied supportN




MIS: A toolF






23

Introduction

Benefits of ITS and MIS: Case study of Hubballi-Dharwad (Video)

1. Introduction










ITS allied supportN




MIS: A toolF






24

Introduction



• Mysore (KSRTC)• Bengaluru (BMTC)• Delhi (DTC & Cluster buses)• Mumbai (BEST, NMMT, Mira

Bhayandar etc)• Bhopal• Hubli Dharwad (BRT)• Ahmedabad (Janmarg BRT)• Indore (BRT)• Naya Raipur (BRT)• Pune (BRT)• Hyderabad (TSRTC)• Chandigarh• Jaipur (JCTCL)• Kolkata (CSTC)

An ITS project is not just a technology project

but is a solution for transforming the business

processes.

1. Introduction










ITS allied supportN




MIS: A toolF






25

Introduction




km to 251.7 km.











per km

1. Introduction










ITS allied supportN




MIS: A toolF






26

Introduction



1 Project

Conceptualization

and Design


technology


• Lack of availability of proper documented guidelines for planning

and implementing ITS initiatives for Indian cities

2 Project

Procurement




3 Project

Implementation



• Lack of readiness on part of authority – site, buses, power, users

etc.




• Lack of experience on part of the SI in implementing ITS projects

for large fleet size


4 Operations and

Maintenance

• Vendor lock-in and inability to scale up beyond the terms agreed in

the RFP



1. Introduction










ITS allied supportN




MIS: A toolF






27

Introduction















1. Introduction










ITS allied supportN




MIS: A toolF






28

Introduction







3






1. Introduction










ITS allied supportN




MIS: A toolF






29

Introduction



1. Introduction










ITS allied supportN




MIS: A toolF










30

Introduction





Guidance – Intended to guide the stake holders in a structured way (viz., Planning, Design, Implementation

& Evaluation in order to determine what the ITS is required to do, and how this fits within the broader

corporate service, operations and management strategy. How system & technology will be embedded in the

organization. Followed by implementation & evaluation.

Public Transport Function – It is intended to identify the priority areas for development of urban passenger

transport system, and whether there are ITS applications can assist in that process

ITS Application – The ITS Applications describes what the ITS does and how it does it.

ITS Technology – The ITS Technologies consist of a wide range of physical devices, their embedded

software, and their means of communication. They are the means of implementing the ITS Applications.

1. Introduction










ITS allied supportN




MIS: A toolF






31




1.Need Assessment




Services




Project


Introduction

1. Introduction










ITS allied supportN




MIS: A toolF






32

Business and

Service Context• General service

characteristics• Public transport funding

and cost recovery• Economic regulation• Role of public and private

sectors• Institutional framework• Public transport

restructuring

Planning

• Network and modal planning

• Service planning and specification

• Service contracting and management

• Fares policy and practice

• External communications

• Multi-modal integration

Service Delivery• Vehicle and crew scheduling• Preparation of vehicles for duty• Performance of service delivery• Crew Management• Service Quality Management• Management of incidents• Farescollection• Traveler information• Security and customer services

Operational Support• Demand management• Public transport priorities• Operations control center• Systems payment management• Vehicle and Infrastructure

maintenance• Inventory management• Fleet Management• Environmental program• Operator management• Human resource and development• ICT and ITS system support


& Compliance

• Legal and service compliance• Financial accounting and reporting• Consumption monitoring• Incident analysis


Introduction

1. Introduction










ITS allied supportN




MIS: A toolF






33

Introduction







Mobile App PIS





ITS Application

and Technology


AFCSPIS

1. Introduction










ITS allied supportN




MIS: A toolF






34

Introduction

Understanding ITS and Non-ITS

ITS Systems (Core Functions) Non-ITS Systems (Facilitated Functions)

Operations Management including need-based dynamic scheduling of services;

Automatic Vehicle Tracking

Bus and Crew scheduling and performance monitoring, and overall Management

Route and Driving behavior monitoring--Driver console

Leave Management, grievance handling, and wage administration

Security and safety against Fire hazards Vehicle maintenance scheduling, monitoring and control; Defect analysis and PM schedules

up-gradation

Passenger Information system – On-board & Off-board including for PwDS

Fuel consumption monitoring

Electronic Fare Collection System complete with on-line way-bill transfer, revenue leakage prevention assistance

MIS

When ITS systems are implemented, Non-ITS system often receive many input data from ITS systems (viz., kms run per trip or day, route / conductor wise revenue with transaction

records, vehicle health, MIS etc.).

In some cases, the Non-ITS function can also provide baseline data for ITS systems (viz., Service Scheduling - allotment of crew based on the availability status, number of fit

vehicles that can be provided for operations).

1. Introduction










ITS allied supportN




MIS: A toolF






35

Introduction


ITS Technology

Technology should be analysed from four perspectives:

• System/sub-system: Functions performed by the ITS system, e.g., Operations Management, Fare

Collection, Surveillance, and PIS.

• Location: Where is the technology located, e.g., on vehicles, at the control center, at bus-stops

processor, communications device, and data storage units.

• Technology type: Nature of the device e.g., customer-facing equipment, sensors, data processor,

communications device, and data storage units.

• Role: Generate data (e.g., sensor), process data (e.g., card leader), display (e.g., at-stop information

display), analyse data (e.g., dispatch support), and optimize resources (e.g., scheduling).

Many devices have multiple embedded components and they may perform multiple functions. For example,

a suitable GPS enabled mobile phone may now be sufficient to support AVM functions, while previously it

would have required a radio, a GPS unit, a driver interface/console, and an integrating processor. Similarly,

individual devices may now perform multiple functions, or a suitable combination of two devices where

shared processing may eliminate need for a third device.

Crucial points:

1. Technology is just one component of an ITS project. Organizational structure and operating procedures

are equally important, and all three must be taken into consideration in designing.

2. Technology choices and specifications should not be made until they are fully understood as to what

the ITS is required to do. Issues such as choice of communication or vendor preference should not be

allowed to predetermine design outcomes.

3. Procurement should focus on outcomes rather than on devices.

4. Implementation is a significant task which must be planned and resourced correctly. Adequate time

must be allowed for testing, installation, and commissioning.

1. Introduction










ITS allied supportN




MIS: A toolF






36

Introduction


ITS Platform

An ITS system consists of many inter-connected devices, software, and information. At a minimum, they

need to be able to connect and exchange information. ITS systems and sub-systems may need to perform

the tasks together.

ITS “Platform” concept elements are:

• System Architecture: Mapping all ITS systems and relate them with each other.

• Communication Architecture: defines how the systems and devices communicate with each other, and

what information is to be exchanged.

• Data Model: Consistency in defining the data to be used so that data generated by the system / sub-

system will be in standard/common form.

• Interfaces: Defines the physical connectivity between devices and protocols used for information

exchange.

• Standards: For ensuring that both Vendors and Clients develop hardware and software in a common way,

usually based on international industry consensus.

The ITS deployment team will determine appropriate platform elements. Ideally, it is expected to select

international norms that reflect industry practice and relevant elements of such norms.

Decisive points:

The data requirements fall under the following broad categories:

• Background data, configuration data, and daily assignment data.

• Real-time of event/transaction-specific data that the ITS requires when performing a specific function.

• Data which the ITS system should pass to devices, both for immediate and downstream use.

1. Introduction










ITS allied supportN




MIS: A toolF






37

Introduction

ITS technology and platform: Wireless communication technology network

General PacketRadio Service(GPRS).Download speedup to 114Kbps.

2G

High-Speed Packet

Access (HSPA).

Download speed of

up to 168Mbps.

4G

High-SpeedDownlink PacketAccess (HSDPA).Download speed ofup to 14Mbps.

3G

Introduction of 3G network madevideo calling and seamlessstreaming of video possible.

Long Term Evolution

(LTE).

Download speed of

up to 299.6Mbps

4G

LTE is a 4G network that

supports faster

communication and HD

video streaming.

To date, most of the urban transport network in India uses GPRS, which is 2G wirelesscommunication technology.

In the upcoming projects, ensure to include hardware configuration compatible with highercommunication technology.

1. Introduction










ITS allied supportN




MIS: A toolF






38

Introduction

ITS Allied Support: Infrastructure, back-office, human

Occasionally, an ITS system may be free-standing or plugged into existing ITS systems

without any other requirements. However, most ITS systems are not independent, and they

require supporting infrastructure and back-office support. In this backdrop, three particular

aspects needs to be considered:

• The ITS system may need to share some aspects of the IT platform of the host

organization (e.g., servers, communication, operating systems). Therefore, platform

capacity may need to be increased along with purchase of additional user licenses.

• The ITS system may need to interface with the existing administrative and/or

management IT systems. Therefore, system software amendments may be needed.

• The ITS systems may also need non-ITS supporting technology, including

communications, servers, back-office PCs, printers, office software, and security

software.

• Human Resources – For smooth functioning of ITS, it is essential to define the role of the

consulting team (ITS consultant) and the operational team (urban transport operator)

after commissioning of the ITS project during the contracting period.

These requirements need to be identified, specified, and budgeted for, as part of the ITS

system design and planning.

1. Introduction










ITS allied supportN




MIS: A toolF






39

Introduction






b. GIS server

c. PIS Server with support of streaming Server

(for advt.)

d. SMS


Size of the memory allocated to the server for a given purpose shall be based on expected

load that is likely to come, that is:

1. How many operator's teams in multiples, separated geographically will be accessed

simultaneously (if any)?

2. How many commuters concurrently are expected to access and (or) can be given access?

3. Size suggested for smooth running of application tools including GIS.

4. Provisions for future upgrades (if any).

1. Introduction










ITS allied supportN




MIS: A toolF






40

Introduction

Data Center

Fire safety


Cooling system

Security

Fiber/wifi

Support required for ITS – at control room and in buses, bus stops & stations

1. Introduction










ITS allied supportN




MIS: A toolF






41

Introduction



Having Intelligent Transport System (ITS) that conforms to international standards &supports the transport agency in providing efficient operation & management ofTransportation System for Mysore City.

Vision

Objective

Concept of ITS

Strategy

Strategic Agenda

Target Level: Improve Operation & Management of Intelligent Transport System by use of

GPS, GPRS, and data center for dissemination of information for transport management.

Strategy Level: To provide efficient, clean, safe, and commuter-friendly solutions.

Action Level: Implement GPS based vehicle tracking & monitoring system, and passenger

information system.

Transport Management

Bus Information


Electronic Payment



Improved Transport Efficiency & Productivity.

Tracking, data acquisition, and transmission of data for improved Road Traffic Management & Security.

Better services mobility & access to commuters.

Reduced energy use, emissions & noise.

1. Introduction










ITS allied supportN




MIS: A toolF






42

Introduction


➢ Components

• AVL

• Real-time PIS

(ETA/ETD)

• In-bus display

• CCC

• MIS reports

• EMS

• Training

• SMS & IVRS

• Fleet Management

• Commuter portal

➢ Scope

• 500 buses


bus stops


• 6 terminals


1. Introduction










ITS allied supportN




MIS: A toolF






43

Introduction



• Kick-off meeting• Site Survey• Route Survey• Bus Stop Survey• Site Plan Sign-

off• SRS• Project Plan• Implementation

Plan• Reviews &

Iterations• Finalize

• Power calculations• CCS room design• Communication,

database sizing• S/w specifications• H/w specifications• Design document

for VMU and PIS• Test plans for VMU,

PIS & SFAT• ETA algorithm• EMS• S/w Development &

customization

• FAT for custom hardware (VMU and PIS)

• Software FAT• Procurement of off-

the-shelf and custom hardware

• Software procurement

• Deliveries for full system

• Full system hardware installation

• Full system software installation

• ITS application configuration

• Training• System integration• POP & WIR• System acceptance• Rollout

Implementation

Testing & Operations

Procurement Planning Design & Build

Programme Mgmt.

Regular Review

Risk Mgmt.

Quality Mgmt.

1. Introduction










ITS allied supportN




MIS: A toolF






44

Introduction



1. Introduction










ITS allied supportN




MIS: A toolF






45

Introduction



Data Center

• Servers – all configured in cluster mode (fault tolerance)

• Communication

• GIS

• ITS Application

• SMS/IVRS Applications

• PIS Display Board Applications

• Network & Firewall components

• Web application -(website – http://mitra.ksrtc)

• Internet connectivity 5 Mbps x 2 (redundancy)

• Higher capacity UPS - 2 x 20 KVA online UPS for failover

• Higher capacity DG set - 85 KVA Diesel Generator Backup


Command & Control Center



• Access Control

1. Introduction










ITS allied supportN




MIS: A toolF






46

Introduction





1. Introduction










ITS allied supportN




MIS: A toolF






47

Introduction

Case study: Mysore (Team structure)

KSRTC Mgmt.

Representative


CMC Onsite Operations Manager

Data center team

Network Engg.

Server Engg.

Desktop & PIS Engg.


Support Engg

In-bus equipment team

Bannimantapa depot

Kuvempungara depot

Satgalli depot


team

EMS alerts

Monitoring Team

(Shared team)


KSRTC Operational Team

• DC

• DTO

• DME

• ITS in charge

• Depot Managers

• Assistant Works supervisors

• Assistant Traffic Superintendent / Traffic Inspector (ATS /ATI)

Key Roles of Operations Managers

1. Own complete operations

• Conduct review meeting

• Issue & escalations management

• Implementation & maintain SOP

• Monitor & control Service Level Assistance

2. Dispatchers/ Helpdesk

• Monitor & track buses through ITS application

• Engage crew through audio mechanism

• Answer queries

• Schedule & Route

• Ticketing Management

• EMS alert monitoring

Capacity development –

➢ Exposure to KSRTC officers and staff for handling project

management professionally.

➢ Instructions manual for crew and staff.


CMC Mgmt.

1. Introduction










ITS allied supportN




MIS: A toolF






48

Introduction


1










requirements.

2





equipment.



3


1. Introduction










ITS allied supportN




MIS: A toolF






49

Introduction

5














8



4







1. Introduction










ITS allied supportN




MIS: A toolF






50

Introduction

Key Takeaway

• Understanding what is IT, ITS, and MIS.

• Objectives of ITS & MIS in public transport and how MIS is an effective tool for

performance evaluation.

• Benefits of ITS & MIS to stakeholders is also delineated.

• Insight into ITS technology & platform, and allied support required.

• Challenges faced and the way forward.

• Case study for better understanding.

1. Introduction










ITS allied supportN




MIS: A toolF






51

Fleet Management System (FMS)

Overview

FMS


7

Emergency Mgmt.

6

Driver Standard

Compliance

5

Service Contract

Compliance

4

Schedule Adherence

3Route


Automatic Vehicle

Monitoring

1

The subsystem in FMS is elaborated in the module on "bus operation." Types of MIS

reports and use in monitoring of services is also covered in the same module.

In this module, emphasis is on covering the ITS application aspect without repetition of

contents.1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

52


ITS Technology

FDAS

Emergency Button

GIS Layer

AVM

Driver console

with VHMS

Camera

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

53


ITS Architecture

Emergency

Breakdown

Report Accident The information on the location of the bus is tracked & sent to the server through theAutomatic Vehicle Monitoring (AVM) System which forms the input for the concernedmodule. On receipt of processed information on incidence, CCC follows the SOP laiddown under incident management which strives to cut down on the disruption that islikely to extend to other routes.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

54



Tracking

MISReports

Administration


• Dynamic status reports – GIS map tracking

• Scheduled replay

• Line Diagram

• Alerts monitoring

Route Settings

• Add, delete, cancel trips

• Reschedule trips

• Reason for breakdowns

• Create and upload files to VMU required for

scheduling

VMU Management

VMU ID configurations

GSM/GPRS Parameters

VMU health check

Send command messages to VMU

Generate various MIS reports

TC/KSRTC Supervisors can analyze and enhance operational efficiencies

Reports are downloadable in different formats

User creations and management

Role-based access

Master data management

Alert configurations

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

55




Source: Lumiplan

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

56



Challenges:

1. The volume of commuters increases during these occasions.

2. Often such occurrence takes place over multiple days and passenger movement (arrival and

departure) happens throughout the entire duration.

3. Passenger demand cannot be managed with daily scheduled operation.

4. Bus parking capacity at the venue is often unknown.

5. Hence, special arrangements for catering to this extra load have to be made with utmost care and

precision.

MIS data

• Previous year's performance –

ridership trends, no. of trips

per day, no. of vehicles used,

no. of crews required, the

requirement of other staff, etc.

• Trends over the last two

years – increasing/decreasing

in correlation with adjoining

public holidays/off day.

• Based on past MIS data, trend

analysis is carried out to

quantify the total number of

buses required, considering

holidays, weekends, and

weather forecasting.

Management of fleet for operation of buses

1. For a major part of the operations, fleet from the nearest

depot is taken to avoid dead kms. and losses.

2. In case of shortfalls, based on MIS data on fleet strength ofother nearby depots, instruction is given for supplying spare

buses with the crew to the venue/temporary bus stand.

3. In case of an unprecedented increase in passenger demand,

at any point in time, leading to demand for extra buses, ITS

plays a crucial role by using the vehicle tracking solution.Under this, CCC tracks the buses in special operations and

other scheduled buses (nearby vicinity) with an expected

time of arrival at the stand. Based on this, CCC takes a call

to:

a) either wait for the arrival of special operations buses or,

b) instruct bus drivers who are in the nearby vicinity for re-

routing scheduled bus/buses to cater to the rising demand

with due consideration to no. of passengers on board.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

57






1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

58



Source: LumiplanThe report is generated automatically and can be accessed on the ITS

dashboard from the Manager’s mobile or laptop any time.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

59



Driver console comprises of the following:

• Vehicle health monitoring system (VHMS).

• Communication aid for the driver.

Communication aid for Driver

Each time the driver accelerates or brakes sharply or overspeeds; CCC records the information and flashes a warning to

the driver on the driver’s console. For example, in case of over

speeding, it flashes "Go Slow," as shown in the picture.

Communications to the crew are also passed through the

console.


More than 100 parameters are loaded in VHMS for monitoring vehiclehealth. ECU present in the vehicle sends information to SCU "Signal

Control Unit" through vehicle CAN. The SCU, which is enabled with

GPRS/latest communication technology, communicates the information

to CCC. The ITS server at CCC processes the data, i.e., coding &

decoding, and as per the severity set in SOP, the information is

escalated. The information sent to the officer is mostly in the form of

an SMS. An illustration of the SMS is provided on the right.

The detailed information can also be made available through Wi-Fi or OTA (over the air), etc. This

information is essential for non-ITS system, especially for carrying out preventative maintenance of the

vehicle.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

60



ITS application module in Incident management comprises of the following:

• Incidence - Fire incidence, Breakdown.

• Emergency button.

• Cameras & data storage.

Cameras & data storage

The purpose of on-board cameras is as follows:

• For enhancing the safety & security of passengers and luggage on board

• Assistance to driver especially while reversing.

• In case of incidence, data from DVR can be extracted for further investigation.

• Data can be the transferred via. Wi-Fi or OTA or through other communication. Theduration for which the data can be stored in DVR is a function of the size of the data

and the capacity of DVR.

A potential area of fire hazard is the engine compartment against which Fire Detectionand Alarm System (FDAS) & Fire Detection and Suppression Systems (FDSS) are

present in the bus. In case of a fire incidence, in the engine compartment, the FDAS (asshown in the picture) triggers the alarm in the bus and also sends communication toCCC. To avert the loss of life & property, CCC responds as per the laid down SOP.

Meanwhile, the driver, through the passenger announcement system, intimatespassengers to de-board the bus.

Emergency Button

When the emergency button is pressed by passenger/crew to indicate safety/panicsituation caused by human or natural disaster or vehicle incidence, etc., the SCUcommunicates the information to CCC. The ITS server at CCC process the information

and acts upon it as per the severity set in SOP. The concerned officer gets theinformation in the form of SMS and even a telephonic call.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

61



Source: APSRTCThe report is generated automatically and can be accessed on the ITS dashboard

from the Manager’s mobile or laptop any time.

1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

62


Key Takeaway

• Which areas of fleet management system can the ITS offer solutions to?

• Overview of ITS technology & architecture required for fleet management system.

• Elaboration with the help of case studies.1. Introduction









OverviewA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: SuratE


Case study: PMPMLG

Case study: SuratH



Case study: APSRTCK

63



Electronic Ticketing Machine

Pass System

Card System

M-Ticketing

Digital Wallet

E-Wallet

Pole validator

Gate Validator

Ticketing options shall address all the requirements of the customers.

Cash Cashless

Integration of all cash & cashless travel, and reconciliation of total revenue

earned encompasses ticketing system management.

Server & payment gateway

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


64



Electronic Ticketing Machine (ETM) Master data pertaining to unit fare charges for adult/child and

luggage, concessions, route, and bus service are uploaded on the ETM. Once the configuration is over, the

ETM is ready for use during the journey.

Reports generated

1. Ticket Details – no. of tickets issued to Adults, Child, etc.

2. Validation of Pass viz., through ETM for Students, Elected Representatives,

specially abled and Freedom Fighters etc.. and report generated thereof.

3. Payment made through ETM towards Bus Stand Fee, Tollgate Fee and Bridge

Fee and report generated thereof .

4. Revenue Collection Report.

5. Status Report.

Multipurpose: Enables the conductor to issue tickets/passes/card.

Information Generation: Information on revenue collection is made available

in real-time by transmitting the transaction data to the back-end server through

wireless connectivity.

Safe & Efficient:

• ETMs usage is possible only through a combination of PIN and password. It

facilitates downloading of updated route or fare information through wired or

wireless connection.

• Efficient reconciliation of revenue – less time is required for settlement at the

Cash Counter.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


65


Automatic daily pass vending machine

One of the main attractions of a vending machine is its low maintenance cost, which lowers the overheads,

and occupies less space, simple in operation and is portable. Unlike the ticketing counters, there are no staff

requirements, which means the authority does not have to deal with staff cost, allied leave, etc., and a

machine will happily work 24 hours a day, 365 days a year.

CIRT had undertaken a study on the "impact of daily pass on revenue" in case of discontinuation due to resale

of preprinted daily pass by the passengers. After the study, it was recommended not to discontinue the day

pass; however, should make provision for photographs to avoid resale of a daily pass.

The machine has a user-friendly touch

screen, and software. Passengers can

select preferred languages viz,

English/Hindi/ local language for

communication.

The machine provides commuters with

the facility to buy a daily pass and avoid

long queues at the counter. Passengers

have to select the pass option followed by

getting a picture clicked and finally

payment processing.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


66


Smart cards


1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


67


Smart cards

• The Smart Card must be compatible with

“National Common Mobility Card”

specifications.

• Testing of read & write of Smart Card with

ETMs is a prerequisite.

• Coding for reading real card is also required.

• RBI clearance is essential.

Benefits –

• No upfront costs are involved.



CustomerFriendly

Customers can use the same card for Metroand Bus travel in all the cities and states.




Loyalty Points Loyalty Points Consumers may benefit frompartner banks' loyalty/reward points, asprovided with Debit and Credit cards




Each Public Transport Operators needs tobear significant expenses for maintenanceof infrastructure and workforce for cardissuance, top-up, card replacement, andrefunds.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


68


Smart cards


Negotiating Power

As Open-loop acceptance devices are based on open interoperable standards, there are multiple vendors available for payment acceptance devices, which provides an opportunity for cost and service negotiation.

Closed-loop cards may be of proprietary standards, leading to vendor lock-in for subsequent purchase and renewals of acceptance devices.

No vendor lock in

Open standards based payment acceptance devices provides the freedom for subsequent purchase and renewals of devices.

Proprietary standards may lead to vendor lock-in for subsequent purchase and renewals of acceptance device


Well standardized payment acceptance devices and availability of multiple vendors provides ease of implementation. Payments related scope of work to be taken care of by the partner bank and hence PTOs may focus on their key activities.

PTOs need to evaluate multiple proprietary specifications leading to difficulty in implementation.

Fast Deployment

Due to similar implementation process, best practices, and reference implementation guidelines, there will be standardized procurement practices, and RFPs. This considerably expedites the deployment of digital payments in Public Transport Operators.

Each deployment will have specific requirements and each Public Transport Operators requires considerable expertise for the selection of an appropriate solution

Retail acceptance


Closed-loop cards can only be accepted within their operating environments.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


69


Common Mobility Cards (CMC)

National Common Mobility Card (NCMC), also known as One

Nation One Card, is an inter-operable transport card conceived

by the Ministry of Housing and Urban Affairs (MoHUA) of

the Government of India (GoI). It was launched on 04 March

2019.

The transport card enables the user to pay for travel, toll duties,

retail shopping, and withdraw money. It is enabled through the

Rupay card mechanism. The NCMC card is issuable as a prepaid,

debit, or credit RuPay card from partnered banks such as

the State Bank of India, Punjab National Bank, and others.

The NCMC is an indigenously made product, and is a part of the ”Make In India” project. It was first

conceptualised in 2006 as part of the National Urban Transport Policy (NUTP).

The card has dual interface (contact & contactless) and is interoperable. Thus, it provides solutions to low

value payments for various segments e.g., Transit, Smart cities, Toll, Parking, and other low value merchant

payments in addition to the normal day-to-day retail payments. These specifications supports not only

payment products but also transit applications like passes & government applications such as social security,

driving license, Id/access card etc.

The urban development ministry tasked the National Payments Corporation of India (NPCI) with

management, clearing and settlement of payments, simulating cards and terminals, and maintenance of

network. Bharat Electronics Limited (BEL) has created the reader prototype.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


70


Case study: Surat



Surat Money Card


Source: Lumiplan

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


71


E-wallets

Operational Mechanism:

Under mobile or electronic wallets, the individual pre-loads cash in the e-wallet and uses it to make payments

or transfers. Money is loaded either electronically (using a computer/mobile) through a credit card or bank

account, or physically by handing over cash to a local merchant (point of sale [POS]) or at the ATM counters.

What is required is an internet connection and a mobile /computer. With the technology in place, mobile-

based operations through e-wallets have become a mode for financial inclusion.

There are charges for mobile / e-wallet, which includes registration fees and cash loading charges(above a

limit) towards payment companies/service providers. These charges are at times higher than those for

internet banking. However, the main advantage of e-wallet is that while shopping online, the customer stands

to benefit from the concessions/ offers from the payment companies in the form of cash-backs, etc.

Benefits of e-wallets

The use of debit cards requires access to the designated point of sales and ATM counters. However, in the

case of e-wallets, money moves along with the holder, and he can access it from an instrument held in his

hand – his mobile or computer, giving much flexibility for the account holder. Further, e-wallets avoid the

dangers associated with card thefts.

For those who stay far away from ATM/bank branches, as in rural areas, money is still accessible to them at

the click of a button. In case of any requirement for physical cash, they just need to go to the nearby banking

correspondent or a local merchant who can double up like an ATM. Thus, e-wallet comes handy for those who

do not have a bank account, net banking, or credit card, especially those who may otherwise be ineligible for

receiving them. At present, services are not generally designed to handle significant payments. The use of e-

wallets help in moving away from a cash-based economy. In the process, all the transactions get accounted

for in the economy,which helps in reducing size of the parallel economy.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


72


E-wallets

Types of e-wallets permitted in India

As per the Reserve Bank of India, there are three kinds of e-wallets in India: closed, semi-closed, and open.

Closed e-wallets: The company/entity issues wallets for facilitating purchase of goods and services sold by

them (or) in other words, money stored in these wallets cannot be used for transactions with any other

company. These wallets/instruments do not permit cash withdrawal or redemption. Closed wallets are online

accounts, where money gets credited in case of a refund on account of a cancellation or return of a product or

service. Some companies even earn interest on these deposits.

As these instruments do not facilitate payments & settlement for third party services, issuance and

operationalization of such wallets are not classified as payment systems. Hence, RBI approval is not required

for issuing them. e.g., companies like Flipkart.com, Makemytrip.com, Bookmyshow.com, etc.. issue closed

wallets to their consumers.

Semi-Closed e-wallets: These wallets can be used to transact online and offline, including buying goods and

services, financial services, payment of fees, premiums, etc., through/to merchants, which have a specific

contract with the issuer to accept the payment instruments. These wallets do not permit cash withdrawal or

redemption by the holder. An RBI approval is required to start and operate a semi-closed wallet.

Since these wallets are handled by non-banking agencies (banks and non-banking financial agencies cannot

issue semi-closed wallets), they are required to deposit this money in an escrow account with a partner bank.

Interest on these deposits depends on the agreement between the payment company and the bank. Wallets

for amounts up to Rs.10,000/- can be created under this category by accepting minimum details of the

customer, provided the amount outstanding at any point in time does not exceed INR 10,000/- and the total

value of reloads during any given month also does not exceed INR 10,000/-. Amount up to INR 50,000/- can

be created in wallets by accepting any 'officially valid document' which is compliant with anti-money

laundering rules. E.g., Paytm Wallet, Freecharge Wallet, Citrus, Oxygen, etc.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


73


Wallets amounting up to INR 10,000/- can be created under this category by accepting minimum details of

the customer, provided the amount outstanding at any point of time does not exceed INR 10,000/- and the

total value of reloads during any given month also does not exceed INR 10,000/-. Amount up to INR 50,000/-

can be created in wallets by accepting any ‘officially valid document’ which is compliant with anti-money

laundering rules. Amount up to INR 1,00,000/- can be created by with full Know Your Client norms (KYC) and

can be reloaded. Example:

1. Paytm Wallet,

2. Freecharge Wallet,

3. Citrus,

4. Oxygen

5. AirTel Money, which is used for making payments for a range of services like money transfer from Airtel

Money to another bank account or any other Airtel Money Wallet or paying select utility bills is an example

of Semi Closed E Wallet

Open e-wallets: Open Wallets can only be issued by banks or in partnerships with banks. These wallets can

be used to perform all the transactions of a semi-closed wallets plus withdraw cash at ATMs or banks and

transfer funds. However, cash withdrawal at POS is permitted only up to a limit of INR 1000/- per day subject

to the same conditions as applicable on debit cards (for cash withdrawal at POS). Example:

1. M-Pesa is an open wallet run by Vodafone in partnership with ICICI Bank.

2. Axis Bank’s e-Wallet Card’, can used for making payments on sites that accept Visa cards, with a minimum

limit of INR 10, and a maximum limit of INR 50,000, and a validity of 48 hours.

3. Pay Zapp by HDFC Bank, etc.. are few open wallets in India.

E-wallets

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


74



Digital Wallet E-Wallet

Card details are saved in the wallets which

enables card-less transactions.

Money is preloaded in the wallets to transact

card-less.

Money remains in user's bank account or

credit card.

Money moves from user's account to either a

merchant’s current account or an escrow

account.

Example - Masterpass, Google Wallet, Apple's

Passbook.

Example - Paytm Wallet, Freecharge Wallet,

Mobikwik.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


75







1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


76


Case study: Surat (Ridership and revenue)

Source: Lumiplan

Top/Last 5 Stops and Route –Ridership and Revenue Hour basis Ridership and Revenue


1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


77



An urban passenger transport system often has multiple revenue sources, ranging from on-vehicle sales

to quantified subsidy payments, and multiple beneficiaries of those revenues, ranging from the

operators to the public authority. Robust procedures are required so that all revenues are accounted for and

reconciled before making payments to them. The reconciliation process may be manual or computerized in

traditional fare collection systems, but can be automated through a clearinghouse in electronic systems. The

latter has advantages in terms of accuracy, security, and speed.

Ticket sales consolidation: Consolidation of sales revenues varies in complexity depending on the scale of

activities and the range of revenue sources. It is simplest among owner-drivers who only collect their

revenues and most complex where the fares collection system may involve several operators with their

collections accruing from on-board sales by crew, sales from automated vending machines in various

locations, and off-system agents, and internet-based sales channels. Allied to the sale method is the creation

of robust audit trails that routinely tracks revenues from these sources through to the collated deposits in the

banking system so that the movements are fully captured and evidenced. This process also enables primary

data to be collected on revenue sources and allocations for inclusion within the routine management

information system.

Ticket validation conciliation: Validation of travel documents is essential in verifying that legitimate travel

is being undertaken and that the validated travel value has been correctly deducted from the tickets/passes,

and correctly recorded. The validation processes may be complex, where several operators are involved. It

may arise from on-board validation by the crew [either manually or by a machine] or on-vehicle or off-

system free-standing validators. The purpose of conducting validation is to identify the vehicle, route, and

operator involved in the travel undertaken and the cost of that travel. This information is then used as

routine management information data on travel activities and revenue allocation purposes. It can also be

used for verification of payments related to travel undertaken by concessionary pass holders. Allied to the

validation method is the creation of robust audit trails that routinely track the correct allocation of revenues

accrued to various service providers.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


78



Communications: Manual revenue collection systems [that is, those incapable of electronic data transfer]

generate clerical or computerized control systems to verify if revenue management processes have been

reconciled. They also enable identification of any variations for investigation and correction. Complex fares

systems and those systems with many crew, vehicles, operators, and locations require significant manual

input to validate that systems are functioning as planned. Such systems are prone to human error, and may

also be targeted for fraud. Electronic fare collection systems are inherently more accurate and secure but

involve transmission of large volumes of data. Data transfer from a vehicle to its operating base or centralagency can be achieved in real-time with mobile radio communication, or at the end of the duty by physical

data transfer or local communication. However, the volume of stop-based transactions is generally far higher

than on a single vehicle, and data transfer to the central agency then usually requires fixed links such as

high-capacity copper or fiber-optic cable. Consolidation at depot level requires even higher communication

capacity for the central agency, and this will require fiber-optic cable.

Revenue reconciliation: In simple terms, revenue reconciliation is the balance of sales generated to fares

validated over any given period. There are various ways in which travel is sold to passengers, various ways in

which passengers validate their ticket products for travel, and then various ways in which these activities are

communicated to the fares system operator. These have been described in the preceding sub-sections. On ascale of complexity, traditional fare collection systems generate more manual recordings and require a series

of individual inputs, each of which requires reconciliation. In case of any variation, an investigation needs to

be undertaken until reconciliation is established. These processes are time-consuming and prone to human

error or fraud but most can be computerized after the initial data entry.

However, modern electronic fare collection systems lend themselves to automated revenue reconciliationmechanisms which is managed through a clearinghouse that is provided either by the fare collection agency

or the system integrator on its behalf. The financial clearing system has to be robust and accurate and

trusted by all affected parties. This function, and its software capability are central to the successful

implementation of an electronic fare collection system. In either case, the revenue reconciliation process

should enable an array of analytical reports to be generated at any time, place, product and class, series so

that an overview of activity levels can be established. These analytical tools require computerized systems,

and cannot be replicated cost-effectively in the manual revenue management systems.

1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


79


Key Takeaway

• Overview of ticketing management system, ITS technology & architecture.

• Information on various options viz., E-ticketing machine, smart card etc.

• Case studies highlighting extensive use of ITS to track down revenue, ridership etc.1. Introduction












Smart cardsD


Case study: SuratF

E-walletsG


Case study: APSRTCI

Case study: SuratJ


80



Passengers require the following information to plan the journey:

1. Real-time information like route-wise arrival & departure of buses.

2. Type of service (A/c, Ordinary/Express etc.).

3. Approximate travel time for reaching the alighting point.

4. No. of passengers on board, whether to board the bus or wait for the next bus.

5. Next bus on the same route.

6. Fare for the trip, options for cashless transactions.

7. Information on alternatives options at the alighting point, for reaching to the destination.

8. General advice on disruptions en-route (if any).

Passengers require the following information during the journey:

➢ Route and trip details at the start of the trip– start time, likely trip duration.

➢ En-route stops – current stop and next stop at every halt to facilitate alighting.

➢ Connecting routes/modes/transfer characteristics/timings etc. at transfer locations.

➢ Last mile connectivity details at arrival stations at the end of a trip.

➢ Crew details to record feedback on their behavior.

➢ In-journey information is required for all pax including Persons with Disabilities (PwD) through –audio-video pre-

recorded synchronized announcements/displays on-board.

Passengers require following information at BQS to board the right bus:

✓ Route map and operating time table.

✓ Route no. and route destination, of arriving bus.

✓ Arriving Bus category – AC, express, ordinary, limited stop along with tariffs, if possible.

✓ Information as audio- video synchronized announcement/displays as bus stops – particularly useful for PwDs to

enable them to board the right bus without any other help.

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


81


ITS Technology

Source: Lumiplan



inside



1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


82


ITS Technology



1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


83


ITS Architecture


Streaming server aids in providing advertisement between the updates of real-time passenger information system.

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


84


Case study: Mysore


➢ Components

• AVL

• Real-time PIS (ETA/ETD)

• In-bus display

• CCS

• MIS reports

• EMS

• Training

• SMS & IVRS

• Commuter portal

➢ Scope

• 500 buses


bus stops


• 6 terminals

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


85



Objective

• Promote intelligent travel to commuters.

• Reduce waiting time of commuters.

• Provide safe & quality travel.

• Journey planner for commuters.

• Feedback mechanism for citizens.

• Real-time bus arrival reminder.

Overall Features

Source: ppt on “Integrated Intelligent Transport System (IITS) in Navi

Mumbai” by NMMT source internet

Ease

of

Travellin

g

Tic

ket

&Pass

Bookin

g&

Safe

ty

Ease

of

Managem

ent

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


Real-time bus

information

Reminder of bus

arrival

Travel information

sharing via WhatsApp

and SMS

Real-time availability

of seats in buses

E-ticketing through

mobile app

Smart card recharge

through mobile app

Online pass approval

through app

Safe travel through

SOS service

Feedback system of

User

Monitoring system

from Control center

Announcement to

commuters on latest

offerings

Document approval

for availing pass

86



Users can see Real-time

information on bus arrival

and departure

Users can see nearby bus stops

along with walking time

Users can see the last stop of the running

bus

Users can set the alarm to

remind him/her to reach bus

stop

Users can set favorite/frequent routes from a bus stop as per the

travel requirement

Users can share their traveling

details with anyone through WhatsApp

& SMS

User can see the latest

announcements made by NMMT

Features


2 3 4 5 6 71

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


87




location

Information about all

running buses(In green) as

well asScheduled

buses (in blue)


number bus inAPMC Market Bus

Stop

Share yourtravelling detailsw ith your friends/ relatives to takethem on-board in

the same bus


1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


88


Case study: DIMTS (Mobile applications)

Poochh-O by DIMTS Mob App for commuters


1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


89



Sitilink mobile application offers citizens a medium

to plan their journey in an efficient way. Surat

Sitilink application provides multiple options listed as

below:

▪ Journey Planners

▪ M-ticketing

▪ Route and Stops Information

▪ Route Map

SMC Department vehicle application is developed

for real-time vehicle tracking and reporting. It is also

used for initiating operator billing based on AVLS

Data.

Sitilink Supervisor application is developed for

Sitilink operations.

Source: Lumiplan

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


90




Source: Lumiplan

1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


91


Key Takeaway

• Insights into Passenger Information Systems (PIS).

• ITS technology and architecture for same.

• Explanation with the help of case studies.1. Introduction









Insight into PISA

ITS technologyB

ITS architectureC

Case study: MysoreD

Case study: NMMTE

Case study: DIMTSF


92


Operation – Maintenance Interface

Operation Maintenance

Fleet required for Day-to-day operations


and

Availability of spare buses

Workforce availability for

Day-today operations


and

Extra crew available, if any

Intake of fleet Capacity of the depot /

workshop

Buses (if any) lagging

behind schedule due to

various reasons

and

Availability of spare parts

for subject maintenance

Workforce availabilityAgainst each type of

maintenance

and

Extra staff that can be

made available, if any

1. Introduction










OverviewB








93


Overview

Preventive maintenance is defined as a service undertaken by technicians to maintain the bus

in a satisfactory operating condition in order to avoid breakdowns and major operational

failures. Maintenance standards play a significant role in defining vehicle operating costs,

levels of safety and reliability, and pollution. Preventative Maintenance is a decisive factor for

smooth functioning of an effective bus system. The benefits of preventative maintenance are

as under:

• Prevent mechanical failures with a target of zero breakdowns during service provisioning.

• Reduction in emissions.

• Improving fuel efficiency thereby resulting in a reduction of fuel costs.

• Comfort, convenience & safety is prioritized through preventative maintenance.

• The service life of buses are improved.

• Preventative maintenance is less expensive compared to breakdown maintenance which

improves service reliability.

• It also improves safety by reducing the incidence of failure of safety-critical components

such as brakes, tires, and steering mechanisms.

• It helps in anticipating and initiating repairs.

1. Introduction










OverviewB








94



Generally preventive maintenance is set out on the following guidelines:

1. Manufacturer’s warranty requirements / recommendations.

2. Usually conducted at fixed intervals and at intervals as per legal requirements.

3. Criteria is merely borrowed from other transport agencies.

Based on the above criteria, preventative maintenance schedule is streamlined as illustrated

below:

Maintenance Schedule Preventative Maintenance Schedule for Activity

Schedule 1 Daily Maintenance Time-based

Schedule 2 Fortnightly Maintenance Time-based

Schedule 3 Quarterly Maintenance Time-based (or) Kms. based (or) as per OEM’s


Schedule 4 Annual Maintenance Time-based (or) Kms. based (or) as per OEM’s


• In addition to the above, accidental & heavy repair work is also to be carried out though

they are not part of preventative maintenance.

A broad checklist of activities that need to be carried out as per the above schedules are given

in the participants manual.

IT plays a crucial role in tracking (w.r.t due date, date of maintenance completed & kms.

covered) and execution (send alerts to the concern officers) of explicit activities in each

schedule.

1. Introduction










OverviewB








95


Planning of fleet for preventive maintenance using IT

1. In Urban transport, it is expected that maximum buses are to be kept on-road during the day

to meet passenger’s demand with only a few buses remaining in the depot which are due for

quarterly or annual maintenance or in need of heavy repairs.

2. The maintenance management software aids in quantifying total load for schedule-wise

maintenance activity. The table below illustrates schedule-wise workload shown for a depot:

Depot Total fleet

available

Schedules to

be operated

Schedule 1 Schedule 2 Schedule 3 Schedule 4

01 100 90 90 8 1 1

Illustration

3. Shift-wise load is to be segregated based on the following info:

a. Time required to complete the scheduled activity.

b. Request from the fleet management team for want of any specific bus to be taken on

priority.

c. Availability of spare parts, as required, for carrying preventive maintenance activity for

the bus.

d. Generally, for urban transport, it is recommended to plan the shift which is dynamic

based on incoming bus flow. However, bare min. no. of buses, i.e., at least 2-3 vehicles

shall be made available before starting the shift for optimum utilization of the

workforce.

e. Non-core activities shall be outsourced, for example, cleaning & mopping of buses, tire

pressure check, tire puncture removal, driver for moving the bus within the depot etc..

Accordingly, in-house workforce requirement will reduce on account of such

outsourcing.

1. Introduction










OverviewB








96


Planning of fleet for preventive maintenance using IT

Preventative Maintenance Schedule No. of buses Shift Artisan Helper


2200hrs to 0630hrs

14 14


2200hrs to 0630hrs

04 04


0800hrs to 1700hrs

10 10

Schedule 4 1

Heavy Repairs & Oil Change 1700hrs to 0200hrs &

2200hrs to 0630hrs

3 3

Low KMPL vehicle attending & fuel performance monitoring

1700hrs to 0200hrs &

2200hrs to 0630hrs

2 2

Vehicle Examiner In-line with operations 2 2

tires preparation 1700hrs to 0200hrs &

2200hrs to 0630hrs

2 2

Depot Stores 0900hrs to 1800hrs &

0800hrs to 1700hrs

- 2

Battery & Electrical maintenance 1700hrs to 0200hrs &

2200hrs to 0630hrs

2 2

HSD oil top-up 1700hrs to 0200hrs &

2200hrs to 0630hrs

- 2

Body Fitter, Welder & Painter 0900hrs to 1800hrs &

0800hrs to 1700hrs

3

42 43

Table below outlines shift-wise estimated workforce required to complete the scheduled maintenance activities for depot 01 having fleet of 100 buses.

Illustration

1. Introduction










OverviewB








97



Snapshot shows buses due for schedule 2, 3 & 4 of preventive maintenance.

1. Introduction










OverviewB








98


Creation of Bus Master File and updating bus wise spare parts consumption

The snapshot gives vehicle related information such as the make, capacity, engine horse power, engine & chassis no..

Above snapshot gives information on bus-wise material used. This information is useful in maintenance management.

1. Introduction










OverviewB








99


Overview on Fuel Management System

IT application in fuel management ranges from receipt of fuel at the depot to consumption offuel by vehicle and recording the same.


1. Introduction










OverviewB








100


Input - Use of ITS and MIS in Fuel Management Systems

It is the format in which vehicle-wise fuel issue record is maintained. This information can be used as an input for MIS of the fuel management system.

1. Introduction










OverviewB








101


Output - Use of ITS and MIS in Fuel Management Systems

The MIS Report Generated includes:

• Daily Fuel Consumption Statement

• Depot-wise HSD Statement

• Daily KMPL Statements

• Master Statements

• Monthly HSD Inventory Statement

• Vehicle-wise KMPL Statement-Daily

• Individual Vehicle-wise Statement

• Low KMPL Vehicle Statement Daily

• Model-wise Vehicles KMPL Statement

• Vehicles-wise ABC KMPL Analysis System

• Driver-wise KMPL Statement- Daily

• Low KMPL Driver Statement - Daily

ITS Application – Sample Report


1. Introduction










OverviewB








102



Status of

availability

Effective use of

Capital

Reduction in

risk of loss


It gives a clear picture of the

constant flow of materials into

and out of the existing

inventory.

The reports on inventory helps

understand the stock position &

how to address demand;

triggers are sent at the right

time to recoupment/replenish.

The activity will aid in

investment control and planning

of maintenance orientated

operations.

The inventory management can

help in improving the demand

forecasting by analyzing data

trends from the past data. This

minimizes holding and handling

costs, reduces the investment,

and eases cash flows.

1. Introduction












103


Database: Creation for individual items

The above is a format, in which detailed information about the part is collected by the store department as a database

The snapshot shows the master list for some items whose detailed information has been collected.

1. Introduction












104


Requisition slip and Issue slip

The depot sends the requisition slip to stores department. On the same day, the store issues the required items, as available with them.

1. Introduction












105


Need for Workforce Management Systems and benefits thereof

For a public transport, management of workforce plays a very crucial ro le and has significant impact both on

operations as well as maintenance functions. The use of IT, has improved the efficiency of workforce planning

& management.

IT initiatives in workforce management are broadly classified into following subsystem:

1. Leave management system

2. Crew management system

Benefits of Leave Management systems

• Builds confidence within the staff that the system is notdriven by humans and follows all rules and regulations.

• Easy to use;

• Touch Screen Kiosk is similar to ATM.

• Audio instructions in local language for the employee

to navigate to the next step.

• In-built Printer to give leave application

acknowledgement.

• SMS confirmation of leave sanction or rejection

decision.

• Secured;

• Biometric authentication to allow employee access

system.

• Since the data is stored in a centralized server, so is

secured/no tempering of information at the local level.

Since the data of leave application is received in aconsolidated form, for unit head it becomes easier to take a

decision for grant of leave thereby enabling better planning

of crew allocation which earlier was very tedious.

Benefits of Crew Management

System

• Crew will get the duties as per rules

without any human element involved.

• No chance of partiality by the

authorities in case of duty allocation.

• Information of allocated duty is sent

via SMS.

• Since the data is stored in a

centralized server, it is secured and no

tempering of information at the local

level is possible.

• Portal for generating rosters i.e., Duty

Allocation chart and various reports

depending on designation of the crew

and with combination as well.

• The unit head, have to focus only on making provision for last minute non-

availability of crew.

1. Introduction












106


Leave Management Systems

Not

GrantedGranted


1. Introduction












107


Crew Management Systems

Design of crew management system

Screenshot of front view in which the crew is expected to log in using password or bio-metrics and select the depot.


1. Introduction












108


Crew Management Systems


Roster block creation Duty allocation

In this module, roaster blocks are created and accordingly crew duties are assigned.

Example: In the above snapshot, Block 1 comprises of 06 crew duty daily, so a roaster block

of 07 crew duty is created to take care of weekly offs. The detailed duty allocation is shown in

the snapshot “Duty allocation.”

1. Introduction












109


Key Takeaway

In this unit, it was established that non-ITS application support is required for ITS

application. The Non-ITS applications are:

• Preventative Maintenance Management.

• Inventory management assisting in maintenance management planning.

• Workforce management promoting for transparency & efficiency in working.

1. Introduction












110



1. Introduction









Project OutcomesA

Lessons learnedB

111


1










requirements.

2





equipment.



3



1. Introduction









Project OutcomesA

Lessons learnedB

112


5














8




4





• Battery performance of each bus (input & output current)- make & type wise.1. Introduction









Project OutcomesA

Lessons learnedB

113

Key Considerations









1










2

1. Introduction










Key TakeawaysB

114


as:





3




Say, for PIS:





4

1. Introduction










Key TakeawaysB

Key Considerations


115




5




6


part outsourcing?





7

1. Introduction










Key TakeawaysB

Key Considerations


116









8







9

1. Introduction










Key TakeawaysB

Key Considerations


117


be defined first.







being created.4







increase ridership.

6

1. Introduction










Key TakeawaysB

Key Considerations

Key Takeaways

118

7




requirements, etc.




its implementation.

8











1. Introduction










Key TakeawaysB

Key Considerations

Key Takeaways

119





13


up a Public Outreach Programme. Value additions to the project like Mobile Apps,





1. Introduction










Key TakeawaysB

Key Considerations

Key Takeaways

120

Thank You !

Time for discussion

121

Reference table

A. 9

B. 10

C. 11

D. 12-15

E. 16-18

F. 19

G. 20-21

H. 22

I. 23-24

J. 25-28

K. 29-30

L. 31-34

M. -

N. 35

O. 36

P. 37

Q. 38-47

A. 9

B. -

C. 10

D. 11-14

E. 15-17

F. 18

G. 19

H. 20

I. 21-22

J. 23-26

K. 27-28

L. 29-32

M. 33

N. 34-36

O. 37-38

P. 39

Q. 40-49

Delivery PPTParticipant

Manual

A. 48-49

B. 50

C. 51

D. 52

A. 50

B. 51

C. 52

D. 53

Introduction


B. Overview of ITS
















1

Fleet Management

Systems

A. Overview

B. ITS technology

C. ITS architecture


2

122

Reference table

E. 53

F. 54

G. 55

H. 56

I. 57

J. 58

K. 59-61

E. 54

F. 55

G. 56

H. 57

I. 58

J. 59

K. 60-61


Manual

A. 62-63

B. 64

C. -

D. 65-66

E. 67-68

F. 69

G. 70

H. 71

I. 72

J. 73

K. 74

A. 62

B. 63

C. 64

D. 65-67

E. 68

F. 69

G. 70-72

H. 73

I. 74

J. 75

K. 76-78

Fleet Management

Systems








2

Automatic Fare

Collection System




D. Smart cards



G. E-wallets





3

123

Reference table

A. 75-76

B. 77-78

C. 79

D. 80

E. 81-84

F. 85

G. 86-88

A. 79

B. 80-81

C. 82

D. 83

E. 84-86

F. 87

G. 88-90


Manual

A. -

B. -

C. -

D. -

E. -

F. -

G. -

H. -

I. -

A. 91

B. 92

C. 93

D. 94-95

E. 96

F. 97

G. 98

H. 99

I. 100

Passenger

Information

Systems


B. ITS technology

C. ITS architecture


E. Case study: NMMT



4

Preventive

Maintenance

Management

Systems


B. Overview








5

Inventory

Management

Systems




6

A. -

B. -

C. -

A. 101

B. 102

C. 103

124

Reference table

A. -

B. -

C. -

A. 104

B. 105

C. 106-108


Manual

A. 89

B. 90-91

A. 109

B. 110-111

A. 92-95

B. 96-98

A. 112-115

B. 116-118

Workforce

Management

Systems




7

ITS Project in

Mysore

A. Project outcomes

B. Lessons learned8


B. Key takeaways9

125




dbook.pdf)


















Pre-Training Questionnaire

ITS and MIS for Middle Managers: Pre-Training Questionnaire

The questionnaire will only take 10 minutes of your time to get filled.

The purpose of this questionnaire is to understand what you already know about the training theme.

We will ask you to complete another questionnaire at the end of the training so that we can assess

what you have learnt and how the trainers have performed at conveying the key points.

Organization and Individual Details

Name of Organization

Name

Designation

Contact Number

Email Address

No. of buses run by your organization

No. of staff in your organization

Knowledge and Expectation Assessment

Q1. What are your expectations of this training? What do you hope to gain by participating?

A1.

Q2. What is the one thing that you would most like to learn during this training?

A2.

Q3. Please rate your knowledge / skill on the following learning objectives.

A3. Learning Objective Highly

Proficient Proficient Neutral

Slightly

Proficient

Not

Proficient

Understand the city, commuting

needs of passengers, business

process and level of ITS in practice

☐ ☐ ☐ ☐ ☐

Focuses on ITS technologies,

platform & allied facility required

for ITS application in each system

and role of Non-ITS in ITS

application.

☐ ☐ ☐ ☐ ☐

Understanding the data to be

extracted from each system,

processing of data for MIS report

generation and making decisions

☐ ☐ ☐ ☐ ☐

Have adequate skills sets to

assess the requirements of each

system, prepare schematic for ITS

architecture

☐ ☐ ☐ ☐ ☐

Having broad understanding of

ways to overcome technical

hitches in implementation

☐ ☐ ☐ ☐ ☐

Formulate strategic options for ITS

implementation, role to be played

by in-house team and task to be

outsource.

☐ ☐ ☐ ☐ ☐

Validate output & outcomes of ITS

implementation ☐ ☐ ☐ ☐ ☐

Q4. Kindly provide any additional comments for this training.

A4.



Post-Training Questionnaire

ITS and MIS for Middle Managers: Post-Training Questionnaire

The questionnaire will only take 10 minutes of your time to get filled.

The purpose of this questionnaire is to assess the capacity building, assess the trainer, training

material and the training programme. Kindly f ill this questionnaire with respect to your experience

from the training session.

Organization and Individual Details

Name of Organization

Name

Designation

Contact Number

Email Address

No. of buses run by your organization

No. of staff in your organization

Assessment of the Training Session

Q1. Please rate your knowledge / skill on the following learning objectives.

A1. Learning Objective Highly Proficient

Proficient Neutral Slightly

Proficient Not

Proficient

Understand the city,

commuting needs of

passengers, business process

and level of ITS in practice

☐ ☐ ☐ ☐ ☐

Focuses on ITS technologies,

platform & allied facility

required for ITS application in

each system and role of Non-

ITS in ITS application.

☐ ☐ ☐ ☐ ☐

Understanding the data to be

extracted from each system,

processing of data for MIS

report generation and making

decisions

☐ ☐ ☐ ☐ ☐

Have adequate skills sets to

assess the requirements of

each system, prepare

schematic for ITS architecture

☐ ☐ ☐ ☐ ☐

Having broad understanding of

ways to overcome technical

hitches in implementation

☐ ☐ ☐ ☐ ☐

Formulate strategic options for

ITS implementation, role to be

played by in-house team and

task to be outsource.

☐ ☐ ☐ ☐ ☐

Validate output & outcomes of

ITS implementation ☐ ☐ ☐ ☐ ☐

Assessment of the Training Session

Q2. Please rate the training material on the following parameters.

A2. Parameter Very High High Neutral Low Very Low

Extent of coverage ☐ ☐ ☐ ☐ ☐

Relevance of contents ☐ ☐ ☐ ☐ ☐

Practical applicability of case studies ☐ ☐ ☐ ☐ ☐

Easy to understand ☐ ☐ ☐ ☐ ☐

Usefulness of reference material ☐ ☐ ☐ ☐ ☐

Q3. Was the trainer able to achieve the stated learning objectives of the session?

A3. ☐ Yes ☐ No Reasons ________________________________________

Q4. Please rate the trainer on the following parameters.

A4. Parameter Very High High Neutral Low Very Low

Knowledge of the subject ☐ ☐ ☐ ☐ ☐

Communication skills ☐ ☐ ☐ ☐ ☐

Organized and structured approach

☐ ☐ ☐ ☐ ☐

Interactive and engaging ☐ ☐ ☐ ☐ ☐

Q5. Do you think your knowledge / skill / ability on the subject has improved after attending the training session?

A5. ☐ Very High ☐ High ☐ Neutral ☐ Low

☐ Very Low Reasons ________________________________________

Q6. What are your top 3 takeaways from the training you attended today?

A6. 1.

2.

3.

Q7. Please rate the training session on the timing and duration of each module.

A7. ☐ Very Effective ☐ Effective ☐ Neutral ☐ Slightly Effective

☐ Deficient Reasons ________________________________________

Q8. What is your preference of location for this training session?

A8.

Q9. What should be the duration of this training session?

A9. ☐ 0.5 days ☐ 1 days ☐ 1.5 days ☐ 2 or more days

Q10. What should be the frequency of this training session at your level?

A10. ☐ Quarterly ☐ Semi-annually ☐ Annually ☐ Every 2 years

Q11. Kindly provide any areas in which the training requires improvement / Other additional comments

A11.



Group Activity

ITS and MIS for Middle Managers – Group ActivityITS and MIS for Middle Managers – Group Activity

Part A – Ice Breaker Question

Part B – Group Exercise

Part C – Case Study

How ITS & MIS is a solution for requirements of commuters & operators?

Substantiate with requirements /

observation / learnings.

List out some of the problems which you have encountered / observed in implementation of ITS & MIS?

Substantiate with observation / experience

Challenges

Problem Statement: The Scandas city (which doesn’t have ITS & MIS in place), the administration as a part of

enhancing the public transport services has decided to go for implementation of ITS & MIS. Since your group are

the key members of the administration, so your guidance is solicited starting from identification of requirements till

commissioning all the modules.

Solutions

You are required to form a group of 3-5 participants in order to complete this activity. Time required for completion is 40 minutes. Furthermore, 15 minutes would be given to each group to present their outcome.

ITS and MIS for Middle Managers

Documents

Transcript of ITS and MIS for Middle Managers