What are the standards for IoT? What are the requirements for different parts of your business for IoT? For your infrastructure? For your employees? For your customers? For your partners? Examples of Successful Enterprise IOT architecture patterns and use cases. What are problems like security for IoT?

1. Successful Industrial
IoT Patterns
John Mathon
VP, Enterprise Evangelism and
Product Strategy WSO2

2. Agenda
❖ IOT Basics
❖ IoT Standards
❖ Enterprise IoT
❖ Enterprise Patterns

3. Publish/Subscribe
Joe Mary FrankExchange Clearing
This is what I started TIBCO with
Subject
Filter
Subject Filter Subject Filter Subject Filter Subject Filter

4. IoT Markets - Truly Enormous
• Hobbyist (both home and industrial)
o Apple challenged the world to
make apps - 600,000 apps in 2
years
• Consumer
o The consumer is just starting to
have fun
• Industrial
o Already exists
• OEM
o Lots of help available

5. IoT Hardware Segmentation
• Hardware
– Communications
– Hubs
– Devices
– Computation
– Integrated Devices
– Integrators
• Software
– Embedded Software
– Hub Software
– Communications

6. IoT Software Segmentation
Thousands 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

7. IoT Ecosystem Driving Personas
Enterprise IT - Implementers
Gold Seekers - Entrepreneurs
Explorers - Curious
Hunters - Whatever Works
Guns for Hire - Consultants
Hobbyists - Makers
Moochers - Latchers
Mobile Wannabees – Yearners
Gamers
Product Extenders - Add connectivity
Existing Device /Sensor
Manufacturers
Mobile Device Companies
Digital Hardware Companies
Software Infrastructure
Communications Companies
Data Companies
Existing App Companies

8. 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

9. 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

10. 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?

11. 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?

12. 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

13. 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?

14. IoT for the Enterprise - Different requirements
• The building / factory
• The employees
• The customers
• OEM

15. IoT Reference Architecture - Building / Factory
1. Devices
a. Reliable, Secure
b. Hard Connection
c. Device Profile Known
2. Data Caching at local sites
3. Sophisticated Analysis
4. Optimization
5. Diagnosis / Failure Warning
6. Eventing
7. Device Management
8. Integration to Finance,
Accounting, Security
1. Purposes
a. Energy - HVAC, Lighting
b. Automation – Cost reduction
c. Security
d. Quality Engineering
Very High Criticality
Sophisticated Integration not a
problem
May be willing to accept non-
standard if superior security,
functionality

16. IoT Reference Architecture - Employee
1. Devices
a. Secure
b. Device Profile Known
c. Size / Portability
2. Diagnosis / Failure Warning
3. Flexibility to support small variety
of devices
4. Eventing
5. Device Management
6. Integration with Automation
Systems, Sales, Marketing,
Management, Content
Management Systems
1. Purposes
a. Productivity of Employees
b. Convenience
Medium Criticality
Some Integration may be done

17. IoT Reference Architecture - Customer
1. Devices Key Functionalities
required
2. Flexibility to support wide variety
of devices
3. Eventing
4. Store Data
5. Analytics Critical
6. Discovery
7. Good UI
8. Integration with Automation
Systems, Sales, Marketing,
Management, Content
Management Systems
1. Purposes
a. Create Stickiness
b. Create Value for Customer
c. Inexpensive
Application dependent Criticality
High Integration Expected

18. 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 devices
3. Eventing - Some automation
4. Need to Store Data
5. Discovery Easy
6. Good UI
7. Integration with other IoT desirable
1. Purposes
a. Convenience
b. Attractiveness
c. Features
d. Inexpensive
Lower Criticality

19. IoT End to End Needs
Middle 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

20. UI
IOT Reference Architecture
Device
API MgtDev Mgt
Service Bus BPMBigData
Long Term
Analysis
Activity Mgt
Cloud
CEP
Cloud Orchestration/Integration
Com
m
Prov
ider
OS
Application
ESB, Security
OS
ESB, IM, PEP
Data Infrastructure
Hub
Orchestration
Integration
Rules Engine
Data
Dev Mgt
Rules Engine
User Dashboard
IoT Mgt
Dashboard

21. IoT Use Cases
• Car Manufacturer
• Construction Company

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

23. IoT Reference Architecture - OEM
1. Devices
a. Key Functionalities required
2. Flexibility to support wide variety of
devices
3. Eventing
4. Store Data
5. Analytics Critical
6. Discovery
7. Good UI
8. Integration with Automation Systems,
Sales, Marketing, Management, Content
Management Systems
1. Purposes
a. Create Stickiness
b. Create Value for Customer
c. Inexpensive
High Criticality Criticality
High Integration Expected

24. 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

25. 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

26. Connected Car
API Mgt Dev Mgt
Upgrade
Cust Svc Service Bus
Design
BPM
BigData
Long Term
Analysis
Activity Mgt
Service Bus
Polling LoggingEvents
BrakesBrakes
BrakesBrakes
Console
Phone
Watch
3rd Party App /
Device
3rd Party App /
Device
3rd Party App /
Device
Brakes
Hi Priority
Planning
Lo Priority Apps
Cell
Ven Cloud
CEP - Service
The
Car
Car
Com
pany

27. 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

28. 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

29. Connected Construction
API MgtDev Mgt
Cust Svc
Service Bus
Design
BPM
BigData
Long Term
Analysis
Activity Mgt
Phone
Vehicles
Tools
Hi Priority PlanningLo Priority
Cloud
CEP
Building Sites
Vehicles
Vehicles
Phone
Phone
Tools
Tools
Tools
Data Gather
Device
Data Gather
Devices
Wharehouse
Wharehouses
Tools
Data Gather
Device
Contractors
Design Contractor
Planning
Tool
Connected Construction

30. WSO2 Commercial

31. Connect the World

32. We help our customers
become a
Connected
Business

33. 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

34. Systems of Systems Functional Requirements

35. Complete Enterprise Middleware
ONLY company to ever build a complete middleware stack
on-premises, in the cloud and on mobile devices.
SINGLE codebase for all products!

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

37. Thanks4Listening
❖ My twitter: @john_mathon
❖ My blog: CloudRamblings