> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/base-stations/base-stations/integrations-and-3rd-party-systems/bacnet/engineering-data-exchange-file-structure.md).

# Engineering Data Exchange file structure

The EDE file serves to integrate the Aranet PRO BACnet service into third-party systems through offline import. This file
 defines the structure of BACnet project data for a device. When changes are made to the object list in the Aranet PRO
 base, the outdated EDE file, which contains information about available objects, is removed. Users can then request
 the base to generate a new EDE file, which is in CSV format. The first six rows of the file provide descriptions about the
 BACnet project that generated it.
 The EDE file structural components is in the table below.

<table><thead><tr><th width="210">Column name</th><th width="136">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Keyname</td><td>Mandatory</td><td>BACnet specific object type combined with instance identifier</td></tr><tr><td>Device object instance</td><td>Mandatory</td><td>Device object instance ID which owns this object</td></tr><tr><td>Object name</td><td>Mandatory</td><td>Name of the object</td></tr><tr><td>Object type</td><td>Mandatory</td><td>BACnet specific identifier used to identify object type</td></tr><tr><td>Object instance</td><td>Mandatory</td><td>Object instance identifier</td></tr><tr><td>Description</td><td>Optional</td><td>Object description auto-generated by BACnet upon object creation</td></tr><tr><td>State text reference</td><td>Optional</td><td>Not used</td></tr><tr><td>Present value default</td><td>Optional</td><td>Not used</td></tr><tr><td>Supports CoV</td><td>Optional</td><td>Does object supports Cange-of-Value</td></tr><tr><td>Commandable</td><td>Optional</td><td>Is commandable (using priority array)</td></tr><tr><td>Min. present value</td><td>Optional</td><td>Not used</td></tr><tr><td>Max. present value</td><td>Optional</td><td>Not used</td></tr><tr><td>High limit</td><td>Optional</td><td>Not used</td></tr><tr><td>Low limit</td><td>Optional</td><td>Not used</td></tr><tr><td>Unit-code</td><td>Optional</td><td>BACnet specific identifier used to identify the measurement unit</td></tr><tr><td>Vendor specific address</td><td>Optional</td><td>Not used</td></tr><tr><td>Element</td><td>Optional</td><td>Additional field which contains object description</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.aranet.com/base-stations/base-stations/integrations-and-3rd-party-systems/bacnet/engineering-data-exchange-file-structure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.