A blog by Oleg Shilovitsky
Information & Comments about Engineering and Manufacturing Software

Why PLM vendors are fighting “legacy” PLM?

Why PLM vendors are fighting “legacy” PLM?
Oleg
Oleg
20 July, 2018 | 4 min for reading

Last year I shared my thoughts about how to replace legacy PLM and move forward. The idea is pretty simple – build a new PLM, make it co-exist with the one you have and when you’re ready, pull the switch off. It sounds very obvious. What can hold us back? The decision… Company should commit to the change. Such decision is not simple and before to commit to another bulk of investment, company is checking the options.

Earlier this week, my attention was caught almost simultaneously, by two publications  – Propel vs Arena and old cloud PLM and How your legacy PLM is holding you back by Aras.

Here are few notable quotes about Propel:

Propel provides your customers, partners and employees a modern cloud PLM, PIM and QMS solution to help drive product and company success.Unlike older legacy cloud PLM software like Arena or Omnify, Propel brings PLM straight to your customers, partners, field services teams, sales and marketing teams, quality, product teams, suppliers, manufacturing, and engineers. Propel offers the world’s most robust PLM experience for accessing critical product information. View reports, documentation, change approvals and much more on the device of your choosing. Fully engage with your PLM on your desktop, iPhone, Android device or tablet.

…and this is a quote from Aras paper:

Legacy PLM systems consist of a mix of individual products accumulated from years of acquisitions. At best, they may have been loosely stitched together but more often, the result is silos within the PLM system architecture that impede collaboration. Even while legacy PLM systems may boast full functionality across disciplines, the individual pieces of software often do not work well together and don’t facilitate communication and collaboration. For example, creation of a comprehensive bill of materials (BOMs) or an engineering change order that spans multiple disciplines may be impossible because of the multiple systems involved.

It is very interesting to see how both Aras and Propel are fighting the same thing – expansion and legacy. Both vendors are trying to replace the software companies are using today (obviously calling it legacy) and expand usage by providing broader solution to the problem. In the case of Aras, the legacy is Teamcenter and Windchill. and in the case of Propel, it is Arena Solutions.

I can easy find some common themes in both differentiation stories. Here are some of them:

1- Highly flexible. Both Aras and Propel are offering no limits in what data can be managed. It differentiate PLM systems with predefined out of the box schemas.

2- Fast deployment and ease of upgrade. It sounds like two different things, but they serve the same purpose. Propel as a cloud system is easy to start and it supports customers alongside the road. No IT (thanks for cloud). Aras’ upgradability is a way to bring new features and functions with no rev locking.

3- Collaboration. But products are offering solution to augment all data and all roles. Not different from single version of truth, which was a goal for all PLM systems ever, now it is seems to be one step closer.

What is my conclusion? There is a reason why PLM vendors are calling to replace legacy vendors and solutions. Legacy PLM, Legacy Cloud, Legacy…. It is related to one word – competition with status quo. This is one of the most complicated competitions any solution can fight. Changes are hard and business is not running fast to replace one software with another software. The cost of replacement and predictability of implementation are factors that are adding on the side of not to move fast decision. What can convince manufacturing to move fast? Unique business functions and cost. Existing PLM systems in production going out of support and going out of relevance? Complexity of maintenance? New business requirements? Jury is out to check differentiation stories. Meantime, manufacturing companies are continuing to use existing PLM suites and pay maintenance to vendors. Just my thoughts…

Best, Oleg

Want to learn more about PLM? Check out my new PLM Book website.

Disclaimer: I’m co-founder and CEO of OpenBOM developing cloud based bill of materials and inventory management tool for manufacturing companies, hardware startups and supply chain. My opinion can be unintentionally biased.

Recent Posts

Also on BeyondPLM

4 6
9 June, 2009

The weekend normally puts me into a much deeper thinking mode about what to discuss on PLMtwine. Since the post...

30 June, 2009

Short prompt and amazing video. Our life becomes more and more mix of physical and virtual contents. I think Product...

27 November, 2012

Cloud discussions are trending these days. As Autodesk employee, I’m attending Autodesk University 2012 these days in Las Vegas. Autodesk...

16 February, 2009

How can we improve user adoption of PLM in the organization? What technologies can we use?? How can we reuse...

19 December, 2011

Blogosphere and other literature are full of remarks about companies that stuck in different phases of PLM process. You probably...

18 March, 2010

The online space influence on the enterprise systems and processes is increasing. During the last year and half, we have...

24 November, 2017

For the last few weeks I had a chance to speak to many people in engineering and manufacturing with no...

26 October, 2016

I’m planning to come to California next month to speak at Product Innovation conference which will take place at Orange...

27 August, 2014

We love and hate email at the same time. Since early beginning (back in 1962) email remains one of the...

Blogroll

To the top