Topology- and Topology Group Specification
Note: There is a newer version of this specification see VEC 2.0.2
A TopologySpecification is a container for various TopologyNodes, TopologySegments and Zones. A TopologyNode represents an abstract place (meaning without concrete coordinates) in the wiring harness that can be typed either as EndNode, JunctionPoint or Inliner.
A TopologySegment represents a section of a wiring harness where no intermediate electrical contacts appear. In consequence, at the beginning and at the end of a TopologySegment the same wires go in and out. The beginning and the end are each defined by a dedicated reference to a TopologyNode. A TopologySegment can specify various SegmentCrossSectionAreas. These SegmentCrossSectionAreas are not supposed to express configuration-dependant values but different views (Calculated, Measured or Estimated) on the same type-dependant value whereupon the default-type is “reserved design space”. The same applies to SegmentLength.
In contrast to GEO 1.0 the VEC recognises an explicit grouping mechanism for topology. For this the VEC has introduced the class TopologyGroupSpecification which primary acts as a “normal” TopologySpecification being a container for various TopologyNodes, TopologySegments . However, a TopologyGroupSpecification can additionally reference the TopologySpecifications that it groups.
In some cases, a topology can be an instance of another topology. If a more complex assembly or small harness (e.g. like a door) is defined in some place (e.g. in a component library) and then reused elsewhere it might be necessary to instantiate the topology in the target. To keep traceability in these cases, the TopologySegment and the TopologyNode have an instantiated... association to their source element.