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 planposted according to the IT Release Schedule. A yellow box indicates that the plan is not published for this release.

Release ID

R 38.1

R 39.0

R 39.1

R 40.0

R 40.1

Release Category Category 2 Category 3
(inc. Cat 2)
Category 2 Category 3
(inc. Cat 2)
Category 2
Real Time Production Build 6 Dec 2017  7 Mar 2018 6 Jun 2018 12 Sep 2018 5 Dec 2018
1. Preliminary Release Plan Prepared 23 Aug 2017 15 Nov 2017 21 Feb 2018 30 May 2018 22 Aug 2018
2. Market Participant Feedback Period Ends
6 Sep 2017 29 Nov 2017 7 Mar 2018 13 Jun 2018 5 Sep 2018
3. Target Release Plan 20 Sep 2017 13 Dec 2017 21 Mar 2018 27 Jun 2018 19 Sep 2018
4. Final Release Plan 18 Oct 2017 17 Jan 2018 18 Apr 2018 25 Jul 2018 17 Oct 2018
5. Sandbox Implementation 26 Oct 2017 25 Jan 2018 26 Apr 2018 2 Aug 2018 25 Oct 2018
6(a). Production Build
(Non Real Time)
2 Dec 2017 3 Mar 2018 2 Jun 2018 8 Sep 2018 1 Dec 2018
6(b). Production Build
(Real Time)
6 Dec 2017 7 Mar 2018 6 Jun 2018 12 Sep 2018 5 Dec 2018

See 2017 IT Release Schedule

 

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.