CapitalKnowledge

Capital Harness Designer Modular > Capital Harness Designer Modular Application Interface

Nested Production Module

Codes Overview

To manufacture a harness, you can define production modules to create assemblies and sub‑assemblies that can be pre-assembled before they are combined into the final harness.

You can use the PM Module Browser to create a hierarchy of the production modules to match the physical structure of the assemblies and the dependent sub‑assemblies required to manufacture the sections of the harness.

Example Nested Production Modules

A typical manufacturing methodology involves the creation of sections of the harness as production modules that are then combined with other components in a final assembly operation to complete the final harness.

In the following example, the section of the harness includes bundles with connectors C‑11, C‑14, and C‑15, which are grouped under the production module code of the parent bundle (C‑14).

Figure 388: PM1 Containing Three Bundles

All the components are part of the same production module code PM1; however, the bundles connected to C-11 and C15 are also defined as individual production modules (sub-modules):

  • C-14 bundle (parent bundle PM1)

  • C-15 bundle (PM2)

  • C-11 bundle (PM3)

The bundles will be manufactured in the following order to complete the section of the harness:

  • PM3

  • PM2 (assembled with PM3)

  • PM1 (assembled with the combined PM2 + PM3)

In the design, you can create a folder tree of the nested PM codes in the PM Module Browser, to match the manufacturing hierarchy and dependencies of the PM codes. See Using Nested Production Modules.

Figure 389: Nested Production Modules in the PM Module Browser

Production Technical Variations

If you generate Production Technical Variant codes from a top-level parent PM code, the codes are displayed nested under the parent PM code in the folder tree.

Restriction

You cannot generate Production Technical Variant codes on nested PM codes. You must generate variants from the top-level parent PM code to ensure that all the PM codes in the folder tree are considered when calculating the variants.

Figure 390: Production Technical Variant Codes in the PM Module Browser

In a Production Technical Variant Code generated for a nested production module, the source PM code for a component is displayed in parentheses next to its name.

Figure 391: Source PM Codes for Components in Technical Variant Code Shown in Parentheses

Mapping

PM Codes and Modular Breakdown

When you map production modules to automatically generate module designs, the system creates the designs based on the selected PM code and includes the design data associated with any nested PM codes and Production Technical Variant codes.

When you run modular breakdown on a design based on a parent PM code, the system creates diagrams which include the design data associated with any nested PM codes and Production Technical Variant codes.

Note

The Applicable PM Codes field in the Edit Design dialog box is only updated with the applicable codes after you run modular breakdown. See also New Harness Design Dialog Box.

Parent Topic:

Capital Harness Designer Modular Application Interface

Related Topics

  • Automatically Creating Module Designs from Module Codes

  • Generating Production Technical Variations

  • Modular Breakdown

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens

Source: https://docs.sw.siemens.com/en-US/doc/861057055/202410078.capital_hd_user/id0c638df3-4476-4e92-844c-19a665ad14dc · retrieved 2026-07-18