Skip to main content

Insert Assembly Copy

Solid Edge has had the command Insert Part Copy for a long time.  Insert Part Copy functions by allowing you to insert the geometric body of an existing Part, Sheet Metal or Assembly file into another Part or Sheet Metal file.  The geometric body can be optionally inserted associatively as an Ordered feature, or non-associatively in Synchronous mode and supports several options such as making the body a construction, scaling, or mirroring the inserted body.


A similar command was made available in ST5 and later versions called Insert Assembly Copy.  Insert Assembly Copy functions by allowing you to insert an existing Assembly file into another Assembly file.  Unlike Insert Part Copy which inserts a body, Insert Assembly Copy inserts the actual assembly structure under an Assembly Copy node in Pathfinder.  The resulting Assembly Copy is associative to the original such that any changes or additions to the original will be reflected in the copy.   You can of course freeze or break the link of the Assembly Copy which results in the Assembly Copy node becoming non-associative to the original.



The Insert Assembly Copy command has several options which are:
  • Add new components on update (If this is unchecked, adding new parts in the copied from assembly does not update the Assembly Copy with the new parts)
  • Include assembly features
  • Mirror about (uses the same wizard as the Mirror Components command)
  • Exclude Components



Uses for the Insert Assembly Copy include:
  • Creating a mirrored assembly (Left Hand vs. Right Hand)
  • Inserting a base 80% assembly into multiple assembly files and adding optional parts in each to produce 100% configured assemblies.
  • ???  If you can think of any other novel uses, please comment them on this article.

The Assembly Copy function is also used by:
  • The Mirror Components command in Assembly to associatively mirror assembly structure/components.
  • The Multi-Body Publish command to build an assembly of the published bodies for downstream use.

Comments

Popular posts from this blog

Solid Edge ST3 - Part 1 of 4

The Siemens PLM Connection event is over.  Given the change of date and venue due to the flooding of the Opryland Hotel in Nashville, it was a great success.  There were many excellent presentations and "hands-on" training sessions for Solid Edge (including mine) , and even though a formal announcement of the upcoming ST3 is some time away, we got a sneak peak of several new customer driven enhancements as well as some hint of: A "bridge" to help existing users better adopt Synchronous Technology Simulation enhancements PDM enhancements 1000's of customer enhancements from modeling to the user interface Over the next few weeks, I'd like to cover some of the items presented around the customer driven enhancements, but please keep in mind there are still a whole lot of items that will not be presented until the official Solid Edge ST3 launch later in the year. For this post, I would like to cover the User Interface enhancements. You now have...

Dimension Projection Line Breaks

Often when placing dimensions on drawings, the projection lines of some dimensions will cross the projection lines of other dimensions as shown below. Solid Edge provides a function to automatically create breaks in one extension line where it crosses another. This function is called "Add Projection Line Break". It is accessible from the Shortcut Menu when you have a dimension highlighted. The result is shown below. If you wish to remove the projection line break, highlight the dimension, invoke the shortcut menu, and select "Remove Projection Line Break".

Solid Edge V20 Deployed!

I have finally gotten Solid Edge V20 and the Viewer deployed through my organization on Sept. 27th. We deploy SE to over 100 users and the Viewer to over 400 users across about 10 geographic locations in one night over a couple hours. All went well considering this was the first deployment since the new Packaging Specialist started, and it was done on a brand new version of the deployment system we use. We use Microsoft's System Center Configuration Manager (SCCM) which was just upgraded from SMS 2003. http://www.microsoft.com/systemcenter/configmgr/default.mspx . It allows inventorying PC's throughout the org, as well as pushing software to the PC's. To be able to push the software, you must use the MSI supplied by Solid Edge and repackage it as an EXE. Since the MSI is used, you must also install .NET and ISSCRIPT separately (which can also be added to the EXE package). We found that the ISSCRIPT.MSI must be modified to work with SCCM due to the fact that it insta...