Download - Enterprise IoT solution in 30 days
Manolis NikiforakisEx Machina, CEO
Enterprise IoT solution in 30 days
Keynote Speaker @ Boussias IoT Conference, June 2017
About me: Manolis Nikiforakis
BEng Computer Engineering & MSc Internet Computing16 yrs enterprise full stack developerIoT solutions architect
IoT Athens Meetup co-organizerTheThingsNetwork Athens initiatorIoT Guru Network consultant
Dad, biker, kitesurfer, hacker, coffee enthusiast, 3D printer & multicopter builder
74% of IoT projects are NOT successful
Cisco survey of 1,845 business and IT decision-makers in mid-market and enterprise companies
Top reasons include:
● Long completion times● Poor quality of the data collected● Lack of internal expertise● IoT integration problems● Budget overruns
newsroom.cisco.com/press-release-content?type=webcontent&articleId=1847422
Cisco identified two main failure points
1. Integration Complexity
2. Lack of Internal Expertise
https://blogs.cisco.com/news/ciscos-new-iot-platform-will-take-your-projects-past-proof-of-concept
Why do companies struggle with IoT & digital transformation ?
IoT not permanent in agenda
1.559 executives across multiple industries, 78% claim IoT critical
only in 38% was a permanent fixture in their business’ agenda
Reference: MIT Sloan Management Review and Capgemini Consulting
Digital Maturity Index - 65% Beginners
Reference: MIT Sloan Management Review and Capgemini Consulting
Beginner - email, social media, some enterprise software
Conservative - deliberately hang back
Fashionista - aggressive in new tech, lack coordination
Digirati - gaining most value of new tech
The pace of digital transformation is too slow
- Unless you’re the CEO
Reference: MIT Sloan Management Review and Capgemini Consulting
Institutional Barriers
1. Attitudes of Older Workers
2. Legacy Technologies
3. Innovation Fatigue
4. Internal Politics
Where is the CIoTO ?
Reference: MIT Sloan Management Review and Capgemini Consulting
Main failure points - developer’s view
1. Wrong development methodology
2. Closed source approach/technologies
Successful IoT Transformation
IoT & digital transformationis a Journey,
Not a One-Time Event
IoT advice - helicopter view
● Solve a problem that someone cares about● Plan realistically● Fix outdated processes and policies● Drive shared ownership and accountability
○ Partner for success, get engineers with broad skills
● Augment your capabilities with outside resources○ Be skeptical of “IoT experts” and the marketing hype ○ Too early to have many Gurus! (except for http://iotgurus.net/)
● Address resistance to change● Define extended project success and goals● Establish a learning culture, be flexible and adapt
○ Test game-changing business models
Moving from cost savings to REVENUE GENERATION
● Needs strategy & alignment across key stakeholders
● User-centric○ NOT an inside-out approach
● NOT as hardware/box moving○ What to charge○ How to charge○ Go-to-Market
● Technology○ rapid iteration, flexible, no lock-in, secure
Waterfall vs Agile
Waterfall failure for IoT
1. Defining and discussing the full blown project
2. Planning the entire project, searching for the relevant devices,
technologies, dashboards, etc.
3. Presenting to customer and getting feedback.
4. Preparing cost estimates for the entire project.
5. Build everything in one go, sensors, communications, dashboards, rules,
data analytics.
6. Get customer feedback, start resource-intensive changes
IoT breeze, best served with Agile
1. Priority to provide value immediately and continuously through quick development and rapid cycles of enhancements and additions.
2. Welcome changing requirements, at any time, even late in development. Harness change for the customer’s competitive advantage.
3. Deliver application enhancements frequently, every few days/weeks.
4. Developers continuously collaborate with all stakeholders to deliver the most useful application given time and budget constraints.
5. A working IoT application that creates value is the primary measure of progress.
6. Simplicity – the art of identifying out of scope at any given point — is essential.
Open vs Closed
IoT demands the open source advantages
Reference: MachNation - Benefits of an Open Source approach to IoT AEP
IoT Value Chain Decisions
Open-Source SoC
SiFive Freedom E31032-bit RV32IMAC
320+ MHz
Open-Source telecommunications
IoT Value Chain Decisions
Middleware / AEP / IoT PaaS
IoT Application Enablement Platforms - key traits
1 Flexibility of deployment modelCloud-based SaaS - Geo-distributed, multi-tenant, multi-instance - On-premises, edge, fog, scalability, security , fault tolerance
2 Focus on the developer personaCogent system architecture, documented, APIs, barrier-free
3 Sophistication of management capabilitiesDevice management & monitoring sophistication
4 Comprehensiveness of overall platformMaturity of solutions 5 Well-executed partnership strategyHosted/Managed PaaS with tech support and consulting
Reference: MachNation - Five Key Traits of Leading IoT Application Enablement Platforms
IoT USE CASE
Customer: Refrigerator Manufacturer
Subscription based refridgerator monitoring service
Multi-tenant: Manufacturer, 3rd party technicians, end customers
● Phase I - Pilot aiming for MVP○ Temp and door monitoring/alerts○ Get stakeholders working together
● Phase II - Collect insights○ Collect Energy, Vibration, Noise, Weather○ Upgrade hardware & comms LoRaWAN/NBIoT
● Phase III - Disrupt/Innovate○ Scale & Compare○ Weather normalize○ Predictive maintenance○ Cold as a Service new business model
Phase I in 4 weekly Sprints
● Week 1 - Understand scope, set MVP goal○ Identify stakeholders and assumed MVP○ Set framework○ Produce simple demo (simulated data)
Phase I in 4 weekly Sprints
● Week 1 - Understand scope, set MVP goal○ Identify stakeholders and assumed MVP○ Set framework○ Produce simple demo (simulated data)
● Week 2 - Elaborate on simple demo○ Set goal,prepare for PoC: e.g. SONOFF ESP8266 + Managed/Hosted open
IoT PaaS Thingsboard.io
Phase I in 4 weekly Sprints
● Week 1 - Understand scope, set MVP goal○ Identify stakeholders and assumed MVP○ Set framework○ Produce simple demo (simulated data)
● Week 2 - Elaborate on simple demo○ Set goal,prepare for PoC: e.g. SONOFF ESP8266 + Managed/Hosted open
IoT PaaS such as Thingsboard.io
● Week 3 - Deploy PoC in-house / factory○ Get feedback, improve
● Week 4 - Deploy PoC at customer test group○ Get feedback, improve○ Achieve MVP Goal, validate assumptions○ Set next EPIC/Phase
Manolis NikiforakisEx Machina, CEO
twitter·@nikil511site·exm.gr