OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

smartgrid-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [smartgrid-discuss] Whither Grid Standards


I'm glad to hear that there is a desire to create TCs that may set
standards eventually.

While I may be of some help in determining the answers to business
questions, my interest is specifically in the security of the systems.
Clearly, WS-Security has addressed many fundamental issues, but there
is still a big gap between business requirements and the low-level
protocols that secure data and systems.  I hope to help in bridging
those gaps.

Count me in to bring that perspective to the discussion & TCs.

Arshad Noor
StrongAuth, Inc.

Considine, Toby (Campus Services IT) wrote:
> Clearly the point of an OASIS Discussion Group is to see if there is sufficient interest to form the focused TCs. I am particularly interest in WS-Calendar (or whatever) as I think that we can get it off the ground and completed quickly. oBIX has gotten about half way there, but I fear a component of a control system standard will not be picked up elsewhere (for social reasons). 
> 
> oBIX needs it because a significant component of enterprise responsiveness is letting building systems easily receive scheduling information from business programs. Most of us regularly invite 7 people and a room to a meeting. If the "room calendar" could inform the building systems to be ready on time, and to ventilate for 8 people, more efficient operations would result. We have all been in conference rooms that are freezing with 4 people in attendance, and sleepy when 15 are in attendance...
> 
> There are some remaining issues in such a standard. Do I put my performance contract inside the Calendar (as a meeting is) or outside but within the same payload? Would I refer to one, or several, oBIX contracts from within the Calendar? Could contracts refer to one or several calendar items? It seems to me that the same issues would come up if the calendar was part of a BPEL, or part of OpenADR, or even part of WSDM. 
> 
> In all cases, though, the issue is "Be ready at 10:00 for xxx and keep ready until 11:00". This puts responsibility for ramp-up time (or ramp-down time, for DR) in the agent, which strikes me as the SOA way to do things...
> 
> As to other TCs:
> 
> Well, let the discussions begin.
> 
> 
> "A man should never be ashamed to own that he has been in the wrong, which is but saying ... that he is wiser today than yesterday." -- Jonathan Swift
> 
> Toby Considine
> Chair, OASIS oBIX TC
> Facilities Technology Office
> University of North Carolina
> Chapel Hill, NC
>   
> Email: Toby.Considine@ unc.edu
> Phone: (919)962-9073 
> http://www.oasis-open.org 
> blog: www.NewDaedalus.com
> 
> 
> 
> -----Original Message-----
> From: Arshad Noor [mailto:arshad.noor@strongauth.com] 
> Sent: Sunday, December 07, 2008 8:47 PM
> To: Toby Considine
> Cc: smartgrid-discuss@lists.oasis-open.org
> Subject: Re: [smartgrid-discuss] Whither Grid Standards
> 
> Nice vision, Toby.
> 
> However, do your see these discussions materializing focused
> Technical Committees (TC) that create standards for these
> problems, or just discuss issues?
> 
> Arshad Noor
> StrongAuth, Inc.
> 
> Toby Considine wrote:
>> To start things off, I am sending my blog from tonight to this 
>> discussion group.
>>
>> tc
>>
>> Whither Grid Standards
>>
>> On last Friday's phone call about advancing the OpenADR specification to 
>> a national and perhaps international standard, we agreed to continue the 
>> discussion in an open forum at the OASIS site (www.OASIS-Open.org 
>> <http://www.oasis-open.org/>). OASIS, or the Organization for the 
>> Advancement of Structured Information Standards, has long been the home 
>> for the underpinnings of e-commerce, for web security, and for service 
>> oriented architecture. OASIS is also home to a number of domain-specific 
>> standards, such as LegalXML, Open Office, and OpenDocs as well as the 
>> foundational web services registry UDDI (Universal Description, 
>> Discovery, and Integration).
>>
>> OpenADR (Automated Demand Response) is a California developed 
>> specification developed for the regulated electricity providers in that 
>> state. Demand-Response (DR) refers to live negotiations between the grid 
>> and its end nodes (buildings) to reduce demand before a shortfall causes 
>> problems. DR is a very important first step on the road to transacted 
>> energy, and solves some big problems in the short term.
>>
>> One effect pulling OpenADR to OASIS is a perception that it is largely 
>> an economic transaction. The end nodes of the power grid contain far too 
>> diverse a mix of systems for grid operators to control well. As Gale 
>> Horst, who works in the Whirlpool Corporation Research & Engineering 
>> Center, has observed, a washing machine cannot respond to a grid request 
>> to shed [electrical] load unless it determines that the grid unless it 
>> has determined that there is no bleach in its current load of laundry. 
>> Every system in a home or business has similar rules that matter within 
>> its own domain. For all but the smallest response, DR will require an 
>> economic incentive and decisions from the agents running all the systems.
>>
>> Even before OpenADR began discussions within the OASIS framework, a 
>> number of standards potentially useful to the new intelligent grid were 
>> underway. oBIX created a specification normalizing the operations and 
>> reporting of control systems as web services. The WS-DD and WS-DP 
>> committee, standardizing web services for device discovery and device 
>> profiles, includes members not just from software and printer makers, 
>> but from a maker of electrical switch gear as well.
>>
>> There may be several of what I call micro-specifications that come out 
>> of this. As far as I know, there is still no standard way to exchange 
>> scheduling via web services as there is ICALENDAR in email. Such a 
>> specification would be useful not only for transmitting schedules from 
>> OpenADR to building systems managed by oBIX, but would be useful in 
>> forward pricing of power generally. It would also be useful in a number 
>> of other standards, such as BPEL (Business Process Execution Language).
>>
>> Emergency signaling is an important area or work within OASIS. One 
>> critical area is standardization of location. These standards include 
>> addresses, geographic points, and geographic territories bounded within 
>> a closed polygon. DR specifically, and utilities in general need the 
>> same information. When a DR aggregator reports the commitments he has 
>> received up to the System Operator, the operator would like the 
>> information aggregated by territory. New standards for emergency 
>> communications anticipate buildings submitting alarms directly into 911 
>> queues. Components of the power grid could do the same, notifying police 
>> to increase patrols in blackout areas and to send officers to direct 
>> traffic. It would be very useful for the power grid and for emergency 
>> response to use the same standards.
>>
>> New business models will encourage a move from hierarchical command and 
>> control operations to symmetrical peer to peer negotiations on the power 
>> grid. Renewable energy sources will decrease reliability. Distributed 
>> generation will create more power sources not under the control of 
>> traditional utilities. Zero Net Energy buildings will make each end node 
>> both a buyer and seller of power. OASIS standards such as WSDM (Web 
>> Services Distributed Management) may find a place in the new grid.
>>
>>  The panoply of WS-Security standards, including federated identity 
>> management, would require more room than I have here - but OASIS is 
>> their home.
>>
>> There is no replacement for the IEEE and IEC standards at the core of 
>> deep control; increasingly, we will have interactions that are more arms 
>> length and economic than that.
>>
>> To join the smartgrid-discuss@lists.oasis-open.org 
>> <mailto:smartgrid-discuss@lists.oasis-open.org> list, send email to 
>> smartgrid-discuss-subscribe@lists.oasis-open.org 
>> <mailto:smartgrid-discuss-subscribe@lists.oasis-open.org>. The list is 
>> open to all, and there is no commitment to join OASIS or participate in 
>> a technical committee implied. For a general discussion of applying 
>> e-commerce standards to new energy, you may be interested in reading 
>> http://www.oasis-open.org/resources/white-papers/blue/
>>
>> ________________________________________
>> "When one door closes, another opens; but we often look so long and so 
>> regretfully upon the closed door that we do not see the one which has 
>> opened for us." -- Alexander Graham Bell
>> ________________________________________
>> Toby Considine
>> Chair, OASIS oBIX TC http://www.oasis-open.org
>> Co-Chair, OASIS Technical Advisory Board
>> Toby.Considine@gmail.com <mailto:Toby.Considine@gmail.com>
>> TC9, Inc
>> Phone: (919)619-2104
>> blog: www.NewDaedalus.com <http://www.NewDaedalus.com>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: smartgrid-discuss-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: smartgrid-discuss-help@lists.oasis-open.org
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]