Editing IoTPlatform
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 10: | Line 10: | ||
[[File:IOTNetwor_ISOlayer_IoTPlatfrom_Arvind.jpg |right| IoT Network in ISO layer world]] | [[File:IOTNetwor_ISOlayer_IoTPlatfrom_Arvind.jpg |right| IoT Network in ISO layer world]] | ||
However with the rapid growth of the consumer electronics business especially smartphones the price point of many sensors and the quality increased by quantum jumps. Sensors incorporated Digital Signal processing (DSP) on device and gave smoothed calibrated signal data. This allowed mixing manufacturers and models of sensors. This required decoupling the application from downstream components. The 7 layer ISO model is a great example where a similar decoupling and a layered Hourglass architecture greatly helped adoption. | However with the rapid growth of the consumer electronics business especially smartphones the price point of many sensors and the quality increased by quantum jumps. Sensors incorporated Digital Signal processing (DSP) on device and gave smoothed calibrated signal data. This allowed mixing manufacturers and models of sensors. This required decoupling the application from downstream components. The 7 layer ISO model is a great example where a similar decoupling and a layered Hourglass architecture greatly helped adoption. | ||
− | The IoTPlatfrom is the natural evolution to a layered architecture in IoT decoupling the devices and hubs/ gateways from middelware sending data to | + | The IoTPlatfrom is the natural evolution to a layered architecture in IoT decoupling the devices and hubs/ gateways from middelware sending data to on or cloud based application and consumers. The graphic from [https://www.eetimes.com/author.asp?section_id=36&doc_id=1326911 Smart Home gets another standard] illustrates the emergence of a decopuled layer. |
The biggest surprise is rapid adoption of new protocols like BlueTooth and modernization of older ones like ISA100 standard developed by the International Society of Automation (ISA) officially called "Wireless Systems for Industrial Automation: Process Control and Related Applications". | The biggest surprise is rapid adoption of new protocols like BlueTooth and modernization of older ones like ISA100 standard developed by the International Society of Automation (ISA) officially called "Wireless Systems for Industrial Automation: Process Control and Related Applications". | ||
==Functionality== | ==Functionality== | ||
− | |||
− | |||
− | |||
There is great deal of fuzziness on features of an IOT Platform. In [http://www.sciencedirect.com/science/article/pii/S2314728816300149 A Survey of Cloud IOT platforms]] Partha Ray visualizes the features of the IoTPlatform as follows. | There is great deal of fuzziness on features of an IOT Platform. In [http://www.sciencedirect.com/science/article/pii/S2314728816300149 A Survey of Cloud IOT platforms]] Partha Ray visualizes the features of the IoTPlatform as follows. | ||
[[File:IoTPlatfromCircleChartFeatures IoTPlatfrom ScienceDirect.jpg|thumb|Functions of IOTPlatfrom]] | [[File:IoTPlatfromCircleChartFeatures IoTPlatfrom ScienceDirect.jpg|thumb|Functions of IOTPlatfrom]] | ||
Line 22: | Line 19: | ||
;Gateway: Handshake with Hub and gateway and Router and work with edge processing | ;Gateway: Handshake with Hub and gateway and Router and work with edge processing | ||
;Middelware: UDP and IP based protocols (MQTT) and simpler non IP based middelware | ;Middelware: UDP and IP based protocols (MQTT) and simpler non IP based middelware | ||
− | ;Data and API:Semantics of the | + | ;Data and API:Semantics of the deice and operations. Zigbee or OneM2M profiles. |
;Monitoring: Anomaly detection, health of devices and hubs and gateways | ;Monitoring: Anomaly detection, health of devices and hubs and gateways | ||
;Deployment: Bulk on boarding, relocation or transfer of facilities, Zoned operation. | ;Deployment: Bulk on boarding, relocation or transfer of facilities, Zoned operation. | ||
Line 29: | Line 26: | ||
;Application Development: Multiple touch points Web , Smartphone ,Chatbots, speech (Amazon Alexa) , SMS and WhatsApp | ;Application Development: Multiple touch points Web , Smartphone ,Chatbots, speech (Amazon Alexa) , SMS and WhatsApp | ||
;Visualization: State of network and zones , facilities . Heatmap of activity and busty data | ;Visualization: State of network and zones , facilities . Heatmap of activity and busty data | ||
+ | |||
== Market Size == | == Market Size == | ||
Line 49: | Line 47: | ||
; AP:An Analytics Platform (AP) is an offering providing sophisticated data federation, statistical modeling and reporting tools to allow users to draw insights from ingested data. Usually, AP capabilities lay northbound of the data ingestion and processing functionality provided by other IoT platforms like AEPs and PESs. In essence, APs offer advanced analytics capabilities drawing using machine learning and artificial intelligence algorithms. SAP HANA is an example of an AP. | ; AP:An Analytics Platform (AP) is an offering providing sophisticated data federation, statistical modeling and reporting tools to allow users to draw insights from ingested data. Usually, AP capabilities lay northbound of the data ingestion and processing functionality provided by other IoT platforms like AEPs and PESs. In essence, APs offer advanced analytics capabilities drawing using machine learning and artificial intelligence algorithms. SAP HANA is an example of an AP. | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
==ToDo== | ==ToDo== | ||
− | === | + | ===LInks to Architecture and Interoperability articles=== |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Detail example=== | ===Detail example=== | ||
===Some IoTPlatforms=== | ===Some IoTPlatforms=== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Considerations in choosing a IoTPlatform=== | ===Considerations in choosing a IoTPlatform=== | ||
− | + | ===Where to follow the evolution=== | |
− | |||
− | |||
− | |||
− | == | ||
− | |||
− | |||
− | |||
− | |||
− |