1. Market Operations Engagement Group Customer Data
July 26, 2016
Presentation material does not represent the views of the Joint Utilities Engagement Group as the group is still in discussion on these topics. Please do not redistribute this deck.

2. Agenda Time Topic 9:00 – 9:15 Introductions 9:15 – 10:30
JU Presentation: Customer Data Aggregation
10:30 – 10:45
Break
10:45 – 11:30
Q&A
11:30 – 12:00
Summary & Next Steps

3. Market Ops - Near term schedule (subject to revision)
7/18
7/25
8/1
8/8
8/15
8/22
8/29
9/5
9/12
Advisory Group
August 10 NYC
September 7 NYC
Stakeholder Engagement Technical Conferences
July 27 (webinar): NWA Suitability, System Data
August 18 NYC: Granular Pricing, Customer Data, Hosting Capacity, Monitoring & Control
September 13 Albany: Cyber Security, ISO/DSP Roles, DER and Demand Forecasting, Load Flow Analysis, Probabilistic Planning
Customer Data
(Tuesday mornings)
DER Sourcing
(Tuesday afternoons)
Granular Pricing
EVSE
July 26
Albany
Aggregation of Usage Data
August 9
NYC
Additional Data Needs
July 19
(By Phone*)
Review 7/13 Stakeholder Comments
August 2
TBD
July 26
Albany
Dependencies With Other REV and Related Proceedings
August 9
NYC
Potential Refinements to NWA Procurement Approach
August 2
(By Phone*)
TBD
August 18 NYC (technical conference)
August 16
NYC
Current State; Opportunities for Utility Collaboration
September 12 Albany
Forecasting Methodologies
August 30
Albany
Principles for Utility Involvement
*Additional phone sessions will be held as needed

4. Customer Data Engagement Group Charter
Purpose: Explore the Joint Utilities' approaches for facilitating market mechanisms that effectively support and encourage the adoption of Distributed Energy Resources while meeting customers’ needs and complying with the DSIP Guidance Order
Topics and Scope: Customer Data
Customer Data
Data Collection, Reporting Frequency and Availability of Usage Data
Discuss how often usage data might be collected by the utility, how often it would be made available to customers/authorized agents, and at what quality level
Discuss customer data platform-related sensitivities (e.g. AMI versus non-AMI systems)
Aggregation of Usage Data
Discuss standardized aggregated data offerings (e.g. kW and kWh by rate class, tax district, zip code)
Discuss utility-sided aggregated data system automation efforts and reporting methods
Discuss standards for anonymizing aggregated data to protect individual customer privacy (e.g. 15/15 rule)
Additional Data Needs
Explore and identify additional useful customer information beyond usage data
Note: pricing for Basic and Value-Added data is a Track Two matter

5. Customer Data Topic Description
Customer Data may identify the person or entity to which it applies
Customer information may include usage data, account/profile data, end-use and other qualitative data, and results from customer-specific analyses
Customer usage data is a subset of customer information and contains a customer's usage or production of energy
The Commission’s REV Track 2 Order defined Basic Data as "the usage for each applicable rate element, including usage bands specified in the applicable tariff. This is the level of data necessary to render, reconstruct and understand the customer's bill"
Usage data can be shared with authorized third parties, or aggregated by various groupings for use by third parties

6. Customer Usage Data – Definitions
Basic Data examples include:
Non-interval - Cumulative kWh, net or accumulated kWh, max recorded kW (if a demand meter is present). If a customer is on a TOU rate, summed usage in TOU periods is also basic data.
Interval - Energy use (kWh, net or accumulated kWh, kW, kVar) at program intervals specific to the customer's meter, as well as cumulative kWh, min/max kW, kVar. If a customer is on a TOU rate, summed usage in TOU periods is also basic data.
To be deemed as Value-Added Data, one or more of the following criteria must be met:
Is not routinely developed or shared
Has been transformed or analyzed in a customized way
Aggregated data falls into this bucket
Is delivered more on an ad-hoc basis or more frequently than basic data
Value-Added Data may be created and/or provided by the utility with a charge to the requestor.
According to the Track Two Order, bill-quality basic data should be made available to customers and third parties of their choosing within 24 hours, at no incremental cost.

7. Guidance Requirements To Address
Supplemental DSIP
Include plans to phase in the ability to provide ESCOs with access to daily, hourly, and eventually, close to real-time access to customer usage information, including budgets and timelines (Att. 1 – Page 21 – SDSIP – 2.F)
Track Two Order
Each utility should continue to work with NYSERDA and should provide aggregated data updates for the Community Energy Reports and the Utility Energy Registry (UER). (p. 149)
Once the utilities automate their systems, Staff should reexamine the adoption of the UER portal to make aggregated community-level usage data accessible to all municipalities and developers. (p. 150)
Each utility, or the utilities jointly, should file a progress report regarding automation efforts September 1, 2016 (p. 151)
At this time, utilities should follow their current internal policies in addressing the anonymity issue for ensuring that aggregated data is sufficiently anonymous. In order to make these policies transparent and enforceable, utilities should develop standardized policy statements in the context of the UER development process and each utility should file its policy as a tariff amendment. (p. 153)

8. Aggregation of Customer Usage Data
JU Presentation:
Aggregation of Customer Usage Data

9. Key Definitions
All aggregated customer usage data is considered Value-Added
The JU propose to define the Standard aggregated data offering as kW or ICAP and kWh data that is aggregated by zip code and/or tax district, and segmented by rate class
For rate classes with TOU periods, kW and kWh data will be aggregated by TOU periods and total
Standard aggregated data offerings will eventually be automated
The JU will charge for standard aggregated data offerings
Non-Standard aggregated data offerings may include kW or ICAP and kWh data that is aggregated by feeder, circuit, and other parameters, where applicable and available
Non-Standard aggregated data offerings are typically delivered ad-hoc or are customized in response to specific requests
Fees for Non-Standard aggregations may vary in each utility's tariff based on the data being requested and the requestor.
The JU anticipate that some current as well as future Non-Standard aggregated data requests may become increasingly commonplace over time. It may be practical for the utilities to automate these requests and eventually reclassify them as Standard aggregated data offerings.

10. Data Aggregation Use Cases
The JU have identified several use cases for aggregated data
Community Choice Aggregation (CCA)
Whole-Building Data Aggregation
Community- Level Planning
The JU seek input from stakeholders on other potential use cases for aggregated data that are highly valuable to customers/stakeholders and that may be viable candidates for automation
Specific aggregation elements (kw, kWh, ICAP, spatial and temporal parameters, etc.)
Estimated volume, use drivers, etc.
The utilities plan to continue to collaborate with each other to identify, define, prioritize and schedule for implementation requests for other aggregations that are of high value to customers/stakeholders and that may be viable candidates for automation

11. Use Case # 1: Community Choice Aggregation
Data Security Agreement
Utilities will require full execution of DSA before any data is provided
Community Choice Aggregation (CCA) Data Provision – two steps:
Aggregated data by municipality - Aggregated data will include monthly usage (kWh) by service classification and total demand/ICAP (kW) by service classification which is used to solicit bids by ESCOs and DER Providers
Individual customer data – Customer-specific data (customer name, address, account numbers) are provided to the ESCO for managing the opt-out process and customer enrollment in Retail Access.
Fees for CCA aggregated data
Utilities will charge fees for providing aggregated and individual customer data as part of a CCA
Utility tariffs – to be filed on August 5th – will vary by price, method and who is charged.

12. Use Case #2: Whole-Building Aggregated Data
The JU currently provide whole-building aggregated data to building owners or authorized agents upon request at an additional charge to the requestor
Usage (kWh) and demand by month by building
Note: not all utilities are asked for this information
The JU also provide aggregated whole-building data to municipalities and local governments to support compliance activities
New York City Local Law 84
Requires building owners to obtain whole-building energy (and water) data and post to Energy Star Portfolio Manager by May 1 annually
State Executive Order 88
The Build Smart New York Program applies to “State Entities and departments over which the Governor has Executive Authority, and (ii) all public-benefit corporations, public authorities and commissions, for which the Governor appoints the Chair, the Chief Executive, or the majority of Board Members, except for the Port Authority of New York and New Jersey.”
Contains annual reporting requirements that detail energy consumption and cost data for all fuels

13. Use Case #3: Community-Level Planning
The Track Two Order states that the utilities should continue to work with NYSERDA and provide aggregated data for the Utility Energy Registry (UER)
Pilot began in 2012
Data provided: kWh and customer counts aggregated by municipality (town name)
Data collection has been a manual process to-date
The JU will charge a fee for supplying the requested data
The UER provides information for energy use analytics and load concentrations analyses
UER data differs from CCA aggregated data in several respects:
CCA data includes demand/ICAP (kW)
CCA data is aggregated by very specific service classifications
CCA may be parsed by tax district or other municipal delineating factors
CCA excludes Retail Access customers
At the current level of UER data granularity, no data service agreement between JU and NYSERDA is utilized

14. Anonymization
Today there are two leading standards for anonymizing aggregated customer usage data:
15/15: requires aggregated data to include a minimum of 15 customers, with no one customer’s load exceeding 15% of the aggregated group’s energy consumption
Adopted in Colorado, Minnesota; adopted in California for Direct Access programs and also used by Southern California Edison
4/80: requires aggregated data to include a minimum of 4 customers, with no one customer's load exceeding 80% of the aggregated group’s energy consumption
Adopted in Illinois, Texas
The JU is considering adopting the 15/15 standard for anonymization
Exceptions may be needed in order to share aggregated data for the purpose of compliance with federal, state and/or local laws
The JU will monitor exception requests and may evolve the standard over time
The JU is interested in stakeholder views and comments on:
Use cases where stakeholders have experienced issues involving anonymization
Which anonymization standards work best and the underlying use cases supporting that view
Each of the utilities will continue to follow their current internal policies for aggregation anonymization per the CCA Order and the Track Two Order, pending the adoption of a JU standard

15. Break

16. Thank you for joining us!
Please contact or
visit our website for more information

17. Appendix

18. Engagement Group Ground Rules*
All stakeholder engagement (advisory group and engagement group) meetings, webinars and information exchange are designed solely to provide an open forum or means for the expression of various points of view in compliance with antitrust laws.
Under no circumstances shall stakeholder engagement activities be used as a means for competing companies to reach any understanding, expressed or implied, which tends to restrict competition, or in any way, to impair the ability of participating members to exercise independent business judgment regarding matters affecting competition or regulatory positions.
Proprietary information shall not be disclosed by any participant during any stakeholder engagement meeting or its subgroups. In addition, no information of a secret or proprietary nature shall be made available to stakeholder engagement members.
All proprietary information which may nonetheless be publicly disclosed by any participant during any stakeholder engagement meeting or its subgroups shall be deemed to have been disclosed on a non-confidential basis, without any restrictions on use by anyone, except that no valid copyright or patent right shall be deemed to have been waived by such disclosure.
AG & EG discussions will be open forums without attribution and no public documents by the AG or EG will be produced unless publication is agreed upon by the group.
*Ground Rules adapted from the JU Advisory Group

19. Overall Engagement Group Purpose & Objectives
The Market Operations Stakeholder Engagement Group (EG) is an open forum for stakeholders who are actively engaged in the REV process and the Distributed System Implementation Plan (DSIP) filings to provide input to, and exchange ideas with, the Joint Utilities of New York (JU) on topics related to grid operations as identified by the Joint Utilities Stakeholder Advisory Group (AG).
Objectives
The AG will advise the JU on the sequence and priorities of topics that Engagement Groups should discuss.
The AG will also provide input on Engagement Group members, discussion scope, and any output documents that would advance greater shared understanding.
The Engagement Groups will hold discussions on identified topics in order to achieve greater shared understanding of issues covered in the DSIP filings, and to build toward common ground through iterative discussion and feedback.

20. Engagement Process Overview
Stakeholder Engagement Schedule
Jan 2016
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
2017
DSIP Final Guidance
Initial DSIP Filings
Supplemental DSIP Filing
Advisory Group Mtgs
Initial DSIP
Stakeholder Engagement*
Supplemental DSIP
Engagement Groups
Distribution Planning**
Grid Operations
Market Operations
Stakeholder
Technical Confs***
*Initial DSIP engagements dates based on individual JU workshop schedule during this period. **ITWG beginning in March, EG begins in May.
*** Stakeholder technical conferences to engage a wider set of participants to inform technical discussions and share Engagement Group results, as needed and in consultation with the Advisory Group
Source: Plan for stakeholder engagement process as reflected in May 5th DSIP filing

21. Advisory Group Members
Contact
Organization
Title
NY DPS
Tammy Mitchell
Dept. of Public Service
Chief, Electric Distribution Systems
DER Provider
Carlos Gonzalez
SolarCity
Director, Grid Engineering Solutions
Pete Fuller
NRG
VP, Market & Regulatory Affairs
Bill Acker
NY-BEST
Executive Director
Greg Geller
EnerNoc
Director, Regulatory & Government Affairs
Large Customer
Mike Mager
Couch White, LLP
Partner
Anthony Fiore
City of NY
Director, Office of Energy
Small Customers & Consumer Groups
Erin Hogan
Dept. of State Utility Intervention Unit (UIU)
Senior Project Manager at NYSERDA
State/Public power
Maryam Sharif
NYPA
Program Manager, Clean Energy Technology
Environmental
Miles Farmer
NRDC
Legal Fellow
Rory Christian
EDF
Director, NY Clean Energy
Marketers
Chris Kallaher
Direct Energy
Director, Government & Regulatory Affairs
Wholesale market
Mike DeSocio
NYISO
Senior Manager, Market Design at NYISO
NYSERDA
John Saintcross
Assistant Director, Smart Grid Research
IPPNY
Chris Wentlent
Exelon
VP, Energy Policy
Joint Utilities
Tom Mimnagh
ConEdison
Department Manager
Damian Sciano
Director, Distributed Resource Integration
John Leana
National Grid
Director, Strategy
Lori Cole
AVANGRID
Manager, Regulatory & Tariffs
John Borchert
Central Hudson
Senior Director of Energy Policy and Transmission Development
Facilitator
Paul De Martini
ICF International
AG Facilitator

22. Supplemental DSIP Topics—Based on Final Order
Engagement Groups
Distribution System
Planning
Grid Operations
Market Operations
Interconnection
Hosting
Capacity
System Data
Monitoring &
Control
Granular
Pricing
Customer Data
Demand
Forecasting
NWA
Suitability
Cyber
Security
ISO/DSP Roles, Responsibilities, Interaction
DER Sourcing
- Procurement
Electric Vehicle Supply Equipment
Topics
DER Forecasting
Load Flow
Analysis
Probabilistic
Planning
Interconnection Technical Working Group
Currently scheduled Engagement Group topics
Currently scheduled Advisory Group topics