Re: [eman] eman framework issue: How to model a meter?
"John Parello (jparello)" <jparello@cisco.com> Tue, 20 August 2013 19:17 UTC
Return-Path: <jparello@cisco.com>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0324611E8145 for <eman@ietfa.amsl.com>; Tue, 20 Aug 2013 12:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44HZp5t2pW1v for <eman@ietfa.amsl.com>; Tue, 20 Aug 2013 12:17:04 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 46BE121F9A7E for <eman@ietf.org>; Tue, 20 Aug 2013 12:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12258; q=dns/txt; s=iport; t=1377026224; x=1378235824; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=yp8GBdNhntJQbprHVRenuOAeCA555nA77pkRgCUWsbY=; b=JTfDmv8n2zLQF0+KfImgft1flqw8nRXt4rmgEmZK6mrUQAAvfPxe4Bw+ vORkMUM1rMEDtHbY3/CS94Vxvz/pgtrqeIUg0mbBDM4hUpG16AD3qOTDZ t6HdRtyU9V/jnk0SgGCsrYabHpI+QXnsc0LaVbYjspvRpJKBjmNmMraLd 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj0FAETAE1KtJV2c/2dsb2JhbABXA4JBRDW3X4hLgSYWdIIkAQEBAwEBAQFrCwULAgEIDgonBycLFBECBA4FiAoGDK0+jx2BKAwEBgEJCIMKeQOXZYEtkCmDHA
X-IronPort-AV: E=Sophos; i="4.89,921,1367971200"; d="scan'208,217"; a="249625455"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 20 Aug 2013 19:17:03 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r7KJH2He015033 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 Aug 2013 19:17:02 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.176]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Tue, 20 Aug 2013 14:17:01 -0500
From: "John Parello (jparello)" <jparello@cisco.com>
To: Bruce Nordman <bnordman@lbl.gov>
Thread-Topic: [eman] eman framework issue: How to model a meter?
Thread-Index: AQHOnXyq7tpuq+6Q/0CDBwtkFHCxz5mep8EA//+5JWSAAGKCAP//tVB9
Date: Tue, 20 Aug 2013 19:17:01 +0000
Message-ID: <BB79100D-BCE8-4D74-B47B-882BB92AF0E9@cisco.com>
References: <F9AC12FC-49D5-4CD0-886C-6AE80C442F25@quittek.at> <CE38E868.CFE88%brads@coraid.com> <3B0EE04D-E5F5-46C9-8539-E22FBEB07CE1@cisco.com>, <CAK+eDP-_MTwPaXUznAJUZWM06JmjrUdLO57CXQs5+vCEnwnR5A@mail.gmail.com>
In-Reply-To: <CAK+eDP-_MTwPaXUznAJUZWM06JmjrUdLO57CXQs5+vCEnwnR5A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_BB79100DBCE84D74B47B882BB92AF0E9ciscocom_"
MIME-Version: 1.0
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] eman framework issue: How to model a meter?
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 19:17:09 -0000
Good catch let's change "perform metering" to "perform measuring" then yes go with simple. So broad categorization of the device/component and continue to leave complex capability modeling out. Jp Sent from my iPad (expect ridiculous spelling mistakes) On Aug 20, 2013, at 11:44 AM, "Bruce Nordman" <bnordman@lbl.gov<mailto:bnordman@lbl.gov>> wrote: The current draft of the EMAN framework says: "A meter is a type Energy Object and any Energy Object can perform metering." This seems to indicate that devices can meter, components can meter, and power interfaces can meter. On the other hand, Juergen notes that the meter classification is not available to power interfaces. This appears to be a contradiction. It is possible to require declaring a "primary function" for a device, including whether it is a device that can only perform metering, but that seems to be an unnecessary complication and not derivative of any requirement. Juergen's point is that metering (or measuring--I defer on that choice of wording) can be simply and flexibly modeled as just a capability that any EO can have. It is unnecessary to make the Framework more complicated than that. There are plenty of additional complications that could be added that don't derive from any requirement. --Bruce On Tue, Aug 20, 2013 at 10:51 AM, John Parello (jparello) <jparello@cisco.com<mailto:jparello@cisco.com>> wrote: <snip> > > You ask "Do we need to model metering capability at all"? Yes, because > smart meters, in particular sub-meters, are a key part of real time energy > monitoring. > Just to be clear we used "meter" is a type of device (which acknowledges you other points, and if you want to model capability the value would be "measuring". So a "metering capability" doesn't make sense. It would be "measuring capability". Again we removed the capabilities attribute. After quite some years deploying these systems that distinction is second nature for me but we should be precise. Jp > Regards, > > Brad > > On 8/20/13 1:09 AM, "Juergen Quittek" <ietf@quittek.at<mailto:ietf@quittek.at>> wrote: > >> Dear all, >> >> Here is another framework issue: How to model metering capabilities of >> devices? >> >> Our framework draft (draft-ietf-eman-framework-08) models metering >> capability by categorizing devices and components into either a producer, >> a comsumer, a meter, or a distributor, see pseudocode on page 43. >> >> I think this approach is broken. It may be useful for modeling simple >> scenarios, but it does not work as general model. >> >> There are two problems with this approach. >> >> 1. The either-or classification. A meter is typically not just a meter, >> but as well a consumer that consumes energy when doing it's job. A PDU >> that meters power at it's outlets is a meter and a distributor and a >> consumer. The same holds for a PoE switch. These are not either meters or >> consumers, they are meters and consumers and some of them are also >> distributors at the same time. >> >> 2. The categorization as 'meter' is only available for devices and >> components, not for power interfaces. But obviously a device with >> metering capabilities meters at (some of) its interfaces. Take the PoE >> switch that meters power at some or all of its PoE outlets. It would be >> natural to label the power interfaces at which metering capabilities are >> available as 'metered'. It appears strange to classify the device as >> 'meter'. >> >> The basic question here is: Do we need to model metering capability at >> all? If yes, we should model it as an attribute, not as a category; and >> we should model it as attribute of the power interfaces as well. >> >> BTW, if we model metering capability (monitoring), we should consequently >> model circuit breaker capability (control) at power interfaces as well. >> >> Cheers, >> Juergen >> _______________________________________________ >> eman mailing list >> eman@ietf.org<mailto:eman@ietf.org> >> https://www.ietf.org/mailman/listinfo/eman > > _______________________________________________ > eman mailing list > eman@ietf.org<mailto:eman@ietf.org> > https://www.ietf.org/mailman/listinfo/eman _______________________________________________ eman mailing list eman@ietf.org<mailto:eman@ietf.org> https://www.ietf.org/mailman/listinfo/eman -- Bruce Nordman Lawrence Berkeley National Laboratory nordman.lbl.gov<http://nordman.lbl.gov> BNordman@LBL.gov<mailto:BNordman@LBL.gov> 510-486-7089 m: 510-501-7943
- [eman] eman framework issue: How to model a meter? Juergen Quittek
- Re: [eman] eman framework issue: How to model a m… Brad Schoening
- Re: [eman] eman framework issue: How to model a m… John Parello (jparello)
- Re: [eman] eman framework issue: How to model a m… John Parello (jparello)
- Re: [eman] eman framework issue: How to model a m… Bruce Nordman
- Re: [eman] eman framework issue: How to model a m… John Parello (jparello)
- Re: [eman] eman framework issue: How to model a m… Juergen Quittek
- Re: [eman] eman framework issue: How to model a m… Juergen Quittek
- Re: [eman] eman framework issue: How to model a m… Juergen Quittek
- Re: [eman] eman framework issue: How to model a m… Brad Schoening
- Re: [eman] eman framework issue: How to model a m… John Parello (jparello)
- Re: [eman] eman framework issue: How to model a m… Juergen Quittek
- Re: [eman] eman framework issue: How to model a m… Brad Schoening