Weekly OpenADE Meeting Notes

1. Weekly OpenADE Meeting Notes Tuesday, January 14, 2014

2. OpenADE Task Force Topics • Issues Raised and Implementation Questions • How to use BR=bulkID with application to account and account groupings, as well as, large ThirdParty collections of Authorizations. • Service Request 83 – including Function Block for optional customer info (service point address, etc.) • Service Request 84 – having nscopeselection screen on Data Custodian Site vs 3rd Party site • Service Request 85 – Duplicating TOU and CPP from ReadingType to INtervalReading as in SEP 2.0 • New Resources for OpenADE Exchange requested • Tariff Model Resource • Customer Information Resource • Green Button Connect My Data Testing and Certification • Complete function block descriptions • Complete test case requirements

3. Green Button Connect My Data Testing and Certification • Complete function block descriptions • Current: • [FB_3] Green Button Connect My Data • [FB_13] Security and Privacy classes • [FB_14] Authorization and Authentication (OAuth) • [FB_19] Partial update data • New?: • Resource Level REST • SFTP for Bulk • REST for Bulk • Use Case 1: Client Registration • Offline Authorization to Complement OAuth – should this be outside the scope of standard and testing or standardized • No standard isolated way to get the token to a third party without OAuth • On exceptional basis some customers can’t be required to use a web account • Sometime commercial accounts don’t need privacy and want a service provider just to register the data. • Could use Notification service to tell TP about new authorizations made by DC. Out of band how RetailCustomer is identified to the TP • “transitive” model TP gets bulk data from DC and then becomes DC – can this architecture be of help here?

4. Service Request 83 – including Function Block for optional customer info (service point address, etc.)

5. Service Request 84 – having scope selection screen on Data Custodian Site vs 3rd Party site

6. [85] Time of Use tier indicator alignment with SEP 2.0

7. Here is a list of topics raised by you all that we will touch on • Issues Raised and Implementation Questions • How to use BR=bulkID – relates to HD #61 • Service Request 83 – including Function Block for optional customer info (service point address, etc.) • Service Request 84 – having scope selection screen on Data Custodian Site vs 3rd Party site • Tariff Model Resource • Green Button Connect My Data Testing and Certification • Complete function block descriptions • Complete test case requirements

8. How to use BR=bulkID – relates to HD #61 • Application Profiles • BulkID was proposed for large sets of authorizations • One account level authorization on top of service level accounts – how to do this • Degrees of freedom we have now – can we cover • Subscription – 1 or more Usage Points • Granularity of a customer authorization • BulkID • “macro” for a large set of existing authorizations • Is there another degree needed?

9. Contributed by Jerry Yip • Clarification/confirmation about ESPI standard:  Does ‘shared resource key’ referenced in the NAESB Ratified word doc correspond to Access Token for oAuth? • Yes: This is the access token in the new Oauth 2.0 paradigm. • Formal Submission of Application Profile for bulk (vs. batch?) use case as part of GB/GBC Conformance Testing Plan • Write up coming to test concept of BulkIDs • Question:  (options to address 1 Acct to many SA issue)- Does UUID correspond to usage point (1-to-1 relationship)?  Is there passing of UUIDs (as resource terms in Scope section of GBAuthorization) during authorization sequence?  (how would 3rd Party know multiple usage points have been authorized via single oAuth sequence/login?)- Can multiple access tokens be issued (1 token per SA) per oAuth session? • An Authorization is one access_token • How does Third Party get to know the depth of data (how many Ups) are in the authorization • Perhaps an extension of scope string to have numUPs? • Request to consider scope selection screens at Data Custodian Portal instead of 3rd party portal (Need customer to select SAs to share – only Data Custodian has that info) – also minimizes number of redirects (?) • Customer info as optional functional block (atom feed) for authorization (sharing with 3Ps) • John suggests – prep a large multi account data set and test against a reference sw implementation and measure. SFTP and Streaming, compressed and non-compressed method and compare.

10. =

11. How to use BR=bulkID with application to account and account groupings, as well as, large ThirdParty collections of Authorizations • Establish Use Case Story for Commercial Accounts • Design Scope String(s) that convey it • Repaint the storyboard with appropriate content

12. Application Profile • Per footnote 1, pg 20 of GBAuthorization.doc: • A “Web Customer” may actually manage more than one “Retail Customer” where “Retail Customer” is an actual “Customer Account”.   Thus identifying the specific Retail Customer may be part of the scope selection on both sides. The scenarios in this section refer to the “Retail Customer” for simplicity. • Suggest: new FB or Application Profile to properly capture this scenario • [FB_31] Web Customer Manages Multiple Customer Accounts (OR: 3.9 Application Profile) • For GBCMD, this FB/AP contains tests associated with a Web Customer accessing a Data Custodian’s Web Portal to manage multiple customer accounts. Upon log in to the Data Custodian’s Web Portal, the web customer can manage multiple customer accounts, for which each customer account can represent multiple usage points (for electricity and/or gas). This mostly impacts large agricultural and commercial customer accounts for which a single web customer can represent hundreds to thousands of individual usage points – imagine a franchise manager with multiple branch locations across a data custodian’s service territory. • In this scenario, the Web Customer should have the ability to authorize, deauthorize and change scope on an individual “usage point” basis and optionally at the larger aggregated web customer or customer account basis. This includes the ability to perform one-time authorization of multiple customer accounts by a single web customer to third party, and any subsequent scope changes (whether on an aggregated or individual basis) – third party acknowledgement/communication of which customer accounts have been authorized, deauthorized or whose scope has changed needs to be determined. • Notes: • Whether scope selection in this scenario should live on the 3rd party portal vs. the Data Custodian’s portal needs to be determined as well. • Collection has one description or multiple? • What is the scope string for this use case? • Is there a need for a bulkId in this case (maybe not). • New Scope Resource Term= “BulkAccountCollection” • Scope= “FB=4,5,15;IntervalDuration=3600;BlockDuration=monthly;HistoryLength=13;BulkAccountCollection” • 1/14/2014 • To allow the TP to know how many Ups are being provided, suggest Add to BulkAccountCollection a number of UsagePointsBulkAccountCollection=nnn

13. UsagePoint Grouping in Commercial Account Management BulkId SubscriptionId UsagePointId /web account Via gui Scope= “FB=4,5,15;IntervalDuration=3600;BlockDuration=monthly;HistoryLength=13;BulkAccountCollection”