For those of you that use revision manager, this may be a non-issue, but some users still have an issue with intelligently moving or renaming subassemblies or parts. So at the risk of over simplifying the issue, I’ve put together a simple example to illustrate how to achieve this task.
The scenario: I have created a Test folder representing my server. Inside this folder there are 5 other folders as shown below:
Folder1, Folder2, and Folder3 each contain a different assembly. These 3 assemblies all use a subassembly that currently resides in the OLD folder. The goal is to move and rename the subassembly from the OLD folder to the New folder, without breaking the links to the 3 assemblies in Folder1, Folder2, and Folder3.
To start the process, I open the OLD folder, locate the subassembly, and RMB click on it to select “Open with Revision Manager”.
Note: I could also open the View and Markup program from the Start Programs menu and then open the file in Revision Manager, from View and Markup.
Once in Revision Manager, I highlight the subassembly and its components as shown below.
Note: If you click on the top left grey square, it will highlight all the occupied rows below it.
Next, I go to the Tools tab and select the Where Used command, in the Assistants group.
The Where Used dialog appears and allows me to set up my search scope. In this example, I want to search the TEST folder in my C drive. Notice that I have also toggled on the Include subfolders option, near the bottom of the dialog.
Note: Under the Process options button, I could filter the type of files that I am searching.
Once my search scope is set up, I click Next. The process runs and reports back to me the Number of documents processed: and the Number of documents found:
I click Finish, to dismiss the dialog. I am left with a list of where the subassembly and its components are used. Remember this list is only based on my search scope. If the subassembly or its components are used outside of my TEST folder, it will not show up unless I expand my search scope.
Now I will move and rename my subassembly. To do this I RMB click over the highlighted components and select Set Action to Rename.
Note: I could also click on the Rename command on the home tab, in the Action group.
Notice the New Filename column becomes populated.
I now either click on the Set Path command, on the Home tab > Action group, or RMB click and select Set Path from the shortcut menu. This launches a browse dialog. From there I select the New folder, which is the location that I want to move the subassembly and its components.
When I click OK, the New Filename column is updated to the new path.
Now I can rename the components. In this case, I want to replace the “exp” prefix with a “new: prefix. To do this I select the Replace command from the Home tab>Edit group.
I set the dialog up to find and replace “exp” with “new”, as shown below.
Once I completed this process I see the new names, along with the new location, listed in the New Filename column.
These changes have also occurred in the Where Used section of the Revision Manager.
Before I tell the system to make these changes, I need to tell it to update all the parent assemblies that use this subassembly and its components. To do this I first highlight all the listed parent assemblies, as shown below.
Next I either click on the Update command on the Home tab>Action group, or I RMB click and select Set Action to Update from the shortcut menu. This populates the New Filename column in the Where Used section as shown below.
Now I simply review all my actions and once satisfied I click the Perform Actions command.
Once the process is complete, I can exit the Revision Manager, and confirm my changes. I confirm that my OLD folder is now empty and that my New folder is populated with the newly named subassembly and its components.
I can open the assemblies in Solid Edge or Revision Manager to confirm that there are no broken links.
Although this was a simple example, you can see how this can be used on a larger scale. Revision Manager is a powerful and reliable tool that helps you manage your data in a non-managed environment. If your data has become too large to easily manage you should consider implementing Teamcenter.
Teamcenter is the world's most widely used PLM solution. For manufacturing companies who need to deliver increasingly complex products while maximizing productivity and streamlining global operations, Teamcenter helps increase revenue, get to market faster, reduce costs and improve product quality. Teamcenter simplifies PLM with targeted applications available to do what customers need when they need it. Platform capabilities get customers up and running quickly with a high definition user experience to inform decision-making anytime, anywhere. Applications are built on the PLM platform to help customers grow their deployment strategically over time.