Importing Custom Templates And Components

It can be useful to be able to import components and templates set up outside DesignBuilder to models. This page explains how to do it. The process is not fully documented and requires a willingness to experiment, but in most cases it is fairly straightforward. The recommended process is as follows:

 

  1. Export a .ddf file containing similar model data to that which you would like to import.
  2. Rename it to have extension .zip so it can be opened in WinZip, WinRAR or similar zip file editor.
  3. Open the .zip file to see a series of .cdt (compressed .dat files).
  4. Extract the .cdt files and open them in a text editor.
  5. Study the format - there is no documentation to explain the format, but it is usually fairly easy to work out by reference to the corresponding DesignBuilder dialogs and the headers. Each .cdt file consists of a line of category ids, followed by a header line which indicates the meaning of the fields below. Each further line is a record with fields separated using the "#" character. See below for an example of ActivityTempates.cdt.
  6. If you need to make more widespread edits then it is usually easiest to import the .cdt file into a spreadsheet. Here the data can be edited and exported again using tab delimiters and replacing tabs with "#" in a text editor. Note you must avoid including adjacent "#" characters in the .cdt and the easiest way to ensure this is to search for "##" and replace with "# #". Note the first column starts with "#".
  7. To create a .ddf file for importing to DesignBuilder use the reverse process. Create the .cdt files (by modifying equivalent existing files) paying careful attention to all fields. Then create the .ddf by zipping the .cdt files to be imported and renaming to use the .ddf file extension.
  8. Import the .ddf file to the DesignBuilder model.
  9. A common requirement is to create compact schedules from data from other sources (e.g. measurements or energy code references). You can use the above procedures for this by adding schedule records to Schedules.cdt. Compact schedule data is stored in the field CompactData. Note that end of lines are marked by "|^" sequences. So a compact schedule like:

Schedule:Compact,

7:00 - 18:00 Mon - Fri,

Fraction,

Through: 31 Dec,

For: Weekdays SummerDesignDay WinterDesignDay,

Until: 07:00, 0

Until: 18:00, 1,

Until: 24:00, 0,

For: Weekends,

Until: 24:00, 0,

For: AllOtherDays,

Until: 24:00, 0 ;

 

Becomes text data in the Schedules field "CompactData":

 

Schedule:Compact,|^7:00 - 18:00 Mon - Fri,|^Fraction,|^Through: 31 Dec,|^For: Weekdays SummerDesignDay WinterDesignDay,|^Until: 07:00, 0,|^Until: 18:00, 1,|^Until: 24:00, 0,|^For: Weekends,|^Until: 24:00, 0,|^For: AllOtherDays,|^Until: 24:00, 0 ;|^