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

Back to basics: PLM and Single Point of Truth?

Back to basics: PLM and Single Point of Truth?
olegshilovitsky
olegshilovitsky
14 December, 2009 | 2 min for reading

I’m continuing with a set of ‘back to basics’ questions and discussion. My topic today is about singularity or what known in PLM as “a single point of truth”. I remember the time before computers were widely spread in engineering and manufacturing organizations and people used “Drawing on the wall”. The famous statement back to that time was – if you see drawing on the wall, think maybe there is “another wall”. Computers supposed to resolve the problem of multiple walls. However, the problem becomes even worst. Now you may have an unlimited number of “electronic walls” in your email system, disk on your laptop, server in your location or different enterprise systems. PLM comes with a very promising and illusive statement about single point of truth. From PLM standpoint, it defined as capability (or ability) to manage single (or unique) version of product data in your organization.

Now, my questions today about how to manage this uniqueness? Is it something you can see as an achievable goal for your next PLM implementation or wishful thinking? Is it something we can realistically implement in the organization with all systems we have in place? Can we achieve it in a single shot, or we need to have multiple steps to get there?

Here is my take on this (and I’m making it the most provoke as I can think about).

1. PLM Singularity (or single point of truth) represents a fundamental interest of people in the organization to organize and manage product data.
2. We can implement it in the organization, but it requires a significant effort that may vary depends on organization complexity and number of other systems involved into product development process and number of geographical locations company plan to cover by this system.
3. Implementing of singularity may take multiple steps until it will be achieved in the organization.

So, what is my conclusion today? I think, singularity cannot be considered as a goal for PLM implementation. The final cost can be too heavy to carry, and it will take long time to get there. Realistic PLM implementation need be done as “go by steps” approach. Each step will achieve goals helping organization to resolve specific issues they have in the organization or optimize existing processes. This is the only way to create something I’d call – lean PLM. If you want to implement single point of truth, think about playing “singularity chess” before :). (thanks, Paul Burgess blog for picture)


Just my thoughts. I’m looking forward to your comments.
Best, Oleg

Recent Posts

Also on BeyondPLM

4 6
17 January, 2014

Enterprise software choice is a complex decision process. The time when you was able to buy a software from trusted...

17 March, 2009

In today’s world, more and more companies need to collaborate globally. In the supply chain, this is a result of...

7 June, 2018

PLM adoption is one of the most intriguing things in engineering and manufacturing software. The ideas of PLM systems are...

22 May, 2009

Once in a while, industries, companies, or developers come up with something that they think will change the technological and...

15 December, 2010

The conversations about future CAD and PLM solutions is not a new thing these days. I decided to re-read some...

12 January, 2018

It’s a new year outside. The time is running fast and we are moving towards 2018 with new questions about...

25 July, 2014

SaaS, PaaS, IaaS, DMaaS, … I’m sure marketing folks are having lots fun of new xaaS acronyms. The amount of...

8 April, 2011

I want to get back to the topic of Out-of-the-Box PDM systems. The topic isn’t new. The following post by...

2 June, 2009

Watching multiple demos and analyzes of Microsoft Gemini Project.  Since a huge amount of corporate and product related data is...

Blogroll

To the top