Module Relationships Report

You can query and report on the relationships between module codes, especially any Mandatory relationships that have been defined. You can also identify related codes in the same code space (codes that contain inclusive or technical module codes), or in different spaces (production module codes that correspond to the selected set of functional module codes) and highlight the types of relationship between them.

Figure 404: Module Relationships: Same Code Space

In Figure 404, a module with a higher specification stereo unit (FM9) still contains the same power wiring (FM8) as a standard stereo. Therefore, FM8 will be included as it has an inclusive relationship with FM9. So where an optional higher specification stereo is selected by a customer and this order is forwarded to the harness manufacturer, the manufacturer will be able to easily identify all required modules to fulfill the order.

Based on the selected source module code the report also identifies which technical module codes are required and the reasons for their inclusion. In the example, the system has analyzed the code relationships for the user selected code FM1 and automatically added technical module code TFM33 to satisfy the set. The reason being TFM33 has an inclusive relationship with FM1. This mapping information is especially useful in identifying links between the original specification of module content and the “real world” content, which will actually be manufactured.

Clicking the Required PM Codes tab reports on the relationships between functional modules and corresponding sets of production modules.

On occasion, after Required FM/PM codes are selected one of the following warning messages may be displayed:

• A solution was found but some codes required to satisfy the input bring in additional content This may be displayed where functional module codes do not map exactly in a 1:1 relationship with production module codes. This could be where production codes contain more than one functional code due to predefined inclusive relationships and the practicalities of manufacturing. For example, a stereo (FM8) and its wires (FM10) have an inclusive relationship and will always be built together in the production scenario—they could both be tagged PM1. Selecting to report only on FM8 will also bring in the additional content FM10 and will be duly reported as such.

• No solution, the following source codes are assigned to components that have no target space code This may be displayed where functional module codes exist without corresponding production module codes assigned.

The following topics are available:

• Generating Module Reports

Parent Topic:

Capital Harness Designer Modular

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens