> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/workflows/energy-efficiency/specification-44/appliances.md). # Appliances Where alternative heat loads are required, these may potentially displace the heat loads provided in the H6V2 Verification methodology. This approach allows for more specific calculations tailored to actual building conditions and equipment specifications. The table below provides general data on common appliances, including their annual energy consumption values, product reference details, energy star ratings, and the assumed weekly usage frequency used during testing. These values can serve as a starting point for heat load analysis and, through further optimisation strategies, can assist in reducing the overall heating loads within a space. By understanding the actual energy consumption patterns and heat contributions from various appliances, designers can make more informed decisions about heating and cooling demand implication.

Appliance	1 Year Energy Cost	Product Reference	Energy Star Rating	Uses per week
Clothes Dryer	144 kWh	Euromaid Model: EHPD700W - Link	6	1
Clothes Washer	185 kWh	BOSCH Model: WGG254Z0AU	5.5	7
Computer Monitor	82 kWh	HP Model: HSTND-9221-A , L7010t	6	70
Dishwashers	111 kWh	V-ZUG Model: 41082	6	7
Fridges and freezers	151 kWh	Smeg Model: FAB28RDP9176	6	168
Televisions	190 kWh	FFALCON Model: FF50RU62	6	70

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.betterbuilding.io/user-guide/workflows/energy-efficiency/specification-44/appliances.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.