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

PLM Model: Granularity, Bottom-Up and Change

PLM Model: Granularity, Bottom-Up and Change
olegshilovitsky
olegshilovitsky
3 May, 2010 | 2 min for reading

Few weeks ago, I had chance to post about PLM Data Model. I think, PLM space has a real lack of discussions about data modeling. It seems to me, PLM vendors and developers are too focused on process management, user experience and other catchy trends. At the same time, everybody forgot that data model is bread and butter of every PDM/PLM implementation. I want to open some debates about what I see missing in current PLM data models.

Granularity
I’m very happy, this word started to catch up attention of people. It came in multiple discussions I had last time with some of the colleagues in the CAD/PDM/PLM software domain. Chis mentioned in it his Vuuch (www.blog.vuuch.com) blog. Al Dean also had chance to talk about it on his Develop3D (www.develop3d.com). One of the problems in PLM is a diversity of implementation and needs. PLM tools implemented lots of functional goodies over the past decade. However, the customization becomes a mess. It looks to me, current data model organization is outdated in most of PLM systems these days.  The last revolution PDM/PLM made was about 15 years ago when the notion of “a flexible data model” was introduced. Today, the next step should be done.

Bottom-up
How to build an efficient data model for PLM implementation? How to build a model that answers to the specific customer needs. Current vendor’s proposal is to make a selection from the list of all possible “modules”. It comes in a form of “best practices”. In my view, it is really “bad” practices. Selecting of big data model chunks put too many model constraints and create compatibility problems. The idea of bottom-up data modeling relies on the capability to define very granular pieces of data and grow bottom up in building a model that reflects customer needs.

Cost of Change
What is the most killing factor in today’s PDM/PLM software. In my view, it is cost of change. PLM models become not flexible and keep lots of dependencies on PLM system implementations. The future, in my view, is building very granular functional services alongside with the bottom up data model schema. It will allow to decrease cost of change, reduce dependencies between components and in the end, reduce a cost of change.

What is my conclusion? I think, technology matters. Without thinking about technologies, PLM won’t be able to make a next leapfrog. It becomes urgent. PLM model is a natural starting point to improve PLM implementation.

Just my thoughts…
Best, Oleg

Share

Recent Posts

Also on BeyondPLM

4 6
28 January, 2023

ChatGPT was taking the industry by storm for the last few months. Unless you live under a rock, I’m sure...

25 February, 2009

In one of the previous posts , I thought about how it would be possible to use a WIKI engine to...

20 May, 2013

Searching for information is a tricky thing. Search may sounds as a simple operation, but in fact,  it is translated...

16 May, 2019

Financial information is not a typical topic in my articles. However, in a spirit of diversity in the thinking process,...

20 October, 2010

The following message on twitter from Jonathan Scott of Razorleaf made me think about the future of vertical integration in...

15 May, 2023

The topic of “intelligent part numbers” (IPN) came across again. This time it caught my attention via the post on...

23 August, 2009

The following article got to my attention this morning. Newsgator started back in 2004 as RSS syndication and stretching their...

3 January, 2025

Happy New Year! As I reflect on the past year, 2024 was a pivotal time for Beyond PLM and sharing...

4 June, 2018

In my article last week – How to avoid “focus on business” cliche in PLM sales , I introduced typical PLM...

Blogroll

To the top