What's in a number?

Part numbering in PLM has always been an interesting point of discussion, even after so many years since PLM evolved, with different people having their own fixed views. It is getting even complicated with the CTM (contract to manufacture) and CDM (contract to develop and manufacture) models. Each of the parties involved in the above models have their own PDM/PLM system with their own part numbers. So a single item could have multiple numbers across different parties involved, which naturally complicates things. Imagine you being called by different names and everyone trying to map your name to their own internal name. What a mess? Hopefully this topic will die soon and the industry can focus on more important issues. I will share the lessons I have learned from part numbering:

1. Part numbers are tied to legacy data and processes. Before selecting a PLM system, take time to understand how the legacy data is organized and processed. Smart numbering, such as dash numbers, and the logic around such numbers are not supported by all PLM applications.
2. Create visibility with the end users, rather than the managers, who know how most processes work.
3. Change Management - Try to convince the users to adopt the industry standard practice (though it is questionable if such a standard exists) rather than trying to force a solution on them. The earlier they know the better it is.
4. Changing existing part numbers to new numbers could be disastrous. These part numbers could have propagated to downstream systems such as ERP and MES. Make an impact analysis on if it is worth making the change on all these systems? Make an end to end analysis rather than just focusing on engineering processes.

If ERP and Finance processes could be standardized and talk the same language irrespective of tools used then PLM should be able to do the same. Will it happen?

More to come. Stay tuned!