ws-calendar message

Subject: [OASIS Issue Tracker] Created: (WSCALENDAR-127) The use ofiCalendar to schedule device services across a large domain of buildings(or equipment within a building) could have the unintended effect of loadsynchronization.

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: ws-calendar@lists.oasis-open.org
Date: Tue, 30 Nov 2010 17:07:15 -0500 (EST)

The use of iCalendar to schedule device services across a large domain of buildings (or equipment within a building) could have the unintended effect of load synchronization. 
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: WSCALENDAR-127
                 URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-127
             Project: OASIS Web Services Calendar (WS-Calendar) TC
          Issue Type: Bug
          Components: schema
    Affects Versions: cd01
         Environment: PAP04 WS-Calendar Review John Ruiz
            Reporter: Toby Considine
            Assignee: Toby Considine


I have one architecturally significant comment to this document.  The use of iCalendar to schedule device services (for example the specification identifies Demand Response as a possible application) across a large domain of buildings (or equipment within a building) could have the unintended effect of load synchronization.  For example, if a DR event is delivered with iCalendar to 1,000,000 buildings and set to end at 5pm, there is the possibility that the entire reduced load comes back online at exactly 5pm, causing a demand spike and potential grid instability.  I would have thought that there would be a randomization interval provided as an optional element of the Interval time segment (or part of the performance attributes) to prevent this type of occurrence.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira