Traceability of Components

For some use cases (e.g. virtual validation) it is essential to know for a component box, which components (e.g. fuse) are used together with which wire. In a 100% harness variant, this information can be derived completely from the information available for a component box, the component box connections, the mounted components and the connected harness connectors.

However, in a 150% harness variant, this is not possible. Such an example is illustrated in the diagram. A Component_slot has two variant dependent mounted fuses (Var Y & Var Z). The Component_slot is internally connected with two cavities of a Component_box_connector. The connector on the component box has a coupled harness connector with two cavities and three variant dependent wires (Var A, Var B, Var C). To derive which fuse applies to a wire, the variant conditions (associated modules) of all participants would have to be evaluated. In a scenario where the fuses and the wire were controlled by the same modules, this would be feasible. In a scenario where the fuses and the wires were controlled by different modules (e.g. the fuse by a "base" module and the wires by different "feature" modules for the same base) this results in wrong conclusions. To derive the information correctly, the logistic control information (e.g. boolean logic) would have to be evaluated. For a "simple" wire / fuse validation tool, this would be far beyond the scope and in some cases not even manageable with the available information.

However, in the process the variants conditions for the components are derived from a specific selection (e.g. a fuse for a specific wire) and then, later, optimized. In order to allow e.g. validation use cases, the KBL shall preserve this specific selection information.

To fulfill this feature, the KBL 2.5 introduces an association between Component_pin_map (the representation of a specific pin) and the Contact_point. The semantics is defined as "the pin of this specific component is applicable for all wires attached to the referenced Contact_point(s).