Re: [recipe] Energy reduction / static management / dynamic management

Chris Lonvick <> Thu, 26 March 2009 13:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C269B3A63EB for <>; Thu, 26 Mar 2009 06:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Wl1kGPv+DiLR for <>; Thu, 26 Mar 2009 06:43:51 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B3D963A684B for <>; Thu, 26 Mar 2009 06:43:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.38,426,1233532800"; d="scan'208";a="274555387"
Received: from ([]) by with ESMTP; 26 Mar 2009 13:44:45 +0000
Received: from ( []) by (8.12.11/8.12.11) with ESMTP id n2QDijsv021477; Thu, 26 Mar 2009 06:44:45 -0700
Received: from ( []) by (8.13.8/8.13.8) with ESMTP id n2QDijjA008483; Thu, 26 Mar 2009 13:44:45 GMT
Date: Thu, 26 Mar 2009 06:44:45 -0700 (PDT)
From: Chris Lonvick <>
To: Stuart Cheshire <>
In-Reply-To: <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2986; t=1238075085; x=1238939085; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;;; z=From:=20Chris=20Lonvick=20<> |Subject:=20Re=3A=20[recipe]=20Energy=20reduction=20/=20sta tic=20management=20/=20dynamic=20management |Sender:=20; bh=j6eVM6xUGj+lz+udENQ6dA/KmVdwi5I9G4LHsImrKJ0=; b=YmzYy8a3BwjYRhHbGADSqY1eLgGrg9CjRG5SEwynWYcELnuiIKgG0vlBiV FDnpCEIKBq3DaXmhfkZ/Hrkg8g/EbAwnkdkAyTFlCByBdzOgaled76PBWQO0 xPtmv6n55+rAA8sI86jSwd8TgFukGMsAGBevzLjOzUXYao/Hfut1s=;
Authentication-Results: sj-dkim-1;; dkim=pass ( sig from verified; );
Subject: Re: [recipe] Energy reduction / static management / dynamic management
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Mar 2009 13:43:52 -0000


I'm sorry that I couldn't make it.  Many thanks for the notes.

Theme (3) is being worked on by the OpenADR (Open Automated Demand 
Response) Communication Standard group.
They have had several successful field trials.


On Thu, 26 Mar 2009, Stuart Cheshire wrote:

> Some quick thoughts after tonight's dinner:
> Here are three (certainly not the only three) broad themes we might want to 
> think about.
> 1. Simple reduction of absolute energy usage. There are two aspects to this, 
> measurement and control.
> 1a. Measurement -- allowing people to determine where energy is going in 
> their homes. This alone is an important part of enabling people to save 
> energy, by knowing where they're using energy. The first step to replacing 
> your refrigerator with a more efficient one is discovering that your current 
> refrigerator is using too much energy. I'd like to see a world where every 
> power outlet or light switch includes a power meter, which can be 
> interrogated over the network to find out how much power is being drawn from 
> it at any moment.
> 1b. Control. For example, using less energy by automatically turning off 
> lights in unoccupied rooms. Here the theme is not more efficient devices, but 
> less use of the devices you have.
> 2. Time-sensitive use of energy. When the electricity company charges more 
> for peak-time usage, signaling refrigerator compressors, air conditioning, 
> hot tub heating, electric car charging, and similar high-load devices to try 
> to limit their consumption during peak time can reduce the peak load on the 
> electricity grid, and reduce the customer's electricity bill, even though the 
> total energy consumption may be the same. The difference here is that you're 
> not trying to reduce your hot tub heater's total energy consumption, you're 
> trying to control *when* it consumes that energy.
> 3. Dynamic adaptation to current spot pricing. This is an extension of (2). 
> Whereas in (2) the peak and off-peak hours for each day of the week are 
> published well in advance, with spot pricing the instantaneous price of one 
> kWh is not published in advance, but instead is announced in an hour-by-hour 
> or even minute-by-minute basis, according to current demand. The difference 
> between this and case (2) is that case (2) can be handled entirely within the 
> home, by simply entering the peak/off-peak hours manually into some 
> controller, but case (3) would require active communication with the 
> electricity company to determine the current price, which is a larger 
> challenge.
> Stuart Cheshire <>
> * Wizard Without Portfolio, Apple Inc.
> * Internet Architecture Board
> *
> _______________________________________________
> recipe mailing list