REVISIONS - How do I break parent - sibling links between revised part

[dhernandez32]

I want to know how to break PARENT-SIBLING LINKS between REVISED PARTS or assemblies.

Whenever a part or assy is revised, a link is created between the parent and sibling components. This is desireable when one wants to know EVERYTHING about the history of the part.

But there is a drawback to this for me. The drawback for me is that when the new revision ( sibling) is released, the original part ( the parent ) gets moved to the obsolete folder. This for me is a problem becasue i need both the parent for some machines and I need the sibling for other machines.

WHY I DO THIS
I do this because it is convenient becasue when i do a revision, i ALSO GET THE DRAWING automatically. This is what I want. BUT I need to break the parent-sibling relation that is created. I do not want to do a SAVE AS operation becasue when i do this, i loose the drawing and that wasts my time.

Also the reason I do not use the copy command inside revision manager is becasue i cannot tell which parts will need changing by looking at revision manager (which is text based).

-------------------------------------------
In the following I provide more details if you want to know more. But the basic question is stated above.

SE enviornment:
We use insight an sharepoint and work with managed folders.

The reason I want to break parent-sibling link between revisions is because I find it useful to use REVISIONS to create NEW machines based on OLD machines. BUT i want to preserve the OLD machine intact.

Let me explain how I want to work and let me explain what ALMOST works but fails at the end.

DESIGN SITUATION:
I design machinery with 500 + parts.
I Often am called upon to create a new variation of this machine which needs heavy modes of 250 out of 500 parts. So 250 parts are existing parts and 250 are heavy modifications of existing parts.

MY CURRENT WORK FLOW:
1. I open the top level machine and do a REVISION on it. So if the original top level assy is number 100.asm then i call the revision 100-1.asm
2. After carfully reviewing the project, I identify which of the 500 parts will be modified.
3. Next, I begin creating REVISIONS without modifying any parts. I just spend time creating revisions and saving them as 'dash-1' numbers. So if part 123 needs to be modified, then i do a REVISION on that part from the parent level and name it 123-1 and so on.
The reason i do this is to create a new part AND HAVE THE DRAWING FOLLOW THE PART. Also this procedure saves me time as i need not do a replace. once the revision work is done.
4. I finish my design.
5. With this procedure I obtain everything i want; the drawings are done, the solid model is done, and the assy is done.

THE PROBLEM I HAVE
1. The problem I have is that if i do a RELEASE on the new package, SE will send the ORIGINAL non revised parts to the OBSOLETE folder. This is undesireable becasue these original parts are perfectly good parts that are used in other machines. Therfore i do not want them to end up in the obsolete folder.
2. SE by default REMEMBERS what part is the parent of a revision. There is a hidden parent-sibling link between revisions. I WANT TO DELETE THIS LINK so that the parent of the revision does not end-up in the OBSOLETE folder when I release the project

 

[toffeet]

Good morning,

Are you familiar with the admin.exe and option.xml files? When you open your option.xml file with admin.exe you can change the “Life cycle – make obsolete” option to allow override. When changes are made to your option.xml file remember to update it in Solid Edge options.

Regards,
Theodore Turner

Solid Edge ST2 SP5 on WinXP x64

 

[Kenny_G]

I would rcommend that revisions only be used for parts where fit/finish/function is unchanged. Essentially if the part is not backwards compatible with older machines, it cannot be a revision and instead must be a new part. If you use Revision Manager to do the copies of the models to new names, you can also find the drawings and copy them at the same time.

Now if you're depending on the revision rules to open files, you can always open your old machines using the "As Last Saved" option to get the specific revision that was placed in that structure of every component/subassy even if it has been moved to Obsolete. I would view this as a workaround to the method mentioned in the paragraph above though.

Ken G.

http://grundey.blogspot.com

 

[dhernandez32]

Thank you Ken for your comments.
Thank you Theodore.
I now understand I've been abusing or REVISIONS.

In my business, I create new machines using variatons of old ones which are still in use on other machines.

It is easy to open up a top level assy and start rev'ing parts up to create new variations which will end up being new parts(with dft attatched). For me using rev manager is harder becasue it is text based and becasue it is important to me NOT to create duplicate part numbers for the same part. To avoid duplicate part numbers, i now need to do a replace for all the parts that DID not change and delete unmodofied copies. That is a pain in the ass.

To solve the problem i created, i copied the project to an unmanaged folder, deleted the original version in the managed folder and added the unmanaged folder back into the managed folder. That worked.

Theodore,as far as changing the option.xml file is concerned, i am all in favor but iam not important enough to get that changed right now. If it were my business, I would turn that feature off and continue working as i worked on this project,...it's too easy!

Thanks