Decoupled Part Numbers!

What’s in a name?

In this article, we delve into the concept of separating a file's filename from the part number used for purchasing the item. More often than not, a file's name corresponds to its part number, which works well in most scenarios. However, it can become problematic as items progress into the 'released' state, and purchasing and manufacturing activities come into play.

In the context of a PDM environment, particularly when dealing with SolidWorks files, employing a custom property, such as '<Company Name> PART NUMBER,' to store the actual part number offers numerous advantages. This approach allows for the decoupling of the file's name from its part number, and there are compelling reasons to adopt this practice.

To begin, let's explore a method for automatically capturing the filename within a SolidWorks file and using it as the part number. By utilizing the built-in function '$PRP:"SW-File Name"' as the 'Value/Text Expression' for the 'PART NUMBER' custom property, the field is instantly populated with the file's name. This built-in function proves highly valuable because it dynamically updates the 'PART NUMBER' property value if the file is renamed or copied to a new name, ensuring seamless synchronization.

Using the $PRP:"SW-File Name" to capture the filename to the PART NUMBER property

Why would we consider decoupling the filename from the part number in SolidWorks? Let's examine this with an example. Suppose we are designing an O-ring that assumes a non-circular shape, like a rectangular slot. How would we effectively manage this in SolidWorks? If we were to create a part to model the deformed shape, its filename might correspond to a dash number associated with the assembly where the O-ring is utilized. For instance, the assembly file might be named '123456,' while the deformed O-ring part could be '123456-01.' However, procuring '123456-01' directly might prove challenging.

By incorporating an embedded custom 'PART NUMBER' property, we gain the flexibility to assign any desired value to this field, such as the actual part number under which the standard O-ring is purchased. In doing so, we successfully decouple the filename from the part number. When generating a bill of materials (BoM) table or reviewing the BoM readout in PDM, we can utilize the 'PART NUMBER' field instead of relying on the filename. While in most instances, the filename coincides with the part number, having a 'PART NUMBER' property allows us to manipulate this information behind the scenes to ensure that the BoM accurately reflects our procurement or fabrication requirements.