Search Archives
Why New Daedalus?

Daedalus was the mythical great architect and artificer of the classical world. Today, embedded intelligence is enabling the most profound changes in the way we create and use buildings since his day.

Building Intelligence meets the Intelligent Building. The Intelligent Building negotiates with the Intelligent Grid. How will this transform how we interact with the physical world?

More on the Web
Login
Powered by Squarespace
« The view from 400 miles, and 100 years away | Moving beyond Demand Response (DR) – Pricing Services »
Monday
Aug162010

EnergyStar 2.0 Interfaces and Enterprise Interaction

Earlier this month, a few of us met for the NAESB PAP10 (Energy Usage) task force to discuss EPA EnergyStar Climate Control 2.0. We met to consider how the draft affected the work going on to define a standard for communicating energy usage. The draft EPA specification describes the changing requirements for EnergyStar certification. The EnergyStar certification is aimed for the home markets. Much of the specification discussed consumer interfaces for smart thermostats. My understanding is that the proposed release of this standard is in November of this year.

What caught my eye within the specification were abstract standards for communicating with a home HVAC system. The clear direction of this work is to increase competition and speed innovation in home systems by reducing the integration costs of mixing and matching major system components, i.e., air handler, heat pump, furnace, and smart thermostat.

To me, it is clear that an abstract interface to home systems could be an abstract interface to the small commercial package system. It could also be the abstract interface to each zone in a larger commercial installation. Such an interface would “dis-integrate” commercial building systems in ways that would more easily accept floor-by-floor and even suite-by-suite system and technology upgrades.

Enterprise interfaces to building systems must allow interaction without requiring that enterprise programmers learn mechanical engineering. They must allow coordination and monitoring without letting financial and business programmers screw things up. They must be generic to let one integration work for many technologies.

Don’t look for support for this from the usual standards bodies. Many of the participants are looking to preserve existing business models and fight over scraps. Maybe a newcomer could arrive with an open API and cool enough technology to make everyone else follow.

Or maybe, it could come from outside, from an EPA standard for homes.

PrintView Printer Friendly Version

References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>