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


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

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

Subject: [OASIS Issue Tracker] (ENERGYINTEROP-705) General Recommendations

     [ https://issues.oasis-open.org/browse/ENERGYINTEROP-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-705:
    Assignee: Toby Considine  (was: William Cox)

> General Recommendations
> -----------------------
>                 Key: ENERGYINTEROP-705
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-705
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Donald Hammerstrom https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00008/2111DJH_CTS_Review.pdf
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>            Priority: Major
>              Labels: ARCH-CONF
>             Fix For: ctsWD16
> Here is a summary of how CTS might be modified to extend its applicability to the future cases discussed in this white paper:
> 1. Select and use a sign convention that will allow electricity quantity to be consistently expressed as a signed quantity.
> 2. Consider the practice of supporting sets of price/quantity pairs (i.e., vertices) to approximate the functional relationships between price and quantity in a single time interval. This would be a natural extension to CTS, which currently supports a single price/quantity pair.
> 3. Specify a price (e.g. â) to indicate inflexibility. The pairing of this indication with a quantity would thereby represent a constant, inflexible supply or demand quantity. Upon completing this extension, the use of existing baseline quantities can become a design option rather than implied necessity. Regardless, documentation should not be silent concerning this current limitation of CTS to only flexible supply and demand components, which implies the need for a baseline apart from CTS.
> 4. CTS appears to be silent concerning the effects of location. While it is claimed that locational impacts are in scope, it is not clear that an Actorâs circuit location must be communicated.
> See attachment (URI in environment) for graphics

This message was sent by Atlassian Jira

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