Looking for a Compass for Navigating the IoT Platform Landscape

Saverio Romeo
November 8, 2016

 

The market landscape of IoT platforms – software middleware for the Internet of Things – is rich in solutions with a continuous flow of new ideas. That is a sign of momentum in the space, but at the same time, an indication of confusion and controversy. Organisations aiming to run their own IoT strategy are facing the challenge of choosing a platform from more than 300 available in the market. The controversy lies in the fact that those platforms offer different combinations of services.

Therefore, the definition of an IoT platform becomes blurry and difficult to grasp. The conclusion is that all IoT market players are not only navigating in beautiful waters, rich in ideas, but also in troubled ones, because there is no clarity on how to interpret those ideas. Beecham Research has explored this space since the M2M era. Currently, the work is focussing on the definition of a benchmarking model that helps the various stakeholders of the IoT community to safely navigate those waters. This article will illustrate this work, which extends from the days of M2M platforms to the development of a compass for the IoT platform landscape.

From M2M SES to IoT platforms – responding to rising complexity

At the beginning of this decade, the number of platforms was limited. M2M Service Enablement Service (SES) Platforms, as defined by Beecham Research in the first study on the topic dated 2010, represented a market segment known only to experts. Despite that, they were the enablers of M2M applications and, for organisations providing M2M SES platforms, the platform delivered a strong element of competitive advantage. As shown in Figure 1, there were 30 platforms in the marketplace, providing 54 different services, mainly about device management and connectivity management capabilities.

Figure 1

Figure 1: Evolution of M2M/IoT platforms [source: BRL]

In 2012, the number of platforms rose to more than 60 offering 114 different services. This growth reflected an increasing demand of new services due to the complexity of projects adopters were facing. It was clear that the monetization of M2M projects was not just about connectivity and devices, but services were a strong revenue source. However, moving towards a service-centric approach was not easy. M2M adopters were not ready for such a move and deploying M2M solutions was neither easy nor painless. Possessing M2M solutions was not perceived as a strategic move. And, organisations, which experienced the potential of using machine-generated data, were often running difficult in-house activities. The response of M2M SES platform providers to all this was to move from the idea that the platform should be reinvented for different sectors towards the idea that the platform should be a horizontal layer on which any type of M2M application could be developed. That horizontal layer should have abstracted the application development from the device and the type of connectivity. That vision was possible because M2M applications revolved primarily around monitoring a specific type of device, gathering a specific type of data, using a specific type of connectivity, and running some simple analytics on the data. The M2M SES platform was largely horizontal, able to be used in different applications with very few vertical adaptations. That situation is not easily applicable to the IoT vision.

The context-centric view of the Internet of Things

The IoT vision is about a context and the situation of the context that changes continuously. The context is a space in which there are different types of devices, gathering different types of data, using different types of connectivity, speaking different protocol languages, having different security needs, interacting with different types of devices. In order to make sense of all this, which means understanding the context and taking decisions within the context, the set of services offered by an IoT platform should be richer and more complex. And, if connectivity management and device management layers remain important, the IoT platform requires their sophistication in order to manage the plethora of diverse devices, but, it also requires advanced data management services, application development services, API management services, and security services as shown in Figure 2.

Figure 2

Figure 2: Typical architecture layers of IoT platforms [source: BRL]

Defining the compass for selecting IoT platforms

Using Figure 2 as a reference architecture, we can then assess IoT platforms in the marketplace based on two sets of indicators. The first set looks at the technological aspects.

  • Device and connectivity management. Device discovery, authentication, management, and control;
  • Context-awareness. Collecting, managing and using contextual information (event processing for example);
  • Scalability. . Being able to enlarge the deployment of devices, agnostically from the type of devices (importance of drivers and APIs) and type of connectivity;
  • Data management services.Being able to orchestrate and analyse different data sources;
  • Interoperability. Being flexible enough to engage with other software solutions and exogenous data sources;
  • Edge-orientation. Enabling intelligence at the edge;
  • Security. Ensuring the security, privacy and integrity of the data gathered;
  • Application enablement tools. Level of sophistication and usability of application enablement tools.

The second set of indicators looks at the business aspects:

  • Horizontal versus vertical coverage.The IoT platform is either able to be adopted in any context (horizontal) or is designed for one or more contexts (vertical) such as manufacturing or smart cities;
  • Provision of support. The IoT platform provider offers technical support to the adopters of the platform;
  • Innovation enabling. Creating an ecosystem of users and developers through application enablement suites;
  • Cloud services. Types of cloud services offered;
  • Level of partnerships. Consolidate the ecosystem of partners in order to enhance services and offer solutions in specific verticals and contexts;
  • Market penetration. Presence in the market place;
  • Flexibility and extensibility. Capacity of enhancing the offer either through in-house developments or through partnerships or acquisition.

The next step is to define a rating scale for each of these indicators. The rate should give an insight on the relevancy of each criterion for the IoT platform under scrutiny. The analysis of the ratings should then enable the selection of potential candidates which warrant further investigation.

Beecham Research has run a first test of the compass on a limited number of platforms selected for their market relevancy. The compass has enabled the researcher to group IoT platforms and running the comparison within the groups has produced good results in terms of output and usability.

Conclusions

The move from M2M applications towards the context and situational-centric view of the Internet of Things has brought business opportunities and a proliferation of ideas, but also complexity. The IoT platform is the essential middleware layer that enables that richness and governs that intricacy. The IoT community has responded with a tremendous flow of ideas creating a rich landscape of offers. That abundance has also brought difficulties in selecting an appropriate platform for specific business purposes. Therefore, a benchmarking framework that enables companies to screen the offers and select potential candidates is necessary. This paper has proposed an approach for that framework. That approach is not the final answer, but is a step towards a more informed assessment of IoT platforms and a tool to make the IoT platform landscape less cloudy to all stakeholders.

 

Readings

Atzori, L. et al. 2010. The Internet of Things: A Survey. Computer Networks 54(15)

Bandyopadhyay,S. et al. 2011. Role of Middleware for Internet of Things: A Study. International Journal of Computer Science and Engineering Survey (IJCSES), Vol.2, No.3, August 2011

Cavalcante, E. et al. 2015. An Analysis of Reference Architectures for the Internet of Things. ACM

Duke-Woolley, R. 2012. SES2. M2M Service Enablement Service (SES) Platforms – An Update. Beecham Research

Duke-Woolley, R. 2010. Assessment of M2M Service Enablement Service Platforms. Beecham Research

Ebert, C. et al. 2016. Reference Architectures for the Internet of Things. IEEE Software

Nakhuva, B. et al. 2015. Study of Various Internet of Things Platforms. International Journal of Computer Science & Engineering Survey, 6/6

Perry, M.J. 2015. Evaluating and Choosing an IoT Platform. O’Reilly

Romeo, S., Duke-Woolley, R. 2014. The Evolution of SES Platforms in an IoT Environment. Beecham Research

Web sources

More than 50 IoT Platform Providers websites

The Internet of Things (IoT-A): http://www.iot-a.eu/public

Industrial Internet Consortium (www.iiconsortium.org)

 


 

Saverio RomeoSaverio Romeo is a Principal Analyst at Beecham Research. He runs research in the areas of M2M, Internet of Things, and wearable technologies and has published in areas such as mobile healthcare, smart cities, smart utility, data analytics, smart farming, M2M/IoT connectivity, and M2M/IoT platforms. On these subjects, Saverio has also advised organisations such as Vodafone Group, Sierra Wireless, Telit International, Sony, Inmarsat, Wireless Logic and GSMA.

Previously, Saverio worked as an M2M/mobile analyst at Frost & Sullivan, telecommunications policy analyst at Technopolis Group and European Commission and as a software developer. Saverio is also a Visiting Fellow at the Centre for Innovation Management Research at Birkbeck. His research revolves around entrepreneurship in high-tech sectors and IoT policy. He has published five academic journal articles, six book chapters, and 11 conference papers.

Saverio holds three Master Degrees, one in Telecommunications Engineering (University of Naples “Federico II”), one in Information Technologies (“Politecnico di Milano” University – CEFRIEL) and one in Innovation Management and Technology Policy (Birkbeck, University of London). He speaks fluent English; he is native Italian and is intermediate in Modern Greek.

 

 


 

Subscribe to the Newsletter

Join our free IoT Technical Community and receive our Newsletter.

Subscribe Now


Calendar of Events

The 2nd IEEE International Conference on Internet-of-Things Design and Implementation (IoTDI 2017)
18-21 April 2017
Pittsburgh, Pennsylvania, USA

2nd Convergent Internet of Things (C-IoT) Workshop
21-25 May 2017
Paris, France

IEEE IoT Vertical & Topical Summit for Agriculture
21-25 May 2017
Paris, France

IEEE International Symposium on Circuits & Systems (ISCAS 2017)
28-31 May 2017
Baltimore, Maryland, USA

2017 Global Internet of Things Summit (GIoTS)
6-9 June 2017
Geneva, Switzerland

The 1st EAI International Conference on Smart Grid Assisted Internet of Things (SGIoT 2017)
11-13 July 2017
Sault Ste. Marie, Ontario, Canada

See More Events


Call For Papers

IEEE Internet of Things Journal
5G and Beyond - Mobile Technologies and Applications for IoT - Submission deadline: 31 March 2017
Cognitive Internet of Things - Submission deadline: 31 March 2017
Internet of Mission-Critical Things - Submission deadline: 1 May 2017
Multimedia Big Data in Internet of Things - Submission deadline: 31 May 2017
Emerging Social Internet of Things: Recent Advances and Applications - Submission deadline: 15 June 2017
Trust, Security and Privacy in Crowdsourcing - Submission deadline: 1 July 2017


Past Issues
January 2017
November 2016
September 2016
July 2016
May 2016
March 2016
January 2016
November 2015
September 2015
July 2015
May 2015
March 2015
January 2015
November 2014
September 2014