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