> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloneable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Export to DDS

> Set up the configuration, poles, owners and wire statuses, then export a job from Cable Tracing as a DDSDI file, review the checks and import it into DDS.

Export a traced job to DDS so your designers can start from what was found in the field. You'll get one DDSDI file to import as a design, with the poles, framings, anchors, down guy wires, spans and conductors.

This video shows the steps on this page:

[Cable Tracing: Export to DDS](https://www.loom.com/embed/ac7a7cef67074d3db50206d7f95fd426)

## Before you export

Complete these four tasks before you export. An admin only needs to do the first one once for each configuration.

### Build the configuration from your DDS standards

An admin builds the configuration from your standards file and your owner list, under **Settings → Configurations → New configuration → From DDS standards**.

The standards fill the pick list. Framings, conductors, equipment and anchors are read only, so every part you choose is one that DDS has.

![The Pick list step of the configuration showing the standards it came from, ten framings, and DDS read-only categories for wires, equipment and anchors](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/config-dds-picklist.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=768f84ab381f47d4aa22f1341ea871f0)

Under **Export settings**, the **DDS** block shows the standards, the owner list, the utility name in the file, and the embedment rule.

![The DDS block in Export settings with the standards name, operating company, owner source with 3 owners, the utility name and an embedment rule of 10 percent plus 2 ft](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/config-dds-export.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=aa6f9d7cfc5b40cd414c0d2554c55a78)

### Set the standard and owner for each pole

1. On the map, open a pole.
2. Set its **Material**, **Length** and **Class**. Cloneable finds the matching pole in your standards and shows a green check.
3. Set its **Construction status** and **Pole owner**. The pole's status only reaches DDS if you choose **Follow the pole's status** when you export.

![The fields for a pole: Southern Pine Pole, length 40, class 4, matched to Wood pole 40 ft class 4](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/pole-standards.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=c405af8425d518c366b79d3ef624a766)

### Set the owner for each part

In Cable Tracing, each part's card has an **Owner** field. On a framing's card, it's at the top. Choose an owner from the list, which contains the owners from your owner list plus **Unknown**. Cloneable can't send an owner to DDS if it isn't on that list.

![The Owner list on a framing card: Example Utility, Unknown Utility, Example Comm and Unknown Communication](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/owner-list.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=f41a4bef4961d9b0578eb927f4b3004c)

### Set the construction status for each wire

Every wire on a card has a **Status** row with three choices: **Existing**, **Install** and **Remove**. The status stays **Existing** until you change it, so set **Install** or **Remove** on each wire that's being installed or removed.

![A framing card where each primary has a Status row with Existing, Install and Remove, with the first row outlined](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/cable-status.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=20b6d9ee847098691c456115ee547bb1)

* The status belongs to the whole wire. If you set it at one pole, it applies on every span the wire runs.
* A wire lashed to a messenger takes the messenger's status in the DDS file, even if you give the lashed wire its own status on the card.

## Export the job

**1. Open the DDS export**

Leave Cable Tracing. In the map toolbar, click **Export data**, and then click **Export to DDS**.

![The Choose export method list with Export to DDS outlined](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/export-menu-dds.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=af7e0690b5c9b733e0258a5a01d1f785)

**2. Choose the status and names**

Set the options in the dialog:

| Option | What it does |
| - | - |
| **Construction status** | Sets how poles and their parts are marked in the file. See the two choices below this table. |
| **Include elevation (GPS altitude)** | Sends GPS altitude only when every pole has an accurate reading, which means an RTK fix or a vertical accuracy within the limit shown in the dialog. |
| **Design name** and **Utility name** | Sets the names DDS shows for the design. |

For **Construction status**, choose one of these:

* **Existing** is the default. Every pole, framing and piece of equipment is marked Existing, even if a pole has another status.
* **Follow the pole's status** marks each pole and its parts with the pole's **Construction status**. Use it when pole statuses should carry into the design. A pole with no status is marked Existing if it came from the DDS design, and Install if it was added in the field.

With either choice, any **Status** you set on a wire stays in the file, unless the wire is lashed to a messenger.

![The Export to DDS dialog with construction status, the elevation switch, design name, utility name and two warnings](https://mintcdn.com/cloneable/DURhhdL1DEbEmk4r/images/tracing/dds-dialog.jpg?fit=max\&auto=format\&n=DURhhdL1DEbEmk4r\&q=85\&s=398f030a2cd26bd87ef113682a68ecb5)

**3. Read the checks**

The dialog lists warnings, notes about the file, and anything under **Not in this export**. None of these stop the export. To go to the pole or part for a row, click **Open the pole** or **Open the part** on that row.

![The lower part of the dialog: Include elevation switched off, two warnings with Open the pole buttons, and nine notes with Open the part buttons](https://mintcdn.com/cloneable/DURhhdL1DEbEmk4r/images/tracing/dds-dialog-checks.jpg?fit=max\&auto=format\&n=DURhhdL1DEbEmk4r\&q=85\&s=9694f3534fe6c7491494b29cd3a06abd)

**4. Download the file**

Click **Export DDSDI**. If the file has warnings, the button shows how many. A `.ddsdi` file downloads.

![The message DDSDI exported, 7 poles, 2 warnings](https://mintcdn.com/cloneable/JI5h3XifL4I2sezO/images/tracing/dds-exported.jpg?fit=max\&auto=format\&n=JI5h3XifL4I2sezO\&q=85\&s=ab2794026af8d5dbb4cff615762aaa49)

**5. Import the file into DDS**

In DDS, load the same standards that the configuration was built from, and then import the `.ddsdi` file as a design.

## Check the design in DDS

After the import, make sure that:

* Every pole is there, with the right catalog pole and owner.
* Each framing appears on its pole. DDS uses the framing's name to build its hardware.
* Conductors run from pole to pole in the positions you traced, with the status you set.
* Guy wires run to their anchors.

## Common DDS warnings

The same rows appear in the Issues panel in Cable Tracing, ending with **· DDS**.

| The row says | What it means | How to fix it |
| - | - | - |
| The standards file has no conductor bank list | Conductor groups aren't named after a bank, so DDS may ask you to choose a bank during import. | After the import, check the conductors on each span. |
| Span conductor groups fit no conductor bank in the standards | The conductors in a group don't match any bank in your standards, so DDS may ask you to choose a bank during import. | Check the wire types you chose against your bank list. After the import, check the conductors on each span. |
| An attachment sits above the pole top | A part's height is above the top of the pole in the design. | Check the pole's length, or move the part to where it mounts. |
| Wires have no DDS conductor: left out of the file | The wire type was never chosen, or it isn't a conductor in your standards. | Open the part and choose the wire type. |
| A wire traced onto no span | The wire is on only one pole. | Land it on the next pole, or click **Line ends here**. |
| Not in a framing | A crossarm was placed by itself. DDS only accepts an arm as part of a framing. | Click the **Not in a framing** tag on the arm, and put the arm in a framing. |
| A framing is unfinished | One of the parts in the framing wasn't placed. | Open the pole and place the part, or skip it. |
| No height | A part has no height. | Calibrate the photo, or type the height. |
| Not tied to an anchor | A guy wire isn't tied to an anchor. If the pole has one anchor, the guy wire exports on that anchor. If the pole has no anchor, the guy wire is left out. | On the guy wire's card, tie it to its anchor. If the pole has no anchor, add one on the map first. |
| Anchor only on the photo | The guy wire is tied to an anchor that isn't on the map, so it's left out. | Add the anchor on the map, and then tie the guy wire to it. |
| A lashed cable is Install on an Existing messenger | A DDS file can't give a lashed wire its own status, so the wire takes its messenger's status. | Change the messenger's **Status** only if the messenger itself is being installed or removed. |

### Notes about the file

A note tells you how the file was written. You don't need to act on a note unless this table says so.

| The note says | What it means |
| - | - |
| The crossarm goes out 8.0 ft, the length in its framing's name | The arm's length came from the framing's name. Choose the arm's size on its card only if the length is different. |
| Kept the midspan on one span; other measured midspans left out | DDS accepts one measured midspan for each dead-end section. |
| Pole elevations: their location has no altitude | No elevation is sent for these poles. DDS reads a missing elevation as 0, so Cloneable sends elevations for all poles or for none. |
| Which way a crossarm points, and where insulators sit along it | A DDS import file has no place for this information. |

For other problems, see [Cable Tracing troubleshooting](https://docs.cloneable.ai/guides/tracing/troubleshooting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.