IT Release Schedule

Details of proposed changes to IESO systems and reports being revised for the current release are available here. Each release includes a preliminary, target and final plan—posted according to the IT Release Schedule. A yellow box indicates that the plan is not published for this release.

Target Release Plan

Final Release Plan

Release

Release ID R56.1 R57.0 R57.1 R58.0 R58.1
Release Category Category 2 Category 3
(incl. Cat 2)
Category 2 Category 3
(incl. Cat 2)
Category 2
Real Time Production Build 2 Dec 2026 3 Mar 2027 2 Jun 2027 8 Sep 2027 1 Dec 2027
1. Preliminary Release Plan Prepared 19 Aug 2026 18 Nov 2026 17 Feb 2027 26 May 2027 18 Aug 2027
2. Market Participant Feedback Period Ends 2 Sep 2026 2 Dec 2026 3 Mar 2027 9 Jun 2027 1 Sep 2027
3. Target Release Plan 16 Sep 2026 16 Dec 2026 17 Mar 2027 23 Jun 2027 15 Sep 2027
4. Final Release Plan 14 Oct 2026 13 Jan 2027 14 Apr 2027 21 Jul 2027 13 Oct 2027
5. Sandbox Implementation 22 Oct 2026 21 Jan 2027 22 Apr 2027 29 Jul 2027 21 Oct 2027
6(a). Production Build
(Non Real Time)
25 Nov 2026 24 Feb 2027 26 May 2027 1 Sep 2027 24 Nov 2027
6(b). Production Build
(Real Time)
2 Dec 2026 3 Mar 2027 2 Jun 2027 8 Sep 2027 1 Dec 2027

Four times per year, the IESO schedules a Preliminary Release Plan detailing upcoming changes to IESO systems that have been assessed to have an impact on participants. Comments on IT changes in the plan can be sent to pending.changes@ieso.ca. Each release includes a preliminary, target and final plan, categorized as the following:

  • Category 3 releases (occurring twice a year) require market participants to make changes to their own technical interfaces with the IESO. Normally, significant system changes are the subject of stakeholder consultation well in advance of this release process.
  • Category 2 releases (occurring four times a year) require market participants to make a change in procedure or to update documentation, but not to modify any IT systems.
  • Category 1 releases do not have any impact on market participants and are managed through the IESO's internal release process. Market participants are notified only of any applicable outages, via the Planned IT Outages webpage.

Updates to the Preliminary Plan are added to the Target Release Plan, which is also open for comment by participants. New items are added to the Target Release Plan if required, and are posted through the IT Release Schedule.

The Final Release Plan is published one week in advance of the Sandbox implementation date, when changes are made available in the Sandbox environment for testing and training. Participants can contact IESO Customer Relations for more information if Sandbox access is required.

After the testing period is complete, the IESO will release the changes in Production, as shown on the IT Release Schedule. Accompanying documentation for the changes is available on Pending Changes – Documents as part of the baseline process.