SlideShare a Scribd company logo
Introducing OSIsoft Open Edge Module
...the Open Source Platform for the Internet of Things
2
Introducing Fog Computing
“An architecture that uses one or more collaborative end-user clients or
near-user edge devices to carry out a substantial amount of storage,
communication, control, configuration, measurement and management.”
https://en.wikipedia.org/wiki/Fog_computing
3
Introducing Fog Computing
“A decentralized computing infrastructure in which data, compute,
storage and applications are distributed in the most logical, efficient
place between the data source and the cloud.”
http://internetofthingsagenda.techtarget.com/definition/fog-computing-fogging
4
Issues for Data in IoT, IIoT and Fog Computing
• Connectivity
• Intermittent networks
• Network windows
• Low bandwidth
• Security
• Authentication (single/dual)
• Encryption (at rest and in motion)
• Attestation
• Operating Environment
• Temperatures
• Dust, water, humidity, acidity
• Power sources
• Capital expenditure and Operating Costs
• Latency / Response Time
• Predictable response time
• Minimal or no network latency
• Data Quantity
• Millions or billions of sensors
• Billions or trillions of data points
• Data Quality
• Errors and malfunctions
• False positives/negatives
• Compatibility and Fragmentation
• Multiple and non interoperable
stacks, platforms, frameworks
5
What If...
… you can use the same platform for server
development and deployment on any layer,
managing and consuming your data where is
needed?
6
What If...
… you can use the same platform for server
development and deployment on any layer,
managing and consuming your data where is
needed?
… you can bring the advantages of Cloud
Computing at any layer of IoT and IIoT?
7
Introducing the Open Edge Module
The Open Edge Module is a platform for the Internet of Things and an
essential component in Fog Computing.
It uses a modular microservices architecture including sensor data
collection, storage, processing and forwarding to historians, Enterprise
systems and Cloud-based services.
The Open Edge Module can run in highly available, stand alone,
unattended environments that assume unreliable network connectivity.
8
Introducing the Open Edge Module
N
S
W
E
Edge
Fog
Cloud
Cloud-to-Cloud
Edge-to-Edge
Edge-to-Fog Edge-to-Fog
Fog-to-Fog
Fog-to-Cloud
9
Use Cases - Smart Fleets
10
11
Use Cases - Data Centres Monitoring
12
Open Edge Module Architecture
13
Nomenclature
North
South
14
Micro-Services Architecture
• The module is more modules
• It is a number Micro-services
• Co-operate to provide the Open Edge Service
• Micro-services allow
• Distribution
• Scale-out/Scale-up
• Resilience
• Best language/deployment choices
15
Core Micro-Service
• Centre of the Open Edge universe
• Provides REST API
• Provides system level management
• Schedules activity
16
Southbound Interface
• Traffic to/from actuators & sensors
• Multiple device interfaces
• Many different protocols
• Push mode v’s Pull mode devices
• Southbound micro-service plugin infrastructure
• Multiple southbound micro-services
17
• Hides protocol, push/pull mode details
• Moves sensor data to buffer storage
• Pushes updates/management requests to
devices
Southbound Micro-Service
Sensor
Readings
Management
Requests
18
Northbound Interface
• Path to the cloud/analytics
system
• Drains buffered sensor readings
• Transforms to analytics store
• Manages connectivity &
bandwidth
19
20
Storage Micro-Service
• Persists local configuration data
• Buffers sensor data
• Buffers management requests
• Plugin storage interfaces
• Configuration data in tabular store
• Sensor data in time series store
21
Open Edge Module Security
● Pluggable authentication
● Central certificate
management
● Protocol specific encryption
22
Application Interfaces
• Applications access buffered data
• Perform analysis at the edge
• Data accessible via REST API
• IN/OUT Communicator mimics traditional
data stores
23
Open Edge Module Management
• Millions to Billions of nodes
• Really don’t want to manage these
• Must run unattended
• Provision Centrally
• Manage configuration changes centrally
• Update centrally
24
Unattended Updates/Upgrades
Private Snap
Store
snap refresh
FogLAMP
Update
App A
(current)
App B
(current)
App C
(current)
foglamp 26
foglamp 27
foglamp 28
(current)
foglamp 29
(new)
25
Demo
Texas Instruments
CC2650 SensorTag
Raspberry Pi
Running the
Open Edge Module
CoAP protocol
Bluetooth
OMF Northbound
Historian
PI System by OSIsoft
26
Demo
Raspberry Pi
Running the
Storage and Core
microservices
HTTP Open Edge
Module protocol WLAN
OMF Northbound
Historian
PI System by OSIsoft
DHT22 with
Southbound nanoservice
27
Where is the Open Edge Module?
GitHub: https://github.com/foglamp/FogLAMP
ReadTheDocs: http://foglamp.readthedocs.io
...and we will be on snapcraft, IRC and Slack soon.

More Related Content

Introducing the Open Edge Module

  • 1. Introducing OSIsoft Open Edge Module ...the Open Source Platform for the Internet of Things
  • 2. 2 Introducing Fog Computing “An architecture that uses one or more collaborative end-user clients or near-user edge devices to carry out a substantial amount of storage, communication, control, configuration, measurement and management.” https://en.wikipedia.org/wiki/Fog_computing
  • 3. 3 Introducing Fog Computing “A decentralized computing infrastructure in which data, compute, storage and applications are distributed in the most logical, efficient place between the data source and the cloud.” http://internetofthingsagenda.techtarget.com/definition/fog-computing-fogging
  • 4. 4 Issues for Data in IoT, IIoT and Fog Computing • Connectivity • Intermittent networks • Network windows • Low bandwidth • Security • Authentication (single/dual) • Encryption (at rest and in motion) • Attestation • Operating Environment • Temperatures • Dust, water, humidity, acidity • Power sources • Capital expenditure and Operating Costs • Latency / Response Time • Predictable response time • Minimal or no network latency • Data Quantity • Millions or billions of sensors • Billions or trillions of data points • Data Quality • Errors and malfunctions • False positives/negatives • Compatibility and Fragmentation • Multiple and non interoperable stacks, platforms, frameworks
  • 5. 5 What If... … you can use the same platform for server development and deployment on any layer, managing and consuming your data where is needed?
  • 6. 6 What If... … you can use the same platform for server development and deployment on any layer, managing and consuming your data where is needed? … you can bring the advantages of Cloud Computing at any layer of IoT and IIoT?
  • 7. 7 Introducing the Open Edge Module The Open Edge Module is a platform for the Internet of Things and an essential component in Fog Computing. It uses a modular microservices architecture including sensor data collection, storage, processing and forwarding to historians, Enterprise systems and Cloud-based services. The Open Edge Module can run in highly available, stand alone, unattended environments that assume unreliable network connectivity.
  • 8. 8 Introducing the Open Edge Module N S W E Edge Fog Cloud Cloud-to-Cloud Edge-to-Edge Edge-to-Fog Edge-to-Fog Fog-to-Fog Fog-to-Cloud
  • 9. 9 Use Cases - Smart Fleets
  • 10. 10
  • 11. 11 Use Cases - Data Centres Monitoring
  • 12. 12 Open Edge Module Architecture
  • 14. 14 Micro-Services Architecture • The module is more modules • It is a number Micro-services • Co-operate to provide the Open Edge Service • Micro-services allow • Distribution • Scale-out/Scale-up • Resilience • Best language/deployment choices
  • 15. 15 Core Micro-Service • Centre of the Open Edge universe • Provides REST API • Provides system level management • Schedules activity
  • 16. 16 Southbound Interface • Traffic to/from actuators & sensors • Multiple device interfaces • Many different protocols • Push mode v’s Pull mode devices • Southbound micro-service plugin infrastructure • Multiple southbound micro-services
  • 17. 17 • Hides protocol, push/pull mode details • Moves sensor data to buffer storage • Pushes updates/management requests to devices Southbound Micro-Service Sensor Readings Management Requests
  • 18. 18 Northbound Interface • Path to the cloud/analytics system • Drains buffered sensor readings • Transforms to analytics store • Manages connectivity & bandwidth
  • 19. 19
  • 20. 20 Storage Micro-Service • Persists local configuration data • Buffers sensor data • Buffers management requests • Plugin storage interfaces • Configuration data in tabular store • Sensor data in time series store
  • 21. 21 Open Edge Module Security ● Pluggable authentication ● Central certificate management ● Protocol specific encryption
  • 22. 22 Application Interfaces • Applications access buffered data • Perform analysis at the edge • Data accessible via REST API • IN/OUT Communicator mimics traditional data stores
  • 23. 23 Open Edge Module Management • Millions to Billions of nodes • Really don’t want to manage these • Must run unattended • Provision Centrally • Manage configuration changes centrally • Update centrally
  • 24. 24 Unattended Updates/Upgrades Private Snap Store snap refresh FogLAMP Update App A (current) App B (current) App C (current) foglamp 26 foglamp 27 foglamp 28 (current) foglamp 29 (new)
  • 25. 25 Demo Texas Instruments CC2650 SensorTag Raspberry Pi Running the Open Edge Module CoAP protocol Bluetooth OMF Northbound Historian PI System by OSIsoft
  • 26. 26 Demo Raspberry Pi Running the Storage and Core microservices HTTP Open Edge Module protocol WLAN OMF Northbound Historian PI System by OSIsoft DHT22 with Southbound nanoservice
  • 27. 27 Where is the Open Edge Module? GitHub: https://github.com/foglamp/FogLAMP ReadTheDocs: http://foglamp.readthedocs.io ...and we will be on snapcraft, IRC and Slack soon.