Segment
Note: There is a newer version of this specification see KBL 2.5.sr1
A Segment is a distance in the Topology where no intermediate electrical contacts appear. If a Topology contains routed wires, then the wires at the beginning of a Segment have to be the same as in the ending. Every segment has its conditions like length, temperature range, etc.
Segments are a logical construct to describe the physical representation of a wiring harness topology. Therefore a segment is only valid if it has a physical manifestation. Segments with a length of 0 or less do not have a physical manifestation and are therefore not valid.
Additionally the usage of segments with a length of 0 create problems in the overall process. For example the synchronization of 3D / 2D systems becomes harder or even impossible and the handling of wire protections on those segments is also unclear.
General Information
| Attribute | Value |
|---|---|
| Owner | 5_Topology |
| Applied Stereotype | |
| Base Classifier | Changed_element |
| Is Abstract | false |
| Derived Classifiers |
Attributes
| Name | Type | Mult. | Description | Owning Classifier |
|---|---|---|---|---|
| Id | String | 1 | The id specifies the identifier of the Segment. |
Segment |
| Alias_id | Alias_identification | 0..* | The alias_id specifies additional identifiers for the Segment. Example: Segement Ids may vary from one CAD system export to another. Therefore the CAD system Id is improper for Id attribute. Id shall have a value which is unique within the harness. Alias_id may be used for the CAD system Id. |
Segment |
| Start_vector | Double | 0..3 | The start_vector specifies the tangent of the center curve at the start position. Note: The value can be derived from the center_curve. To avoid that the receiving system has to calculate the value, it can be explicitly specified. |
Segment |
| End_vector | Double | 0..3 | The end_vector specifies the tangent of the center curve at the end position. Note: The value can be derived from the center_curve. To avoid that the receiving system has to calculate the value, it can be explicitly specified. |
Segment |
| Virtual_length | Numerical_value | 0..1 | A designed (virtual) length means that the value is derived automatically in a CAD Tool (e.g. from a 3D Geometry). |
Segment |
| Physical_length | Numerical_value | 0..1 | An adapted (physical) length means that the value is not the exact value taken from the CAD tool, but is adapted in some way. Adapted values are supposed for further use in the process, especially as basis for the product specification. Adapted values are normally created for example by rounding the designed values. |
Segment |
| Form | Segment_form | 0..1 | The form specifies information on the geometric shape of the Segment. The following values shall be used: - ‘circular’ - ’noncircular’ |
Segment |
Outgoing Relations
| Type | Role | Mult. | Mult. | Description |
|---|---|---|---|---|
| B_spline_curve | Center_curve | 0..* | 1 | |
| Node | End_node | 1 | 0..* | |
| Cross_section_area | Cross_section_area_information | 0..* | 1 | |
| Processing_instruction | Processing_information | 0..* | 1 | |
| Fixing_assignment | Fixing_assignment | 0..* | 1 | |
| Node | Start_node | 1 | 0..* | |
| Protection_area | Protection_area | 0..* | 1 |
Incoming Relations
| Type | Mult. | Role | Mult. | Description |
|---|---|---|---|---|
| Node | Folding_direction | 0..1 | Defines the direction (Segment) in which this Node will be folded (see Description of Node). |
|
| Routing | 0..* | Mandatory_segments | 0..* | References a list of segments that are mandatory to be visited during the routing process. As a consequence the Segments determined by a routing algorithm shall contain these Mandatory_segments. |
| KBL_container | 1 | Segment | 0..* | |
| Dimension_specification | 0..* | Segments | 0..* | Defines an ordered list of segments along which the dimension specification is defined. |
| Routing | 0..* | Segments | 0..* | Represents the result of a routing algorithm. |