Delivering a commercially successful end-to end IoT Solution.
•Download as PPTX, PDF•
1 like•282 views
John Savage, Action Point CTO, presented this talk 'From Concept to Concrete. Delivering a commercially successful end-to end IoT Solution.' at the recent IoT Summit in the Galway Mayo Institute of Technology. He talks about what you should look out for if embarking on an IoT project.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Delivering a commercially successful end-to end IoT Solution.
Similar to Delivering a commercially successful end-to end IoT Solution. (20)
More from Miriam O'Brien
Recently uploaded
Recently uploaded (20)
Delivering a commercially successful end-to end IoT Solution.
- 1. From Concept to Concrete. Copyright © 2016 – Action Point Innovation Ltd.
- 2. Delivering a commercially successful end-to end IoT Solution. Copyright © 2016 – Action Point Innovation Ltd.
- 3. Who we are IoT Custom Software Developers and System Integrators. Copyright © 2016 – Action Point Innovation Ltd.
- 4. Common Project Pitfalls Unclear Objectives Unrealistic Expectations Tentative Stakeholders Copyright © 2016 – Action Point Innovation Ltd.
- 5. Unclear Objectives Don’t let Techies Rule the Roost - IoT is a great solution, looking for a problem - Sensors and Instrumentation is (relatively) Easy - To get from Concept to Concrete requires a Concrete Concept Copyright © 2016 – Action Point Innovation Ltd.
- 6. Unrealistic Expectations Don’t let Non-Techies Rule the Roost - Lots of “Easy” Building Blocks - Lots of Marketing Spin - C-Suite Expectations can swell Copyright © 2016 – Action Point Innovation Ltd.
- 7. The Ultimate Balancing Act? Copyright © 2016 – Action Point Innovation Ltd.
- 8. Easy Stakeholders > Manufacturing, Consumer Goods… Hard Stakeholders > Insurance and Smart Cities IoT may require novel business models > Funding required to prove Tentative Stakeholders Who will Pay? Copyright © 2016 – Action Point Innovation Ltd.
- 9. Typical “Project Budget” Journey How much will “it” cost? “it” requires more than the obvious requirements MVP, Go-Live, CapEx, OpEx… Copyright © 2016 – Action Point Innovation Ltd.
- 10. The “Bright” Idea An app for a smart light bulb - that’s pretty easy right? Copyright © 2016 – Action Point Innovation Ltd.
- 11. Development Costs The commercial reality behind the “Bright” Idea IOT Device Management Operational Costs So how do you manage budget for something as complex as this? Customer Service Roadmapping Platform Choices (Desktop, iOS, Android etc.) Architecture Design UI/UX Design Development Testing Connectivity (WiFi, BLE, Sigfox, Zigbee) Logistics Manufacturing Provisioning Field Engineering Support Billing Engine Server/Storage Infrastructure Support Updates MVC vs Go-live vs future enhancments Support Device & System Updates Copyright © 2016 – Action Point Innovation Ltd.
- 12. The Drake Equation How can we estimate the number of technological civilizations that might exist among the stars? Anyone know what this is? Copyright © 2016 – Action Point Innovation Ltd.
- 13. Drake Equation for IoT Budgets? 8 Major Components Device/Sensor Edge Gateway Connectivity Cloud Infrastructure Server Application(s) Client/Mobile Application(s) Analytics Services & Support Copyright © 2016 – Action Point Innovation Ltd.
- 14. Incrementalism is Key Copyright © 2016 – Action Point Innovation Ltd.
- 15. Summary Forewarned is forearmed Embrace an MVP and Incremental Progression Be prepared for Complex Cost Model Work with PARTNERS, not Vendors Copyright © 2016 – Action Point Innovation Ltd.
- 16. Questions? www.action-point.com Copyright © 2016 – Action Point Innovation Ltd.
Editor's Notes
- Hi Enjoying day? Perilous Journey
- People understand slices Pulling the components together is challenge Set the scene => Orgs embarking => Can’t afford to make mistakes
- SI in the IOT space multiple partners and Unified solution Industrial IOT in automotive manufacturing => four external partners in partnership with Dell and Intel We have turned down more IOT projects than we have started. Things we look for.
- Main challenges => Three categories. Detail to come Common sense, but plague IoT in particular
- Don’t let the techies… I’m a true techie myself. Solution problem. IoT is enabled by “easy” h/w and s/w blocks and ubiquitous connectivity. Someone has to pay the bills. Make “why” is clear within and throughout ALPS management questions Direct revenue not always goal => AGA marketing Ensure Objective understood => ROI/business outcome => let technology row in behind
- Loads of 10 minute demos => Show blocks => commercially ready end-to-end to survive real world => Coordinate moving parts Action Point’s often first technical input Significant “expectation management” activity” Implementing an IoT => bringing all the components together => extremely complex => will impact all elements of your business. Non-techie => be prepared to scale back => use the power of building a Minimal Viable Product MVP => fully functioning => proves the techies => non-techies see working system => rove the viability without huge risk.
- IoT projects look easy from side lines=> L:ook familiar? Balance technical bottom up with non-technical top down => Get the best from all members Find the Balance.
- Team is balanced => who will drive it? Key stakeholder can be unsure. Hear about benefits, but don’t believe. What’s in it for me? Traditional software projects => new products/services => Easy roi. IoT value-add can require leap of faith. What is exact beneft? Manufacturing are easy! Stakeholder not in the room. Public in a city. “build it and they will come” = scary Operational stakeholder different to financial => resolve conflict? Stakeholder must drive & fund => Not confident = trouble Must get stakeholder comfortable. Common question? So how much will “it” cost?
- Over a decade = expecting “how much will it cost” after 15 minutes “we don’t yet know what “it” is, so we can’t say until we work closely with you”. IoT projects => “it” is very often a vague vision or accidentally huge in scope. IoT projects => “budget journey” vs. “budget process” Here’s why…
- Smart lightbulb company => extremely well prepared. Sample lightbulb and detailed screen mockups Described app in detail => Cool functions “Lets build a mobile app that connects to a smart light bulb” – that’s easy right? 1-hour conversation changed their world.
- Slide = Lots in full product lifecycle => Two jump out. How to connect app to bulb? WiFi/Sigfox/BLE/Gateway… All a have a significant manufacturing impact. Other is Customer Service functionality. Public have questions you need to answer. CS team need information. Business model => Billing management? Lot to consider => Not all are relevant to every project Hard-won experience => enumerate your cost centres
- So…. Estimating the scope => full of unknowns. Does anyone know what this is? Yes/No?? Drake Equation => 60s => estimate how many aliens in universe Real value not answer but thought process prompted to solve. A very solid structure to use when contemplating an otherwise impossible question. So…
- “Drake Equation” for IoT budgets? We tried, but not as eloquent => By some measures ET counting is easier! 8 major components => Correspond to the IoT stack. Real challenge is not independent factors. Example, cheap software at edge costs edge processing and bandwidth. Lightweight Analytics vs heavyweight impacts full stack. Layer on top project goals of Prove a concept vs. go-live to 100,000+ city and CapEx/OpEx tradeoffs => complexity costing an IoT project. Estimating = beast… almost elephant?
- How do you eat an elephant? One bite at a time! Can’t overemphasise power of MVP in IOT. Do your MVP right! Each step fully usable. MVP focusing on just the hardware or just the cloud => One layer => Not dealing with main IoT complexity => all the layers interact with each other. Narrow end-to-end will prove you’ve cracked the nut
- In Summary => I hope you have insight on complexities. I purposely no tech deep-dive => Building blocks are there. Experienced partners Exist. Each Layer of IOT is easy => Why it’s exciting. Real challenge => Bring it together => single coherent solution… commercially successful! Final advice => IoT => bring in “partners” rather than “vendors”. Requirements will almost certainly change => Work with enablers of success Thank you for your time.