Capital Harness Designer Modular > Capital Harness Designer Modular Harness Processing

Modular Breakdown

This routine creates child designs from a parent harness, generating harness objects in the child designs based on the module codes applied to them in the parent.

This includes terminal assignation which resolves instances where there may appear to be multiple terminals assigned to a single wire. The modular workflow uses this method rather than using the Cavity Component Management action. If this action is performed on a modular harness and multiple cavity terminal / seal data is found, legitimate modular harness data can be incorrectly removed. In this scenario, the system displays a warning message. See also Cavity Component Management.

The Module Breakdown procedure is only available if a modular harness has been selected for processing. If functional modules designs already exist for the parent, any content in those designs is deleted and regenerated, when the process is initiated.

The ability to run module breakdown on a design may depend on its release level, and the behaviors assigned to that release level in Capital Project Manager. See also the Capital Project Manager User Guide.

Running the Modular Breakdown process creates a design log file detailing the results of the process, as well as any warnings or errors that may have occurred. By inspecting these design logs, you can investigate the causes of any problems encountered. See also “Design Logs” in the Capital Design Tools - Common Functions User Guide.

Not-on-BOM Reference Components

Where an additional component is assigned to a module that is different from its parent main node component, modular breakdown includes the additional component on its target design by also placing its parent object on the design as a not-on-BOM “reference” component.

As a “reference” component, its “Included On BOM” attribute is cleared, meaning that it is ignored when generating any Modifying the Bill of Materials. This applies to all components that can have a module code assigned to them that is different to the one assigned to their parent component.

Modular

				Breakdown Options

Where Technical Module codes exist, the system uses the following hierarchy for performing module breakdown and engineering checks:

User specified Technical Module Codes
System generated Technical Module Codes
User specified Module Codes
System generated Modules Codes

In addition to the core actions required to perform a modular harness breakdown, the following optional actions are available for selection from the Modular Breakdown screen of the Harness Processing Dialog Box:

Remove Breakout Tape From Non-Junctions?

Removes unnecessary breakout tape. For example, a parent harness may have a junction with three or more branches, and a child harness may have only two because of component distribution, and might not require breakout tape.

Merge Bundles and Identical Insulations

If a junction is removed on a child module so that there are only two bundles remaining, the system deletes the junction node and merges the bundles together, replacing the node with a grip point. If the bundles have identical insulation runs these also will be merged into one. Project Preference Settings Use the following Project Preference settings to configure additional actions. “Check Properties and Values when Merging Bundles” enables you to specify if bundles that have properties defined against them can be merged. See Automatic Bundle Merging for usage examples. You can refine the preference further using the following project preferences: “Properties Excluded from Bundle Merge Property Check” — Use to specify properties that, if present on bundles, will be excluded from the “Check Properties and Values when Merging Bundles” check.

“Properties that Block Bundle Merge” — Use to specify properties that, if present on bundles, will prevent bundles being merged.

“Check Properties and Values on Insulation Runs and Layers when Merging Insulation Runs” enables you to specify if insulation runs / layers that have properties defined against them can be merged. See Automatic Bundle Merging for usage examples. You can refine the preference further using the following project preferences: “Properties Excluded from Insulation Run Merge Property Check” — Use to specify properties that, if present on insulation runs / layers, will be excluded from the “Check Properties and Values when Merging Insulation Runs” check.

“Properties that Block Insulation Run Merge” — Use to specify properties that, if present on insulation runs / layers, will prevent the runs being merged.

“Merge Bundles and Insulation Runs if Dimension Exists at Optional Node” controls whether or not to merge bundles and insulation runs where a dimension start or end point exists at a node that could potentially be removed.

“Merge insulation run within specified distance from junction” — enables you to configure a tolerance, to allow insulation runs that are offset from a junction to also be considered for merging. If two insulation run ends are offset at a distance equal to or less than the defined tolerance, the composite / modular breakdown process considers them as merge candidates, and merges them if all other conditions are satisfied.

“Delete spot tapes within a certain distance from junctions of merged insulation” — enables you to configure a tolerance to control spot tape deletion. Where insulation runs are merged, any spot tapes that are placed at a distance from the junction node that is equal to or less than the defined tolerance are removed by the composite / modular breakdown process. Note Spot Tapes within the tolerance, that are placed on other objects, are not deleted. Spot tapes that are within the tolerance, but beyond the ends of the merged insulation run, are not deleted.

Remove Splices With 2 Identical Wires?

Removes any splice where only two wires remain and where the wires are identical in color, material, and spec. The splice is replaced with one wire with that color, material, and spec.

Generate Replacement Wire Names?

Renames any wires inserted as a result of the application of the Remove splices with 2 identical wires? option, using the prefix SPL- followed by an incrementing number.

Select Cavity Components

Reselects cavity component part numbers for each child module, overriding any automatic selections made on the parent design. Terminals/Seals Stay With Wires (not Connectors) Where a connector and wire are in different modules: With this option selected, the process breaks down the terminals into the module containing the associated wire ends.

With this option cleared, the process breaks down the terminals into the module containing the associated connectors. This is typical of an aerospace type flow where the terminals are loose and are fitted with the connectors.

Optimize Splice Positions

Performs splice repositioning on each module being processed. Analyzes each splice on the module marked as “Repositionable” and relocating it to its optimal position, subject to any rules and constraints associated to the design.

Ignore Diagram Protection

Cleared by default Selected, modular breakdown deletes all the diagrams of each selected child design (regardless of their protection status), and recreates them from your chosen parent “Reference Diagrams”. Any manual layout modifications you have made are lost. See Preserving Changes Made to Derivative and Module Diagrams. The protected status of the diagram is not changed.

Apply Skeletal Styling

Cleared by default. Applies a minimal, skeletal style to the diagrams produced during harness processing. This is useful where you are not concerned with the appearance of the child diagrams, and it can significantly reduce the time taken to process the design where complex style sets are used. See Skeletal Styling.

Assemblies

Based on their module codes, the modular breakdown process:

Adds any Assemblies (and their constituent components) to all child designs and sets their Included On BOM attribute, see Figure 416 (Edit Assembly Dialog Box), according to the set of rules described in the “Assembly Breakdown Examples”.

Figure 416: Included On BOM

The assemblies on the child designs are tagged with the relevant module code(s). Figure 417 shows the Edit Assemblies dialog box.

Figure 417: Code

The components that are present in the assembly on the child design are tagged with the relevant module codes, and the Assembly attribute is populated with the assembly name. Figure 418 shows this on the Edit Connector Dialog Box.

Figure 418: Assembly Attribute Setting

Assembly Breakdown Example 1

A component that is part of an assembly is assigned to a module and its assembly is not assigned to that module.

Post modular breakdown result:

The system automatically populates the child module design with the assembly.
The assembly is present as a reference object only. Its Included On BOM attribute is not set (cleared).

Assembly Breakdown Example 2

A component that is part of an assembly is assigned to a module and its assembly is also assigned to that module.

Post modular breakdown result:

The system automatically populates the module design with the assembly.
The assembly is present as a valid BOM item. Its Included On BOM attribute is set (selected).

Assembly Breakdown Example 3

A component that is part of an assembly is assigned to a Production Module (PM) parent and its assembly is not assigned to that PM parent.

Post modular breakdown result for all related Production Module Variant (PMV) designs:

The system automatically populates the PMV design with the assembly.
The assembly is present as a reference object. Its Included On BOM attribute is not set (cleared).

Assembly Breakdown Example 4

A component that is part of an assembly is assigned to a PM parent and its assembly is also assigned to that PM parent.

Post modular breakdown result for all related PMV designs:

The system automatically populates the PMV design with the assembly.
The assembly is present as a valid BOM item. Its Included On BOM attribute is set (selected).

Module Design Type	Assembly Assigned to Design?	Assembly Assigned a PM Parent Code and Child is Variant of Same Parent	Assembly on BOM?
Standard	Yes	N/A	Yes
Standard	No	N/A	No
Technical	Yes	N/A	Yes
Technical	No	N/A	Yes
TVPM	No	Yes	Yes
TVPM	No	No	No

Parent Topic:

Capital Harness Designer Modular Harness Processing