Question
Preparing for introduction of PDM/PLM system (part I, duplicates)
We are preparing for the introduction of a PLM/PDM system.
Our directory based "vault" was investigated and, as expected, there are "some" problems
One of them being duplicates.
Instances from family tables were saved as a individual model file.
Also the opposite occured, inidividual models were also added in family tables.
I recently have been put in charge of (garbage, coming to america) removal of the duplicates.
First thing I did put those duplicates outside the scope of the search-path.
Next step is to identify which assembly contains an instance and which contains the individual part-file.
If I remember things well from way back when there wasn't a bytecount in the model files
internally
family table items are referenced like "3 3 instance<generic>"
individual files are referenced like "3 3 modelname"
For my investigation I'm using a DOS fgrep and a windows grep to identify
which assemblies refer to the individual file
I've created a dos batch file that does this for all found duplicates
fgrep -r -n -x "3 3 800100030" d:\prosrv\rel > c:\temp\800100030.txt
basically what this does is
list all files that contain a string "3 3 model-name"
recurse through directory d:\prosrv\rel
redirect output to file model-name.txt
This fgrep does not see the difference between "3 3 instance<generic>" and "3 3 modelname"
nor does it allow me to specify where the search string should be located in the line.
The windows grep allows me to specify that the search-string need to be at the beginning and the end of a line
but only allows me to search for a single string at the time
So both methods have their pro and cons
Having identified which assemblies I need to have a look at and
having the duplicates removed from the search-scope
I noticed that all the assemblies open properly and that they al of a sudden refer to object from family table.
I opened and saved an assembly and noticed (wordpad) that the internal notation of the duplicated individual partfile
changed from
"3 3 modelname" to
"3 3 instance<generic>
Question :
Is pro capable of switching from individual partfile to instances from a family table ?
Does my memory still serve me well about the internal model notation
3 3 modelname
3 3 instance<generic>
Are there other mehods of investigating what I'm trying to achieve here ?
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Our directory based "vault" was investigated and, as expected, there are "some" problems
One of them being duplicates.
Instances from family tables were saved as a individual model file.
Also the opposite occured, inidividual models were also added in family tables.
I recently have been put in charge of (garbage, coming to america) removal of the duplicates.
First thing I did put those duplicates outside the scope of the search-path.
Next step is to identify which assembly contains an instance and which contains the individual part-file.
If I remember things well from way back when there wasn't a bytecount in the model files
internally
family table items are referenced like "3 3 instance<generic>"
individual files are referenced like "3 3 modelname"
For my investigation I'm using a DOS fgrep and a windows grep to identify
which assemblies refer to the individual file
I've created a dos batch file that does this for all found duplicates
fgrep -r -n -x "3 3 800100030" d:\prosrv\rel > c:\temp\800100030.txt
basically what this does is
list all files that contain a string "3 3 model-name"
recurse through directory d:\prosrv\rel
redirect output to file model-name.txt
This fgrep does not see the difference between "3 3 instance<generic>" and "3 3 modelname"
nor does it allow me to specify where the search string should be located in the line.
The windows grep allows me to specify that the search-string need to be at the beginning and the end of a line
but only allows me to search for a single string at the time
So both methods have their pro and cons
Having identified which assemblies I need to have a look at and
having the duplicates removed from the search-scope
I noticed that all the assemblies open properly and that they al of a sudden refer to object from family table.
I opened and saved an assembly and noticed (wordpad) that the internal notation of the duplicated individual partfile
changed from
"3 3 modelname" to
"3 3 instance<generic>
Question :
Is pro capable of switching from individual partfile to instances from a family table ?
Does my memory still serve me well about the internal model notation
3 3 modelname
3 3 instance<generic>
Are there other mehods of investigating what I'm trying to achieve here ?
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.