room 5 best practices for developing smart connected products
TRANSCRIPT
October 2014
Best practices for developing smart connected products
byErik Ljung
Questions? post in question panel tweet to #room5iot [email protected]
Welcome to our IoT technical webinar
2
embedded & wireless
graphics UX/UI
Tactel AB foundedin Malmo, Sweden
1995
Tactel opens first US office in San Diego
20072005
Tactel AB acquires Southend Studios
2009
Tactel receives first external
capital
Tactel US becomes independent subsidiary
2011 2013
Tactel US becomes Room 5
Incorporated
multimedia
android
IoT
Smart connected products
smart phones
iOS
windows phones
About Room 5
3
• Embedded development• Kernel (Power/GFX)• Middleware and frameworks• Cloud and Web 2.0• Mobile application development• 3D graphics rendering• Software Architect• Technical Lead• Engineering Management
About Erik Ljung, early IoT pioneer
• Sony Ericsson• Qualcomm• Amazon• DARPA• L3 - Photonics
What’s the Internet of
Things?
Smart connected products and applications
Typical issues facing an IoT solution architect• No master reference architecture• Multiple technical disciplines, with various
development life-cycles• Multiple integration points
Our approach
• Our approach is to start with the scope of the product – what are trying to accomplish?
• Identify primary use-case(s) that span multiple technical disciplines– Custom or existing cloud services, integration points?– Persistent connectivity?– Seamless or manual connectivity setup?– Communication protocols?– Security aspects?– What type of handset(s) should be supported?
• Based on the high-level system architecture do the deep dive in each area– Off-the-shelf platforms, frameworks, components?– Development tools?– Timeline and planning?– Traditional embedded and HW requirements like BOM, power budget, memory ..?
• Mesh• ZigBee• Flexible IP Gateway
Industrial assets calling home
The smart construction site
Remote access to a smart controller
A next generation smart lock
The other way around
Summary
• Start with the scope of what you are building and the primary use-cases• Let the primary use-cases drive the high-level architecture and design choices• Base it on existing reference architectures• Once the high-level architecture aligns the primary use-cases consider your in depth technical
options• Iterate the design with input from various technical disciplines• As a solution architect give yourself a broad understanding of the various building blocks
Lets avoid grumpy engineers that need to patch a broken architecture ..
Thank you!
14
Q&A
15
• Feedback via survey• Executive webinar on Nov 12th at 10am PDT
“Co-creation, the hidden disruption in IoT”
• Next technical webinar in this series in January 2015• Questions or schedule a 1:1 strategy session with Erik?
contact Karen Mills: [email protected], 760-585 9562
Next steps
16
Our Clients