Please use this portal to submit ideas for our development team to consider in its roadmap. For support or data issues, please send an email to: iedr-support@esource.com to receive more immediate assistance.
Shera - thanks so much for your Idea and question!
Customers will be able to authorize their consent to a third party to access their data through the Green Button Connect protocol in the Efficient and Effective Access to Existing Customer Billing Data Use Case.
Timing: MVP
If an ESE already has consent to access customer(s) data, how would your existing LOAs ideally be transitioned into the IEDR platform? What would be the impact of having to ask existing customers for new authorization?
Timing: TBD
Per the IEDR White Paper and DAF Order, DSA (data security agreement) is the terminology used by the IEDR program (i.e.Data Dictionary; use cases; features) for documentation related to authorization of and access to customer data. It would be helpful for us to better understand how you use LOAs:
Our understanding is that LOAs are: between an ESE and a customer; used to access raw customer data and for benchmarking purposes; PDFs accessible for customers to sign online and offline; used to verify customer's authentication. Please confirm if these assumptions are correct.
How are the authentication process and uses different for residential customers and commercial customers? It would be helpful if you could explain the process in steps. Are there scenarios in which agents are authorized to procure on behalf of the customers?
Timing: Phase 2
IEDR will be the centralized platform for accessing customer energy data in NYS; the details for authorization and consent are being determined by DPS in the Data Access Framework (DAF) Order (currently in process). Once DAF is finalized IEDR will implement the required protocols.
Timing: TBD
Aggregated customer data will also be available to users on IEDR which will not require customer consent, which will be addressed in multiple future Use Cases.
Timing: Phase 2
We will have user community engagement as use cases and supporting features are further defined and prioritized; we look forward to working with you (and others)! (We will be able to track Ideas submitted in the Ideas Portal to epics and features as they are voted on, prioritized, defined/designed and released for a fully transparent feedback loop.)
Shera - thanks so much for your Idea and question!
Customers will be able to authorize their consent to a third party to access their data through the Green Button Connect protocol in the Efficient and Effective Access to Existing Customer Billing Data Use Case.
Timing: MVP
If an ESE already has consent to access customer(s) data, how would your existing LOAs ideally be transitioned into the IEDR platform? What would be the impact of having to ask existing customers for new authorization?
Timing: TBD
Per the IEDR White Paper and DAF Order, DSA (data security agreement) is the terminology used by the IEDR program (i.e.Data Dictionary; use cases; features) for documentation related to authorization of and access to customer data. It would be helpful for us to better understand how you use LOAs:
Our understanding is that LOAs are: between an ESE and a customer; used to access raw customer data and for benchmarking purposes; PDFs accessible for customers to sign online and offline; used to verify customer's authentication. Please confirm if these assumptions are correct.
How are the authentication process and uses different for residential customers and commercial customers? It would be helpful if you could explain the process in steps. Are there scenarios in which agents are authorized to procure on behalf of the customers?
Timing: Phase 2
IEDR will be the centralized platform for accessing customer energy data in NYS; the details for authorization and consent are being determined by DPS in the Data Access Framework (DAF) Order (currently in process). Once DAF is finalized IEDR will implement the required protocols.
Timing: TBD
Aggregated customer data will also be available to users on IEDR which will not require customer consent, which will be addressed in multiple future Use Cases.
Timing: Phase 2
We will have user community engagement as use cases and supporting features are further defined and prioritized; we look forward to working with you (and others)! (We will be able to track Ideas submitted in the Ideas Portal to epics and features as they are voted on, prioritized, defined/designed and released for a fully transparent feedback loop.)
Timing: Ongoing + TBD