Unbuildable

Option Combinations Attached to Design

Configuration generation builds configurations based on the defined physical harness levels. A level is often required to be part of multiple configurations in order that every one of the options it supports is ‘active’ in at least one configuration. However, in some cases Capital Systems Integrator will attempt to build a combination of options that is not actually required (this is particularly common where a level supports multiple vehicle models). If this combination is not possible to build, based on the harness level definitions, it will result in unnecessary warnings.

The warnings have the form:

Warning: The Configurations for Vehicle Model {0} are unable to support Option {1} from Level {2} of Harness {3}

In order to assist configuration generation and avoid these warnings, you may provide a set of unbuildable option combinations for one or more vehicle models. This data must be attached to the design using the API to create IXAttachedData. A reference document describing attached data access is available. Refer to the document AttachedDataAccessGuide.pdf in the \doc\plugin directory of your Capital installation.

The attached data must be in comma-separated format and takes the following form:

Copy

Vehicle models,vm1,vm2,...
Options,opt1,opt2,...
Options,opt3,opt4,opt5...

Each vehicle models row identifies the vehicle models for which the following unbuildable option combinations apply.

Each options row identifies a combination of options that are not required to be built for the previous vehicle model(s).

If different vehicle models have different unbuildable option combinations, there can be several sections like this.

Usage Example

Here is a relatively simple example using an Options and Levels report for a design.

There are two sets of mandatory, mutually-exclusive options:

• Option folder A with options A1, A2, A3

• Option folder B with options B1, B2, B3

Figure 154: Options Table from Options and Levels Report

The vehicle models and harness levels are:

Figure 155: Vehicle Models and Harness Levels

In harness H2, level H2L2 supports both vehicle models vm1 and vm2. The options in those vehicle models are mandatory and mutually-exclusive so the system assumes that H2L2 needs to support all the combinations of those.

Vehicle model vm1 supports A1, A2, B1, B2, B3. The system therefore assumes that, for vm1, the level H2L2 needs to support A2 with B1, A2 with B2, A2 with B3. This is because they are all supported by the vehicle model and that harness level supports them all.

For vm2, the system assumes that H2L2 must support A3 with B1, A3 with B2, A3 with B3.

If you look at harness H1, there is no level that supports A2 with B1. This is because A2 with B1 is an invalid configuration of this vehicle so that combination will never be built. However, in harness H2, it looks like level H2L2 supports A2 with B1.

As a result, when Capital Systems Integrator generates configurations (Generate Vehicle Configurations action in wiring synthesis), it tries to create a configuration that supports A2 with B1. It can select a level from harness H2 for this but cannot select a level from harness H1. The system therefore displays an error message.

Figure 156: Unbuildable Options Error

You do not intend to use level H2L2 in a vehicle that supports A2 with B1. You intend to use it in a vehicle that supports A2 with B2, A2 with B3, A3 with B1, A2 with B2, or A3 with B3. Level H2L2 supports B1 only because it is needed for vm2.

You want to specify that A2 with B1 is an invalid combination (unbuildable). You cannot do this when specifying harness levels in Capital Systems Integrator. You therefore use a plugin to attach data to the design that tells Capital Systems Integrator that A2 with B1 is unbuildable. The attached data (in a CSV file) looks like this:

Figure 157: Attached Data CSV File

Referencing this attached data, the configuration generation action recognizes that it does not need a configuration that supports A2 with B1 so does not create one. Therefore an error message is avoided.

Parent Topic:

Option Combination

Capital Systems Integrator User Guide, 2512.2606

Unpublished work. © 2026 Siemens