Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource Model: Local Energy Price #6

Open
jjmilburn opened this issue Oct 1, 2020 · 0 comments
Open

Resource Model: Local Energy Price #6

jjmilburn opened this issue Oct 1, 2020 · 0 comments
Labels
resource model wanted Request for industry insight on how to model a given resource type

Comments

@jjmilburn
Copy link
Contributor

jjmilburn commented Oct 1, 2020

Related to, but not quite the same as demand_response.

Demand response assumes that a controlling device is able to make DRLC requests, and there isn't much bidirectional negotiation (either the demand response event is accepted, or rejected).

A 'local energy price' resource type (or set of resource types) would enable devices to automatically negotiate energy flows (on a timeframe of 10s of seconds/minutes, not appropriate for subsecond responses) similar to the scheme described by "Local Power Distribution" .

This model would introduce the notion of a 'local energy price', so that the price could be lower during the day (in a solar-powered system), encouraging devices to consume more energy during that time, and higher at night - this loadshifting can have real positive impacts on the amount of energy in/out of the battery, increasing battery lifetime.

See also: https://drive.google.com/file/d/0B8B9XW6B7prlOWI1Mk9yWWNWbVU/view

image

@jjmilburn jjmilburn added the resource model wanted Request for industry insight on how to model a given resource type label Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resource model wanted Request for industry insight on how to model a given resource type
Projects
None yet
Development

No branches or pull requests

1 participant