In Part 1 of this blog series, I spoke of the IoT taxonomy, and in Part 2, about device connectivity. That said, I haven’t really mentioned how to make this real. The reality in implementing IoT scenarios will require a wide degree of technical capability and connectivity.
From a capability standpoint, an IoT platform must cater to the following:
- Device Management
- Device Provisioning (On-Boarding/Retiring/etc.) – Ability to onboard, retire, and connect to APIs of devices as well as build device specific connectivity
- Device Security – Ability to have Encrypted/secured control & connectivity as well as authentication / authorization / and trusted provider access
- Device Monitoring – Ability to measure sensor information on device to provide analytics or monitoring of the performance and life of device and device components
- Device Connectivity –
- Data Interchange – Includes integration protocols for movement of data including MQQT or high volume data ingest mechanisms
- Device Data Sync – Ability to deal with online/offline connectivity scenarios including synchronization of data or API calls
- Data Storage & Processing–
- Storage – Ability to store massive amounts of device data (primarily for the M2D scenarios mentioned in blog 1)
- Processing – Time-series & related operators, graph & related algorithms, and predictive capabilities. Industry Vertical Connectivity – Ability to have connectors to specific types of standard devices by industry. I’ll cover this in more detail ina subsequent blog.
- Developer Tooling – Ability to have developer tooling to easily build out scenarios that include devices as part of the business setting.
Finally, building a business scenario to deliver M2A, M2M, M2D, or M2P will require other capabilities such as analytics, middleware, database, and Hadoop. Putting together this set of end-to-end capabilities will likely be costly and difficult to manage. Which is why I would argue that a cloud platform-as-a-service– extended to cover this range of capabilities-will be one of the simplest ways to get the benefit of bringing a business process to leverage the connectivity of things. This could be through either new IoT applications being built on a Cloud Platform-as-a-Service or taking existing applications (on-premise or cloud SaaS apps) and “extending” them with a Platform-as-a-Service, to ensure the process can be modified to an IoT scenario by leveraging device communication.
To take advantage of a connected world through IoT, SAP is investing in enabling the HANA Cloud Platform with an IoT Cloud Pack, that provides the required capabilities to build IoT apps or Extend existing Apps
This IoT Cloud Pack will include Device Management, Data Storage, and Device Connectivity with developer tooling, making HANA Cloud Platform the defacto choice to build IoT applications for SAP, our partners, and our customers.
However, it will be important to understand device connectivity by industry, and I’ll address that in Part 4 of this blog series, so stay tuned.
Also, for more details on SAP’s strategy for IoT, see some of these assets.