Internet of things presents a significant opportunity for service providers. The number of connected devices is growing exponentially and is projected to reach 50 billion by 2020. Service providers with their extensive networks and other assets are exceptionally well positioned to reap significant financial benefits from the tremendous growth of IoT. Most service providers have embraced IoT. Their strategies have differed, but trends have started to emerge. Some operators, typically smaller ones, have pursued a horizontal strategy, seeking to be primarily a connectivity provider; other service providers, seeing significant value in the application part of IoT, have pursued a vertical strategy, where they have end-to-end offerings along chosen verticals. Examples include Verizon’s focus on fleet management and smart cities, Orange’s focus on healthcare.
To succeed in a vertical approach, service providers must consider several important imperatives and embrace the fact that the IoT framework and drivers for success can differ materially from their established business model and operations.
- Although service providers have significant connectivity assets, primarily in terms of 3G, 4G/LTE, and in some cases WIFI and wired connectivity, it is important to recognize that IoT may have different connectivity needs, will require low-power WAN connectivity (LPWAN), such as LoRA, Sigfox, LTE-M1 and NB1, and will involve a significantly larger number of connected devices than their networks today are designed for. Major operators are making significant strides in testing and deploying these technologies. LTE-M1 seems to be gaining favor with Verizon and AT&T in the US. LoRa has momentum in Europe, with the Netherlands building a country-wide LoRa network.
- Operating in a vertical will necessitate deep expertise in that vertical. Service providers typically will lack that expertise. Therefore, they need to acquire and integrate the right assets, hire experts, and structure the right partnerships. Failing to execute on these initiatives will put their business at risk.
- The service providers’ current organizations are often attuned to the needs of their existing business with established methods and procedures, a carefully planned and deliberate go-to-market strategy, and operational and business support systems that are often based on yesterday’s technology and market needs. IoT requires agility and a dynamic go-to-market strategy, which should closely align with the needs of the vertical. To customers in the vertical, IoT is not a standalone service they receive from the service provider but rather an integral part of their operations and business strategy. The service provider will need to work with them to understand their needs and build the capabilities to satisfy those needs.
- IoT generates substantial amounts of data, which often needs to be processed in real time. Therefore, a significant amount of the data generated needs to be processed at the edge of the network, to avoid the delays and bandwidth bottlenecks which would result if the data were sent to remote data centers. Therefore, service providers need to build “fog computing” infrastructure. This will be a marked change from the way their networks are currently architected.
- A key driver for IoT is analytics. Improving operations or preventing failure are often at the heart of what leads industries to adopt an IoT strategy. There are three main levels of analytics in IoT:
Therefore, it is essential for service providers to create a well thought out analytics capability that is specifically tailored to the needs of the IoT verticals on which it is focused. Analytics is still an immature capability for service providers, and often the capability is hosted in various parts of the business based on specific needs. This approach will not work for IoT, which requires a cohesive and holistic approach. Therefore, the service provider should create an IoT specific capability that addresses the needs of the vertical and make it separate from other analytics initiatives across the company.
- Security is a key challenge when it comes to IoT. The significant amount of data collected in IoT should be protected at all stages of the collection, transition through the network, processing and warehousing. Furthermore, in some industries, for example, healthcare, there are privacy rules and regulation that need to be satisfied. Although service providers are well positioned in that regard with a good track record, the needs of IoT will by far exceed the security demands of their current business, and therefore, they need to define a comprehensive security management ecosystem to protect the IoT environment end to end.
- Given the complexity of the IoT solutions, and the scope of what needs to be offered, it is imperative that service provider structure the right partnerships with the appropriate entities to offer an end-to-end solution that meets the needs of the customers in the verticals. This is not trivial, because such partnerships are likely to be broader in scope and intricacy than what is mostly typical for them. Although this provides significant opportunities for them, it also introduces an element of risk.
- The business metrics that will drive the IoT business operation are markedly different from established business processes for most service providers. Traditionally, service providers have been primarily connectivity enablers. Service providers that have embraced the vertical IoT approach have taken on a major role as solutions providers that requires them to build deep expertise along specific verticals to establish new business and operational processes and metrics, new revenue expectations and arrangements (e.g. revenue share). Furthermore, it is essential that service providers do not bind their IoT business by tightly associating it with the rest of the business. On the contrary, they should keep it as a separate business, operating at arm’s length from the traditional business, with independent leadership and structure, independent financial goals and metrics, and its own operating environment.
