Unbundling is an interesting trend in many industries these days. It is relatively new marketing and business activity that helps to create new business offering, packages and product configurations. In many situations “unbundling” is a disruptive factors in many industries. Here is how it explained in Wikipedia article:
Unbundling is a neologism to describe how the ubiquity of mobile devices, Internet connectivity, consumer web technologies, social media and information access[1] in the 21st century are affecting older institutions (education, broadcasting, newspapers, games, shopping, etc.) by “break[ing] up the packages they once offered, providing particular parts of them at ascale and cost unmatchable by the old order.”[2] Unbundling has been called “the great disruptor”.[3] “Unbundling” most basically means simply the “process of breaking apart something into smaller parts.”[4] In the context of mergers and acquisitions, unbundling refers to the “process of taking over a large company with several different lines of business, and then, while retaining the core business, selling off the subsidiaries to help fund the takeover.”[5]
Enterprise software is well known by existing large “bundled” application suites. For long period of time, vendors developed large set of packaged applications. On the other side, customers’ demand was to achieve high level of vertical integration between product lines and product families. Last year, I explored some perspective on the future of unbundling in enterprise software and PLM. One of the drivers behind future “unbundling” is related to interests of customers to get better optimized software environment, focus on specific groups of users and driving faster ROI and fast implementations.
My attention caught my Aras blog post – If all you have is Teamcenter Everything Becomes a 3D CAD Problem. The article speaks exactly about the problem of bundles in engineering software. It discusses different needs of users in an organization. The split Aras introduced by Aras goes between people that need to get on 3D CAD software and rest of organization. Here is the passage, which explains that.
The 3D CAD vendors have created very complex file configuration management problems. Independent of how you manage your enterprise product lifecycle, you have to worry about breaking the configuration integrity of these fragile 3D CAD systems. Given the unique complexity of the 3D CAD problem, do you really expect that a single enterprise tool will be able to manage the entire product information data set and processes? Or is it better to manage CAD with the PDM system provided by the CAD vendor, and use a more suitable enterprise system to manage the majority of the product information and processes? Thousands of end users managing the true majority of product information and use cases have been asked to wait decades while exotic 3D CAD centric PLM systems are deployed to the specification and requirements of the few design engineers. But what is the missed opportunity cost to the business?
I can see Aras’ marketing and business message for “unbundling”. As non-CAD PLM vendor, Aras is looking how to disrupt integrated suites provided by PLM vendors such as Siemens PLM and maybe others. At the same time, for customers looking how to solve a specific set of problems outside of engineering organization, to deliver such unbundled solution can be an interesting and efficient strategy.
There are lot of questions that customers will raise as soon as vendors like Aras will unbundle specific 3D CAD functionality from broader scope of process management. To achieve both vertical integration and granularity in platform and tools is very hard and this is a weak point in Aras strategy compared to integrated PLM suites. Few weeks ago, I debated that topic with Chad Jackson of Lifecycle Insight. Read about debates here – CAD: Engineering bundles vs. granular apps. More of my ideas and thoughts about the same topic is here – PLM: Tools, Bundles and Platforms.
What is my conclusion? To unbundle complex engineering applications suites as PLM is not easy. Vertical interesting is very important and it will be hard to give up them. Flexibility and agility are on the top priority lists for IT managers when it comes to management of application and resources these days. It looks like an interesting topic to put on the list for PLM vendors and software architects these days. Unbundling was very disruptive in many domains. Will PLM domain can be disrupted by unbundling into platforms and granular apps. Will 3D CAD become the first tool to unbundle from PLM? It is a good question to ask. Just my thoughts…
Best, Oleg
Pingback: Engineers and email workhorse()
Pingback: Engineers and email workhorse | Daily PLM Think Tank Blog()