Merging Harnesses

You can merge harnesses in a Capital Systems Integrator diagram to form one harness.

Restrictions and Limitations

• If a harness has multiple instances, you cannot merge it with another harness by dragging a sliced bundle end. You must drag a non-sliced end. However, you can merge instances of the same harness to form one instance by dragging a sliced end to any place on the other instance.

• Deleting an inline pair which has sliced bundle instances directly connected to both sides will merge only the directly connected bundle instance from the incoming harness. The non-connected bundle instance from the incoming harness becomes a new harness, with merged properties and attributes, because a bundle cannot have more than two instances. For example, an incoming harness HR will be merged into a target harness HL. Figure 9: Sliced Bundles Example - Before Inline Deletion
  
  
  The connected HR bundle instance merges into HL. The remaining HR instance becomes a new harness. Figure 10: Sliced Bundles Example - After inline Deletion

Prerequisites

• The merge behavior is controlled by the Harness Merge Criteria project preferences. Those preferences allow you to control which harness is the incoming harness and which is the target harness that is retained after the merge. The preferences also control whether properties, rules, and constraints are merged from the incoming harness to the target harness. Ensure that you have set them as required. See Project

Preferences for Capital Systems Integrator Designs for descriptions of the project preferences.

• Consider whether you want to turn the Auto Harness Merge toggle on or off to control whether the Harness Merge Criteria project preferences are applied automatically during a harness merge or whether you are prompted to review the behavior during each merge. See Turn Auto Harness Merge On or Off in the Capital Design Tools - Common Functions User Guide.

Procedure

Either:

• Drag the bundle grip point at the end of one harness to a point on the other harness where you want to connect and merge them.

• Delete an inline pair that connects two harnesses.

Results

• The incoming harness or harnesses are merged with the target harness.

• The Main tab in the Output Window at the bottom of the application reports on the outcome of the merge. The target harness is hyperlinked. You can click the target harness link to highlight it in the diagram and in the Design Browser (Design tab).

• If you have selected to merge properties from the incoming harness with those on the target harness, this is done except where the target harness has a property of the same name already.

• If the incoming harnesses and target harness had different colors, the target harness color is retained for the merged harness. Note After the merge, you can protect the target harness color on the merged harness by using Exclude from Apply style or Fix Style functionality on the merged harness. See Apply Style or Excluding the Shapes

and Graphics of an Object Instance from Apply Style and Update Border in the Capital Diagram Styling User Guide.

• Mergeable attributes from the incoming harness are set on the target harness, unless the target harness already has a value for that attribute.

• If only one harness has a domain specified, the resulting harness has that domain. If both harnesses have domains, the domain from the target harness is used.

• Promoted options from the incoming harness are added to the target harness, unless the target harness has that option already.

• Giveaway options on the incoming harness are merged onto the target harness without affecting any existing giveaway options on the target harness. An option cannot appear in the giveaway of a harness more than once, so:

If a giveaway from the incoming harness already exists as part of a “Give Away With” group on the target harness, it is not added.

If any member of a giveaway group on the incoming harness already exists as part of a giveaway group or as a single giveaway on the target harness, the group is not added. If a giveaway group exists on the incoming harness with the same name as a giveaway group on the target harness, the group is renamed when added to the target harness. The renaming uses the format _ where is an integer generated to ensure that the name is unique within the harness.

• Harness levels from the incoming harness are replicated onto the target harness, unless the target harness already has a harness level that is equivalent.

If an equivalent level is found, the attributes and properties of the top-level harness level are replicated onto the equivalent top-level harness level on the target harness, without overwriting any existing properties or attributes. If no equivalent level is found, the harness level and all its children are replicated to the target harness. If the target harness already has a harness level with the same name as a level being replicated from the incoming harness, the replicated level is renamed using the format _ where is an integer.

• The part number from the target harness is retained.

Parent Topic:

Harness

Capital Systems Integrator User Guide, 2512.2606

Unpublished work. © 2026 Siemens