Share
 
 

Using Copy Design with Factory and Members

Use these best practices to copy your factory and member files.

The usual design intent of component families is for reuse. Therefore, a copy consuming family members is expected to reuse family members or to replace family members by others. In case you need to copy family member anyway, be aware that Copy Design has to remove the member's link to the family.

Copying Members in an Assembly

As a best practice, do not copy Factory or Members when copying an Assembly. Doing so will break the links to the factory.

Copying iPart Factory

Derive a new iPart from an existing iPart Factory with the following workflow. This is essentially performing a Save Copy As.

  1. Copy iPart Factory.
  2. Edit Factory table.
  3. Rename members.
  4. Make modifications.
  5. Save Factory in up-to-date state.
  6. Generate new members.
  7. Check-in.

Copying iAssembly Factory

Use these practices when copying an iAssembly Factory.

Bottom Up Approach

  • iParts first
  • Nested iAssemblies

Copy iParts Factory separately

  • Regenerate members with new file names.

Copy iAssembly

  • Replace with new iParts/iAssembly members during Copy Design.
  • Regenerate Members with new File Names.

Was this information helpful?