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
14 May, 2009

Look at this news about Google Cloud: 1. MS Office: 0. Actually, most of the discussion here is about when...

28 April, 2024

In the world of engineering and product lifecycle management (PLM), Excel and other forms of spreadsheets have long been well...

12 August, 2023

JIRA software, developed by Atlassian, is a widely recognized tool used for software development teams for bug tracking, issue tracking,...

22 June, 2020

PLM industry has a new marketing darling – SaaS. It was just two weeks ago when I shared news about...

10 April, 2020

Earlier this week, another virtual session of CIMdata PLM Market and Industry Forum provided a bunch of interesting ideas and...

23 May, 2010

Welcome to Beyond PLM! I will be starting blogging here very soon. For the moment, please check my Daily PLM...

6 May, 2009

Last month, I wrote a few posts about Bill of Materials. My interest was to investigate how to improve Bill...

1 September, 2019

One of the presentations during last ConX19 event last week in San-Diego, was from Craig Brown, former PLM leader of...

7 October, 2013

There are almost as many cloud storage services as clouds in the sky these days. Cloud opens a huge opportunity...

Blogroll

To the top