---
title: "Configuration report"
---

# Configuration report

Writing a Markdown configuration report of a DeltaV export with counts, modules per area and controller, classes, alarms, sequences and check findings.

**Verification state:** modelled. On the real DeltaV 14.5.1 export, a 575-line report of about 47 KB was written in about 1.2 s; its alarm and chart totals match the Alarms table and the sequence reader. **Whether the counts match DeltaV's own reports is not verified.** The window waits about a second on a 25 MB export. Not on Windows.

## Write the report

Run **Write DeltaV Configuration Report** on the export in the active editor, or **Write Configuration Report** on an export in the DeltaV Plant view.

1. The module reads the editor's text when the export is open (unsaved changes included), else the file.
2. It writes `<export>.report.md` next to the export, in UTF-8. It asks before replacing an existing report.
3. The report opens.

Nothing is written for a missing or unreadable export.

## What it holds

| Section | Content |
|---|---|
| Summary | Summary counts of the export |
| Modules | Per area and per controller |
| Classes | With their instance counts |
| Alarms | By priority, and the disabled alarms |
| Sequences | With their sizes |
| Findings | The [checks](https://neuralinverse.com/docs/modules/dcs/checks/) with their lines |

Every section states what it is read from and that it is the module's reading of the export, not DeltaV's. Table cells escape pipes and Markdown, so the report renders as written.