Customer Partnership Group November 3, 2015 Presented by: Indu - - PowerPoint PPT Presentation

California ISO

Demand Response Registration System Customer Partnership Group November 3, 2015

Presented by: Indu Nambiar, Business Solutions Manager Mike Lucas, Project Manager

California ISO

Purpose of today’s meeting

• Phase 2 Technical Specification Review

– Review DRRS Phase 2 Technical Specifications – Posted on caiso.com on September 18, 2015 – Stakeholder Q&A – Phase 2 CPG next steps

Page 2

California ISO

Todays agenda

Time Topic Presenter

1:00 – 1:15 Opening Comments/Introductions

• Meeting purpose/agenda

Nathan Hall

1:15 – 1:30 Phase 2 – project timeline

Mike Lucas

1:30 – 2:00 Phase 2 technical specification overview

Indu Nambiar

2:00 – 3:00 Phase 2 clarifying Q&A

All

3:00 – 3:15 Phase 2 next steps

Mike Lucas

3:15 – 3:30 Wrap-up

Nathan Hall

California ISO

 Initial Customer Partnership Group (CPG) meeting May 12, 2015  Published Final Business Requirements Specification June 4, 2015  Last CGP meeting October 10, 2015  Today’s technical CPG meeting November 3, 2015

• User Training

March 21-23, 2016

• Market Sim

March 23 – April 21, 2016

• Go Live

April 28, 2016

Phase 2 – Project Timeline

4

California ISO

• Provides stakeholders information on concepts for

development of system enhancements to streamline and further automate registration process – For participants using PDR and RDRR models

Phase 2 enabling demand response – registration enhancements BRS

5

Completed

• Business unit(s) review and approval for phase 2 BRS
• Capture and record users initial set of requirements

California ISO

Locations Status Lifecycle

6

Create Locations Status = “New” Action = ‘Save’ Start Perform Location Validation Status = “Processing” Action = ‘Save & Submit’ Is Location A Duplicate? Alert DRP: Duplicate Location Status = “Duplicate” Yes Yes DRP Wishes To Continue With Duplicate? Engage Defense Process Status = “Duplicate” Yes End No Valid Location? No Show Errors No Perform LSE/UDC Review Status = “Pending” Location Review Completed? Yes Review Deemed Completed Location Status = “Inactive” Review Deemed Denied Location Status = “Pending”

California ISO

Registration Status Lifecycle

7 Create Registration Status = “New” Start Perform Registration Validation Status = “Pending” Is Registration Valid? Registration Status = “Confirmed” Yes Submit Registration Status = “Pending” Show Error End No Start DRP initiates registration termination

California ISO

Locations & Registration Maintenance Job

8 Is Registration Effective End Date in the past Registration Status = “Terminated” End Start Check Registration status nightly Yes Current status of Registration is unchanged No

Is Location Effective End Date in the past Location Status = “End-dated Location” End Start Check Location status nightly Yes Current status of Location is unchanged No

California ISO

Locations – Use Case

9

Location Status New/Duplicate Location Pending Location Inactive Location Active Location Processing/End-Dated Location

A location is said to be "New", if it has been created but NOT yet submitted for review. A location is "Duplicate" when the same SAN for the same UDC is owned by two different DRPs A location is "Pending" when the DRP submits the location, validation has successfully completed, and the review process has been initiated. A location is said to be an "Inactive Location", if it has completed the review process and is NOT a part of any registration that is in "Pending" or "Confirmed" status. A location is said to be an "Active Location", if it is a part of a registration that is in "Pending" or "Confirmed" status. A location is "Processing" when the DRP submits the location and it is being validated. A location is said to be an "End-Dated Location", if the effective end date of the location is prior to the current date. End-dated locations are logically equivalent to deleted records.

Attempt to Modify any of the fields of a Location

On the UI: (a) User clicks on the "Edit" button (b) The edit location form is presented to the user to make all changes needed without the current location becoming "End- Dated" Using the API: All modifications to the existing location shall be accepted. The location shall have a status of "New" when Action = "Save" or status of "Processing" when Action = "Submit" with the effective dates and all other attributes provided by the DRP. Note: Terminate Registration (TR) Flag shall be ignored. On the UI: (a) User clicks on the "Edit" button (b) The edit location form is presented to the user to ONLY end-date the location. No other changes are permitted. Using the API: Any location in Pending status can only be end-dated. All other request for modifications shall be rejected. Note: Terminate Registration (TR) Flag shall be ignored.

Following modifications are allowed without the current location becoming end dated: (a) Location Name (b) Address Fields (c) Effective start date to be greater than the current start date (d) Effective end date to be less than the current end date On the UI: (a) User clicks on the "Edit" button (b) Existing location becomes "End dated" (c) A new location with status of "New" is created and the edit location form is presented to the user to make changes Using the API: (a) The existing location becomes "End Dated" (b) A new location with status of "New" when Action = "Save" or with a status of "Processing" when Action = "Submit" is created with the effective dates and all

• ther attributes provided by the DRP.

Note: Terminate Registration (TR) Flag shall be ignored. All changes shall be accepted - Following modifications are allowed without the current location becoming end dated: (a) Location Name (b) Address Fields On the UI: (a) User clicks on the "TR Override" Button (b) A warning message appears with details of Registration in which the location is currently participating (c) User clicks on "TR Override Location" button to confirm (d) Registration that had this location is "Terminated" (e) All Locations associated to that registration, except for the location being modified, will become "Inactive" (f) The existing location becomes "End Dated" (g) A new location with status of "New" is created and the edit location form is presented to the user to make changes for this new location Using the API: Check Terminate Registration (TR) Flag -

• 1. If TR Flag = "YES"

(a) Registration that had this location is "Terminated" (b) All Locations associated to that registration, except for the location being modified, will become "Inactive" (c) The existing location becomes "End Dated" (d) A new location with status of "New" when Action = "Save" or with a status of "Processing" when Action = "Submit" is created with effective dates & all other attributes provided by the DRP.

• 2. If TR Flag = "NO", Reject the submission by

the DRP

No changes are permitted. Submission by the DRP shall be rejected. Note: Locations in "Processing" status are locked by the application for validation and End-dated locations are logically deleted records.

California ISO

Registrations – Use case

10 Registration Status New Registration Pending Registration Confirmed Registration Terminated Registration

A Registration is said to be a "New", if it has been created but NOT yet submitted. A registration is "Pending" when the DRP submits the location, and validation is in progress. A registration is said to be "Confirmed", if validation completes successfully. A registration is said to be "Terminated", if the effective end date of the registration is prior to the current date. Terminated registration are logically equivalent to deleted records.

Attempt to Modify any

• f the fields of a

Registration

On the UI: (a) User clicks on the "Edit" button (b) The edit registration form is presented to the user to make all changes needed to the registration without the current registration becoming terminated. Using the API: All modifications to the existing registration shall be accepted. The registration shall have a status of "New" when Action = "Save" or status of "Pending" when Action = "Submit" with the effective dates and all other attributes provided by the DRP. Note: Terminate Registration (TR) Flag shall be ignored. On the UI: (a) User clicks on the "Edit" button (b) The edit registration form is presented to the user to ONLY Terminate the registration. No

• ther changes are permitted.

Using the API: Any registration in Pending status can only be Terminated. All other request for modifications shall be rejected. Note: Terminate Registration (TR) Flag shall be ignored.

Following modifications are allowed without the current registration becoming terminated: (a) Registration Name (b) Effective start date to be greater than the current start date (c) Effective end date to be less than the current end date On the UI: (a) User clicks on the "TR Override" Button (b) A warning message appears with details of Registration (c) User clicks on "TR Override Location" button to confirm (d) Registration is "Terminated" (e) All Locations associated to that registration will become "Inactive" (e) A new registration with status of "New" is created and the edit registration form is presented to the user to make changes for this new

• registration. User can cancel out of the form if a

new registration is not needed. Using the API: Check Terminate Registration (TR) Flag -

• 1. If TR Flag = "YES"

(a) Registration is "Terminated" (b) All Locations associated to that registration will become "Inactive" (c) A new registration with status of "New" when Action = "Save" or with a status of "Pending" when Action = "Submit" is created with effective dates & all other attributes provided by the DRP.

• 2. If TR Flag = "NO", Reject the submission by the

DRP

No changes are permitted. Submission by the DRP shall be rejected. Note: End-dated registrations are logically deleted records.

California ISO

• submitDRLocations_v1– submit a create or modify request for a location
• submitDRLocations_v1_DocAttach– submit a create or modify request for a location(s) for .net

clients

• retrieveDRLocations_v1– retrieve request for a DRRS Location(s)
• retrieveDRLocations_v1_DocAttach – retrieve request for a DRRS Location(s) for .net clients
• retrieveDRBatchStatus_v1– to request the status on a submission of a create or modify
• retrieveDRBatchStatus_v1_DocAttach– to request the status on a submission of a create or

modify for .net clients

• submitDRRegistrations_v1 – submit a create or modify request for a registration
• submitDRRegistrations_v1_DocAttach – submit a create or modify request for a registration(s)

for .net clients

• submitDRLocationsReview_v1 – submit a location review request
• submitDRLocationsReview_v1_DocAttach – submit a location review request for .net clients
• retrieveDRRegistrations_v1 – retrieve request for a DRRS Registration(s)
• retrieveDRRegistrations_v1_DocAttach – retrieve request for a DRRS Registration(s) for .net

clients

Modified and New Web Services

11

California ISO

All technical documents are available on www.caiso.com under Release Planning  2016 Releases  Independent 2016 Releases  Enabling demand response Phase 2 – Registration  Technical specifications

• Summary of Use Case – Locations & Registrations
• Lifecycle – Locations & Registrations
• Technical Specification
• Artifacts Package (wsdl & XSDs)

Technical Documents

12

California ISO

Next steps

Page 13

• ISO to continue development of Phase 2 System

Requirements Specifications

• Please submit additional questions and/or clarifications on

Phase 2 to mailbox CPGDemandResponse@caiso.com by November 10, 2015.