Skip to content

Team-Nando/OE2-Asset_Capacity

Assessment of Operating Envelopes to Orchestrate DERs - OE Algorithm 2: Asset Capacity

This repository is part of the project Assessing the Benefits of Using Operating Envelopes to Orchestrate DERs Across Australia funded by CSIRO. This project provided key metrics and recommendations for distribution companies (known as Distribution Network Service Providers [DNSPs] in Australia) and AEMO (the Australian system operator) to assist them in their decision-making process when defining the most suitable Operating Envelope (OE) implementations in a given distribution area.

In this repository, we use interactive code via Jupyter Notebook and Python as well as a realistic residential low voltage (LV) network to demonstrate the process and necessary calculations for the Asset Capacity OE Algorithm produced by The University of Melbourne. This demonstration is useful for different stakeholders (e.g., DNSPs, AEMO, CSIRO, regulators, consultancy companies, technology providers) as it can help them familiarise with the corresponding algorithm and the required inputs as well as the pros and cons.

Asset Capacity OE

The Asset Capacity OE is the simplest OE implementations investigated in the project. At a given moment in time, it only considers the spare thermal capacity of the distribution transformer (i.e., thermal capacity minus net demand of all the customers) and splits it among active customers. It is the least accurate OE approach as it does not consider voltage aspects.

  • Required Monitoring: At the secondary of the transformer (aggregated P and aggregated Q per phase).
  • Required Electrical Models: None.

For simplicity, the case study used to demonstrate the OE algorithm corresponds to a low voltage (LV) network without modelling the upstream high voltage (HV) network. Although some adaptations have been made to ensure realistic voltage fluctuations at the distribution transformer of the LV network, the results are not exactly the same as those presented in the Final Report of the project (which used an integrated HV-LV network model). Nevertheless, the behaviour of the OE algorithm and the qualitative nature of the results remain the same.

Run the Code

Choose one of the options below to run the code.

A. Cloud Option ☁️: Google Colab

Just click on the badge . You don't need to install anything 🤓💪.

B. Local Option 💻: Jupyter Notebook

Make sure you have installed all the pre-requisites (Anaconda, dss_python, requirements). Otherwise, you will not be able to go through the repository.

  1. Download all the files using the green <> Code button at the top right.
    • You will get a ZIP file with a folder that contains all the files.
    • Unzip the file and place the folder somewhere on your computer/laptop.
  2. To open the Jupyter Notebook file (extension ipynb) you need to:
    • Open Anaconda Navigator
    • Click on Launch Jupyter Notebook (it will open in your browser)
    • Upload the unzipped folder (with all the corresponding files) to Jupyter Notebook (the location is up to you)
    • Go inside the folder and open the ipynb file

All the instructions will be in the ipynb file.

Credits

Arthur Gonçalves Givisiez ([email protected])
Andres Avila Rojas ([email protected])
Nando Ochoa ([email protected] ; https://sites.google.com/view/luisfochoa)

Licenses

Since this repository uses dss_python which is based on OpenDSS, both licenses have been included. This repository uses the BSD 3-Clause "New" or "Revised" license. Check all corresponding files (LICENSE-OpenDSS, LICENSE-dss_python, LICENSE).

About

No description, website, or topics provided.

Resources

License

BSD-3-Clause and 2 other licenses found

Licenses found

BSD-3-Clause
LICENSE
Unknown
LICENSE-OpenDSS
BSD-3-Clause
LICENSE-dss_python

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published