1 / 9

UtilityAMI HAN Task Force

UtilityAMI HAN Task Force. June 15, 2007. Agenda. Introductions TF operating rules Scope and deliverables of the TF Base Assumptions Review Presentation by the CA IOU HAN working group HAN Use Case Review and discussion HAN Requirements Review – form and depth discussion

knut
Download Presentation

UtilityAMI HAN Task Force

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. UtilityAMI HAN Task Force June 15, 2007

  2. Agenda • Introductions • TF operating rules • Scope and deliverables of the TF • Base Assumptions Review • Presentation by the CA IOU HAN working group • HAN Use Case Review and discussion • HAN Requirements Review – form and depth discussion • New business – OpenPCT TF formation • Adjourn

  3. TF Operating Rules • OpenHAN is a TF of the UtilityAMI WG and operates under the same governing rules • This is a utility driven activity • Members in good standing of the UCA International Users Group which represent a utility are eligible to vote • Utility members are permitted to put any issue on the table for discussion or vote • Any member may contribute / comment • A majority of utility members may vote to table any issue

  4. TF Scope and Deliverables • Scope – Requirements for utility applications that utilize a home area network interface implemented in utility owned equipment • Assumptions • Technology and platform independent – well defined interfaces • Not addressing any particular regulatory requirements • Non prescriptive – requirements only apply if a utility is implementing a Home Area Network Interface in a meter – if you have a HAN, then these are the requirements • Deliverables • Use Cases • Tool to generate / validate requirements • OpenAMI to maintain • Common Requirements Document • To give vendors guidance • For other organizations to develop details

  5. CA IOU HAN TF Contribution • Scope and vision for utility implemented HAN’s

  6. HAN Use Cases – Updates to SCE/OpenAMI Use Cases • C1 - Customer reduces their Usage in response to Pricing or Voluntary Load Reduction Events. • C4 - External Clients use the AMI to interact with devices at Customer Site • D1 - Distribution Operations curtails customer load for grid management • I1 - Utility installs, provisions and configures the AMI [and Utility HAN] system • I3 - Utility Upgrades AMI system to Address Future Requirements

  7. Use Case Notes • SCE and SDG&E will submit use cases • User to display device interaction scenario – C2, C3 • Prepay, service request/info, usage display • AMI system to EMS scenario • Reliability response scenario – D1 • No opt-in / opt-out • Price response scenario – C1 • Opt-in / opt-out – California -> must be part of a program • Override button scenario • HAN management – Derivation of I2 – and Title24 • Device provisioning - – initial and update • Security credential establishment • Heartbeat, Diagnostics • Firmware upgrade – I1 • New piece for HAN • Customer HAN evolution management • Customer generation scenarios • Net metering, EV interface, PV, etc. – V2G • Security threat scenarios – Title 24 work

  8. Requirements Document Deliverable • How much depth? • Similar to UtilityAMI or more extensive? • Review SDG&E contributions

  9. New Business • The CEC would like to see a TF instantiated to address the technical details for implementing the Title 24 PCT • Core Tasks • RDS profile • ZigBee profile • Expansion port profile • Systems Operations – e.g. installation & registration • Security architecture details

More Related