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
16 September, 2010

Email is playing a significant role in the way every organization is management today. Organizations are run by emails these...

10 July, 2015

Disruption is a lovey topic to speculate just before the weekend. Aras-Airbus story gave a context to PLM industry analysts...

21 November, 2011

Do you know what is Microsoft Socl? I didn’t know until yesterday. However, now I know. It is a new...

31 August, 2017

For many years, selling PLM was a fascinating adventure. Tons of stories were published about marketing and sales tactics, selling...

31 March, 2009

I’ll start with a disclaimer. I understand that to start a “format discussion” is at least as dangerous as starting...

5 October, 2018

It has been long time since I covered Autodesk PLM in my blog. Time is running fast and it has...

30 May, 2011

Let’s talk about PLM software development today. Rewind pre-Web 2.0 and pre- iPhone era. Life was simlpe. After SolidWorks finally...

30 March, 2025

I just came back from Ann Arbor this week for the CIMdata PLM Market & Industry Forum. It is a...

5 April, 2014

I’ve been following CIMdata PLM market industry forum earlier this week on twitter. If you’re are on twitter, navigate here...

Blogroll

To the top