Assembly Split in CATIA: How to Separate a Product

How-to basics · Updated November 22, 2026

Yes. In CATIA, you can split an assembly by reorganizing its components into separate CATProduct documents or subassemblies, but “Split” is not usually a single command that automatically divides a whole assembly. If you mean the Part Design Split feature, that cuts a part’s geometry; it does not divide an assembly structure.

What “assembly split” means in CATIA

CATIA uses a product structure to represent assemblies. A CATProduct document can contain component instances, other CATProduct subassemblies, and CATPart components. Each instance points to a component document, while the product tree records how components are grouped and how they relate at that level. Consequently, splitting an assembly can mean several different things:

  • Make subassemblies: group selected components under a new product in the existing top-level assembly.
  • Create separate assembly files: place selected components in another CATProduct so that it can be opened and managed independently.
  • Divide the geometry: cut a solid or surface into pieces. This is a part-design operation, not a product-structure change.
  • Divide work for different teams: separate design ownership, release packages, or supplier data while controlling which references remain shared.

Before changing anything, decide which result you need. A nested subassembly is still part of the larger assembly; a separate CATProduct is a separate document, but it may still refer to the same underlying CATPart files. Those are useful but different outcomes.

How CATIA represents an assembly

In CATIA V5, a CATProduct is generally the document that holds assembly structure, component instances, and assembly-level relationships. A CATPart holds part geometry and its part features. A component shown in a product tree is often an instance of a document, rather than a self-contained duplicate of its geometry. The same CATPart can therefore be used in multiple places or products.

This distinction matters when separating an assembly. Creating a new product and adding existing components usually creates references to their existing documents; it does not automatically make independent copies of every part. Changes made to a shared CATPart can affect every product that references that file. Conversely, copying part files to a new location and relinking a product creates a different data-management situation that needs careful checking.

Constraints are also associated with the product level where they were created. If you move components into a new subassembly or recreate them in another product, do not assume that all original constraints will follow automatically. The tree, component links, placements, and constraint relationships each need to be considered.

Choose the right kind of split

For a cleaner tree but one coordinated design, create a subassembly inside the top-level product. For a deliverable that can be opened as its own assembly, create a separate CATProduct. If the purpose is to provide a supplier with geometry, consider whether the supplier should receive editable CATParts, neutral-format geometry, or another approved deliverable; simply making another CATProduct may leave references to files they do not have.

Use the intended downstream workflow to guide the choice. A manufacturing team may need stable component identities and assembly constraints. A layout review may need only the arrangement and simplified geometry. A release or supplier package may require controlled copies, renamed documents, or neutral exports. CATIA configuration, company procedures, and data-management systems can affect the appropriate method, so confirm those requirements before breaking links or changing file locations.

Prepare a safe working copy

Save a separate working copy before restructuring a released or important assembly. In CATIA V5, use the normal save workflow for the documents involved; when several linked files need to be renamed or relocated together, review the available Save Management options rather than assuming that saving only the top-level CATProduct copies every dependency. Exact dialogs and available commands can vary with release, configuration, and how files are managed.

Before editing, make a short inventory of the intended split:

  • List the components that belong in each new group, including repeated instances.
  • Identify the top-level product and any existing subassemblies that should remain intact.
  • Note which components are shared by more than one group.
  • Record important constraints, reference geometry, and external links that must continue to work.
  • Decide whether the new product should reference original part files or use independent copies.

This preparation prevents a common mistake: treating a visual selection in the tree as proof that all required documents and relationships have been captured.

Create a subassembly within the existing product

For a structural reorganization, the usual goal is to make a new product beneath the existing top-level product and place the intended component instances within it. In CATIA V5 Assembly Design, a new product can generally be created through Insert > New Product. Command availability and wording may differ in other CATIA releases or workbenches.

  1. Open the assembly and save the working copy.
  2. Select the top-level product in the specification tree, then create a new product using the available New Product command.
  3. Give the new product a meaningful name that describes its function or contents.
  4. Move or place the intended component instances under the new product using the tree-editing method supported by your CATIA version and company setup.
  5. Inspect the tree and update or recreate constraints at the appropriate product level.
  6. Update the product and check for unresolved links, unexpected movement, or broken constraints.

Do not delete the original instances merely because the new product appears in the tree. First confirm that the components are represented correctly in the new group and that the assembly still updates as expected. Moving existing instances within a product structure is not the same operation as creating a fresh set of instances, and the exact result can depend on how the edit is performed.

Make a separate CATProduct assembly

To produce a separate assembly document, create a new CATProduct with File > New and choose Product, or use the equivalent product-creation workflow available in your installation. In CATIA V5, the new product can be populated with existing components through Insert > Existing Component. The command is intended to add existing product or part documents; it does not by itself guarantee that the original assembly’s complete constraint scheme will be copied.

A cautious workflow is to add the required existing components, arrange or constrain them in the new product, then save and reopen the new CATProduct to confirm its references resolve. If the components must keep their exact relationships from the source assembly, consider whether an existing subassembly can be retained as a component instead of rebuilding the group from individual parts. Keeping the existing subassembly can preserve its internal organization, but it may also retain links and dependencies that you intended to separate.

For example, suppose a machine assembly contains a motor, coupling, and pump mounted together, plus a frame and guard. A service team might need the motor-coupling-pump group as a separate service assembly. Creating a subassembly can make the tree easier to understand while keeping the group inside the machine product. A separate CATProduct can make the group independently accessible, but its mounting position relative to the frame belongs to the larger assembly and may need to be represented or documented separately.

References, constraints, and independent copies

Three checks are especially important after a split. First, verify document references: does the new product point to the intended CATPart and CATProduct files? Second, verify placement: are components positioned correctly in the new assembly, and are required constraints present and satisfied? Third, verify ownership: should changes to a part in the new assembly also affect the original product?

If both assemblies should use the same design definition, shared references may be appropriate. If they must evolve independently, merely saving another CATProduct is not enough; you may need copies of the relevant component documents and a deliberate relinking process. Use your organization’s approved CATIA data-management procedure where applicable. Copying files outside that process can leave duplicate names, broken references, or uncertainty about which file is authoritative.

After restructuring, update the product and examine the tree for missing-document indicators or other warnings. Reopen the saved product in a clean session if practical, especially before sending it to someone else. A product that looks correct while the source documents remain open may still fail when transferred to a machine or folder that lacks its referenced files.

CATIA Split versus Part Design Split

The word “Split” can cause confusion because CATIA also uses Split for geometry operations. In Part Design, a Split feature uses a cutting element, such as a plane or surface, to divide or trim a body according to the selected side and feature settings. That changes the part’s geometric feature history. It does not create a new CATProduct, move components in the specification tree, or separate assembly constraints.

Use a Part Design Split when the task is to modify a solid or surface within a part. Use product-structure editing when the task is to group, move, or separate assembly components. If you need two physical parts from one solid, a geometric split may be only one stage: you may also need to create or manage separate part documents, depending on the design intent and release workflow.

Common problems and how to avoid them

  • The new product opens with missing components. Its references may point to files outside the transferred folder or to paths unavailable on the receiving computer. Use the approved link and packaging workflow and test the saved deliverable.
  • Components are present but not constrained as expected. Constraints may have belonged to the original product level. Recreate or retain the required relationships, then update and inspect the result.
  • Changes appear in both assemblies. The products may reference the same CATPart documents. That can be intended; if independent editing is required, arrange separate part copies and links.
  • The tree is reorganized but the model behaves differently. A change in product hierarchy can affect where assembly relationships are managed. Compare placements and constraint status rather than relying only on the displayed tree.
  • A user expects one automatic “split assembly” button. Product restructuring is not the same as a geometric Split feature. Choose the operation based on whether the target is the assembly tree, the file structure, or part geometry.

Frequently Asked Questions

Does CATIA have a Split Assembly command?
There is not one universal command that automatically divides an entire assembly into independent assemblies. In CATIA V5, the typical approach is to create or reorganize products and manage component references, using commands such as New Product and Existing Component where appropriate.

How do I make a subassembly in CATIA V5?
Create a new product beneath the appropriate top-level product, then place the intended component instances within it using the tree-editing method supported by your version. Check constraints and update the assembly afterward; do not assume every relationship transfers automatically.

Will splitting an assembly duplicate its CATPart files?
No, not necessarily. Adding existing components to another CATProduct commonly references existing documents. To make independently editable copies, copy and relink the relevant part documents through a controlled workflow.

Are assembly Split and Part Design Split the same thing?
No. Part Design Split modifies part geometry using a cutting element. Separating an assembly means changing product organization, component references, or both.

Can I send the new CATProduct to someone as a standalone file?
Only if its referenced CATProduct and CATPart documents are also available to the recipient, or the assembly has been packaged or converted according to the required delivery process. Reopen and check the deliverable from its final location before sending it.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.