In today’s market there exists hundreds of IoT "solutions" - products and services that help people connect and consume device data, to and from the cloud. While these platforms can vary in cost and capabilities, many of them share a set of features commonly found in modern content management systems. This begs the question: Could a CMS replace these key features? This presentation will demonstrate how to leverage a modern CMS as one or more key components of an IoT solution: * Provisioning and configuring gateways and devices. * Recording normalized time series data. * Consuming time series data. * Granting organizations and users access to the data.

1. Building IoT Solutions
Using Core CMS Features

2. The Intro
A brief history of me, my approach to
software, and my IoT journey thus far

4. The Question
How can Content Management Systems
support IoT efforts?

5. The Utility Model
CONSUME
TRANSMIT AGGREGATE DISTRIBUTE CONSUMECOLLECT

6. Primary IoT Use Cases
Condition
Monitoring
Remote
Control

7. The CMS Opportunity in IoT
Data Definition
Managed User Access
APIs

8. The Experiment
Implement a CMS with minimal customization
as an IoT solution

9. What is MINIMAL?
Core Workflows and Configs
Plugins
Third-Party Services
Light Custom Code

10. System Components
TRANSMIT AGGREGATE DISTRIBUTE CONSUMECOLLECT

11. Data Definition
Temperature
Pressure
Humidity
Joystick Position
LED Matrix
Location
+
{
records: [
{ signal: 'temperature', value: '' },
{ signal: 'pressure', value: '' },
{ signal: 'humidity', value: '' },
{ signal: 'joystick', value: '' },
{
signal: 'led_matrix',
value: [
[0,0,0],[0,0,0], ...
]
},
{ signal: 'location', value: {...} }
]
}

12. Device Connectivity
Device Key (GUID)
Serial Number
Alias
Signal Data

13. Users and Provisioning
temp: °F
raspi-1234
raspi-abcd
raspi-1-a-2-b.v1
raspi-*

14. Getting The Data
raspi-1234
/raspi-1234

15. Remote Control
{
"key": "5b380ccf403b3",
"controller": "led",
"action": "scrollText",
"params": {
"text": "Hello World!",
"speed": 0.05
}
}

16. All Together Now...

17. The Demo

18. The Results
Mission Accomplished?

19. Is it MINIMAL?
Core Workflows and Configs
Plugins
Third-Party Services
Light Custom Code

20. Is it Useful?
Is it Adaptable?
Is it Scalable?
Other Considerations?

21. Time Spent per Week

22. Effort Breakdown

23. The Next Steps
Where do we go from here?

24. nick.leguillou@gmail.com
https://www.linkedin.com/in/nick-le-guillou-1090177/

25. Fin