"Used on" parameter

[hbarker]

How can I add a USED ON paramater to a drawing sheet so that it would automatically fill in the correct parent assembly number when I'm detailing a component drawings.


Thanks in advance,
HB

 

[appinmi]

In the model, reate the parameter Used_on and give it the value. In the drawing format, create/modify a table and enter &Used_on in one of the blocks. You could also insert a note @[Used on:&Used_on@]

 

[hbarker]

Thanks appinmi,


Is there a way for the Used_on parameter to be automatically given a value from the next level assembly or do you have to manually type in this assembly number?


Thank in advance,
HB

 

[appinmi]

If it is possible, I do not know how to get the value from another assembly. I haven't tried it before. I just type in the parameter value.

 

[telecomguy]

Intralink is capable of knowing where a part is used. We have parameters that come from Intralink on our drawing template (&proi_revision). If you are using Intralink, you might look at ways of scripting the "where used" report function to create a string parameter that can be assigned to your part.


I'm a little out of my league on that one though. You may want to post over in the Data Management or Software Deveolopment forums.


<tg>

 

[dr_gallup]

You definately need Intralink or some form of PDM for this function. After all, there is no way for a part to know where it is going to be used. You could manually put this in initially but what is to stop someone else from reusing this part in another assy? We typically have a lot of slightly different products from a bunch of mix and match parts. Any given part could be used in 1 or 101 assemblies.

It is just my opinion but putting USED ON in a drawing is bad practice. Depending on how custom or generic your part is to the application, this data could be out of date before the ink dries. Assemblies can call parts, parts should not call assemblies. Just my $.02.


Edited by: dr_gallup

 

[telecomguy]

"It is just my opinion but putting USED ON in a drawing is bad practice"


Agreed. USED ON is a legacy from before bits and bytes came along. Now it's way easier to search where something is used rather than shuffling through a stack of assembly drawings looking for a part number in a table.

<tg>