Professional Documents
Culture Documents
Adobe - Case Study
Adobe - Case Study
Acknowledgement
I would like to thank the staff from Adobe and their Drivers
who tirelessly assisted us during the pilot. Special thanks to
Nisarg, Prajjwal, Jaimin, Anurag, Haresh & Madan from
drivebuddyAI team for taking extra efforts to conduct this pilot
and deriving such insights for the industry. This pilot is one of a
kind in India and I hope this could become a benchmark for
making Indian Roads safer.
www.reallygreatsite.com
Pilot Program
Main Goal
PROVING A PROOF OF
CONCEPT TO HAVE ACTIVE
DRIVING SAFETY BY USING
ROAD FACING CAMERA AND
DRIVER FACING CAMERA
GENERATING ALERTS ON TIME
TO AVOID COLLISIONS AND
DISTRACTION EVENTS FROM
THE DRIVERS.
Plan of Action
www.drivebuddyai.com
PHASE
ONE
DATA COLLECTION, DRIVER
BEHAVIOR AND CHALLENGES
www.drivebuddyai.com
When we installed the vehicles in enough. We requested the fleet
highly urban areas i.e. Delhi-NCR, very manager to arrange for two drivers
interesting observation we had was only in a day and those drivers should
that in all the traffic jams, the network not be changed during the course of
used to be congested and loose the the pilot.
speed and connectivity. This caused an The car was being driven by two of the
issue for receiving high volume video drivers, day shift and night shift drivers.
data on time and ultimately resulted in Day shift started from 4pm to 9pm and
delayed delivery of cloud based night shift started from 9pm to 8am till
services. During the times when there the next morning. We were provided
was no connectivity, the cloud with all the driver details for making
platform showcased the last updated reports accordingly along with photo
location and remained the same ID.
because of no updates in the data.
The Phase lasted for almost two weeks
Conclusion Week - 1
where the data was collected from the
In the first week of installation, we
single vehicle from both the devices.
faced many challenges including
Here are few findings from the data
driver manhandling, obstruction for
analyzed.
camera, network challenges. This
resulted in poor data collection, which
Camera Misalignment
made no sense.
This was one of the biggest hurdle in
We called it off and decided to restart executing successful driver facing
Phase - I again. algorithm in running vehicle where
drivers used to disalign the camera
Phase - I Restart from it's actual viewing position,
India is a country where we as drivers causing the wrong detection.
are not used to have any kind of
assistance in the vehicle. We are less
used to the technology around us and
so for the cab drivers it is expected that
they don't attend to any aftermarket
technology. This is a serious challenge
Driver Facing Camera Misalignment
and we decided to take it on by talking
to drivers about the device and its When this misalignment was
functionality. Explaining them about identified, and the drivers were asked
the device and the functionality. Ergo, about the issue, the issue was IR light
came driver training as a value add. for night vision. Here was the challenge
We also faced an issue about the where majority of drowsiness and
changing (unauthorised) drivers. Being distractions happened during the
a driver observation platform, to night and the night-vision IR caused
prepare a report on a particular driver issue for the drivers.
and the driving amount of time must
be sufficient
www.drivebuddyai.com
Unauthenticated Drivers
This was one of the features we
developed and implemented during
the pilot phase. We had good data for
the driver faces and we took 10
pictures from phone too from different
angles for both the drivers. We applied Driver Distracted driving on 30th Aug 7:29 am
our face recognition AI model to all the
driver face data we received from the Driver Evaluation
device and identified three instances
Driver - 1
when other drivers were driving the
vehicle. This feature is very much
important and value addition for the
fleet manager to identify and get
notification of driver changes.
www.drivebuddyai.com
Driver - 2
www.drivebuddyai.com
PHASE
TWO Enabling Dual Camera View in a vehicle
www.drivebuddyai.com
Day - 3 Test Scenario - 3 - Testing Upward
The day - 2 turned out to be a bit of Direction
disappointment for the product and The test was carried out by
performance where it didn't do well making driver to put the vehicle
in the testing. on a fixed speed and then made
him look at the downward
The reason was still unidentified, We continuously for 5-10 seconds.
worked out on a solution and then The vehicle was controlled by one
tried again for the testing. of the admin with Hand brake
and steering wheel.
This time the vehicle was taken on The device did generate few alert
an empty area where there were no sounds but was not satisfactory
outside objects and testing could be enough for creating user
carried out without any causality experience as it looked like false
caused to the vehicle. alarms which generated after few
seconds of the event happened.
Test Scenario - 1 - Testing Left
Distraction Test Scenario - 4 - Testing
Drowsiness
The test was carried out by
making driver to put the vehicle The test was carried out by
on a fixed speed and then made making driver to put the vehicle
him look at the left side on a fixed speed and then made
continuously for 5-10 seconds. to close the eyes continuously for
The vehicle was controlled by one 2-3 seconds.
of the admin with Hand brake The vehicle was controlled by one
and steering wheel. of the admin with Hand brake
The device did buzz but with and steering wheel.
certain delay and was not upto The device did not generate alerts
the mark. and didn't work satisfactorily.
www.drivebuddyai.com
Conclusion
The Phase - II of the pilot was deciding enough that the functionality expected
was not achieved with 100% success rate. There many reasons behind it but it
turned out to be a great learning experience for the team trying to achieve
something which a very few organizations have tried and achieved significant
success.
The learnings were technical from the algorithms to the hardware. The learning
of operations of running and executing successful pilot which can turn out to be
a successful in Indian market was significant too. The learning of deploying an
active component in the vehicle which is definitely not for monitoring but
intended to interact with the driver where drivers have to get benefit out of it.
Technology Learning/Challenges:
Indian traffic conditions are very different than foreign traffic conditions which
are highly organized specifically in US, Japan, Europe.
Creating an AI which can work on Indian context is very complex task
considering variety of probabilities, changing in each city. For example the
Noida region has battery operated auto-rickshaws which are only limited to
urban North India.
The traffic movement on Indian city roads where employee transportation
cabs run are highly dense and creates problem in road facing camera for
generating alerts, as the vehicles run too slow and too near (bumper to
bumper traffic). Generating alerts in traffic scenarios will be annoying for the
drivers and passengers too but though the vehicle remains prone to crash if
the safe distance is not maintained.
The hardware required to run the inference must be reliable enough to run
through long times continuously.
The reason why driver distraction algorithm failed during the testing but
worked on solo testing was, "The testing was carried out with the vehicle
fully occupied, having three person sitting at the back, the driver facing
camera did detected the other faces too in the image frame received
and resulted in confusions for generating alerts and though resulted in
failure."
www.drivebuddyai.com
ADOPTION OF ACTIVE SAFETY SYSTEM IN VEHICLES - INDIAN
MARKET PERSPECTIVE
Indian fleet management industry has evolved since last few years with huge
adoption of GPS based tracking systems.
Next phase of adoption came in late 2010s was OBD - II based devices
including GPS tracking.
Indian government made it mandatory for all commercial vehicles to have
GPS based tracking systems after increase in cab aggregation business from
uber & ola like companies in late 2017.
The GPS tracking systems are certified with AIS140 which is also a mandate
for commercial vehicles.
Indian fleet management systems are highly tracking based where
monitoring of the drivers is thought to be important and any misbehaviour from
drivers lead to the cuts in wages. This is helpful in a way where drivers tend to
cause damage to the systems installed in the vehicle meant for tracking.
For active safety devices, the different type of mindset is required from the fleet
managers as well as from the drivers. Indian ecosystem is less sensitive about
the safety where preventive mechanism is not easily accepted. Another
important aspect is about drivers where majority of drivers do not have
habit of any kind of assistance in the vehicle where they tend to listen to
certain assistance and act on it accordingly.
Now the world is heading towards the era of Artificial Intelligence and data
centric approach where data and insights can help making decisions for
organizations.
The approach would be to get insights from the drivers from the device,
analyze the driving pattern, annotate the data, train the AI models, validate
and then upgrade the hardware back again with learned intelligence from
thousonds of drivers.
This will lead to autonomy in the upcoming future where India will too lead the
race in the Autonomous Systems globally by solving the most complex traffic
ecosystem.
www.drivebuddyai.com