our experience with m2m
TRANSCRIPT
our experience with m2mJüri Tarkpea, CTO, Oskando
oskando - brief technological history
……. - 2007: hardware design, development and production in quantities of ~100-1000
2007: started web software development
2011 - …. killed hardware design and production
2013Q3 merger with autolog (dk), currently having 35’000+ m2m units in SaaS
my background
web development. only.
scared of all hardware
have soldered only a few guitar cables
have not read this book ->
google: m2m people
google: webdev people
m2m
machine to machine
at least one of these machines is serving one narrow purpose and is always pretty stupid
m2m
specific hardware for reading&writing IO digital/analog IO, GPS, temperature
communication channelusually tcp/udp over gsm (gprs, sms, voice, ussd) or satellite
server / userstorage and data processing
a few examples
gps tracking / security gps/io data to server
remote switchingsaunas / car heaters / boom barriers / air pumps
remote sensingweather / road conditions
hardware challengesdevelopment & technology
long time from zero to “done in development”. long time from “dev” to “production”
difficult to debug
costs every physical piece costs. installation costs. maintenance costs.
high expectations sofware is expected to break or have bugs. hardware is not.
communication challenges
costs, againare you counting bytes, megs, gigs?
what is the expected availability?
server-side challenges
the amount of data we’re currently going at
350 incoming messages per second 3.7G of raw data per day
business challenges
does not scale well
extra hassle with warranties, export/import, finances, stocking, installation etc
m2m market
twice as fast development as mobile
much bigger in perspective
starting m2m business?
strong financesstrong support
exceptionally good hardware & software
why would anyone do it?
uncertainty"
can be very interesting & exhausting
in touch with physical life
