Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building IoT Solutions Using Core CMS Features

55 views

Published on

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.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Building IoT Solutions Using Core CMS Features

  1. 1. Building IoT Solutions Using Core CMS Features
  2. 2. The Intro A brief history of me, my approach to software, and my IoT journey thus far
  3. 3. The Question How can Content Management Systems support IoT efforts?
  4. 4. The Utility Model CONSUME TRANSMIT AGGREGATE DISTRIBUTE CONSUMECOLLECT
  5. 5. Primary IoT Use Cases Condition Monitoring Remote Control
  6. 6. The CMS Opportunity in IoT Data Definition Managed User Access APIs
  7. 7. The Experiment Implement a CMS with minimal customization as an IoT solution
  8. 8. What is MINIMAL? Core Workflows and Configs Plugins Third-Party Services Light Custom Code
  9. 9. System Components TRANSMIT AGGREGATE DISTRIBUTE CONSUMECOLLECT
  10. 10. 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: {...} } ] }
  11. 11. Device Connectivity Device Key (GUID) Serial Number Alias Signal Data
  12. 12. Users and Provisioning temp: �F raspi-1234 raspi-abcd raspi-1-a-2-b.v1 raspi-*
  13. 13. Getting The Data raspi-1234 /raspi-1234
  14. 14. Remote Control { "key": "5b380ccf403b3", "controller": "led", "action": "scrollText", "params": { "text": "Hello World!", "speed": 0.05 } }
  15. 15. All Together Now...
  16. 16. The Demo
  17. 17. The Results Mission Accomplished?
  18. 18. Is it MINIMAL? Core Workflows and Configs Plugins Third-Party Services Light Custom Code
  19. 19. Is it Useful? Is it Adaptable? Is it Scalable? Other Considerations?
  20. 20. Time Spent per Week
  21. 21. Effort Breakdown
  22. 22. The Next Steps Where do we go from here?
  23. 23. nick.leguillou@gmail.com https://www.linkedin.com/in/nick-le-guillou-1090177/
  24. 24. Fin

×