Capital Harness

Classic Design Migration Overview

You can migrate (export/transfer) designs from Progress or Oracle installations of Capital Harness Classic into Oracle or Embedded installations of Capital. All design content and branch layout detail is retained.

The process has two stages:

• Premigrate — export the designs from the Capital Harness Classic installation as a package of associated files. Manifest XML — A configuration file, (in format 1.xml, 2.xml) that lists the target project and the relevant associated DSI and DXF files that have been selected for premigrating.

DSI — Contains harness detail information. One DSI file is created for each Capital Harness design. The following items of data are not included with the harness detail information: Capital Harness audit trail data and design change data — not supported by the DSI format.

Capital Harness multicore marker data — this functionality does not exist in Capital Harness Designer or Capital Harness Designer Modular.

DXF — An image file of the Capital Harness Classic designer diagram that you can open and view in Capital Harness Designer or Capital Harness Designer Modular, for reference purposes, when the migration is complete. One DXF file is created for each Capital Harness design.

• Migrate — Run the Capital Migrate tool from the Capital installation, to import the designs into a target project, where they can be opened in Capital Harness Designer or Capital Harness Designer Modular.

Figure 9: Capital Harness Classic Migrate Flow Overview

You can migrate single composite and modular harness designs of any release level.

• Composite and modular parent designs are migrated with their associated derivative or module relationships preserved but without any derivative or child harness diagrams. You can run composite/modular breakdown once the designs are successfully migrated to the Capital installation to create the relevant derivative/child harnesses.

• You can migrate individual derivative and child module designs, but the association to their parent is not preserved.

Migration Rules

Design names must be unique within a project and the combination of part number and revision must be unique within the database.

As these details may already exist in the Capital installation, these rules are applied when designs are migrated.

Figure 10: Migration Rules

Bridge

Options

When you run the migrate process, the system imports the DSI files in accordance with the settings and pre-processor plugins that you have configured in the Bridge Options dialog box.

See also “DSI Harness and Wiring Connectors” in the Capital Connectors User Guide.

Parent Topic:

Migration of Designs From Capital Harness Classic

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens