Cloud Services: Seen through the lens of ‘Product-design-influenced-by-Supply-Chain’ thought process

In class we discussed few companies that are making paradigm shift in product design owing to the supply chain processes, Ikea being the classical example. I was curious to find out if this thought process could be paralleled with IT industry. Unfortunately, nothing interesting came up in the search. Falling back to my industry experience, I recounted the supply chain issues an IT company would face when delivering its products (either software or hardware).

Let’s consider the supply chain issues of a software company:
* Multiple platforms means multiple product lines
* Standardization preferred over customization - Owing to mass distribution
* Licensing issues - Tied to PCs based on serial keys
* Version control
* Last but not the least, issue of support and service

And, for a hardware IT company issues are:
* Manufacturing, warehousing and delivery - Not to forget the usual issues seen in these operations such as forecasting, optimal resource utilization
* Convincing customers to scale up to newer and better hardwares
* Need to build backward compatible firmware upgrades
* And, yet again support and services

Cloud services (including but not limited to Software-as-a-Service) as we know is a paradigm shift in the software product design. Users pay on usage basis, often without lengthy contracts and are not necessitated to ‘own’ the software. In fact, few IT hardware vendors such as Cisco, Motorola, Juniper and Aruba (to name a few) are adapting the SaaS concept to virtualize even some of the hardware components. Thus most of the above listed supply chain pain points are either taken out from the equation or at least modified such that points of variance is reduced. And, in effect a consistent and controlled product could be delivered to customers.

Further, taking cue from the article ‘Biosphere rules’ let us analyze how moving to cloud based delivery would help the IT companies vis-a-vis traditional product delivery and maintenance (in other words ‘phasing-in-Biosphere rules’),

Think few materials: In IT terminology it would translate to fewer IT resources for development and testing. By moving to cloud based products IT companies can cut down on the development efforts on multiple platforms. For IT hardware companies by cutting down one SKU, the consumption of resources and thereby reductions in cost is self evident.
Rethink Design: Not only for the IT companies but even for the deployed company the cloud based offering will enforce new design in terms of IT infrastructure. The budgeting, infrastructure, integration and maintenance design would change and change for good.
Think scale economies: By taking the offerings into cloud, all of a sudden the product is global. And, roll out of products to customers is no more linear. Scalability is easy and more importantly with a center point control it is more controlled too.
Rethink the buyer-supplier relationship: Often the decision to chose an IT vendor is more for the reason that support and maintenance services of one vendor is better than the other, no matter how good the product is of the latter. With cloud based systems, the support services can be run from vendor’s office without having to invest on on-site support services. This would translate to better buyer-supplier relationships.
In conclusion, I think even though this wasn’t the thought process that kicked off the cloud based system paradigm but it is an interesting perspective. And, it does make sense when the developments on cloud services are looked from supply chain perspectives. We can state that the one of the motivations for cloud services were possibly to avoid the supply chain issues of traditional IT product/service delivery. Would you agree with that?