Embed Size (px)
Citation preview
Rule 24 DRP/Aggregator Set Up Steps & CISR-DRP Overview August 30, 2016
Agenda
Rule 24 Set Up Steps
PG&E’s Customer Information Service Request-
Demand Response Provider (CISR-DRP) Form Key content
Instructions for completing and submitting the form:
Electronic Signature
Wet signature
Receiving and Utilizing Customer Data Data sent via ShareMyData (SMD)
Data sent via Electronic Secure File Transfer (ESFT)
ShareMyData Platform Overview
How do I register?
Participation in IOU and Third-Party DR programs Restrictions on dual participation
Unenrollment guidance 2
High Level Overview DRP Set up Brad Wetstone
Rule 24 Set up Non Utility DRP N
on
Uti
lity
DR
PR
ule
24 (
PG&
E)ES
FT (
PG&
E)SM
D (P
G&
E)
DRP now able to submit CISR-DRP
Forms(7.0)
Contacts the ESFT admin for set up in
ESFT system(4.0)
DRP Completes the DRP information request form
and returns to DRP relations mailbox
(2.0)
Send acknowledgment email to DRP (Include
Rule 24 DRP ID)(6.5)
Initiates connectivity testing with DRP
ESFT(4.1)
Does the DRP Connect with
ESFT(4.2)
YES
Non Utility DRP registers as a
standard user in SMD(5.0)
Works with DRP to correct connectivity
issues (4.3)
NO
YES
Supplies the Non Utility DRP with Information on how to
get started(1.0)
Notifies ESFT group that DRP will be
calling(3.0)
Notifies PGE Rule 24 of Completed SMD
setup(6.3)
END
Start
Initiate connectivity with SMD
(6.0)
Does the DRP connect with the
SMD system?(6.1)
Works with DRP to correct connectivity
issues (6.2.)
NO
YES
Pass all connectivity processes for both SMD and
ESFT(6.4)
NO
CISR-DRP Form Overview Steve Debacker
Key Content on PG&E’s CISR-DRP Form
Identifies and references the regulatory rules and PG&E’s policies
under which the release of data shall occur
Identifies that release is subject to CPUC jurisdiction
Identifies parties involved
Provides contact information for parties
Sets scope: Identifies the service agreements subject to data release
Information authorized to be released to DRP(s) (interval data, rate
schedule, sublap, etc.)
Actions that DRP(s) are allowed to request (shortening interval length,
PDP unenrollment)
Timeframe of authorization
Data delivery method
Collects enough information to allow for validation by PG&E
Signature blocks
6
Submitting a CISR-DRP
7
CISR-DRP with electronic signatures:
1. DRP works with the customer to complete the CISR.
2. The customer electronically signs the form.
3. The DRP(s) electronically sign the completed customer e-signed form.
4. Attach the one-page e-signature Certificate of Completion corresponding
to all of the electronic signatures used on the form to the CISR-DRP.
5. The DRP posts the e-signed form to PG&E’s ESFT.
6. PG&E is accepting e-signatures using the following two vendors: (1)
Adobe eSign (formerly EchoSign); and (2) DocuSign.
CISR-DRP with wet signatures or a scan of wet signatures:
1. DRP works with customer to complete the CISR and get a paper copy of
the completed CISR to the customer.
2. The customer ink signs the paper CISR and sends it to the DRP.
3. The DRP ink signs a paper copy of the completed customer-signed form.
4. The DRP scans the completed customer-signed and DRP-signed form.
5. The DRP posts the scanned image to PG&E’s ESFT.
Do not send customer information to PG&E via e-mail.
CISR-DRP Form
8 Link to CISR-DRP Form
CISR-DRP Form, Cont.
9
10
Sample Bill Do not provide
the Account #
as SAID
11
Sample Bill, Cont. Do not
provide the
Account # as
SAID
Process flow for reviewing submitted CISRs
12
Common Errors Found on Submitted CISR-DRP Forms
System automatically checks for CISR form errors.
Most Common Errors
1. The Service Agreement ID (SAID) entered on the CISR form does
not exist in PG&E’s systems as an SAID. The Account ID, Meter
#, or SubSA for a CCA-served customer may have been entered
instead.
2. The SAID is not active. This could be due to the customer moving
to a new address.
3. The SAID entered on the CISR form is an SAID in PG&E’s
systems, but it is not for electric service (e.g., it’s for gas).
4. The service address entered on the CISR form does not match the
service address in PG&E’s systems.
5. Form is incomplete. For example, the customer or DRP did not
select the appropriate check boxes or did not sign in the
appropriate signature block.
13
Receiving and utilizing customer data Overview Steve Debacker
Data Flows Item Transmitted From To Notes
Completed CISR from
DRP to PG&E
ESFT DRP PG&E Uses folder
“Vendor to PG&E”
Historical and Ongoing
monthly usage quantities
SMD API* PG&E DRP
Historical and Ongoing
interval usage data
SMD API PG&E DRP
Other Rule 24 data
(Sublap, DR programs,
etc.)
ESFT PG&E
DRP Uses folder “PG&E
to Vendor”
Exceptions to submitted
CISR
ESFT PG&E
DRP Uses folder “PG&E
to Vendor”
Do not send customer information to PG&E via e-mail.
Data flow
15
*Application Program Interface
SMD – What’s Provided?
•Account Identifiers
•Commodity Type (Gas or Electric)
•Date
•Time
•Usage Hour
•Interval Number
•Interval Length (15 vs 60 min)
•Daylight Savings Flag
•Direction of Energy (NEM/Solar)
•Billing History
•Demand
•Unit of Measure (Interval vs Summary)
•Usage Value (Wh)
•Unique SA UUID
•Interval Billed Flag
•Quality of Reading (interval)
•Usage Summary (duration, start)
•Quality of Reading (usage summary)
**Note: This is a summary and not intended to represent a comprehensive list of data elements
ESFT Folders
Each DRP will be assigned a unique 10-digit DRP ID. This ID will be used to name each DRP’s respective ESFT main folder.
A DRP named ABC Company has been assigned by PG&E a Rule 24 ID = 1000000225
17
Data Elements Sent ESFT
General
CISR_Docket Rule 24 ESFT Flat File
CISR_SA_ID Rule 24 ESFT Flat File
CURRENT_SA_ID Rule 24 ESFT Flat File
UUID Rule 24 ESFT Flat File
Customer_Name Rule 24 ESFT Flat File
Service_Address Rule 24 ESFT Flat File
Service_City Rule 24 ESFT Flat File
Service_State Rule 24 ESFT Flat File
Service_Zip Rule 24 ESFT Flat File
Sublap_Name Rule 24 ESFT Flat File
Pnode Rule 24 ESFT Flat File
Electric_Rate_Schedule Rule 24 ESFT Flat File
Customer_LSE_Company_Name Rule 24 ESFT Flat File
Customer_MDMA_Company_Name Rule 24 ESFT Flat File
Customer_MSP_Company_Name Rule 24 ESFT Flat File
Meter_Number Rule 24 ESFT Flat File
Meter_Type Rule 24 ESFT Flat File
Data_interval_Collected Rule 24 ESFT Flat File
Cust_Meter_Read_Cycle Rule 24 ESFT Flat File
Cust_Service_Voltage_Class Rule 24 ESFT Flat File
DR Programs
Cust_DR_Program Rule 24 ESFT Flat File
Cust_DR_Program_Status Rule 24 ESFT Flat File
Cust_DR_Program_Enrollment_Date Rule 24 ESFT Flat File
Cust_DR_Program_De-Enrollment_Date Rule 24 ESFT Flat File
Cust_DR_Program_Term_Date_Regardless_Financial Rule 24 ESFT Flat File
Cust_DR_Program_Term_Date_Without_Financial Rule 24 ESFT Flat File
18
Data File Sent ESFT
Comma separated values (CSV)
no quotes on header
quotes on data elements
Utility Unique Identifier (UUID).
This is the value used as Service Account Number (SAN) in
CAISO DRRS. Must have the leading UPGE_____.
19
Data File Details
2 meters and 2 DR programs = 4 rows
1 meter and 2 DR programs = 2 rows
20
Share My Data Overview Lindsay Miller
The Program — What is it?
• API platform that allows PG&E customers to share their interval meter data and account information with a third party.
• There are no restrictions as to meter type.
• Offers electric & gas interval data, billing data, and account PII.
• Historic data is available, as is daily usage data on an ongoing, subscription basis.
The Platform — How does it work?
• Share My Data implementation follows the national Energy Service Provider Interface Standard, also known as ESPI.
• The ESPI standard was developed and adopted to ensure consistency in the data provided to third parties by utilities across the nation.
• The ESPI standard prescribes the technical framework for delivering functionality around customer authorization, data exchange and the format of the authorized data that is exchanged.
The Platform — How does it work?
• Authorization: OAuth 2.0 is implemented for customer to 3rd party authorization.
• Data Exchange: Restful APIs are utilized for exchange of data.
• Note: Per ESPI Security requirements, APIs are over 2-way SSL using SHA-2 certificates.
• Data Format: Atom (XML language) formatting of the data that is exchanged.
The Process – How do I register?
Step 1: Information Gathering
You’ll need some important information before you register, so please gather the following ahead of time:
• Tax ID – Your 9-digit U.S. Employer Identification Number (EIN)
• Business & Technical Contact information
• OAuth 2.0 and Data Access/Notification URIs – Functional URI’s preferred, but placeholders will work.
• Valid SSL Certificate - You’ll need this to complete registration. All certificates must be 2048 bit, SHA-2 certificates. Certificates cannot be self-signed.
The Process – How do I register?
Step 2: Review Technical Documentation
We highly recommend studying the following resources:
From greenbuttondata.org:
• Green Button Implementation Agreement
• ESPI OAuth 2.0 Sequence Diagram
• Green Button Data Software Development Kit
PG&E Developed Software Development Kits
• Available in Python and Javascript
The Process – How do I register?
Step 3: Register for Access
The Share My Data registration process allows you to identify yourself to PG&E as a company that would like to access customer-authorized data and set up access to our APIs.
Register at sharemydata.pge.com
• Review and Submit Your Registration
• Confirm Your Email Address
• Submit Your SSL Certificate
The Process – How do I register?
Step 4: Complete Testing
The purpose of testing is to verify that you are able to connect to our systems. Once we have your SSL certificate, we will send you an email with your credentials and instructions to begin testing.
There are three tests that must be completed before customers can release their data to you:
• API Connectivity Test
• OAuth 2.0 Test
• Application Information Resource Request
**Note: You will have 90 days to complete testing. If you do not complete testing within 90 days, you will need to re-register.
Participation in IOU and Third-Party Administered DR Programs Steve Debacker
Brad Wetstone
Dual Participation Restrictions
30
Under Rule 24, a customer cannot be enrolled in a PG&E event-based
DR program and included in a third-party DRP’s CAISO registration
during the same time period.
The Rule 24 restriction on dual participation applies to the following
event-based programs and rates.
Aggregator Managed Portfolio (AMP)
Capacity Bidding Program (CBP)
Base Interruptible Program (BIP) Aggregated
Peak Day Pricing (PDP)
SmartRate (SMR)
SmartAC
Base Interruptible Program (BIP)
Demand Bidding Program (DBP)
Schedule Load Reduction Program (SLRP)
Optional Binding Mandatory Curtailment (OBMC) Plan
Guidance for PG&E DR Program Unenrollment
31
Peak Day Pricing PG&E will initiate unenrollment only when the customer is included in a
CAISO registration. The start date for the CAISO registration must be no
sooner than or equal to the customer's effective PDP unenrollment
date. To help ensure that a customer is unenrolled prior to the effective
start date of the CAISO registration, PG&E strongly recommends that the
customer initiate the unenrollment process by contacting the customer's
PG&E account representative or calling 1-800-PGE-5000.
Other PG&E DR Programs (AMP, CBP, BIP, etc….)
Customers initiate the unenrollment process for a particular PG&E DR
program prior to the DRP including the customer in a CAISO registration.
It is important that the start date of the CAISO registration must be
greater than or equal to the end date of the PG&E DR program
participation.
To learn more about how customers can unenroll from PG&E DR programs
visit the FAQ section of PG&E’s Rule 24 –Third Party DRP website.
Contact information
PG&E’s Rule 24 Website for DRPs/Aggregators
www.pge.com/en/mybusiness/save/energymanagement/electricrule24/thirdparty.page
Share My Data: www.pge.com/sharemydata [email protected]
ESFT: [email protected]
PG&E’s Rule 24 Team: [email protected]
DRAM website: www.pge.com/dram
32
