Consultation has been postponed until further notice.
Stakeholder Update | December 9, 2024
The AESO thanks all stakeholders for their participation the Market Tools User Group. While the announcement of the Restructured Energy Market (REM) interrupted our plans to improve our existing market interfaces, all of your excellent feedback provided participant-focused requirements that we are carrying into the tools development process in support of the REM. Once the market changes and accompanying solutions have settled, the user group will return to ensure market participants continue to have a voice in the evolution of our market tools. In the meantime, stay connected to the REM engagement and subscribe to the AESO stakeholder newsletter for the latest updates. The REM tools implementation team will be connecting with our participants during the process to present the new interfaces and support you all in updating your tools and processes.
Purpose
The purpose of this engagement is to better understand the operational needs of AESO market tool users. We will establish and work with a market tools user group* to build this understanding, improve and evolve our market tools. *For the purposes of this engagement, a “user group” is defined as the community of users of a software solution.
Scope
The scope of this engagement will be focused on all software solutions the AESO provides to support and enable market tools to market participants.
Stakeholder Update | December 9, 2024
The AESO thanks all stakeholders for their participation the Market Tools User Group. While the announcement of the Restructured Energy Market (REM) interrupted our plans to improve our existing market interfaces, all of your excellent feedback provided participant-focused requirements that we are carrying into the tools development process in support of the REM. Once the market changes and accompanying solutions have settled, the user group will return to ensure market participants continue to have a voice in the evolution of our market tools. In the meantime, stay connected to the REM engagement and subscribe to the AESO stakeholder newsletter for the latest updates. The REM tools implementation team will be connecting with our participants during the process to present the new interfaces and support you all in updating your tools and processes.
Purpose
The purpose of this engagement is to better understand the operational needs of AESO market tool users. We will establish and work with a market tools user group* to build this understanding, improve and evolve our market tools. *For the purposes of this engagement, a “user group” is defined as the community of users of a software solution.
Scope
The scope of this engagement will be focused on all software solutions the AESO provides to support and enable market tools to market participants.
ETS and ADaMS Narrated Presentations | October 2022
Market Tools User Group has finished this stage
Stakeholder Consultation | March 27, 2023
Market Tools User Group has finished this stage
Present recap of 2022 activities and engage stakeholders on plans for first half of 2023.
API Prioritization Exercise | April 17 - June 16 2023
Market Tools User Group has finished this stage
Requesting stakeholder feedback to help plan the rollout of web APIs for the ADaMS and ETS tools.
API Prioritization Exercise Stakeholder Feedback | July 2023
Market Tools User Group has finished this stage
The AESO will share a summary of the stakeholder feedback received through the API Prioritization Exercise by end of July 2023 through a narrated presentation
APIs to be released | by end of 2023
Market Tools User Group has finished this stage
AIES Generation Capacity API (which includes Mothball data) | July 2023
Azure API Gateway Implementation (foundation for ADaMS and ETS) | in progress
The Load Outage API will utilize the Azure gateway | early Q4, 2023
Stakeholder Update | Q4 2023
Market Tools User Group has finished this stage
Next set of actions scheduled will be announced
End of year wrap-up
Postponed until further notice.
Market Tools User Group is currently at this stage