1 / 8

PNM High-Penetration PV thru Grid Automation & Demand Response

PNM High-Penetration PV thru Grid Automation & Demand Response. Jonathan Hawkins Manager, Electric Distribution Standards PNM Grid-InterOp 2009 Denver, CO Nov 17-19, 2009. High-Penetration PV thru Grid Automation & Demand Response. UC4. UC2. UC1. UC3.

len
Télécharger la présentation

PNM High-Penetration PV thru Grid Automation & Demand Response

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. PNM High-Penetration PV thru Grid Automation & Demand Response Jonathan Hawkins Manager, Electric Distribution Standards PNM Grid-InterOp 2009 Denver, CO Nov 17-19, 2009

  2. High-Penetration PV thru Grid Automation & Demand Response UC4 UC2 UC1 UC3 • Changes to existing architecture (if applicable) • Interface implications to legacy systems • Architecture Considerations for Emerging/changing requirements • Improved Benefits from Architecture Changes • Overall Project Lessons Learned (3-5 Slides) • Topics could be wide ranging (project planning, resources, stimulus implications, software integration, hardware installation, customer acceptance, etc.) • What surprised you? What information would member utilities find interesting? • Q&A

  3. PNM’s Smart Grid – Additions to existing Architecture • Changes to existing architecture (if applicable) • Interface implications to legacy systems • Architecture Considerations for Emerging/changing requirements • Improved Benefits from Architecture Changes • Overall Project Lessons Learned (3-5 Slides) • Topics could be wide ranging (project planning, resources, stimulus implications, software integration, hardware installation, customer acceptance, etc.) • What surprised you? What information would member utilities find interesting? • Q&A

  4. Interface implications to legacy systems • Communications Protocols – IEC61850/DNP3 • Cyber-security Standards • IEC61850 interface to Home Area Network (via inverter interface) and commercial building’s energy management system (e.g. BACNet) • Distributed Energy Resource response translation through the architecture to billing system • New customer contracts – e.g. demand response, renewables through AMI, penalties for opt-out, strict measurement of renewable energy certificates (RECs)

  5. Considerations for emerging/changing requirements • Communication and Cyber-security Standards still evolving • Specifying multiple protocols where possible and cost-effective • IEC61850 and DNP3 • Zigbee, Homeplug, Smart Energy Profile, 6LoWPAN • Concerns of multiple profiles • Protocol interfaces (translation) • Latency requirements (does an alternate protocol dictate a higher latency) • Bandwidth requirements • Varying communication time requirements (e.g. 1 sec. control data vs. 15 min. pricing data)

  6. Improved Benefits from Architecture Changes • Economic • Start with Ability to send “real-time” prices • Price components could be • Distribution grid loading • Day-ahead load Forecast • Wholesale prices (regional hub based) • Carbon pricing • Target “Firmed up” renewables (Dispatchable) • Reliability • Ability to unload feeders • Prevent overuse of equipment/extend equipment life (e.g. LTCs, Cap Banks) • Ability to “right size” feeder equipment • Back office efficiency – multiple systems able to use data

  7. Overall Project Lessons Learned • Modeling will be critical • Little is known or tested on battery control algorithms; DG placed at end of feeder vs. beginning of feeder could be completely different • Models need to be calibrated on the front end for acceptance - GridLAB D and OpenDSS modeling has started • Lots of data will be needed to validate front and back ends of modeling effort • Functional/org structure issues have to be raised as SG architecture is developed • Groups/functions will need to be in place and staffed that don’t exist now • These are costs that have to be identified along with equipment costs • Technology gaps and incumbent architecture need to be displayed to industry from a non-silo’d perspective • Architecture needs to incorporate NIST and align with other demo projects

  8. Thank You! Questions?

More Related