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

How Big Is Product Lifecycle Data?

How Big Is Product Lifecycle Data?
olegshilovitsky
olegshilovitsky
6 July, 2010 | 2 min for reading

Product-related data is one of the most important aspects of any PLM implementation. When you talk about PLM implementation, the topic of product-related data (or IP) is very often becomes a center of the conversation.  There are multiple sources of this type of data in the organization. In my view, one of the PLM goals is to have a control of this data and provide tools to manage the overall lifecycle. One of the PLM implementation challenges is to provide wide support for product-related data. The topic I want to discuss is related the ability of PLM product to handle full scope of this product lifecycle data.

I read the article Oracle, SAP working on Exadata support. The core of this conversation is about how to scale up and provide extensive support for big data handling in the organization. Have a read of this article and make you opinion. Mine is simple – both Oracle and SAP understood the size of the potential problem (data size). They are working in multiple directions to find a solution for data sizing in transactional enterprise application. Should PLM care? This is a very good question in my view…

PLM and Product Lifecycle Data Problem
One of the challenges PLM is having for many years is getting control of product-related data. My observation shows that product-related data is not completely controlled by PLM systems in the majority of PLM implementations. Even with a very successful PLM implementation, data is scattered between multiple data sources and PLM is only one of them. In addition to that, product-related data can be located in the diverse set of applications used for product development.

Product Data, Size and PLM value
The full value of Product Lifecycle Management is directly dependent on how what scope of product-related data is covered by PLM. The wider scope can maximize PLM value for organizations. With all current developments, PLM is looking on starting from design to manufacturing strategies and development of social-oriented application, sizing can easily become one of the potential bottlenecks related to the ability to support large scope of data.

What is my conclusion? I think, to understand sizing of product lifecycle data is important in order to build right operational and strategic plans related to data management. Data is growing fast. Future PLM implementation can suffer from problems related to data sizing. How to scale up PLM implementation in terms of size can be one of the most important questions in the future. Just my thought…

Best, Oleg

Share

Recent Posts

Also on BeyondPLM

4 6
6 October, 2012

I have many discussions these days about cloud PLM with variety of people in different roles – technical, marketing, sales,...

27 June, 2012

If you are technology savvy these days, you probably know what is Apache Hadoop. It originally came to us from...

6 February, 2019

Engineering.com article A Solidworks user look at Onshape brought my PDM twisted mind again to what I call CAD version of Turgenev’s...

20 May, 2009

I think language is one of the barriers for successful collaboration. Therefore, I’m really excited about a new feature in...

22 January, 2022

In my two years old article in the Onshape blog, I shared my thoughts about what will be PLM systems...

7 November, 2018

I just came from PLMx Chicago. Great conference organized by MarketKey – practically the only independent PLM event in U.S....

31 March, 2024

Last week, I had the opportunity of attending the CIMdata Industry and Market Forum in Ann Arbor, MI. This annual...

20 November, 2018

I’m continuing to publish my notes and comments from AU2018. If you never been at AU… it is big. The...

27 August, 2010

I had a chance to read an article by ebizQ related to Cordys BPM. For those who is not aware...

Blogroll

To the top