Rather than the term platform, which implies that a company creates an orchestration role or marketplace, systems of delivery might be a better way of explaining a path forward for connectivity providers trying to supply more value for their customers and create new roles within the value chain.
In the enterprise software as a service space, some argue for approaches that are more agile because something akin to an operating system can be envisioned: a way of breaking down silos and allowing horizontal integration.
The problem is either too much integration (too “tight” and therefore not flexible) or too loose (little to no effective integration). Think of the way application programming interfaces are used to allow systems to work together, in a more loosely-coupled manner.
The analogy for connectivity providers is to become something of a process orchestrator, integrating various functions on behalf of a customer. The older model of system integrator comes to mind, but in the context of orchestrating the use of resources, more than creating the resources.
Creating a system of delivery arguably is far easier than creating a platform. One arguably sees this in the software as a service business. “SaaS is upping its game with a growing number of vendors downplaying 'best of breed' and talking instead of a 'rising tide' where they become centralizing hubs in which an ecosystem of other apps are operationalized,” notes S&P Global.
That sounds akin to “platform,” but might be better characterized as “orchestration.” Agility and alignment arguably are parts of it. Integration might arguably be part of it. Overcoming silos is part of the idea.
The key observation is that almost every effort made by connectivity firms to increase value for customers will require some orchestration of value to create a solution. Though not easy, it is perhaps easier to envision a large connectivity provider becoming an orchestrator of value than becoming a true platform.
No comments:
Post a Comment