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

What’s wrong with “analog PLM”?

What’s wrong with “analog PLM”?
Oleg
Oleg
6 July, 2015 | 4 min for reading

analog-computing-devices-plm-old

In engineering world, digital vs. analog differentiation can be explained in a very precise manner –  analog is using electrical signals. Opposite to that digital is using binary format. Things are much more complicated when “digital” term comes into marketing realm.

Accenture article Faster, fitter, better: Why product innovation is going digital is taking a marketing spin and coming with the term of “digital PLM” as a system or approach that can help companies to improve their product development processes and improve innovation. I like the following passage explaining the difference between digital and non-digital PLM worlds:

Such models, where the multiple processes and systems live in silos, inhibit the flow of relevant information needed to optimize product development. Engineers, for example, are often disconnected from the new-product introduction process. As a consequence, new-product launch teams don’t always hear about critical last-minute design changes. And because vital insights are not shared, the solutions that eventually emerge from this fragmented system just aren’t meeting customer expectations for innovation and relevance. Moreover, because of this linear approach, product launch is often delayed.

It made me think more about “digital vs. analog”. An obvious thing to think about companies are using “paper” trays to share information and manage processes. I can see it as an option. But the chances are companies are using at least emails to share information. Still can be very complicated way to collaborate. I guess most of companies are trying to step up from an analog way of sharing information and manage changes using emails into the realm of PLM systems. But it doesn’t go very well in many situations or it gets very expensive. So, what is the problem with inefficiency with “analog PLM” implementations?

One of the core elements of every PLM system is its “data model”. Jos Voskuil provided a good explanation about what is “PLM data model” in his last article – Importance of PLM data models. According to Jos, the success of PLM implementation depends on an efficient organization of PLM data models. Here is the passage that explains that:

My conclusion for both situations is that it all leads to a correct (PLM) data model, allowing companies to store their data in an object-oriented manner. In this way reflecting the behavior the information objects have and the way they mature through their information lifecycle. If you making compromises here, it has an effect on your implementation, the way processes are supported out-of-the-box by a PLM system or how information can be shared with other enterprise systems, in particular, ERP. PLM is written between parenthesis as I believe in the future we do not talk PLM or ERP separate anymore – we will talk business.

Jos is absolutely right in his assumption. The traditional world of PLM implementations is requiring to translate everything into PLM data models. Take every PLM system and you will see this step as an essential element of every implementation. If I refer to the engineering definition of “analog” system, it means to translate the real world – organization, data, processes into “analog world” of data models. With a full respect to flexible PLM data models and architectures, this translation is creating distortion and the process itself is very complicated.

Is there a better way? I think digital PLM (or whatever other name our marketing genius  bring) will have to abandon old “analog PLM” practices of data modeling as a complex and outdated approach. Digital PLM will be able to use native representation of product information and product development processes across silos without translation into variety of PLM data models abstractions. It doesn’t mean data models will disappear tomorrow. Software will have to use data models anyway. But customers and implementers will be excluded from the loop.

What is my conclusion? Think about existing PLM data modeling approach as a way to translate native sound or video signals into electric signal to transmit it into organization. Think about it as an “analog approach” similar to what we had in the past in audio and video recording. In PLM it created a whole level of implementation complexity – a need to define data models and and map organizational reality into these models. Future “digital PLM” will have to bring a better way and exclude people from a formal data modeling loop. It will make PLM systems simpler to understand and easier to implement. Just my thoughts…

Best, Oleg

picture credit Wikipedia article presenting an ancient analog computer

Recent Posts

Also on BeyondPLM

4 6
21 March, 2011

One of my blog readers shared with me slides of Paul Saunders presentation about MRO software from the Miami Aircraft...

23 March, 2018

Collaboration becomes increasingly important for manufacturing companies. Earlier this week, the news about Airbus deal with Google G-suite created some...

29 June, 2016

One of the news that caught my attention yesterday was Autodesk announcement to acquire CADSoft Eagle PCB design tool from...

18 July, 2015

One of the topics I’m following closely these days is cloud CAD development trend. To make cloud CAD work from...

25 April, 2012

What is the next file system that will be available for our disposal? Cloud file system. Really? In the past...

13 May, 2018

PLM consulting is an interesting part of PLM business. Traditionally, PLM projects were big and expensive. When you about to...

7 October, 2011

I’ve been watching what happens around Oracle Open World 11 earlier this week. Among multiple topics, the announcement about Oracle...

19 September, 2013

GitHub is a well known social network for programmers. According to Wikipedia article, GitHub is a web-based hosting service for...

27 July, 2017

There are different levels of PLM implementation complexity – long planning, budget overrun, customization delays. Tons of articles are written...

Blogroll

To the top