# Cost Estimating[LINK]

In order to understand how to include cost estimates, it may be helpful to first define some terminology and provide an overview of the process used in EnergyPlus. There are three broad steps involved. The first involves determining *construction* costs by summing individual “line items.” The second involves determining *project* costs by adjusting construction costs to account for things like profit and design fees. The third involves comparing the current simulation to a reference case so that marginal increases can be calculated. Each of these steps involves using one of the three ‘ComponentCost’ objects described below.

## ComponentCost:LineItem[LINK]

Each instance of this object creates a cost line item and will contribute to the total for a cost estimate. Each line item is reported in table form in the tabular report file. The user must request that this report be generated by including a Output:Table:SummaryReports object with the Component Cost Economics Summary option selected. The style of a tabular report can be controlled using the OutputControl:Table:Style object.

Cost estimates are not currently general in that they cannot be performed for every type of component that could be included in an EnergyPlus model. Although a “General” option is available where all information needed for the cost line item is input by the user, the usefulness of cost modeling within EnergyPlus is expected to be enhanced when quantities are obtained from elsewhere in the input file or computed during a simulation. The cost computations are programmed in selected ways for selected objects. The objects available and the type of cost modeling that may be performed are discussed in detail in the discussion of Reference Object Type field. A particular instance of this object will always have many blank fields. Entering values in too many fields may cause an error because the program may determine how a particular cost is to be calculated based on the presence of non-zero values in particular fields. The input object includes fields that are reserved for future use in expanded cost estimate and investment analyses planned for future versions of EnergyPlus. If you would like to request additional objects or different methods of modeling component costs, feel free to describe your needs and submit a request via email to energyplus-support@gard.com.

This field is a user-selected name that will appear in the line item description of the cost report. It is not used in the calculation but allows identifying a line item in the subsequent report.

This field is not yet used and may be left blank.

#### Field: Line Item Type[LINK]

The cost estimate line item calculation will be controlled by the name entered in this field. The requirements for the remaining input, and the cost calculations performed, will vary depending on the object referenced here. Only selected objects can be entered here. The objects available for cost estimating are listed in the following table showing the active fields and options available for each.

##### General

This choice of object is used to calculate costs in a general way. No quantities from internal calculations are used. All information needed for the cost line item is input by the user. The Cost per Each and the Quantity fields that follow need to have values.

##### Construction

This choice of object type is used to calculate the costs associated with surfaces based on the type of Construction used for the surface. Costs are entered on a per-square-meter basis. The program finds all the surfaces that have the type of Construction named in the Reference Object Name field that follows and determines the total area. If the model includes duplicate surfaces, as for interior partitions or floors, these will be detected and not double-counted. The cost entered in Cost per Area field ($/m2) is used for each surface. The line item subtotal is calculated by multiplying the number of units by Cost per Area. The Cost per Area should include all the material layers defined in the Construction.

##### Coil:DX or Coil:Cooling:DX:SingleSpeed

This choice of object type is used to calculate the cost of direct expansion cooling equipment. Cost can be entered in three different ways, (1) per each, (2) per kW total cooling capacity, or (3) per kW total cooling capacity per COP (coefficient of performance). The program will determine which method to use by examining which input fields have non-zero values. It is an error to specify costs in more than one way. The per-each approach is most useful for discrete packages. The per-kW approach is useful for autosizing DX coils with the same COP. The per-kW-per-COP approach is convenient for modeling autosized DX coils with differing COPs as long as a linear relationship is sufficient.

The wildcard character “*” may be used in the object name field that follows to allow a single line item to include all of the DX coils in the model.

##### Coil:Heating:Fuel

This choice of object type is used to calculate the cost of gas-fired heating equipment. Cost can be entered in three different ways, (1) per each, (2) per kW of heating capacity, or (3) per kW total cooling capacity per nominal efficiency (actually uses the per kW per COP field). The program will determine which method to use by examining which input fields have non-zero values. It is an error to specify costs in more than one way. The per-each approach is most useful for discrete packages. The per-kW approach is useful for autosizing heating coils with the same efficiency. The per-kW-per-Eff approach is convenient for modeling autosized heating coils with differing efficiencies as long as a linear relationship is sufficient.

The wildcard character “*” may be used in the object name field that follows to allow a single line item to include all of the gas heating coils in the model.

##### Chiller:Electric

This choice of object type is used to calculate the cost of a central chiller. The object name entered in following field must correspond to a Chiller:Electric object name defined elsewhere in the input file. Cost can be entered in three different ways, (1) per each, (2) per kW total cooling capacity or (3) per kW total cooling capacity per COP (coefficient of performance). The program will determine which method to use by examining which input fields have non-zero values. It is an error to specify costs in more than one way. The per-each approach is most useful for discrete chillers. The per-kW approach is useful for autosizing chillers with the same COP. The per-kW-per-COP approach is convenient for modeling autosized chillers with differing COPs as long as a linear relationship is sufficient.

##### Daylighting:Controls

These choices of object type are used to include the cost of controllers needed to control electric lighting in response to daylight. The only option for entering costs is “per each”. The wildcard character “*” may be used in the following object name field to allow a single line item to include all of the simple and detailed daylighting controls in the cost model.

##### Shading:Zone:Detailed

This choice of object type is used to calculate the costs associated with attached shading surfaces. Costs are entered on a per-square-meter basis. The cost calculations are similar to those for heat transfer surfaces but are handled separately because “Construction” is not defined for a shading surface. The object name entered in the following field must correspond to a Shading:Zone:Detailed object name defined elsewhere in the input file.

##### Lights

This choice of object is used to calculate the costs associated with electric lighting. Costs are entered on either a cost-per-each basis or as a cost-per-kilowatt-of-design-level. (This design level is an input in the Lights object.). The object name entered into the following field must match the name of a Zone object defined elsewhere in the input file.

##### Generator:Photovoltaic

This choice of object is used to calculate the costs associated with a photovoltaic system. Costs are entered on a cost-per-kilowatt-of-rated-capacity. The rated capacity of a photovoltaic generator is calculated for cost modeling by exposing the surface to a 1000 W/m2 incident radiation using the area fraction and nominal fixed efficiency input by the user (from the Generator:Photovoltaic object). The object name entered into the following field must match the name of a Generator:Photovoltaic object defined elsewhere in the input file.

#### Field: Item Name[LINK]

This field is used to refer to a specific instance of an object. The wildcard character “*” is acceptable for some objects as described above for the previous field.

#### Field: Object End Use Key[LINK]

This field is not yet used and may be left blank.

#### Field: Cost per Each[LINK]

This field is used to enter cost information on a per-each basis. The units are dollars ($).

#### Field: Cost per Area[LINK]

This field is used to enter cost information on a per-area basis. The units are dollars per square meter ($/m2).

#### Field: Cost per Unit of Output Capacity[LINK]

This field is used to enter cost information on a per-kilowatt basis. The units are dollars per kilowatt ($/kW).

#### Field: Cost per Unit of Output Capacity per COP[LINK]

This field is used to enter cost information on a per-kilowatt-per-COP basis. The units are dollars per kilowatt per non-dimensional COP ($/kW-COP). Note that this field can be used for Coil:Heating:Fuel cost modeling in which case the better terminology would be per-kilowatt-per-non-dimensional-efficiency.

#### Field: Cost per Volume[LINK]

This field is not yet used but will be used to enter cost information on a per-cubic-meter basis. The units are dollars per cubic meter ($/m3).

#### Field: Cost per Volume Rate[LINK]

This field is not yet used but will be used to enter cost information on a per-cubic-meter-per-second basis. The units are dollars per cubic meter ($/(m3/s)).

#### Field: Cost per Energy per Temperature Difference[LINK]

This field is not yet used but will be used to enter cost information on a per-watt-per-Kelvin basis. These units will be used to represent a UA description of coils and the like. The units are dollars per watt per delta K ($/(W/K)).

#### Field: Quantity[LINK]

This field is used to directly enter the line item quantity. The units should correspond to what is used in the Per Each field.

Some examples of this object in an IDF:

```
ComponentCost:LineItem,
PSZ Equipment from scaling , !- Name
, !- Type
Coil:DX, !- Line Item Type
ACDXCoil ZN1 , !- Item Name
, !- Object End Use Key
, !- Cost per Each {$}
, !- Cost per Area {$/m2}
, !- Cost per Unit of Output Capacity {$/kW}
82.5; !- Cost per Unit of Output Capacity per COP {$/kW}
ComponentCost:LineItem,
Lighting Equip: ZN2_E_Space_1, ,
Lights,!- Line Item Type
ZN2_E_Space_1, ,
,!- Cost per Each {$}
,!- Cost per Area {$/m2}
3300.000;!- Cost per Unit of Output Capacity {$/kW}
ComponentCost:LineItem, DL controls: ZN4_W_Space_1, ,
Daylighting:Detailed, !- Line Item Type
ZN4_W_Space_1, ,!- Item Name
125.000, !- Cost per Each {$}
,!- Cost per Area {$/m2}
;!- Cost per Unit of Output Capacity {$/kW}
```

## ComponentCost:Adjustments[LINK]

This object can be used to perform various modifications to the construction costs to arrive at an estimate for total project costs. This object allows extending the line item model so that the overall costs of the project will reflect various profit and fees. Only one object of this type can be included in the input file. The results are included in the Construction Cost Estimate Summary table by request using the Output:Table:SummaryReports object with the Component Cost Economics Summary option selected.

#### Field: Miscellaneous Cost per Conditioned Area[LINK]

This optional field can be used to enter a cost model for miscellaneous project costs that are not included in the line item modeling. Miscellaneous costs are entered in dollars per square meter of conditioned floor area. This field allows including the costs of project elements that go beyond what can be modeled using “ComponentCost:LineItem” input objects including such things as structural components, site preparation, finishes, etc. The value input in this field will be multiplied by the conditioned floor area and listed in the Construction Cost Estimate Summary table. The miscellaneous project costs are added to the line item model total to determine the “modeled and miscellaneous Construction costs” that will be multiplied by the fractions in the following five fields.

#### Field: Design and Engineering Fees[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for design and engineering fees. Note that is not the same as a fraction of the total cost estimate.

#### Field: Contractor Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for Contractor fees. Note that is not the same as a fraction of the total cost estimate.

#### Field: Contingency[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added for contingency. Note that is not the same as a fraction of the total cost estimate.

#### Field: Permits, Bonding and Insurance[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for permitting, bonding, and insurance costs to the project. Note that is not the same as a fraction of the total cost estimate.

#### Field: Commissioning Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for commissioning services. Note that is not the same as a fraction of the total cost estimate.

#### Field: Regional Adjustment Factor[LINK]

This optional field can be used to enter an adjustment factor to account for regional differences is construction costs. The factor will be applied to the modeled and miscellaneous construction costs to determine and amount that should be added, or subtracted, to account for local variations in construction costs. The default factor is 1.0. The additive adjustment is calculated by subtracting 1.0 from the value entered in this field. This field is useful for using national average data in the line item and miscellaneous construction cost models and then altering the results based on regional differences.

An example of this object in an IDF is:

```
ComponentCost:Adjustments,
467, !- Miscellaneous Cost per Conditioned Area
0.07, !- Design and Engineering Fees
0.07, !- Contractor Fee
0.10, !- Contingency
0.04, !- Permits, Bonding and Insurance
0.015,!- Commissioning Fee
1.136; !- Regional Adjustment Factor
```

## ComponentCost:Reference[LINK]

This object can be used to allow comparing the current cost estimate to the results of a previous estimate for a reference building. This object parallels the ComponentCost:Adjustment object but adds a field for entering the cost line item model result for the reference building. All the various adjustments to the project cost estimate are available here to allow using factors that differ between the current and the reference building models. The factors entered in the field associated with this object are applied to the reference building while the factors listed in the ComponentCost:Adjustment object are applied to the current building model cost estimate. Only one object of this type can be included in the input file. The results are included in the Construction Cost Estimate Summary table by request using the Output:Table:SummaryReports object with the Component Cost Economics Summary option selected.

#### Field: Reference Building Line Item Costs[LINK]

This field is used to enter a dollar amount representing the total for the reference building that the user would like to compare to the line item cost model for the current building model. A typical source of data for this would be the “Line Item Subtotal” from a previous EnergyPlus simulation.

#### Field: Reference Building Miscellaneous Cost per Conditioned Area[LINK]

This optional field can be used to enter a cost model for miscellaneous project costs that are not included in the line item modeling. Miscellaneous costs are entered in dollars per square meter of conditioned floor area. This field allows including the costs of project elements that go beyond what can be modeled using “ComponentCost:LineItem” input objects including such things as structural components, site preparation, finishes, etc. The value input in this field will be multiplied by the conditioned floor area and listed in the Construction Cost Estimate Summary table. The miscellaneous project costs are added to the reference building line item subtotal to determine the “modeled and miscellaneous construction costs” that will be multiplied by the fractions in the following five fields.

#### Field: Reference Building Design and Engineering Fees[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for design and engineering fees. Note that is not the same as a fraction of the total cost estimate.

#### Field: Reference Building Contractor Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for Contractor fees. Note that is not the same as a fraction of the total cost estimate.

#### Field: Reference Building Contingency[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added for contingency. Note that is not the same as a fraction of the total cost estimate.

#### Field: Reference Building Permits, Bonding and Insurance[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for permitting, bonding, and insurance costs to the project. Note that is not the same as a fraction of the total cost estimate.

#### Field: Reference Building Commissioning Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for commissioning services. Note that is not the same as a fraction of the total cost estimate.

#### Field: Reference Building Regional Adjustment Factor[LINK]

This optional field can be used to enter an adjustment factor to account for regional differences is construction costs. The factor will be applied to the modeled and miscellaneous construction costs to determine and amount that should be added, or subtracted, to account for local variations in construction costs. The default factor is 1.0. The additive adjustment is calculated by subtracting 1.0 from the value entered in this field. This field is useful for using national average data in the line item and miscellaneous construction cost models and then altering the results based on regional differences.

An example of this object in an IDF is:

```
ComponentCost:Reference,
683060.000, !- Reference Building Line Item Costs {$}
467.0, !- Reference Building Miscellaneous Cost per Conditioned Area {$/m2}
0.060, !- Reference Building Design and Engineering Fees {dimensionless}
0.070, !- Reference Building Contractor Fee {dimensionless}
0.100, !- Reference Building Contingency
0.04, !- Reference Building Permits, Bonding and Insurance {dimensionless}
0.0075,!- Reference Building Commissioning Fee {dimensionless}
1.136; !- Reference Building Regional Adjustment Factor {dimensionless}
```

## Economics Cost Estimate Reporting[LINK]

Cost estimate results are only output to tabular reports; they are not available in the standard output file (.eso). The results are included in the Construction Cost Estimate Summary table by request using the object Output:Table:SummaryReports object with the Component Cost Economics Summary option selected. The figure below shows an example of summary output using html style for tabular reporting. A second table is produced that provides the line item details with one line for every line item object. Per-area cost modeling and cost normalization are based on total conditioned floor area which is also provided in the tabular report.

“Line Item Subtotal” is the sum of items explicitly modeled in the cost estimate. For the reference building, this value is input by the user. For the current building, this value is the sum of line items which are detailed in Cost Line Item Details table that follows.

“Misc. Cost” is the product of the user-defined Miscellaneous Cost Model (per Square Meter) and the conditioned floor area.

“Regional Adjustment” is the produce of the user-defined Regional Adjustment Factor and the conditioned floor area.

“Design Fee” is the product of the user-defined Design and Engineering Fee Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Contractor Fee” is the product of the user-defined Contractor Fee Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Contingency” is the product of the user-defined Contingency Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Permits, Bonds, and Insurance” is the product of the Permits, Bonding, Insurance Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Commissioning” is the product of the user-defined Commissioning Fee Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Cost Estimate Total” is the sum of eight items above and represents the total project cost estimate.

“Cost per Conditioned Building Area” is the Cost Estimate Total divided by the total conditioned floor area. This represents a normalized cost intensity.

## Cost Estimating[LINK]

In order to understand how to include cost estimates, it may be helpful to first define some terminology and provide an overview of the process used in EnergyPlus. There are three broad steps involved. The first involves determining

constructioncosts by summing individual “line items.” The second involves determiningprojectcosts by adjusting construction costs to account for things like profit and design fees. The third involves comparing the current simulation to a reference case so that marginal increases can be calculated. Each of these steps involves using one of the three ‘ComponentCost’ objects described below.## ComponentCost:LineItem[LINK]

Each instance of this object creates a cost line item and will contribute to the total for a cost estimate. Each line item is reported in table form in the tabular report file. The user must request that this report be generated by including a Output:Table:SummaryReports object with the Component Cost Economics Summary option selected. The style of a tabular report can be controlled using the OutputControl:Table:Style object.

Cost estimates are not currently general in that they cannot be performed for every type of component that could be included in an EnergyPlus model. Although a “General” option is available where all information needed for the cost line item is input by the user, the usefulness of cost modeling within EnergyPlus is expected to be enhanced when quantities are obtained from elsewhere in the input file or computed during a simulation. The cost computations are programmed in selected ways for selected objects. The objects available and the type of cost modeling that may be performed are discussed in detail in the discussion of Reference Object Type field. A particular instance of this object will always have many blank fields. Entering values in too many fields may cause an error because the program may determine how a particular cost is to be calculated based on the presence of non-zero values in particular fields. The input object includes fields that are reserved for future use in expanded cost estimate and investment analyses planned for future versions of EnergyPlus. If you would like to request additional objects or different methods of modeling component costs, feel free to describe your needs and submit a request via email to energyplus-support@gard.com.

## Inputs[LINK]

## Field: Name[LINK]

This field is a user-selected name that will appear in the line item description of the cost report. It is not used in the calculation but allows identifying a line item in the subsequent report.

## Field: Type[LINK]

This field is not yet used and may be left blank.

## Field: Line Item Type[LINK]

The cost estimate line item calculation will be controlled by the name entered in this field. The requirements for the remaining input, and the cost calculations performed, will vary depending on the object referenced here. Only selected objects can be entered here. The objects available for cost estimating are listed in the following table showing the active fields and options available for each.

## General

This choice of object is used to calculate costs in a general way. No quantities from internal calculations are used. All information needed for the cost line item is input by the user. The Cost per Each and the Quantity fields that follow need to have values.

## Construction

This choice of object type is used to calculate the costs associated with surfaces based on the type of Construction used for the surface. Costs are entered on a per-square-meter basis. The program finds all the surfaces that have the type of Construction named in the Reference Object Name field that follows and determines the total area. If the model includes duplicate surfaces, as for interior partitions or floors, these will be detected and not double-counted. The cost entered in Cost per Area field ($/m2) is used for each surface. The line item subtotal is calculated by multiplying the number of units by Cost per Area. The Cost per Area should include all the material layers defined in the Construction.

## Coil:DX or Coil:Cooling:DX:SingleSpeed

This choice of object type is used to calculate the cost of direct expansion cooling equipment. Cost can be entered in three different ways, (1) per each, (2) per kW total cooling capacity, or (3) per kW total cooling capacity per COP (coefficient of performance). The program will determine which method to use by examining which input fields have non-zero values. It is an error to specify costs in more than one way. The per-each approach is most useful for discrete packages. The per-kW approach is useful for autosizing DX coils with the same COP. The per-kW-per-COP approach is convenient for modeling autosized DX coils with differing COPs as long as a linear relationship is sufficient.

The wildcard character “*” may be used in the object name field that follows to allow a single line item to include all of the DX coils in the model.

## Coil:Heating:Fuel

This choice of object type is used to calculate the cost of gas-fired heating equipment. Cost can be entered in three different ways, (1) per each, (2) per kW of heating capacity, or (3) per kW total cooling capacity per nominal efficiency (actually uses the per kW per COP field). The program will determine which method to use by examining which input fields have non-zero values. It is an error to specify costs in more than one way. The per-each approach is most useful for discrete packages. The per-kW approach is useful for autosizing heating coils with the same efficiency. The per-kW-per-Eff approach is convenient for modeling autosized heating coils with differing efficiencies as long as a linear relationship is sufficient.

The wildcard character “*” may be used in the object name field that follows to allow a single line item to include all of the gas heating coils in the model.

## Chiller:Electric

This choice of object type is used to calculate the cost of a central chiller. The object name entered in following field must correspond to a Chiller:Electric object name defined elsewhere in the input file. Cost can be entered in three different ways, (1) per each, (2) per kW total cooling capacity or (3) per kW total cooling capacity per COP (coefficient of performance). The program will determine which method to use by examining which input fields have non-zero values. It is an error to specify costs in more than one way. The per-each approach is most useful for discrete chillers. The per-kW approach is useful for autosizing chillers with the same COP. The per-kW-per-COP approach is convenient for modeling autosized chillers with differing COPs as long as a linear relationship is sufficient.

## Daylighting:Controls

These choices of object type are used to include the cost of controllers needed to control electric lighting in response to daylight. The only option for entering costs is “per each”. The wildcard character “*” may be used in the following object name field to allow a single line item to include all of the simple and detailed daylighting controls in the cost model.

## Shading:Zone:Detailed

This choice of object type is used to calculate the costs associated with attached shading surfaces. Costs are entered on a per-square-meter basis. The cost calculations are similar to those for heat transfer surfaces but are handled separately because “Construction” is not defined for a shading surface. The object name entered in the following field must correspond to a Shading:Zone:Detailed object name defined elsewhere in the input file.

## Lights

This choice of object is used to calculate the costs associated with electric lighting. Costs are entered on either a cost-per-each basis or as a cost-per-kilowatt-of-design-level. (This design level is an input in the Lights object.). The object name entered into the following field must match the name of a Zone object defined elsewhere in the input file.

## Generator:Photovoltaic

This choice of object is used to calculate the costs associated with a photovoltaic system. Costs are entered on a cost-per-kilowatt-of-rated-capacity. The rated capacity of a photovoltaic generator is calculated for cost modeling by exposing the surface to a 1000 W/m2 incident radiation using the area fraction and nominal fixed efficiency input by the user (from the Generator:Photovoltaic object). The object name entered into the following field must match the name of a Generator:Photovoltaic object defined elsewhere in the input file.

## Field: Item Name[LINK]

This field is used to refer to a specific instance of an object. The wildcard character “*” is acceptable for some objects as described above for the previous field.

## Field: Object End Use Key[LINK]

This field is not yet used and may be left blank.

## Field: Cost per Each[LINK]

This field is used to enter cost information on a per-each basis. The units are dollars ($).

## Field: Cost per Area[LINK]

This field is used to enter cost information on a per-area basis. The units are dollars per square meter ($/m2).

## Field: Cost per Unit of Output Capacity[LINK]

This field is used to enter cost information on a per-kilowatt basis. The units are dollars per kilowatt ($/kW).

## Field: Cost per Unit of Output Capacity per COP[LINK]

This field is used to enter cost information on a per-kilowatt-per-COP basis. The units are dollars per kilowatt per non-dimensional COP ($/kW-COP). Note that this field can be used for Coil:Heating:Fuel cost modeling in which case the better terminology would be per-kilowatt-per-non-dimensional-efficiency.

## Field: Cost per Volume[LINK]

This field is not yet used but will be used to enter cost information on a per-cubic-meter basis. The units are dollars per cubic meter ($/m3).

## Field: Cost per Volume Rate[LINK]

This field is not yet used but will be used to enter cost information on a per-cubic-meter-per-second basis. The units are dollars per cubic meter ($/(m3/s)).

## Field: Cost per Energy per Temperature Difference[LINK]

This field is not yet used but will be used to enter cost information on a per-watt-per-Kelvin basis. These units will be used to represent a UA description of coils and the like. The units are dollars per watt per delta K ($/(W/K)).

## Field: Quantity[LINK]

This field is used to directly enter the line item quantity. The units should correspond to what is used in the Per Each field.

Some examples of this object in an IDF:

## ComponentCost:Adjustments[LINK]

This object can be used to perform various modifications to the construction costs to arrive at an estimate for total project costs. This object allows extending the line item model so that the overall costs of the project will reflect various profit and fees. Only one object of this type can be included in the input file. The results are included in the Construction Cost Estimate Summary table by request using the Output:Table:SummaryReports object with the Component Cost Economics Summary option selected.

## Inputs[LINK]

## Field: Miscellaneous Cost per Conditioned Area[LINK]

This optional field can be used to enter a cost model for miscellaneous project costs that are not included in the line item modeling. Miscellaneous costs are entered in dollars per square meter of conditioned floor area. This field allows including the costs of project elements that go beyond what can be modeled using “ComponentCost:LineItem” input objects including such things as structural components, site preparation, finishes, etc. The value input in this field will be multiplied by the conditioned floor area and listed in the Construction Cost Estimate Summary table. The miscellaneous project costs are added to the line item model total to determine the “modeled and miscellaneous Construction costs” that will be multiplied by the fractions in the following five fields.

## Field: Design and Engineering Fees[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for design and engineering fees. Note that is not the same as a fraction of the total cost estimate.

## Field: Contractor Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for Contractor fees. Note that is not the same as a fraction of the total cost estimate.

## Field: Contingency[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added for contingency. Note that is not the same as a fraction of the total cost estimate.

## Field: Permits, Bonding and Insurance[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for permitting, bonding, and insurance costs to the project. Note that is not the same as a fraction of the total cost estimate.

## Field: Commissioning Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for commissioning services. Note that is not the same as a fraction of the total cost estimate.

## Field: Regional Adjustment Factor[LINK]

This optional field can be used to enter an adjustment factor to account for regional differences is construction costs. The factor will be applied to the modeled and miscellaneous construction costs to determine and amount that should be added, or subtracted, to account for local variations in construction costs. The default factor is 1.0. The additive adjustment is calculated by subtracting 1.0 from the value entered in this field. This field is useful for using national average data in the line item and miscellaneous construction cost models and then altering the results based on regional differences.

An example of this object in an IDF is:

## ComponentCost:Reference[LINK]

This object can be used to allow comparing the current cost estimate to the results of a previous estimate for a reference building. This object parallels the ComponentCost:Adjustment object but adds a field for entering the cost line item model result for the reference building. All the various adjustments to the project cost estimate are available here to allow using factors that differ between the current and the reference building models. The factors entered in the field associated with this object are applied to the reference building while the factors listed in the ComponentCost:Adjustment object are applied to the current building model cost estimate. Only one object of this type can be included in the input file. The results are included in the Construction Cost Estimate Summary table by request using the Output:Table:SummaryReports object with the Component Cost Economics Summary option selected.

## Inputs[LINK]

## Field: Reference Building Line Item Costs[LINK]

This field is used to enter a dollar amount representing the total for the reference building that the user would like to compare to the line item cost model for the current building model. A typical source of data for this would be the “Line Item Subtotal” from a previous EnergyPlus simulation.

## Field: Reference Building Miscellaneous Cost per Conditioned Area[LINK]

This optional field can be used to enter a cost model for miscellaneous project costs that are not included in the line item modeling. Miscellaneous costs are entered in dollars per square meter of conditioned floor area. This field allows including the costs of project elements that go beyond what can be modeled using “ComponentCost:LineItem” input objects including such things as structural components, site preparation, finishes, etc. The value input in this field will be multiplied by the conditioned floor area and listed in the Construction Cost Estimate Summary table. The miscellaneous project costs are added to the reference building line item subtotal to determine the “modeled and miscellaneous construction costs” that will be multiplied by the fractions in the following five fields.

## Field: Reference Building Design and Engineering Fees[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for design and engineering fees. Note that is not the same as a fraction of the total cost estimate.

## Field: Reference Building Contractor Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for Contractor fees. Note that is not the same as a fraction of the total cost estimate.

## Field: Reference Building Contingency[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added for contingency. Note that is not the same as a fraction of the total cost estimate.

## Field: Reference Building Permits, Bonding and Insurance[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for permitting, bonding, and insurance costs to the project. Note that is not the same as a fraction of the total cost estimate.

## Field: Reference Building Commissioning Fee[LINK]

This optional field can be used to enter a fraction of modeled and miscellaneous construction costs that should be added to account for commissioning services. Note that is not the same as a fraction of the total cost estimate.

## Field: Reference Building Regional Adjustment Factor[LINK]

This optional field can be used to enter an adjustment factor to account for regional differences is construction costs. The factor will be applied to the modeled and miscellaneous construction costs to determine and amount that should be added, or subtracted, to account for local variations in construction costs. The default factor is 1.0. The additive adjustment is calculated by subtracting 1.0 from the value entered in this field. This field is useful for using national average data in the line item and miscellaneous construction cost models and then altering the results based on regional differences.

An example of this object in an IDF is:

## Economics Cost Estimate Reporting[LINK]

Cost estimate results are only output to tabular reports; they are not available in the standard output file (.eso). The results are included in the Construction Cost Estimate Summary table by request using the object Output:Table:SummaryReports object with the Component Cost Economics Summary option selected. The figure below shows an example of summary output using html style for tabular reporting. A second table is produced that provides the line item details with one line for every line item object. Per-area cost modeling and cost normalization are based on total conditioned floor area which is also provided in the tabular report.

Economics Cost Modeling [fig:economics-cost-modeling]

“Line Item Subtotal” is the sum of items explicitly modeled in the cost estimate. For the reference building, this value is input by the user. For the current building, this value is the sum of line items which are detailed in Cost Line Item Details table that follows.

“Misc. Cost” is the product of the user-defined Miscellaneous Cost Model (per Square Meter) and the conditioned floor area.

“Regional Adjustment” is the produce of the user-defined Regional Adjustment Factor and the conditioned floor area.

“Design Fee” is the product of the user-defined Design and Engineering Fee Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Contractor Fee” is the product of the user-defined Contractor Fee Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Contingency” is the product of the user-defined Contingency Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Permits, Bonds, and Insurance” is the product of the Permits, Bonding, Insurance Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Commissioning” is the product of the user-defined Commissioning Fee Fraction and the subtotal for construction costs (which includes the Line Item Subtotal, Misc. Cost, and Regional Adjustment).

“Cost Estimate Total” is the sum of eight items above and represents the total project cost estimate.

“Cost per Conditioned Building Area” is the Cost Estimate Total divided by the total conditioned floor area. This represents a normalized cost intensity.

Documentation content copyright © 1996-2020 The Board of Trustees of the University of Illinois and the Regents of the University of California through the Ernest Orlando Lawrence Berkeley National Laboratory. All rights reserved. EnergyPlus is a trademark of the US Department of Energy.

This documentation is made available under the EnergyPlus Open Source License v1.0.