Successful Industrial IoT Patterns

John MathonVP, Enterprise Evangelism and

Product Strategy WSO2

Agenda

❖ IOT Basics

❖ IoT Standards

❖ Enterprise IoT

❖ Enterprise Patterns

Publish/Subscribe

Joe Mary FrankExchange Clearing

This is what I started TIBCO with

Subject Filter

Subject Filter Subject Filter Subject Filter Subject Filter

IoT Markets - Truly Enormous• Hobbyist (both home and

industrial)o Apple challenged the world

to make apps - 600,000 apps in 2 years

• Consumero The consumer is just

starting to have fun

• Industrialo Already exists

• OEMo Lots of help available

IoT Hardware Segmentation• Hardware

– Communications– Hubs– Devices– Computation – Integrated Devices– Integrators

• Software– Embedded Software– Hub Software– Communications

IoT Software SegmentationThousands of Companies already providing Software and Services

• Device Abstraction - taxonomy and description of all IoT devices EVRYTHNG• Data Storage - means to store data from IoT devices DEVICEHUB• Pub Sub platforms - M2M or M2C communication PUNUB• Analysis - analysis of device data INFOBRIGHT• Visualization - mobile device, application or web app tools FREEBOARD• Integration - orchestration of real time events to perform actions IFTTT• Service - services to individuals, corporations, government XIVELY

IoT Ecosystem Driving PersonasEnterprise IT - ImplementersGold Seekers - EntrepreneursExplorers - CuriousHunters - Whatever WorksGuns for Hire - ConsultantsHobbyists - MakersMoochers - LatchersMobile Wannabees – YearnersGamers

Product Extenders - Add connectivity

Existing Device /Sensor Manufacturers

Mobile Device CompaniesDigital Hardware CompaniesSoftware InfrastructureCommunications CompaniesData Companies Existing App Companies

Main Business Drivers IoT

1. Cost Reductions - Consumer, Building, Operations

2. Increased Quality - Operations

3. Convenience - Employee, Consumer

4. Stickiness - Business Top Line

5. New Products / Markets - Business Top Line

Almost Every Business will be interested for some reason

IoT Best Practices to build for Enterprise

Build a Great Device

❖Security

❖Encrypt Data at rest and in motion

❖Allow fine grained control of authorization around controls and data visibility

❖Provide automated upgrade service

❖Ease of Use

❖Provide multiple UI mechanisms for cell phones, web, apis and visually on the device itself if it makes sense

❖Data

❖Provide Device Management functionality including ability to wipe device, upgrade and configure through Dev Management APIs

❖Power Management, Failure Detection

❖Must warn well in advance, Send still alive message and detect failures, tampering

❖APIs

❖Provide APIs to everything as Enterprises can build integration

IoT Standards Much Left To Do • Hardware / Embedded

– Communications - Zigbee, NF, Zwave, BLE, 802.11ah, Cellular, IEEE 802.15.4 and …– Security, Discovery, Application - Allseen Alliance, OIC, IIC, Google Thread,

Zigbee, IEEE P2413, OneM2M

– Hubs - SmartThings, Vera, Insteon, Ninja, Homey, Apple and ...

• Data

– Where is the data? Device, Hub, Local, Cloud, Enterprise, Hybrid

• Security – Who sees what you have? How do you add? How do you remove? Who can do what?

Who can see what? How do you upgrade? How do you monitor?

– UMA

• Orchestration Tools– ESB, BPM, Rules Engine, IFTTT, other ?– Where is the control/Orchestration? Cloud, Dedicated Device, Cell Phone?

IoT Security Issues• Authentication - How do you know the device or user is who they say they

are?• Authorization - What can that user / device do?• Logging - How do we monitor?• Update - How do we upgrade?• Encryption - Always, sometimes, how?• Enforcement Points - Security distributed?• Policies - Establishing automation (UMA) for groups of people or devices• API - API keys? More?• Data - Field level security?• Privacy - Who can see?

IoT Security State of Affair❖ Consumer - Terrible, Terrible, Terrible

❖ No Authentication, Frequently no encryption

❖ No automated upgrading

❖ No control over who can see or do what – Fine Grained Authorization

❖ Enterprise - Somewhat better

❖ Some devices auto upgrade

❖ Some devices have fine grained authorization

❖ Most devices have encryption data in motion, some for data at rest

IoT Integration Issues• Different Communication protocols• APIs, SDKs for mobile or servers, Cloud Services, Device level Services, Hub

Services• How to scale?• Who owns the device?• Privacy• Authorization • Which Orchestration Tools or Products?

IoT for the Enterprise - Different requirements

• The building / factory

• The employees

• The customers

• OEM

IoT Reference Architecture - Building / Factory 1. Devices

a. Reliable, Secureb. Hard Connectionc. Device Profile Known

2. Data Caching at local sites3. Sophisticated Analysis4. Optimization5. Diagnosis / Failure Warning6. Eventing7. Device Management8. Integration to Finance,

Accounting, Security

1. Purposesa. Energy - HVAC, Lightingb. Automation – Cost

reductionc. Securityd. Quality Engineering

Very High CriticalitySophisticated Integration not a

problemMay be willing to accept non-

standard if superior security, functionality

IoT Reference Architecture - Employee 1. Devices

a. Secureb. Device Profile Knownc. Size / Portability

2. Diagnosis / Failure Warning3. Flexibility to support small

variety of devices4. Eventing5. Device Management6. Integration with Automation

Systems, Sales, Marketing, Management, Content Management Systems

1. Purposesa. Productivity of

Employeesb. Convenience

Medium CriticalitySome Integration may be done

IoT Reference Architecture - Customer 1. Devices Key Functionalities

required

2. Flexibility to support wide variety of devices

3. Eventing4. Store Data5. Analytics Critical6. Discovery7. Good UI8. Integration with Automation

Systems, Sales, Marketing, Management, Content Management Systems

1. Purposesa. Create Stickinessb. Create Value for

Customerc. Inexpensive

Application dependent CriticalityHigh Integration Expected

IoT Reference Architecture - Consumer 1. Devices

a. Key Functionalities required

b. Security less immediate concern

c. Ease of Use

d. Size / Portability

2. Ultra wide variety of devices3. Eventing - Some automation4. Need to Store Data5. Discovery Easy6. Good UI7. Integration with other IoT desirable

1. Purposesa. Convenienceb. Attractivenessc. Featuresd. Inexpensive

Lower Criticality

IoT End to End NeedsMiddle ServicesCustomer Device

OS

Application

Security

Communication / Power Mgt

Visualization / APIVisualization

OS

Security / PolicySecurity

OS

Visualization / API

Data Stream / Storage / Mgt

Eventing/Analysis/Optimize

Orchestration / Integration

Eventing/Analysis/Optimize

Interaction Pattern

UI

IOT Reference Architecture

Device

API MgtDev Mgt

Service Bus BPMBigData

Long Term Analysis

Activity Mgt

Cloud

CEP

Cloud Orchestration/Integration

Comm

Provider

OS

Application

ESB, Security

OS

ESB, IM, PEP

Data Infrastructure

HubOrchestrationIntegration

Rules Engine

Data

Dev Mgt

Rules Engine

User Dashboard

IoT Mgt Dashboard

IoT Use Cases• Car Manufacturer

• Construction Company

IoT Use Cases• Car Manufacturer• Construction Company• Hospital• Shopping / Online merchants• Corporate Office• Home / Consumer

IoT Reference Architecture - OEM 1. Devices

a. Key Functionalities required

2. Flexibility to support wide variety of devices

3. Eventing4. Store Data5. Analytics Critical6. Discovery7. Good UI8. Integration with Automation

Systems, Sales, Marketing, Management, Content Management Systems

1. Purposesa. Create Stickinessb. Create Value for

Customerc. Inexpensive

High Criticality CriticalityHigh Integration Expected

IoT UseCase – Connected Car - Tesla• Tesla

– 60% employees software engineers– Integration of hardware key– User Experience Important – Tesla redesigned the car from the ground up

– Even other electric cars basically look like an ICE care. Not fully integrated.– Feedback to Tesla

• Tesla Connected Car PROVES the case 98-99% customer satisfaction 2 years in a row• Ability to upgrade truly amazing• Smartness of the car astonishes

Tesla did more than build an electric car. They have created disruption in:– Car integration– Safety – broke previous safety ratings– Performance – faster than any production car in the world– Service – upgrades over the air, remote service, no maintenance required– Smartness – knows where to go, how high to go, what temperature, charges anywhere– IOT – connected all the time, data streaming back to the factory

ConnectedCar - Functionality– All hardware systems of the car integrated with digital platform to control, monitor,

automate, monitor• Eventually leading to self-driving car

– Integrated Apps in Car - Calendar, GPS, Energy, Settings, Entertainment, Phone, Climate, Profiles

• Smart Car - knows when to lift suspension, when to ask me where to go, when to climatize the car

– Always Connected - monitor, find, pre-condition, secure– Unattended Upgrade - Feature improvement, Service Improvements– Feedback to Manufacturer

• Data used to improve service and design decisions, normal use, crash, ...• Data used to optimize function, improve capabilities• Easy bug report

– External Apps - Tesla App iPhone, Android, iWatch...– External API - Open API– 3rd party integration - TeslaApps, Logging and Analysis companies

Connected Car

API Mgt Dev MgtUpgrade

Cust Svc Service Bus

Design

BPM

BigDataLong Term Analysis

Activity Mgt

Service Bus

Polling LoggingEvents

BrakesBrakesBrakesBrakes

Console

Phone

Watch

3rd Party App / Device3rd Party App /

Device3rd Party App / Device

Brakes

Hi Priority

Planning

Lo Priority Apps

CellVen Cloud

CEP - Service

TheCar

CarCompany

IOT Use Case – Connected Construction

❖ Management of worksites is difficult. Numerous tools and people are needed and scheduling the expensive tools, people and work can be difficult. Tool breakdowns, changing work plans lead to wasted time and increased costs

❖ IoT the tools, track their usage and location, help contractors manage, track their expensive equipment and plan for their use better

IOT Use Case – Connected Construction

– Tools are instrumented, some with replaceable NFC, some with active IoT to control, monitor, automate

– Cars, trucks, equipment of all sorts even down to hammers can be actively tracked with bluetooth and cell phones or NFC technology

– Integrated Apps on worksite and dedicated devices to collect information – progress, where things are, requesting tools or services

– Unattended Upgrade - Feature improvement, Service Improvements– External API - Open API to encourage integration by 3rd parties– Planning tools to help coordinate complex tool needs and people needs

Connected Construction

API MgtDev Mgt

Cust Svc

Service Bus

Design

BPM

BigDataLong Term Analysis

Activity Mgt

Phone

Vehicles

Tools

Hi Priority PlanningLo Priority

Cloud

CEP

Building Sites

VehiclesVehicles

PhonePhone

ToolsTools

Tools

Data Gather DeviceData Gather

Devices

WharehouseWharehouses

Tools

Data Gather Device

Contractors

Design Contractor Planning

Tool

Connected Construction

WSO2 Commercial

Connect the World

Applicatio

ns

People

Devices

We help our customers become a

Connected Business

Enterprise App Store

API Management SaaS Adoption

Executive Dashboards

PaaS

Mobile Apps

Open Source Adoption

SOA

Cloud Adoption and Automation

Federated Identity

Social Networking

Mobile BYOD

Big Data and Analytics

Systems of Systems Functional Requirements

Complete Enterprise Middleware

ONLY company to ever build a complete middleware stackon-premises, in the cloud and on mobile devices.

SINGLE codebase for all products!

✓ Integration✓ API Mgt✓ Shadow IT✓ App and Device Mgt✓ Identity and Access Mgt✓ Enterprise Scale and Quality

Thanks4Listening❖ My twitter: @john_mathon

❖ My blog: CloudRamblings