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

Existing data prevents companies to improve Part Numbers?

Existing data prevents companies to improve Part Numbers?
Oleg
Oleg
15 August, 2014 | 2 min for reading

historical-part-numbers

Part Numbers is a fascinating topic. I’m coming back to blog about what is the best approach to manage Part Numbers. My last post about it was – Part Numbers are hard. How to think about data first? was just few weeks ago. In that article, I outlined few principles how to keep PN separate from surrounding data focusing on different aspects of parts – description, classification, configurations, suppliers, etc.

Yesterday, my attention  was caught by ThomasNet article – Are Part Numbers Too Smart for Their Own Good? The article nailed down a key issue why companies are still having difficulties with management of Part Numbers. Nothing works from scratch in engineering companies. Complexity of characteristics and history of existing Part Numbers and products are making real difficulties to adopt new PN management concepts. The following passage explains the problem:

Another problem with descriptive numbering is that the description can become out of date and irrelevant over time. Individual parts can have their own life cycles; if a part has been identified according to the product, what happens if that product is discontinued but the part continues to be used in a newer product? Or what if a manufacturer changes vendors and the part number contains the name of the vendor that originally provided the piece?

Gilhooley admits that some Ultra Consultants clients have decided that switching from descriptive to auto-generated numbering would require too much organizational change. Some companies stick with old systems, and some opt for hybrid systems that perhaps retain descriptive numbers for existing parts but use auto-generated numbers for new parts.

It looks like there is no single solution or best practice to solve the problem. The “traditional” engineering approach to keep options to manage a diverse set company configuration looks like the only possible way to solve this problem in existing PLM/ERP systems.

What is my conclusion? History keeps customers from moving forward. There are two aspects of complexity in Part Numbers: 1/ complexity of definition and data classification; 2/ historical records of PN in every company including catalogs and existing products. Together, they create a block to make any changes in existing PN schema and prevent companies from migration towards new approaches. New data modeling technologies must be invented to handle existing data as well as supporting customers to migrate into modern PLM and ERP solutions. Just my thoughts…

Best, Oleg

Recent Posts

Also on BeyondPLM

4 6
20 August, 2012

Despite hot weather and summer vacation time, I can see quite many cloud discussions trending around. I was following OSCON...

6 April, 2017

In my earlier blog I demystified the notion of “monolithic” PLM marketing and shared some technological aspects related to PLM...

14 October, 2023

It is almost 40 years after PLM was introduced by American Motors Corporation (AMC). Digital Engineering article PLM Stays Relevant...

4 September, 2015

Happy Friday! Summer is over and long weekend is just around the corner. A good time to try something new....

2 October, 2017

I’ve been reading Jim Brown’s article about Innovation Platforms over the weekend. Navigate the future! Check the following link to...

29 December, 2011

PLM is a costly piece of software. Software licenses, installation, implementation, support, services. All these components of PLM software make...

23 October, 2014

I want to continue the theme of how do we move to the cloud. While Amazon remains one of the...

29 September, 2014

Cloud PLM architecture and implementations is one of the topics I’m following for the last few years. It is interesting...

28 April, 2016

In software application programming interface (API) is a set of routines, protocols and tools to build a software. An API...

Blogroll

To the top