customer partnership group
play

Customer Partnership Group June 11, 2015 Presented by: Mike Lucas, - PowerPoint PPT Presentation

Demand Response Registration System Customer Partnership Group June 11, 2015 Presented by: Mike Lucas, Project Manager Tarak Thaker, Business Analyst Jill Powers, Smart Grid Solutions Manager ISO SMEs California ISO Purpose of todays


  1. Demand Response Registration System Customer Partnership Group June 11, 2015 Presented by: Mike Lucas, Project Manager Tarak Thaker, Business Analyst Jill Powers, Smart Grid Solutions Manager ISO SME’s California ISO

  2. Purpose of today’s meeting • Phase 2 business requirement specification BRS close out – Review BRS section highlights for registration enhancements – BRS section clarification stakeholder Q&A – Phase 2 enhance registration process flow changes – Phase 2 CPG next steps • Phase 3 initiation of CPG discussions – Introduce ISO enhancement concepts • Metering • Baseline • Settlement – Stakeholder Q&A, request for comments – Phase 3 CPG next Steps Page 2 California ISO

  3. Todays agenda Time Topic Presenter 1:00 – 1:15 Opening Comments/Introductions Nathan Hall • Meeting purpose/agenda 1:15 – 1:30 Phase 2 proposals – project update Mike Lucas 1:30 – 2:30 Phase 2 business requirements specification Jill Powers • review registration enhancements Tarak Thaker • clarifying Q&A • SMEs introduce business process flow 2:30 – 2:45 Phase 2 next steps Mike Lucas 2:45 – 3:30 Phase 3 development initiation Jill Powers • review design concepts Tarak Thaker • ISO stakeholder question discussion SMEs 3:30 – 3:45 Phase 3 next steps Mike Lucas 3:45 – 4:00 Wrap-up Nathan Hall • Request for Phase 3 comments CPGDemandResponse@caiso.com California ISO

  4. Phase 2 – Project Update  DRRS (Phase 1) Live March 24, 2015  DRR Customer Focus Group – ISO on-site April 9, 2015  Initial Customer Partnership Group (CPG) meeting May 12, 2015  Published Final Business Requirements Specification June 4, 2015  Today’s CPG meeting California ISO 4

  5. Phase 2 enabling demand response – registration enhancements BRS  Completed Business unit(s) review and approval for phase 2 BRS • Captures and records users initial set of requirements – Used as input to ISO system development project including:  Business process modeling  System requirements specification development  Use case development • Provides stakeholders information on concepts for development of system enhancements to streamline and further automate registration process – For participants using PDR and RDRR models California ISO 5

  6. DRRS enhanced registration methodology includes • Base functionality for registering PDRs and RDRRs • Effective date synergy across registration components Locations Registrations Resource • Robust API’s and user interface to manage registration processing steps • Business rule exclusivity between PDR/RDRR resource types California ISO 6

  7. Stakeholders business process steps used to structure and build business requirements Three sections: DRS DRRS • Manage locations Registration processing • Manage registrations • Manage resource Transfers remaining registration model and functionality from demand response system into the demand response registrations system California ISO 7

  8. Registration process builds from locations to registrations to resource Resource Location management includes: • review process by LSE/UDC Registration • establishing effective dates for locations Location Location effective dates: • control availability for DRP to use in creating registrations Registration effective dates: • validated against location effective dates • determine resource effective dates Resource effective dates: • validated against registration effective dates • maintained in Masterfile California ISO 8

  9. Location effective dating impacts (examples) • Location effective date changes flexibility added location effective date effective date change (allowed with no review) Extending end date (requires re-review) • Multiple registrations can be created within location effective dates location effective date R1 (allowed) R2 (allowed) R3 (not allowed) R4 (not allowed) California ISO 9

  10. Location management includes new functionality and removal of interim functionality • Location LSE/UDC review period will be configurable – initiated with 10 business days before auto approval – no longer requires ISO review • Duplicate location review and defense process established – incumbent DRP notified to defend – initiated with 10 business day configurable defense period – when no action is taken the location will be end dated • incumbent DRPs registrations may be affected by end dating  Review process  comments require contact information provided to DRP  issue resolution handled outside the ISO • Aggregated locations (ALOC) are no longer needed with registration incorporation into DRRS California ISO 10

  11. Location management business requirements are most extensive Requirements provide flexibility in the modification of location attributes by recognizing their process status: • Create – review (initial) • Modify – review (conditional) • pre/post review – pre/post registration – pre/post resource assignment • End – May result in changes to a registration and/or resource status California ISO 11

  12. New location management processing detailed in BRS: • Locations with node information will be required for registrations requesting a custom resource ID – system validates node against subLAP • Data validations will be performed during location creation – validated against Masterfile • Flexibility in modification of locations provided – BRQ198 details conditions – end dating required only when conditions are not met California ISO 12

  13. BRS section 4.1: Manage Locations BRQ100 - BRQ198 California ISO 13

  14. Registration management is separate process that uses location information for validation purposes • Registration process can begin when DRP has location(s) available – includes validations that may result in registration processing error(s) • Validation errors may require location modifications – returns to location management processing • Registration resubmitted upon correction of errors identified in validation • Registration may be affected by changes in location attributes California ISO 14

  15. Registration attributes have changed • Some attributes of registration have been removed – day ahead identification – discrete dispatch identification • Some attributes of registration have changed – baseline method configurable for additional selections – resource IDs can be chosen or allow system selection – LSE SC ID provided based on DLAP provided California ISO 15

  16. Registration attributes required may be different based on resource • Registration attributes may be impacted by resource Masterfile validations and processing – Including modification of registration attributes such as end dating or LRCV • Registration requesting a custom resource will include total of load reduction capacity value LRCV by pnode – System generated using a registration location information California ISO 16

  17. BRS section 4.2: Manage Registrations BRQ200 – BRQ274 California ISO 17

  18. Resource management requires interfacing with Masterfile and RDT process • Masterfile maintains all resource attributes used in markets – System of record for resource participation • Pmax in MasterFile may differ from registration LRCV – Registration LRCV can be greater than the Pmax – Registration LRCV can be less than the Pmax but not by more than 2 MW s • provides buffer such that Masterfile update is not required when locations are added that increase LRCV • System design to allow 1:many relationship between resource and registration – maintaining 1:1 relationship for Phase 2 development – provides DRRS flexibility that could be leveraged in Phase 3 • allowing multiple LSEs per resource California ISO 18

  19. Resource management goal • Minimize resource participation interruptions due to changes in registration or underlying locations • Location management provides DRP ability to stage registration creation to minimize risk of participation gap • Eliminating gap may not be attainable – dependent on established resource data template processing • Masterfile freezes • Latency between requested updates and actual update in Masterfile California ISO 19

  20. BRS section 4.3: Manage Resources BRQ300 – BRQ330 California ISO 20

  21. DRS User Role to Functionality Mapping DRS User Roles Create, Create. Modify, Modify, User Remove View Review Remove View Administer Role Locations Locations Locations Registrations Registrations Roles DRP YES YES YES YES YES LSE YES YES YES UDC YES YES YES DRP SC YES YES LSE SC YES YES ISO YES YES YES YES YES YES California ISO

  22. Process flows for location, registration and resource management under development • Business process flow chart has been developed and documented based on Phase 2 BRS includes: – Location management • review processes – Registration management • validation processing • attributes system generated – Resource management • resource data template processing touch points • Once completed the document will be posted for stakeholder review and comment California ISO 22

  23. Phase 2 – Next Steps • SRS / CPG August 2015 • Technical Specifications December 2015 Baseline Calculation California ISO 23

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend