PLM Best Practices

rated by 0 users
This post has 3 Replies | 1 Follower

Top 100 Contributor
Posts 11
Points 60
jonasach Posted: Sat, Mar 10 2007 3:38 PM

I would like to create a bom structure with a mix of part numbers which are in the system, and placeholder rows for sub-assemblies which we have not yet determine whether we will build or outsource. The part number prefix has a different value for make or buy parts. This makes taking out a new number difflcult until we have made that decision., yet we need the bom structure.

Is it best practice to take out a new part number for these placeholder rows?

Assume the placeholder rows will have real part numbers by the time the top level assembly is released. 

 

 

  • | Post Points: 35
Top 500 Contributor
Posts 3
Points 0
cwd replied on Mon, Oct 8 2007 4:51 PM
Have you considered using a placeholder part number encoded with the date and time?  Using the date & time would guarantee uniqueness of the placeholder, and you would not have to actually request a real number until you are ready.  It would probably be pretty easy to write a function which would convert the current date/time on the server into a string which could then be used to populate the part number field as a placeholder.
  • | Post Points: 0
Top 500 Contributor
Posts 2
Points 0
The method recommended by CWD is valid and doesn't require anything more than a calendar and watch, therefore no regulation or procedures.  I prefer to use a WIP registry, that is work in progress registry that consists of a part number mask and description.  It's a little more formal and you can have parallel part numbering until you reach a point at which a real part number is required.
Not Ranked
Posts 1
Points 5
ebattle replied on Fri, Jan 15 2010 12:04 PM

How about creating a prefix which indicates that the part number is a placeholder?

  • | Post Points: 5
Page 1 of 1 (4 items) | RSS