Functional

and Production Module Code Maintenance

A module code represents a feature or capability in a harness design. Module codes are used in expressions to convey the explicit inclusion of a module in a particular harness.

Functional Module Codes can be created either at system level, or at project level. If you create them at the system level, they are available to copy to any project. For information on creating Functional Module Codes at system level, see the Capital Project Manager User Guide.

Production Module Codes can only be created at project level. Once created for a project, a module may be applied to any of the designs created within that project. The modules applied to designs are known as “applicable module codes”.

Note

After you have created module codes for your project, you must make them applicable to the designs within that project, otherwise you will be unable to view them. A warning message is displayed explaining this.

To aid data management, you can import or export a project's module code list (including the relevant inclusive/exclusive relationships), as an XML file.

To define relationships between module codes:

• Define inclusive and exclusive relationships for individual module codes. At project level only.

• Group them within module code folders that allow you to specify whether the module codes in the folder are mutually exclusive (that is, none of the module codes within this folder can be selected together in a design) or mandatory (that is, at least one of the module codes within this folder must be selected in a design). At system or project level.

• Create module code combinations that allow you to specify valid selections of module codes. At project level only. Module code combinations and valid selections allow the representation of complex relationships between a group of otherwise unrelated modules by specifying their allowed combinations. Module code combinations reduce the allowable combinations of a set of options, which in turn helps to limit the potentially large number of harness levels that can be generated by the Composite Wiring Synthesis (CWS) procedure in Capital Systems Integrator. A module code combination is a collection of modules that have been arranged into specific, valid selections. For example: If no inclusive or exclusive relationships exist between the six module codes A, B, C, D, E, F, and they are all optional in a particular vehicle model, there are 65 possible combinations. To lower the complexity (or for other design reasons such as supply chain management), the six module codes can be selected in a combination and arranged to permit only the following permutations: (A, B, C, D, E, F)

(B, F)

(A)

(F)

Each of the four combinations of the original six modules is known as a valid selection (that is, there are only 4 valid selections in the module code combination).

The following considerations apply to module code combinations and valid selections:

• A module code can exist as outside of a module code combination or just as one module code combination (that is, not a multiple module code combinations).

• A module code combination does not have to include a valid selection if all module codes are selected.

• Within a module code combination, the only limitation on its valid selections is that they must conform to any inclusive/exclusive relationships between the module code.

• Creating a Functional or Production Folder at Project Level

• Creating a Functional, Production or Technical Module Code at Project Level

• Defining Inclusive and Exclusive Relationships for Module Codes

• Creating a Module Code Combination at Project Level

• Define Module Code Relationships - Examples

• Adding a Valid Selection to a Module Code Combination

• Deleting a Valid Selection from a Module Code Combination

• Deleting a Module Code

• Using Properties on Module Codes

Parent Topic:

Capital Harness Designer Modular

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens