California Solar Initiative

Size: px

Start display at page:

Download "California Solar Initiative"

Jordan Curtis
8 years ago
Views:

1 California Solar Initiative EDI 867 Implementation Workshop March 19, 2009 Performance Data Providers (PDP) & Performance Monitoring & Reporting Service Providers (PMRS) 2

2 - Welcome & Introductions - CPUC Data Request - Recent Program Updates Agenda - PDP Qualifications and Documentation Requirements - Break - PDP Application Process - PA Specific Guidelines - EDI submission requirements - Lunch - EDI 867 Implementation - Background/Benefits - Requirements & Testing - PA Specific Guidelines/Goals - Break - Lessons Learned/Q & A 9:30 9:45 9:45 10:15 10:15 10:45 10:45 11:05 11:05 11:15 11:15 12:00 12:00 1:00 1:00 1:30 2:15 2:25 2:25 3:30 3

867 Implementation - Background/Benefits - Requirements & Testing - PA Specific Guidelines/Goals - Break - Lessons

3 Primary Goals 1. Clarification on current CPUC data request and future M&E requirements 2. Ensure understanding of PDP qualifications and documentation requirements 3. Provide PDPs the information to meet the Electronic Data Interchange (EDI) 867 implementation guidelines for each Program Administrator 4

Ensure understanding of PDP qualifications and documentation requirements 3.

4 CPUC Data Request for CSI Impact Evaluation/Measurement & Evaluation Overall CSI Measurement & Evaluation (M&E) Efforts Purpose: Evaluate CSI impacts to provide reliable results for policy makers, resource planners, and program administrators CSI Impact Evaluation Annual report containing the generation of all CSI participants, demand reduction, PV system performance, greenhouse gas reductions, impacts on transmission and distribution, etc. CPUC has contracted with Itron to perform the CSI Impact Evaluation Will be conducted yearly. In the future, PAs will submit data on behalf of PDPs. Data request issued by the CPUC PDP/PMRS contractors are obligated to provide Itron with data to the extent that data is available Raw 15-min interval data (EDI 867 format if available) for each CSI solar system operating in 2007 and Due to Itron by COB Wednesday, March 25, PG&E contact: Matt Heling (415) or 5

reductions, impacts on transmission and distribution, etc. CPUC has contracted with Itron to perform the CSI Impact Evaluation Will be conducted yearly.

5 Recent Program Updates Recent Advice Filings and Handbook Updates Approved PDP Qualifications and Application Process Approved EDI 867 and Secured File Transfer Protocol sftp as data transfer protocol Approved EDI implementation and mapping guides Defines Communication and Metering Requirements Defines responsibilities of system owners and PDPs regarding meter accuracy and certification Meter must have a visible serial number Meter Certification testing certificate (if requested) Redefine accuracy of electric meter to include the accuracy of all metering system components Clarifies that payments are based on gross generation Define PBI payment timeline & retroactive payments Reporting and documentation requirements 6

meter accuracy and certification Meter must have a visible serial number Meter Certification testing certificate (if requested) Redefine accuracy of electric meter to include the

6 PDP Qualification Process All applicants must be approved Performance Monitoring & Reporting Service Providers on the CEC website Must submit individual PDP applications to each Program Administrator Application to provide PDP services Supporting documentation $25,000 bond in favor of the state of CA Upon approval, Program Administrator will provide information required to submit data in EDI 867 format All qualified PDPs must have EDI 867 capabilities and be setup with the respective PA prior to the payment of any customer incentives Current PDPs will be required to work with the PA to meet guidelines as outlined in CSI program hand book Prospective PDPs submitting applications after April 2009 will be required to have EDI capabilities upon application to provide PDP services 7

data in EDI 867 format All qualified PDPs must have EDI 867 capabilities and be setup with the respective PA prior to the payment of any customer incentives Current PDPs will be required to work

7 Documentation Requirements Incentive Claim Form (ICF) Documentation PMRS/PDP contract or equivalent Executed contract with approved provider(s) Letter from the PMRS and/or PDP provider Invoice from installer detailing services provided Performance Meter make, model and serial number(s) ** Communication with the Performance Meter must be complete prior to submitting the ICF Project Approval Program Administrator issues Incentive Claim Approval (ICA) letter Specifies: data reporting period, PBI start date and incentive rates Provides project specific identifiers (Channel ID, Meter ID etc.) 8

Communication with the Performance Meter must be complete prior to submitting the ICF Project Approval Program Administrator issues Incentive Claim

8 PBI Payment Timeline 1. Incentive Claim Form (ICF) Received 2. PA approves application and issues Incentive Claim Approval Letter specifying the start date of the data collection period 3. PDP submits monthly production data including retroactive data (if applicable) by due date 4. PA reviews and verifies monthly production data and issues PBI payment within 30 days of the end of the 9 data report period

9 EDI 867 Implementation Background EDI 867/sFTP selected as industry standard PDP Workshops and Metering Subcommittee Advice Filings & CPUC Decisions Benefits Simplified Processes as number of customers increases Reduced processing time (PDP and PA) Lower admin costs Faster payments to customers Greater accuracy Common EDI 867 File information Format, CSI application number, etc. **Goal: A smooth transition from the current process of submitting interim Excel date reports to automated EDI submissions 10

Lower admin costs Faster payments to customers Greater accuracy Common EDI 867 File information Format, CSI application

10 PG&E EDI 867 Requirements/Testing Protocols 1. Complete Trading Partner (TP) agreement & Connectivity documentation (Goal: April 15 th, 2009) 2. GXS sets up SFTP/TP profiles and connectivity processes 3. GXS contacts PDP to schedule testing (Goal: May 6 th, 2009) If initial test fails, each PDP has 2 weeks to correct the error and resubmit Guideline: After 3 failed tests, PDP is ineligible to contract with any additional CSI customers (Subject to PA discretion) 4. Upon PG&E approval of received production data GXS moves PDP into production and PDP can submit production data during the next reporting period **Goal: All PDPs set up to provide production data for all customers by end of Q2,

GXS contacts PDP to schedule testing (Goal: May 6 th, 2009) If initial test fails, each PDP has 2 weeks to correct the error and resubmit Guideline: After 3 failed tests, PDP

11 SCE EDI 867 Requirements/Testing Protocols PDP provides the IP Address to SCE to schedule data transfer test PDP Submits public key with the following criteria (SCE needs the actual file): No passphrase, Key type = RSA and Key length = 1024 Public Key Definition: A cryptographic system that uses two keys -- a public key known to everyone and a private or secret key known only to the recipient of the message Partial sample: xxxxx rsa-key Submit EDI Partner Profile to SCE Schedule Data Transfer test After successful testing the PDP receives final approval and will be eligible to send customer generation data 12

the recipient of the message Partial sample: 1024379252263923801602684941xxxxx4162144295811750220185134690559088 5909676840864301437568713776509955123930948629295

12 SCE and EDI 867 Set and Testing Communication begins with PM until ready to start transmitting test files, IT takes lead Pre-Implementation review through to validate proper EDI attributes and header information PDP and IT set up SFTP Servers between SCE and PDP (IP address, public key) SCE will work with PDP to achieve the goal of successful testing of EDI867 file transmission between SCE and PDP by the end of Q2 (may require more than 3 attempts) EDI Software Each PDP should choose their own or use a third party Examples: Altova Mapforce, Gentran (SCE) and EDIDEV 13

public key) SCE will work with PDP to achieve the goal of successful testing of EDI867 file transmission between SCE and PDP by the end of Q2

13 SCE and EDI 867 Guidelines and information for EDI is available in the CSI Handbook in both the Implementation Guide and Mapping Guide The following areas are brought to special attention EDI element separators * = element separator ~ = sub element separator =segment separator Beginning envelop segments of ISA and GS, showing SCE's receiving id and qualifier ISA*00* *00* *01* *16* *080509*1211*U*00400* *0*P*~ GS*PT* * * *1211*1*X* ST SE ST SE 14

separator =segment separator Beginning envelop segments of ISA and GS, showing SCE's receiving id and qualifier ISA*00* *00*

14 SCE and EDI 867 Corresponding ending header envelop segments of GE and IEA. The GE01 value '2' is the number of 867s or the number of ST to SEs GE*2*1 IEA*1* Values in EDI867 which are different between utilities BPT09 -- > Indicates cycle shift number, SCE uses only first shift, so always 1 for SCE, PG&E and CCSE both shift 1 and 2 Possible values (1 1st to 1st of next month, 2 16th to 16th of next month) REF BT 23 --> Indicates Cycle number, SCE calls it Report number 15

different between utilities BPT09 -- > Indicates cycle shift number, SCE uses only first shift, so always 1 for SCE, PG&E

15 SCE and EDI 867 Header information is suppose to be taken care by the EDI software. Below is the header information in detail (RED highlights different values for different utilities) (BLUE changes for every transactions) Field Length Type Value Data Element Summary (Name) ISA01 2 ID 00 No Authorization Information Present ISA02 10 A/N BLANK Authorization Information ISA03 2 ID 00 Security Information Qualifier ISA04 10 A/N BLANK Security Information ISA05 2 ID 01 Interchange ID Qualifier ISA06 15 A/N Interchange Sender ID (DUNS# FOR PDP) ISA07 2 ID 16 Interchange ID Qualifier ISA08 15 A/N Interchange Receiver ID ISA09 6 Date YYMMDD Interchange Date ISA10 4 Time HHMM Interchange Time ISA11 1 ID U Interchange Control Standards Identifier ISA12 5 ID Interchange Control Version Number ISA13 9 N NNNNNNNNN Interchange Control Number (Also in IEA Trailer) ISA14 1 ID 0 Acknowledgement Requested (No) ISA15 1 ID T Usage Indicator (Test, Production, or Information) ISA16 1 A/N ~ Component Element Separator GS01 2 ID PT Functional Identifier Code GS02 15 A/N Application Sender s Code (DUNS# FOR PDP) GS03 15 A/N Application Receiver s Code GS04 8 Date CCYYMMDD Date GS05 4/8 Time HHMM Time GS06 9 N NNNNNNNNN Group Control Number (Also placed in GE Trailer) GS07 1 ID X Responsible Agency Code GS08 6 A/N Version/Release/Industry Identifier Code 16

ID 00 No Authorization Information Present ISA02 10 A/N BLANK Authorization Information ISA03 2 ID 00 Security Information Qualifier ISA04 10 A/N BLANK Security Information ISA05 2 ID 01 Interchange

16 CCSE EDI 867 Requirements/Testing Protocols CCSE is still in the process of selecting a bidder for EDI services 17

17 Resources and Contact Information Pacific Gas & Electric Company (PG&E) Cassandra Mayall: (415) Web: Southern California Edison (SCE) Phone: (866) Suzanne Fuller: (626) Tom Pasker: (626) Web: California Center for Sustainable Energy Phone: (858) Web: PMRS Eligible Providers - Go Solar California website: 18

com/csi Southern California Edison (SCE) Phone: (866)-584-7436 Suzanne Fuller: (626) 633-3106 Tom Pasker: (626) 633-3183 Email: pbi@sce.

18 Questions? 19

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007 The following is an outline of what is expected when receiving VICS