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

Top annoying things about PLM software.

Top annoying things about PLM software.
olegshilovitsky
olegshilovitsky
26 August, 2009 | 2 min for reading

PLM as a combination of technologies, software, and methodology came long way from initial CAD systems, followed by CAE, Product Data Management and Collaboration Software. Some of the PLM-software components are very mature, but some of them are still in the early beginning. While we’ve innovated in many PLM products and technologies, we’ve also continued to disregard pre-existing PLM issues.

Here my list about top annoying things in PLM with no specific order, however, I do believe I started with the most significant ones.

PLM Implementation Scope. PLM software pretends on overall control of product IP and data. By saying that PLM companies, in my view, try to boil an ocean and claim to support unlimited capabilities in management of information and business processes around product development and manufacturing. Multiplied by marketing and sales, PLM creates perception of “do everything” software.

PLM Uniqueness. Ability to support a design process, manage product data and collaboration presented as unique capability of PLM software. Such position creates perception of premium value provided by PLM software and, very often, disregards other available alternatives in managing data and collaboration.

PLM Complexity. I have to admit product engineering and manufacturing are not a simple topic. To manage such processes and data, software needs to achieve a specific level of sophistication and complexity. However, in my view, PLM often exaggerated needed a complexity level and sophistication. In the end complexity creates a significant adoption rate problem. These time people like simple words and simple software.

Terminology. PLM domain created huge terminological barrier for people to get into this space. Number of multiple buzzwords and terms create difficulties to understand business purpose and capabilities of software. Heavy usage of overlapping and confusing terminology put a very significant constraint on ability to use software and tools that come from different software vendors.

Bizarre User Interface. Because of a long life cycle of a software product, user interface is something that was development during many years and contain multiple “historical reasons”. Even if during last few years, user experience was priorities by most software vendors in PLM space, this is still pace requirement multiple improvement and innovation.

Slooooow…. After all, performance isstill one ofthe most discussed issue software vendors isfocusing on. Refresh time, Render Time, regeneration, display, view etc. All these functions are very time consuming and contains space for innovation.

Best, Oleg

Recent Posts

Also on BeyondPLM

4 6
4 February, 2021

My earlier article How to make BOM integrations easy? raised a lot of debates online and offline. It was quite...

24 July, 2009

I’m very happy to share article by Kenneth Wong in DE Online. One Small Step for Office, One Giant Leap...

2 April, 2009

In my previous post “Search for the right BOM – I’m feeling lucky? “, I started to discover possible ways to...

2 February, 2010

I want to propose an unusual theme for our PLM discussion. Let’s talk about trends related to manufacturing and software...

24 July, 2022

SaaS is growing and I can see every day how manufacturing companies are adopting SaaS solutions. What was a vision...

5 October, 2011

Business Intelligence (BI) is a fascinating combination of words. Each time I hear about BI, I’m confused a bit. The...

25 May, 2017

Recent CIMdata cloud PLM research brings attention to PLM cloud circa 2017 and trying to figure out reasons why manufacturing...

16 May, 2018

One of the trending technologies these days is blockchain. Unless you live under the rock for the last few years,...

13 July, 2017

Unless you live under the rock, you know what is SOA (Service Oriented Architecture). It was style of software design...

Blogroll

To the top