Quantcast
Channel: PTC Community : Unanswered Discussions - Modeling
Viewing all articles
Browse latest Browse all 2891

Replacing parts (like hardware) non-windchill

$
0
0

So here is the issue that I would like to solve. Our company has done a very poor job of managing hardware and other parts that are candidates for family tables. Basically they haven't managed it, so it's a free for all which is causing problems. The specific issue that I would like to tackle is multiple copies of the same part number in a family table. To set up an example:

 

Say we have a 1/2" bolt of various lengths the generic in bolt_12, with part numbers 1234 and 4321 in the family table. We will keep it simple, but realize that the actual part has 20 or 30 parts in it. (we'll call this one part A)

 

that part is saved in the hardware folder like it should be.

 

somehow that part got a copy of it saved in the upper level CAD drive. (we'll call this part X becuase it's bad) Both locations are in the search paths on the config files for various reasons. Since there was little foresight into setting up part numbers for hardware, part numbers are created whenever a new length is needed. They have no order, it's just a pull the next number out of the list. So after the generic got copied, now new part numbers are created in the family table, BUT only on one of the copies because no one realized or understood the ramifications, or cared that there was two copies. So now part X has 1234, 4321, and 9999. Meanwhile part A has 123, 4321, and 8888

 

Now we have the issue that we have the same bolt called out in many (who knows how many) different models.

 

I actually have no idea how this even works at all. But we are managing for now, partially by ignoring the problem.

 

My question is, how can I (or is it possible to) reconcile the two models? It will be nearly impossible to go through every model and replace all of the parts manually. Some models are not needed and it would be a waste of time (but I can't define that with the information that I have) and I would surely miss some anyways. The system is "working" right now, however I believe it is setting up little booby traps that may go off at any time.

 

I can go into part A and create all of the parts that were only in part X, but...

 

Can I set references in a part so that if the model was created using part X but only finds the number in part A, it can know what it needs to constrain to so it doesn't blow up the model?

 

Thanks for any help, and as always, if you need more clarification feel free to ask.


Viewing all articles
Browse latest Browse all 2891


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>