Promotion of

Options in Mandatory Option Folders

During wiring synthesis, the system may promote an option in a mandatory option folder to a harness. A project preference controls whether the system automatically promotes other options in that folder to the harness.

The preference is called Mandatory options must be explicitly specified as supported in harness levels. See “Project Preferences for Capital Systems Integrator Designs” in the Capital Design User - Common Functions User Guide.

Figure 153: Mandatory Options Project Preference

Behavior with Preference Not Selected

Note

Standard behavior prior to release 2018.1 and default setting for projects created before 2018.1

If the preference is not selected, the system does not promote the other options in the mandatory option folder.

When an option is not promoted to a harness, the system regards the harness as independent of that option. This means, the levels of the harness can be used in configurations that do support the option and in configurations that do not.

For example, options LHD and RHD are in a mandatory mutually exclusive option folder. Wiring synthesis promotes RHD to harness H1 but does not promote LHD. As a consequence:

• A configuration that supports RHD must use one of the levels of H1 that supports RHD.

• A configuration that supports LHD can use any level of H1 regardless of whether it supports RHD.

Behavior

with Preference Selected

Note

Default setting for a new project

If the preference is selected, when one or more options in a mandatory option folder are promoted to a harness, the system considers the remaining options from that folder as unsupported by all levels of that harness. A configuration supporting only the unpromoted options will not include any level from that harness.

If this is not what is expected, additional options must be promoted to the harness. To do this, you can either:

• Run wiring synthesis with the “Update Harness Options” action that recognizes when additional options from the mandatory options folder should be promoted to a harness and does so.

• Import harness levels from outside Capital so that the import redefines the options affecting the harness. When using an import, it is the responsibility of the tool or person creating the harness definitions to ensure that the additional options are included.

Consider the same example as above where options LHD and RHD are in a mandatory mutually exclusive option folder. Wiring synthesis promotes RHD to harness H1 but does not promote LHD. As a consequence:

• A configuration that supports RHD must use one of the levels of H1 that supports RHD (same as above).

• A configuration that supports LHD will not contain any level from H1.

• If there are any levels of H1 not supporting RHD, these represent an error condition because they support neither LHD nor RHD.

For a detailed, real-world example, consider a harness for a rear door of a car. There may be various devices for controlling the window, door, and audio. They will all be conditional on this being a 4-door vehicle and so may reference option 4-DOOR. It is quite likely that none of the option expressions affecting the wiring of the rear door harness will reference the corresponding option 2-DOOR. However, a rear door harness is clearly not present in a 2-door car. With the preference setting on, once the harness identifies 4-DOOR as an option affecting the harness, it is implicit that the harness is not present in a configuration supporting 2-DOOR, provided 2-DOOR and 4-DOOR are in a mandatory mutually exclusive folder.

Then consider a harness for the right front door of a car. For an RHD vehicle, the right front door is the driver’s door. There may therefore be some wiring that is present only for RHD. It is possible that the equipment and wiring of the front passenger door is a strict subset of that in the driver’s door. If that were the case, there will be no reference to LHD. However, a front right door harness is needed in an LHD vehicle. With the preference setting on, Update Harness Options will recognize this situation and will add LHD as an option affecting the harness.

An alternative mechanism to achieve the same result is to have distinct vehicle models for options that have major effects on the vehicle, such as changing the set of harnesses present in the vehicle. That approach is still available but this preference provides an alternative for those who want fewer vehicle models.

Caution

If this preference is selected for a design created prior to 2018.1, you will need to update both the options recorded as affecting a harness and the harness levels to prevent loss of wiring.

If you export and import designs between projects that have this preference set differently, wiring synthesis will produce different results in the target project from those seen in the original project.

Parent Topic:

Option Folder

Capital Systems Integrator User Guide, 2512.2606

Unpublished work. © 2026 Siemens