phase ii technical subgroup meeting 8 october 19 2018
play

Phase II Technical Subgroup Meeting #8 October 19, 2018 (Docket No. - PowerPoint PPT Presentation

Phase II Technical Subgroup Meeting #8 October 19, 2018 (Docket No. 16-521) https://mn.gov/puc Agenda Time Topic Time Topic 9:30 - 9:45 Welcome, Introductions, Overview of Agenda, Expectations 9:30 9:40 Welcome, Introductions,


  1. Phase II Technical Subgroup Meeting #8 October 19, 2018 (Docket No. 16-521) https://mn.gov/puc

  2. Agenda Time Topic Time Topic 9:30 - 9:45 Welcome, Introductions, Overview of Agenda, Expectations 9:30 – 9:40 Welcome, Introductions, Overview of Agenda, Expectations, Recap 9:45 – 10:00 Review purpose/role of statewide technical requirements 9:40 – 10:50 Operating Agreements and Maintenance Agreements 10:00 – 10:15 Check in on agreed-upon content for utility specific TSMs 10:50 – 11:40 Reference and Definition Reconciliation • UL 1741 (2010) – how cited in MN DIP Att. 4 • DER unit, DER System, DER equipment package – see MN DIP Att. 5 • Control Limited Capacity consistent with MN DIP 5.14 • Inadvertent export • Clarify or replace “ESS Operational Control Modes” to address differences between application of storage capabilities and charge/discharge settings 11:40 – 12:10 Aligning on expectations for One-line Diagram Submittal and Review 12:10 – 12:30 Next Steps; including writing group update

  3. Commission Order January 24, 2017 • The Commission hereby delegates authority to the Executive Secretary to issue Notice(s), set schedules, and designate comment periods for the scope outlined in paragraphs 2 – 3 below. The Executive Secretary will, in cooperation with the Department of Commerce, convene a work group of appropriate size and composition, and may select a facilitator, to develop the record more fully. • The Commission will transition the Minnesota Interconnection Process to one based on the FERC SGIP and SGIA. The Executive Secretary will set schedules and take comments. It is anticipated that the Commission will consider the record and comments within 18 months of this order, to replace Attachments 1, 3, 4, and 5 to its 2004 Interconnection Standards in this Docket. The Executive Secretary will use the Joint Movants’ May 12, 2016 filing, generally, as the starting point for comments. • In the longer-term (nine to twenty-two months), the Executive Secretary will set schedules and take comments on updating the Minnesota interconnection technical standards. It is anticipated that the Commission will consider the record and comments within 24 months of this Order, to replace Attachment 2 to the Commission’s 2004 Interconnection Standards. This stage of work would incorporate newly revised national technical standards, and other issues identified as areas in need of updating. • The Commission hereby designates Commissioner Matthew Schuerger as lead commissioner pursuant to Minn. Stat. § 216A.03, Subd. 9, with authority to help develop the record necessary for resolution of the issues, and to develop recommendations to the Commission in this docket.

  4. Phase II Meetings: Topics and Timeline March 23 Scope/Overview; Inventory of Definitions to Discuss April 13 Performance Categories; Response in Normal and Abnormal Conditions; MISO Bulk Power System June 8 Reactive Power and Voltage/Power Control Performance; Protection Requirements July 20 Energy Storage; Non-export; Inadvertent export; Limited export, Capacity Aug 3 July 20 topics continued Aug 24 Interoperability (Monitor and Control Criteria); Metering; Cyber security Sept 14 Test and Verification; Protocol for witnessing Testing Sept 21 In-Person TSG: Power Quality; Follow up items; TIIR edits discussion Oct 19 References; Definitions; 1-line diagram requirements; Agreements, Frequency Ride-Through Nov 9 Full DGWG Meeting # 7

  5. Recap from September 21 • Commission staff suggested TSG continue Draft TIIR development with the following understanding of how Aggregate Nameplate Rating and MN DIP 5.14.3 limit on capacity applies • Limited value (less than aggregate nameplate rating) is appropriate for some of the steady state analysis during the engineering screens if it is controlled by a means articulated in an interconnection agreement • Aggregate nameplate rating is appropriate for DER capacity for application track. Aggregate Nameplate Rating is expected to be used for fault current analysis, possibly other analysis of dynamic system behavior. • Not all participants had the same expectations as to which version of UL1741 was applicable with regards to certifying a DER, or DER units • PUC Agenda meeting on TIIR proposal anticipated in ~Q4 2019 (was Feb. 2019) • A sub-set of TSG stakeholders will participate in a writing group that will report back to the balance of the TSG at interim milestones • September 21 Meeting Summary will have more details. Goal to finalize feedback by 11/9. 7/15/2019 https://mn.gov/puc 5

  6. Goals for TSG Mtg #8: References; Definitions; One-line diagram requirements; Agreements • Discuss and address draft TIIR language and proposed edits related to Sections 2, 3 and 13 and consider interim MN DIP Attachments 4 & 5, consistent with Draft TIIR Build a shared understanding of • Path forward to an aligned set of expectations regarding Operating Agreements • What work remains with regards to TIIR references and definitions • Opportunities for improvement in the application process regarding one-line diagrams 7/15/2019 https://mn.gov/puc 6

  7. Sample term usage germane to this presentation from IEEE 1547-2018 • distributed energy resource (DER): A source of electric power that is not directly connected to a bulk power system. DER includes both generators and energy storage technologies capable of exporting active power to an EPS. An interconnection system or a supplemental DER device that is necessary for compliance with this standard is part of a DER. [23] (IEEE 1547-2018, Clause 3.1, p. 22) • DER unit: An individual DER device inside a group of DER that collectively form a system. (IEEE 1547- 2018, Clause 3.1, p. 23) • DER equipment package: not defined, Attachment 5 to MN DIP is labeled “Certification of DER Equipment Packages” • Interconnection system: The collection of all interconnection and interoperability equipment and functions, taken as a group, used to interconnect a DER to an Area EPS. [24] (IEEE 1547-2018, Clause 3.1, p. 23) • Footnote 24: This term was frequently used in IEEE Std 1547-2003. Given the scope of the present standard, which may have implications to the design of the entirety of the DER, this standard uses the term “DER” in most places. (emphasis added by staff) 7/15/2019 https://mn.gov/puc 7

  8. Draft TIIR Section 13: Agreements

  9. Operating Agreements - content received from Fresh Energy • Are the process steps and timelines associated with the exchange and execution of the DIA the same for the Operating Agreement? In other words, is it realistic to think they are paired through the entire process? • Might there be a “minor modification” scenario where the operating parameters could change slightly without requiring a new interconnection application?

  10. DRAFT -16-521 Phase 2 – TSG 8 Xcel Energy Prep Slides 10/9/18

  11. Operating Agreement •Specify Power Factor •Contingency Operations •Distribution System Outages and Modifications •Local and Remote Control •Contact Information and Actions •Right of Access •Energy Storage Operating Mode (when Declaration option selected) Note: non-exhaustive list of typical Operating Agreement topics 11

  12. Maintenance Agreement •Routine Maintenance •Metering and Telemetry •Modification to Generation System •Special Facilities Note: non-exhaustive list of typical Maintenance Agreement topics 12

  13. Operating and Maintenance Agreements Brian Lydic Regulatory Engineer Interstate Renewable Energy Council

  14. O&M agreement • TIIR notes a broad non-exclusive list of items that could be included. • It is unclear what the process would be to alter the agreement over time if needed/requested by the utility. • If a customer does not agree with changes to the agreement in the future, how would/could it be resolved? • If a customer requests changes and the utility does not agree, how would/could it be resolved?

  15. Some Suggestions • Make clear when these agreements will be necessary (all IA’s, or only those with X considerations?) • Include Annex in TIIR with typical agreements for PV, storage (or PV+storage) and engine generators, based on default TIIR req’s. • Elaborate on process to initiate updates and resolve disagreements (MIP dispute resolution?) • Define agreement limitations (term, excluded items)?

  16. Discussion regarding edits to MN DER Draft TIIR Section 13 • What needs to be specified with “ESS permitted and disallowed operating control modes”? (IREC question) • Did today’s conversation or reviewing the participant materials submitted for this meeting bring up any additional contributions for Section 13 on Agreements? • Is clarifying language needed regarding what shall or shall not be in an Agreement? 7/15/2019 https://mn.gov/puc 16

  17. Draft TIIR Section 2: References

Recommend


More recommend