Creating Bundles and Harnesses

Capital Systems Integrator Harness Exchange

Original equipment manufacturers (OEMs) can exchange individual harnesses managed at platform level with suppliers. The exchanged data includes all placement, constraint and connectivity information, enabling wire synthesis to be completed on a single harness. The exchanged data does not include the associated logical designs or the library data (you must transfer both of these separately).

Why do this?

Reduce costs You can spread a single design among multiple suppliers in order to distribute the design cost.

You can design and cost harnesses individually as the data becomes available, meaning time is not wasted waiting for the full platform to be complete before costing can begin.

Multiple suppliers can cost the same harness.

Cost of re-work is reduced by changes being restricted to individual harnesses.

Flow for Capital Systems Integrator

Harness Exchange

Note

Although concurrent editing of a Capital Systems Integrator design can provide a productive environment for an OEM and its suppliers to develop vehicle wiring, it is not always feasible (or even desirable) for all the organizations to work within the same network and Capital installation. The steps outlined here, show how the work may be distributed to individuals working within their own Capital environment, by exchanging harness data between Capital Systems Integrator designs.

The OEM synthesizes the full vehicle to determine the initial vehicle wiring and inline interfaces: The OEM prepares the vehicle data as for a standard generative process.

The system designs are created and associated with the Capital Systems Integrator design.

Within Capital Systems Integrator, the topology is prepared (possibly by bridging data from MCAD), the devices and grounds are placed, and then an initial synthesis is performed. Note This synthesis is important because it defines the signals passing through each inline pair - in other words, the interfaces between the harness families.

The OEM exports harnesses and distributes these, together with the latest system designs, to the harness suppliers. Note It is important that the suppliers have a compatible project and Capital Systems Integrator design ready to receive the data.
Each supplier imports their harnesses into the empty Capital Systems Integrator design: The import creates an identical topology with all its bundles and slots.

Inlines are imported as interface connectors (with the required signals defined for each cavity).

Logical devices are placed automatically as they were in the OEM’s design.

					Note 
						The Import Harness action does not support specialized connectors.

Each supplier refines the topology, placement and wiring as required. You can make almost any modification. Wiring synthesis (such as, Modular Wiring Synthesis or Composite Wiring Synthesis) can also be performed, but this is limited to the harnesses with the supplier’s design rather than the scope of the full vehicle.
Each supplier exports modified harnesses and returns them to the OEM for incorporation.
The OEM updates the master design with changes from each supplier and ensures compatibility. All the changes from the supplier are imported. The OEM is able to view this data in the full vehicle context, as well as to run validation such as design rule checks or the Design Assistant.
You can exchange further modifications to the data in either direction. The OEM can provide new revisions of the system designs and can also distribute new harness data if, for example, changes are needed at the inline connector interfaces. The suppliers can also continue to modify their own harness data and provide updates to the OEMs as required.

Harness Sets

When you export multiple harnesses, you have the option to export them as a harness set. If you do this, they are exported as a set in a ZIP file that contains an XML file for each harness.

When importing harnesses, you can import one of these ZIP files. The system scans the contents of the ZIP file looking for harness names and compares them with the harness names on the design.

If there are matching names (and the harnesses are locked), the system allows you to select one matching harness to replace (that is, overwrite the harness in the design with the incoming data).

For example:

If you have a source design with harnesses A, B, C and you export them as a harness set, a ZIP file is created containing three XML files (one for each harness). If you then import this set into a design containing harnesses B, C and D, the import offers you the option of overwriting B or C only. You can select only one of those. If you wanted to import both, you would have to repeat the import process.

If you want to import a harness set into a blank diagram, unzip the XML files and import them individually. The system does not support the import of multiple harness XML files in a single operation (that is, the complete contents of a harness set in one go) because there are difficulties analyzing the impact of import failures on later operations.

Parent Topic:

Creating Bundles and Harnesses