[OASIS Issue Tracker] Updated: (WSCALENDAR-459) Randomize parameterrequested

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/WSCALENDAR-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated WSCALENDAR-459:
-----------------------------------

    Resolution: Won't fix. TC determined that this is not in scope, can be communicated already  (was: Won't fix. TC feels not in scope, can be communicated already)

> Randomize parameter requested
> -----------------------------
>
>                 Key: WSCALENDAR-459
>                 URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-459
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: New Feature
>         Environment: Frances Cleveland and Marty Burns
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>
> WS-Calendar Version 1.0
> Committee Specification Draft 04 /
> Public Review Draft 03
> The Issue
> There is a need for randomization support in the WS-CALENDAR standard that is currently absent. We present some principle reasons why this is needed and provide a simple but powerful solution.
> Discussion
> The numbers of interconnected DER systems are increasing rapidly. The advent of decentralized electric power production is a reality in the majority of power systems all over the world, driven by many factors:
> •	The need for new sources of energy to mitigate the heavy reliance on externally-produced fossil fuels.
> •	The requirements in many countries and US states for renewable portfolios that have spurred the movement toward renewable energy sources such as solar and wind, including tax breaks and other incentives for utilities and their customers.
> •	The development of new technologies of small power production that have made, and are continuing to improve, the cost-effectiveness of small energy devices.
> •	The trend in deregulation down to the retail level, thus incentivizing energy service providers to combine load management with generation and energy storage management.
> •	The increased demand for electrical energy, particularly in developing countries, but also in developed countries for new requirements such as Electric Vehicles (EVs).
> •	The constraints on building new transmission facilities and increasing environmental concerns that make urban-based generation more attractive. 
> These pressures have greatly increased the demand for Distributed Energy Resources (DER) systems which consist of both generation and energy storage systems that are interconnected with the distribution power systems.
> DER systems challenge traditional power system management. These increasing numbers of DER systems are also leading to pockets of high penetrations of these variable and often unmanaged sources of power which impact the stability, reliability, and efficiency of the power grid. No longer can DER systems be viewed only as "negative load" and therefore insignificant in power system planning and operations. Their unplanned locations, their variable sizes and capabilities, and their fluctuating responses to both environmental and power situations make them difficult to manage, particularly as greater efficiency and reliability of the power system is being demanded.
> At the same time, DER devices could become very powerful tools in managing the power system for reliability and efficiency. The majority of DER devices use inverters to convert their primary electrical form (often direct current (dc) or non-standard frequency) to the utility power grid standard electrical interconnection requirements of 60Hz (or 50Hz) and alternating current (ac). Not only can inverters provide these basic conversions, but inverters are also very powerful devices that can readily modify many of their electrical characteristics through software settings and commands, so long as they remain within the capabilities of the DER device that they are managing and within the standard requirements for interconnecting the DER to the power system.
> DER systems are becoming quite "smart" and can perform autonomously according to pre-established settings. They can "sense" local conditions of voltage levels, frequency deviations, and temperature, and can receive broadcast emergency commands and pricing signals, which allow them to modify their power and reactive power output. They can also operate according to schedules or in response to direct control commands.
> Given these ever more sophisticated capabilities, utilities and energy service providers (ESPs) are increasingly desirous (and even mandated by some regulations) to make use of these capabilities to improve power system reliability and efficiency.
> The IEC 61850-90-7 states as a requirement "there is a time-window randomization that requires DERs to respond to commands using a random number within the time window to actually initiate the command. This staggers the responses and prevents sharp jumps whenever a new command/request/pricing signal is broadcast."
> Therefore, a capability is required to provide an indication that randomized responses are required and a time window within which the end device will create a random "start response".
> The Solution
> We provide this background to emphasize the need for a randomization capability for any general scheduling model to be utilized in conjunction with distributed energy resources. We have reviewed the current draft of the WS-CALENDAR standard and find that support for this essential capability is not present now, but would be almost trivial to add. We propose the following modification to the standard as follows:
> Section "3.2.2 Tolerance: What is Timely Performance" in the standard provides a number of modifiers for the interpretation of time references in the WS-CALENDAR schedules. For example, the Start Before Tolerance allows a specification for a tolerance for earlier than scheduled starts. Similar specification constraints are added including: Start After Tolerance, End Before Tolerance, End After Tolerance ...
> We suggest that the addition of one additional attribute will complete the list of tolerance statements to enable explicit randomization capability:
> Random	Given all other constraints in the tolerance element list, the duration given for Random implies the need to randomize the event time within this parameter. There shall be equal probably of any value based on the granularity and the Random period.
> This modifier is simply added to the schema as:
> <xs:complexType name="ToleranceValueType" mixed="false">
>    <xs:annotation>
>    <xs:documentation xml:lang="en">
>          A tolerance value is a set of durations which indicate the allowed
>          tolerance for the indicated value, e.g. startafter=PT5M indicates that
>          5 minutes late is acceptable. 
>    </xs:documentation>
>    </xs:annotation>
>    <xs:sequence>
>       <xs:element name="startbefore" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="startafter" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="endbefore" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="endafter" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="durationlong" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="durationshort" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="granularity" type="xcal:DurationValueType" minOccurs="0" maxOccurs="1"/>
>       <xs:element name="random" type="xcal:DurationValueType" minOccurs="0"/>
>    </xs:sequence>
> </xs:complexType>

-- 
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