energyinterop — archive

Feedback proposals and questions

From: William Cox <[email protected]>
To: [email protected]
Date: Wed, 14 Sep 2011 03:18:00 -0000

Ed, Gerry, and all -- Yes, in broad strokes that's the approach. The metaphor is multiple stream of intervals flowing from the future into the past. Feedback including energy and power, prices, baselines, and more. They need a consistent approach, but have varying payloads in the attachment. The Historical/Present/Future (H/P/F) approach envisions projections becoming more accurate projections becoming actual recorded information as the interval moves from the future to the past. More in the morning - I'm going to sleep on the draft (not literally) and finish before the meeting. Thanks! bill -- William Cox Email: [email protected] Web: http://www.CoxSoftwareArchitects.com +1 862 485 3696 mobile +1 908 277 3460 fax On 9/13/11 5:17 PM, Koch, Edward wrote: 4E5F8FDF186E2E42A40243DCF2EA68E703029999@DE08EV1005.global.ds.honeywell.com type= cite > I don't want to be too presumptuous as to what Bill is doing, but I believe that yes the calendar object that has the attached values is part of the feedback message just like baselines and DR signals are. From: Gerald Gray [ mailto:[email protected] ] Sent: Tuesday, September 13, 2011 12:57 PM To: Koch, Edward; [email protected] Subject: RE: [energyinterop] Feedback proposals and questions Hi Ed, I like what you have hear Ed. I your proposed change to the service operation patterns, are we assuming then that the calendar info is/would come back on any feedback request so we don't need a separate interaction just to get schedules? If so, then I agree with this change. Gerald R. Gray, PhD <mailto:[email protected]> <http://www.guiding-principle.com/> cell: 517.455.4824 fax: 517.913.6024 From: Koch, Edward [ mailto:[email protected] ] Sent: Tuesday, September 13, 2011 3:37 PM To: [email protected] Subject: [energyinterop] Feedback proposals and questions Enclosed is a document that we can use as in our meeting tomorrow morning to discuss Feedback. Bill and I split up the work. He is working on the calendaring mechanisms for attaching feedback values and I am working on the feedback attributes and interaction patterns. Enclosed is a document with my proposed changes and questions for the group. In general I did the following: - Enumerated some working assumptions and overall requirements - Made a minor refactor to group together attributes of a like nature for better readability. - Added a couple of new attributes - Created a datatype that can be used to instantiate values and attach to calendar objects. - Proposed some changes to the operations and their interaction patterns. - Added more documentation to existing attributes The enclosed document illustrates those changes and poses some open questions that we can discuss in our meeting tomorrow. Thanks, -ed Koch