Copyright © 2016 Firelake Capital 1 Peter Shannon May 2, 2016 A Practitioner’s Guide to Commercializing Applications of Computer Vision
Apr 15, 2017
Copyright © 2016 Firelake Capital 1
Peter Shannon
May 2, 2016
A Practitioner’s Guide to Commercializing
Applications of Computer Vision
Copyright © 2016 Firelake Capital 2
Joined Firelake Capital in 2010
• Eye Response Technology startup co-founder
• Systems engineering and computer science by training
• Previously at Atlas Venture from 2005
• Chicago Booth MBA
Investment focus
• Transportation systems
• Food systems
• Energy systems
Peter Shannon
Intersection of
digital and
physical worlds
Copyright © 2016 Firelake Capital 3 3
IT Drivers Big Data
Sensors
Cloud Infrastructure
Computer Vision
Robotics
Sustainability Drivers Distr. Generation (solar)
Batteries
Electrification Complex
Fuel Cells
Ag Innovations
Tech Platforms Industrial IoT
Drones
Autonomous Vehicles
EV Infrastructure
Microgrids
New Bus. Models Software-driven
Finance-driven
Bus. process-driven
“Applications &
Solutions”
Focus on Applications and Solutions
Copyright © 2016 Firelake Capital 4
In my earlier days
Copyright © 2016 Firelake Capital 5
Copyright © 2016 Firelake Capital 6
Copyright © 2016 Firelake Capital 7
Key Challenges — Retrospective
Underlying Technology • USB still 1-2 years away
• Cameras bulky, expensive, low resolution
• Facial recognition algorithms still in academia
• Compute power limited (Intel Pentium)
• No computer vision software libraries
Performance vs. Robustness • Each application has different reqs
• Hard to tell when the product is
“robust enough”
Architecture Choices • Hardware
• Balance competing factors
• Upfront choices you must live with
Copyright © 2016 Firelake Capital 8
Inductive reasoning – is reasoning in which the premises are viewed as supplying strong
evidence for the truth of the conclusion.
While the conclusion of a deductive argument is certain, the truth of the conclusion of
an inductive argument is probable, based upon evidence given.
Computer Vision is Inductive Reasoning
Copyright © 2016 Firelake Capital 9
Deductive vs. Inductive — Development Process
Requirements
Develop
Test
Deploy
Requirements
Develop
Test
Validate Robustness
Deploy
Copyright © 2016 Firelake Capital 10
Consequence of Error
Copyright © 2016 Firelake Capital 11
Copyright © 2016 Firelake Capital 12
Copyright © 2016 Firelake Capital 13
Copyright © 2016 Firelake Capital 14
Copyright © 2016 Firelake Capital 15
Copyright © 2016 Firelake Capital 16
Comparison to Speech Recognition
Copyright © 2016 Firelake Capital 17
Copyright © 2016 Firelake Capital 18
Copyright © 2016 Firelake Capital 19
1995 1995
Copyright © 2016 Firelake Capital 20
2003 2003
Copyright © 2016 Firelake Capital 21
2010 2010
Copyright © 2016 Firelake Capital 22
2016 Today
Copyright © 2016 Firelake Capital 23
More types of risk in a venture multiplies the overall risk and uncertainty in
terms of time, people, and capital required to achieve the end goal.
Overall Risk Factors
Performance
Robustness
Market
Product
Execution
Copyright © 2016 Firelake Capital 24
Implementation Considerations
Copyright © 2016 Firelake Capital 25
Decisions you make now are ones you have to live with for the product’s
lifecycle
Conventional wisdom of Minimum Viable Product, speed to market and
failing fast does not apply in the conventional sense
Plan for the End Game
Copyright © 2016 Firelake Capital 26
• Need to account for a very large number of factors
• For many applications, a machine-learned algorithm is not sufficient
• Additional application-specific algorithms must be engineered
Expect to spend 10% of time on main algorithm design, 90% on additional
logic for robustness
Achieving Robustness is Difficult
Copyright © 2016 Firelake Capital 27
• Hardware-aware software design choices are often necessary
• Picking the best algorithmic approach and the right hardware is difficult,
but a crucial decision that will shape the lifecycle of the product
Vision Products are Hardware-Software Systems
Copyright © 2016 Firelake Capital 28
• Your product is a carefully tuned system unifying software and hardware
working together
• What happens when suppliers upgrade components, e.g. cameras, etc.?
• Cannot be certain system performance will automatically improve
• Your application may need to be re-tuned to accommodate the hardware
Supporting The Product Going Forward
This is an ongoing task you need to
plan for and architect your system for
Copyright © 2016 Firelake Capital 29
• Q&A
Thank You