FEDS can be run on a machine connected to a network. In some circumstances FEDS can even be run remotely from a network computer or file share. However, because each network is different and interference and connectivity issues are possible, for the best performance (and to lower the risk of problems) it is recommended to run FEDS from a local machine.

Sometimes when the system or software crashes, certain files are locked in the system's memory which can cause strange or unstable behavior upon restarting. If this occurs, try quitting FEDS and restarting again. When closed properly, FEDS will tidy up the system resources and work properly the next time it is run.

Weekday, Saturday, and Sunday hot water consumption values are determined using typical usage rates for a given use-area type, along with the number of occupants and occupancy schedule for each day type. Values are also adjusted according to such parameters as the presence or absence of showers and high efficiency fixtures.

FEDS assumes circulating (or loop) hot water systems serve entire buildings. Specifying a loop system for use-area 1 automatically identifies that it also serves use-area 2. Loop systems that only serve use-area 2 cannot be modeled, and the loop selection box is unnecessary and is disabled.

The best way to check the accuracy of a model  is to run FEDS without optimization and compare the annual consumption estimated by FEDS to actual metered data. To do this, go to "Exclude Building Sets" from the "Optimization" option on the "Simulation" screen. Make sure the "Pick Building Sets" method is selected then press the "Select All" button on the left side of the screen (under the list of building sets). After saving, go back and run FEDS. This will take from a few seconds to a couple minutes for FEDS to run the baseline load and consumption calculations for the buildings. Alternatively, running with the analysis type set to "Calibration" will accomplish the same thing. Once complete, review the *.txs report for the case and check the following data:

• General case and building inputs on the first five pages (for any obvious input errors)
• Energy consumption data by fuel type (page 7)
• Electric peak demand value and time of occurrence (page 8)
• Annual energy consumption by fuel type and end use (page 10)

Do not expect these to be identical to the metered data—this is a model representation of your buildings and even if extremely precise, will vary due to discrepancies related to actual vs. average weather, human behavior, and more. Therefore, achieving consumption values from FEDS that are within 10-15% of actual values suggests a reasonably accurate model. An experienced user who is knowledgeable about building energy systems and their interactions can successfully calibrate to a much tighter tolerance.

Generally, it is best to specify the original purpose of the building as the building type, and then modify the use-area type to reflect its current use. Select building type = "Education", use-area type = "Office." The building's construction characteristics are inferred based on building type, while usage parameters (including occupancy, lighting and equipment use, and hot water demand) are based on the use-area type.

Storage capacity for hot water is calculated using the building type and building's design occupancy. For distributed tank systems, values are rounded up to the next increment of typical tank capacity.

A useful rule of thumb is that a full FEDS optimization run will take a couple minutes per building set. However, run-time depends on a number of factors, including computing resources, processor speed, size, and complexity of the case. The more buildings, use areas, and technologies being analyzed, the longer the FEDS run will take. Additionally, the presence and number of central energy plants and thermal loops will also impact run-time. 

Conversely, a calibration run of the same case and computer takes only a few seconds (with additional time to generate the reports). This is because all building sets are excluded from optimization to help focus on the baseline energy results and aid in focusing on model quality assurance and calibration processes.

There is effectively no limit to the number of building sets allowed in a single case if there is enough hard drive space. Currently, each building set occupies approximately 4.3 megabytes of space across all file types. Given adequate storage space, FEDS can be—and has been—used to model an entire community, city, or utility service area.

There is no real limit to the number of buildings that can be modeled in a building set. However, building sets are designed to model buildings that share similar characteristics. The more similar buildings are within a given building set, the more accurate the results will be.

Installing FEDS will require approximately 1.7 GB of hard disk space. It is also important to have enough free disk space for case files. We recommend another 10-30 MB for this depending on the number and size of site models.

No. If a building (or use-area) has any hot water available users should specify 100% of it is served by hot water. As long as there is hot water available in a space, occupants will utilize it even if it is not immediately accessible. The purpose of having the portion served input is to allow the FEDS user to specify entire buildings (or use-areas) within a building set that do not have any hot water. For example, for a building set consisting of 10 buildings in which two of the buildings have no hot water service, they would enter that two buildings (or 20%) for the portion of buildings in this set that have no water heating.

Use the building type or use-area designation that best fits regardless of which list it is on. The building set classes were grouped this way to aid in the selection of common types, but either list may be selected.

The blue arrows indicate inputs that are required for FEDS to run. If any of these cells do not have a value provided, FEDS will not be able to run and will produce an alert either upon saving a screen or updating inferences. Once a valid input value has been provided and saved, the blue arrow will disappear.

The lock symbol that appears next to many of the input cells indicates the value is inferable by FEDS and does not require an input. An open lock icon means the value is not locked and may be changed by FEDS when inferences are updated. The closed lock symbol represents inputs whose value is locked and protected from being changed when inferences are updated. A user may lock a value by either entering a value into one of these cells, or by clicking on an open lock symbol to lock the value that is currently present in the cell.

Input cells that do not have an icon next to them are for values not absolutely required for FEDS to run but are highly recommended. Values, such as the fuel price data and occupancy hours are extremely important (yet a value may not be required for each fuel or day type). Others, such as the energy consumption inputs and building/technology identifications, are not used by FEDS except for reporting and aiding the user in understanding the output.

In FEDS MBtu signifies Million British Thermal Units. Throughout the program, the 'M' prefix represents million or 10⁶ (MW, MBtu), while 'k' represents thousand or 10³ (kWh, kBtu).

For distributed tank systems, FEDS assumes commercial tanks are 80 gallons, while residential units are 50 gallons.

FEDS assumes loop (circulating) systems serve an entire building and, therefore, the number of tanks is inferred to be one for each building, regardless of the number of use areas present.