---
title: "Export a CID"
---

# Export a CID

Cut the configured IED description (CID) of one IED from the SCD, with its communication partners, byte for byte from the SCD's own text.

**State:** CID preparation is verified on the public SCL files: RiseClipse 1.3.0 found nothing new in 377 CIDs cut from them, and each CID taken back by Update IED from IID changed nothing, byte for byte. **No vendor tool or IED has read a CID written here.** Before a CID goes to site, open it in the relay vendor's tool and check it.

The module prepares the CID. Loading it to the IED is done in the relay vendor's tool (see [What's next](https://neuralinverse.com/docs/modules/energy/whats-next/)).

## Export

1. Open the SCD and run **Export IED Configuration (CID)...** (without an SCD open, it asks for one). The SCD is read as the editor holds it, unsaved changes included.
2. Pick the IED.
3. For the Header of the CID, choose **Keep the Header as it is** or **Add a History entry for this export**.
4. Pick where to save; the default name is next to the SCD. The command never replaces a file without asking.
5. The CID opens. Read the warnings: "The CID of <IED> was written, but ..." when the checks find problems in it, or when the SCD has no address for a control block it subscribes to; **Show Log** opens the Energy log.

The command refuses an IED that is missing, defined twice, or on no subnetwork, before asking anything.

## What the CID holds

- The Header as it is; a `Hitem` only when you chose it.
- The subnetworks the IED is on, with its own connected access points.
- The GOOSE and Sampled Values addresses of the other IEDs it subscribes to (by its inputs, Edition 1 inputs matched through the data set, or a control block's `IEDName` list), on any subnetwork.
- The address of each server it is a report client of.
- The substation parts with its logical node bindings, and the connectivity nodes its equipment connects to.
- The IED itself.
- The type templates it uses, followed through every DO, SDO, DA and BDA.

Every kept element is the SCD's own text, byte for byte; a comment directly above a removed element goes with it.

The CID carries the IED with its partners, each cut to what the IED needs, because a subscriber needs the publisher's data set to decode its GOOSE or Sampled Values, and PCM600's own CIDs carry their report clients. In Problems, a `.cid` or `.iid` file with one IED is checked as a CID: the references it makes to IEDs it does not carry are set apart, not marked unresolved.

**Try it:** in an SCD where P2 subscribes to P1's GOOSE `gcb01`, export the CID of P2. It opens with no Problems entry, and keeps the GOOSE address of P1's `gcb01`.

## Size

On a generated SCD of 100 IEDs, the CIDs of all 100 are cut in 111 ms, each read back with no finding.

## Not verified

- Any vendor tool or IED reading the CID.
- Vendors that expect the whole SCD, other IEDs' sections or private data in a CID.
- The CID rules are the module's reading of IEC 61850-6 Edition 2 (2007B4), applied also to 2007B and 2003 files.
- SCDs of DIGSI 5, SEL and Helinks; Windows.

`Private` elements at the root and inside kept elements are copied as they are, and may describe other IEDs.