Science Score: 57.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 3 DOI reference(s) in README
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (7.8%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Basic Info
  • Host: GitHub
  • Owner: we3lab
  • License: mit
  • Language: Jupyter Notebook
  • Default Branch: main
  • Size: 9.72 MB
Statistics
  • Stars: 0
  • Watchers: 6
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created over 1 year ago · Last pushed 7 months ago
Metadata Files
Readme License Citation

README.md

dr-programs

Data Records

Data in this repository consists of metadata (1 CSV file) and program data (1 CSV file):

Metadata - program_parameters.csv

Program Data - usprogramparameters.csv

Metadata

Metadata is stored in two CSV files, one with program parameters and one with simulation parameters. Each parameter takes up one row. - Minimum number of event days (min_days): The minimum number of days the program event is called for a customer per month - Maximum number of event days (max_days): The maximum number of days the program event is called for a customer per month - Minimum duration of event (min_dur): The event should last for more than the minimum duration specified by the program - Maximum duration of event (max_dur): The event should not last longer than the maximum duration specified by the program - Program start time (start_time): The program can be either 24 hours or last for a specified period of time and the start time is generally provided if it is not a 24-hour period - Program end time (end_time): The program can be either 24 hours or last for a specified period of time and the end time is generally provided if it is not a 24-hour period - Maximum Events (max_events): Maximum number of events that can be called in a season - Maximum event hours (max_hours): Maximum total hours of all events called in a year - Events per day (events_daily): The maximum event that a customer can provide on a single day. - Maximum consecutive event days (max_consec): The maximum consecutive days the customer can be called in a particular month - Notification type (notif_type): The event is generally notified the day before or the day of and is captures by this parameter - Notification time (notif_time): If the event is notified the day before or the day of the program generally specifies the time. Note: This can also be historic event related - Notification time delta (notif_delt): The number of hours between the notifcation time and the beginning of an event - Baseline calculation method (base_method): The method used by each program to calculate the baseline energy usage - Presence of historic data (hist_pres): Programs may or may not have historic data present - Payment function (pay_function): Form of compensation for shifts in energy load (or being available to shift energy loads) when called upon - Region (region): The United States Department of Energy separates the states into the West Region, The Southeast and Midwest Region, and the Northeast Region - Days of the Week (dow): Which days of the week can events fall on? - Season (season): Some programs run during the summer, winter, or both - Eligibility (elig): Eligibility to participate in the program (minimum bids, minimum peak demand, etc.) - Company (comp): Which company or companies offer this program - Start month (sm): Month during which the DR event season starts - End month (em): Month during which the DR event season ends - State (state): State in which the program is eligible - Utility (util): Eligible utilities - Trigger (trigger): Event trigger type - Eligible load type (load): What type of load is eligible for participation in the program - Program or rate (program_rate): Classification as a program or a rate by the Department of Energy - Payment Function (function_pay): Function for calculating payment after an event - Baseline Function (function_base): Function for calculating baseline - Delivered Ratio (delivered ratio): = amount reduced/nomination of delivery - Amount reduced: baseline - consumption - Inclusion of weekends (weekends): Does the baseline calculation include weekends or not? - Inclusion of holidays (holidays): Does the baseline calculation include holidays or not? - Inclusion of previous events (prev_events): Does the baseline calculation include previous events or not? - Baseline hours (base_hours): Time of day during which load measurements can be taken for baseline calculation - Range Value (range_val): Number of load measurements taken at a certain frequency for baseline calculation - Range Resolution (range_res): Frequency of load measurement for baseline calculation - Date Range (base_dates): Dates during which load measurements are taken for baseline calculation - Function (function): Function applied to load measurement for baseline calculation - Firm Level Demand (firm_level): Load level that companies are expected to reduce their load to (alternative to baseline)

Program Data

There are 138 individual programs from 45 states and Washington D.C. States not present include Kansas, Nevada, Wyoming, Maine,and Louisiana. Program data includes entries for each parameter outlined in the metadata for each program. Entries of "n/a" indicate that parameter information is unavailable for that program.

This data can be used to calculate incentive payment for simulated demand response events using a generalizable baseline function and payment function. The baseline function is used to calculates the reference energy usage program particpants must reduce their load from to receive incentives. The Payment function will use the baseline energy usage, load reduction, and incentive payment rate to calculate payment awarded for a demand response event.

Methods

To create this dataset, the U.S. DOE Federal Energy Management Program's Demand Response and Time-Variable Pricing website, which listed and described energy management programs across the united States, was referenced.

First, program parameters were defined. These parameters characterize each program by their distinct features. These parameters can be found in program_parameters.csv in the metadata file.

Next, programs were populated in the dataset along with their parameters (if available) and a url link to the program source/website.

The dataset, after being populated, was cross-checked with the U.S. DOE Federal Energy Management Program's Demand Response and Time-Variable Pricing Programs Search.

Simulation Parameters

Simulation parameters can be used to characterize simulated demand response events with the demand response simulator.

References & Acknowledgements


Demand response and time-variable pricing programs and rates | Department of Energy. (n.d.). https://www.energy.gov/femp/articles/demand-response-and-time-variable-pricing-programs-and-rates

Citations


If you want to use this work, please cite using

David, E., Sakthivelu, A., Rao, A., and Mauter, M. (2025). US incentive based demand response program parameters. Version 2. Stanford Digital Repository. Available at https://purl.stanford.edu/ck480bd0124/version/2. https://doi.org/10.25740/ck480bd0124.

In BibTeX format:

@misc{david2024us, author={David, Eres and Sakthivelu, Adhithyan and Rao, Akshay K. and Mauter, Meagan S.}, title={US incentive based demand response program parameters}, publisher={Stanford Digital Repository}, year={2024}, month={Dec}, day={17}, version={2}, doi={10.25740/ck480bd0124}, url={https://purl.stanford.edu/ck480bd0124/version/2} }

Owner

  • Name: we3lab
  • Login: we3lab
  • Kind: organization

Citation (CITATION.cff)

cff-version: 1.2.0
authors:
  - family-names: "David"
    given-names: "Eres"
    orcid: "https://orcid.org/0009-0007-7290-6150"
  - family-names: "Sakthivelu"
    given-names: "Adhithyan"
    orcid: "https://orcid.org/0000-0002-3826-8112"
  - family-names: "Rao"
    given-names: "Akshay K."
    orcid: "https://orcid.org/0000-0002-9054-476X"
  - family-names: "Mauter"
    given-names: "Meagan S."
    orcid: "https://orcid.org/0000-0002-4932-890X"
title: "US incentive based demand response program parameters"
doi: 10.25740/ck480bd0124
version: 2
date-released: 2024-12-17
type: dataset
message: "If this dataset has been useful in your research, we encourage you to cite it using the provided metadata."
url: "https://purl.stanford.edu/ck480bd0124/version/2"
publisher:
  name: "Stanford Digital Repository"

GitHub Events

Total
  • Delete event: 1
  • Push event: 27
  • Pull request event: 5
  • Create event: 4
Last Year
  • Delete event: 1
  • Push event: 27
  • Pull request event: 5
  • Create event: 4

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 0
  • Total pull requests: 3
  • Average time to close issues: N/A
  • Average time to close pull requests: 21 days
  • Total issue authors: 0
  • Total pull request authors: 2
  • Average comments per issue: 0
  • Average comments per pull request: 0.0
  • Merged pull requests: 2
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 3
  • Average time to close issues: N/A
  • Average time to close pull requests: 21 days
  • Issue authors: 0
  • Pull request authors: 2
  • Average comments per issue: 0
  • Average comments per pull request: 0.0
  • Merged pull requests: 2
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • ThyanRevolter (2)
  • fletchapin (1)
Top Labels
Issue Labels
Pull Request Labels