Market Requirements Document

Transcription

1 Market Requirements Document Committee name: Prepared by: Deployment Working Group Joseph H. Cain, P.E. Modified Date: Revision Number: 1 This work was created under the DOE Project Number EE

2 Table of Contents 1 EXECUTIVE SUMMARY BUSINESS OPPORTUNITY Market Problem Value and Benefits to Customers MARKET REQUIREMENTS Landscape BUSINESS-ORIENTED CUSTOMER USE CASES Sales Agreement PV System Design AHJ Plan Review, Permitting, Inspection Utility Interconnection Construction Installation Commissioning Testing Initial Incentive Reporting SUPPORTING DATA MRD Assumptions Page 2 Orange Button Market Requirements Document -

3 1 Executive Summary To be added when consolidated following Area B review. 2 Business Opportunity Describe the market problem and resulting market opportunity. Solar deployment includes construction, testing, and interconnection with the grid. The construction data requirements include land entitlement requirements, permitting, real estate construction regulations, construction project management, and feedback from actual construction processes. Testing of the solar asset involves identifying the data needed to assure safety and reliability requirements are met, as well as the performance and regulatory requirements. During interconnection, the solar asset needs to coordinate closely with the utility and exchange the data needed by both parties for the grid integration process as defined by the Grid Interconnection standards and specifications. 2.1 Market Problem Keeping the customer s perspective in mind, identify and justify any market challenges that exist in the marketplace that require change. List the customer/stakeholder pain points that this standardized approach to data can alleviate. Significant useful data is generated during the Deployment phase of the solar project lifecycle. The Deployment working group focused on ways to standardize the needed data in both the input to, and output from, the Deployment phase. Inputs to the Deployment phase include information regarding site characteristics, locally adopted regulations, environmental and climatic data, and relevant customer information including anticipated electricity usage and potential system production. Outputs from the Deployment phase are used in every downstream phase of the solar asset lifecycle. The PV system is designed in the Deployment phase, including specific components and subsystems, and the system and design information is used in all subsequent phases. Non-standardized data usage in the Deployment phase can cause delays in project delivery and operational timelines while downstream data consumers reconcile the Deployment phase output data to the formats that are needed for their functions. Easier and faster access to the data needed for system design would accelerate the Deployment process. Increased uniformity in the data produced during the Deployment phase would speed Page 3 Orange Button Market Requirements Document -

4 downstream processes by eliminating the need for data consumers to reconcile the data to their specific needs. 2.2 Value and Benefits to Customers Describe the value proposition and list the primary benefits for industry stakeholders from this standardized data approach. Explain how and why this will be better and different than other solutions currently available. The utilization of standardized data types in the input to and output from the Deployment phase will yield benefits to all participants in the solar project lifecycle. Cost effectiveness of solar is largely dependent on economies of scale. The drive to capture economies of scale has driven many companies to use automated design platforms. A widely industry agreed upon and recognized need is to enable accelerated system design and deployment of solar. A standardized data taxonomy could enable a key next step in enhancing the efficiency of automated design platforms. Further examples of a benefits of standardized deployment data to both participants in the solar project lifecycle and end consumers of solar are: Decreased time to market for PV system deployment (accelerated system design) Lower overall project costs due to reduced time for data conversion Decreased time for solar product design, development, and certification Decreased time required for system commissioning and utility interconnection Greater solar project data uniformity leading to fewer mistakes, less rework, and lower overall implementation costs Direct beneficiaries of standardized deployment data include: Stakeholder: Solar Integrators and EPCs Benefit: A standardized and widely accepted Solar Deployment data taxonomy would greatly benefit Solar Integrators and EPCs who are involved in the design, installation, and transition to production of solar assets. The primary benefits include the ability to increase the speed and accuracy of system design and Page 4 Orange Button Market Requirements Document -

5 deployment. Benefits will also be realized in quality assurance, asset reliability, and asset durability. Financial Institutions Consumers Other Solar Project Lifecycle Participants Increased efficiency of financial operations and lower cost of capital (increased bankability). Investors will also reduce their risk due to increased visibility and availability of data. Increased bankability of solar projects and lower transaction costs will enable greater penetration of solar and deliver solar benefits to a larger consumer market. All parties involved in the solar project lifecycle will benefit in standardized deployment data by reducing the time involved for each participant to become oriented to the data being used relevant to their function. Improved efficiency and speed through each phase of a solar project will improve overall project quality, reduce project cost, and improve bankability. 3 Market Requirements 3.1 Landscape The primary goal of the Deployment phase is the design and deployment of a system that safely produces power and meets the needs of the consumer. Data consumed and generated by the Deployment phase includes electrical safety, structural safety, and other permitting concerns. Deployment processes are foundational in the Solar Project lifecycle and all subsequent phases rely on accurate data being generated. The use cases developed by the Deployment working group are: Source: Description: Priority: MR-DEP.001 Sales Agreement, including Customer Acquisition and Feasibility 1 MR-DEP.002 PV System Design, including Electrical & Structural Design 1 MR-DEP.003 AHJ (Authority Having Jurisdiction) Plan Review, Permitting, Inspection, 1 Page 5 Orange Button Market Requirements Document -

6 Approval MR-DEP.004 Utility Interconnection (Plan Approval; Permission to Operate)* 3 MR-DEP.005 Construction/Installation 3 MR-DEP.006 System Commissioning and Testing* 3 MR-DEP.007 Initial Incentive Reporting* 3 *The Area A did not have volunteer resources with the expertise needed to identify the data types required for use cases MR-DEP.004, MR-DEP.006, and MR-DEP.007. The team will interface with Team B resources and identify the data types needed to meet the requirements as defined in those use cases. 4 Business-Oriented Customer Use Cases 4.1 Sales Agreement Use Case: Sales Agreement, including Customer Acquisition and Feasibility Id: MR-DEP.001 Description: This use case addresses the data needs of all pre-deployment activities that facilitate the qualification of potential solar sales. Activities include: 1. Lead generation 2. Qualification of leads (e.g., credit qualification) 3. Presentation of qualified leads to sales staff 4. Consultation with owner 5. Phase I feasibility study (e.g., site qualification, review of actual or estimated electricity demand) 6. Preliminary PV system sizing, selection of components, and system layout 7. Creation and execution of the sales agreement Lead generation includes qualification of leads (credit qualification, site qualification, actual or estimated electricity demand); presentation of qualified leads to sales. Page 6 Orange Button Market Requirements Document -

7 Feasibility process usually occurs in two phases. Phase I typically occurs prior to a sales agreement being executed and Phase II typically occurs after execution of the sales agreement. This use case encompasses Phase I feasibility study process. Phase I feasibility includes: Electricity Demand (historical electrical usage or estimated electrical demand) Site Qualification Constraints of Shading (often based on satellite images) Energy Modeling Estimate of Utility Savings Priority: 1 Primary Actor(s) Lead Generator Sales staff Supporting Actors Project Developer Stakeholders and Interests Technical support staff (often called Technical Sales or Development Engineering ) Real Estate Agent Financial Institution Pre-Conditions Solar not yet installed at the site (or expansion of existing solar installation) Post Conditions Success end condition Sales agreement executed; project handed off to design and finance teams Lead disqualified and removed from consideration or deferred to future reconsideration Failure end condition: Page 7 Orange Button Market Requirements Document -

8 Lead unable to be qualified or disqualified due to insufficient information or other reason (e.g., customer had insufficient credit history or became non-responsive) Trigger Potential customer identified and targeted Data Required: Site Address Historic electrical usage and/or estimated electrical demand Available roof space Orientation and slope of potential rooftop mounting planes Preliminary limitations of shading (e.g., satellite images) Available rebates/incentives Customer credit history (e.g., FICO score) Utility rates for electricity (e.g., tiered rate structures) Extensions: Variations: Frequency: One time or as desired Assumptions: Data available is adequate to perform lead generation process (Google Earth shows shading, etc.) Customer data is accurate up to date 4.2 PV System Design Use Case: PV System Design, including Electrical & Structural Design Id: MR-DEP.002 Page 8 Orange Button Market Requirements Document -

9 Description: This use case addresses the data needs for all pre-deployment PV system design processes, beginning with an executed sales agreement and concluding with design documents ready for submittal to a local permitting Authority Having Jurisdiction (AHJ) and local utility for interconnection. Activities include: 1. Review of sales agreement 2. Site audit 3. Phase II feasibility study (if any issues, then recirculation of data and, if necessary, revise sales agreement) 4. Confirmation of PV panel & inverter selection, PV system layout, selection of mounting system, routing of conductors 5. Energy estimate based on final system configuration 6. Calculation of conductor sizes per NEC requirements 7. For rooftop systems, qualification of existing roof structure 8. For ground mount systems, design of foundation system Feasibility process usually occurs in two phases. Phase I feasibility process typically occurs prior to a sales agreement being executed, and Phase II typically occurs after execution of the sales agreement. This use case encompasses Phase II feasibility study process. Phase II feasibility includes: Desired PV system size per sales agreement Preliminary Design Constraints of Shading (based on site audit data) Energy modeling Recirculation of data if issues are discovered Priority: 1 Primary Actor(s) Site Auditor PV System Designer Professional Engineer in Electrical Engineering (commercial only) Professional Engineer in Civil and/or Structural Engineering (commercial and some residential) Supporting Actor(s) Technical support staff (often called Technical Sales or Development Engineering ) Sales Staff EPC Page 9 Orange Button Market Requirements Document -

10 Stakeholders and Interests Asset Owner Component manufacturers Pre-Conditions Sales process has been successful and sales agreement has been executed. Post Conditions Success end condition: Success end condition is a designed PV system designed: Meets the electrical demand of the consumer according to the sales agreement, and Conformance with locally adopted regulatory codes & standards. Failure end condition: Failure end condition results from one or more of the following: Inability to satisfy terms of sales agreement owing to project constraints Unforeseen expense related to electrical panel or other parts of electrical system Disqualification of roof structure Customer cancellation of sales agreement Trigger: Successful execution of sales agreement Data Required: Site Address Historic electrical usage and/or estimated electrical demand Limitations of Shading (based on site survey data) System Information (# of panels, # of inverters, # of strings, # of combiner boxes, panel and inverter models) Contact information for AHJ; other design professionals Locally adopted codes (i.e., which codes and which editions) AHJ-specific requirements (i.e., local policy) Local temperature data Climatic data (e.g., design wind speed; design snow load; seismic design parameters) Page 10 Orange Button Market Requirements Document -

11 Utility Interconnection parameters For rooftop mounted PV systems: Available roof space Orientation and slope of potential rooftop mounting planes Required fire access pathways for rooftop ventilation Required fire setback from ridge(s) Required Fire Classification of Building Fire Classification of PV System (per UL 1703 & UL 2703) Requirements for Rapid Shutdown Systems (RSS) If rafters: size, spacing, and span of framing members If plated trusses: truss geometry, as well as size, spacing, and span Lumber grade (e.g., DF#2) For ground mount systems: Ground parameters (slope; azimuth; contours) Type of foundation system (e.g., driven steel piles, ground screws, helical anchors) Soil Classification per USCS (or use default soil classification) Extensions: Variations: Frequency: Once per phase Assumptions: 4.3 AHJ Plan Review, Permitting, Inspection Use Case: AHJ (Authority Having Jurisdiction) Plan Review, Permitting, Inspection Id: MR-DEP.003 Description: This use case addresses the data needs for advancing a PV system project through the regulatory enforcement phase prior to and during deployment. Activities include: Page 11 Orange Button Market Requirements Document -

12 1. Fill out and file permit application 2. Submit of plans and reports 3. Plan review 4. Recirculate plans if corrections are required 5. Issuance of permit(s) 6. Site inspection(s) Priority: 1 Primary Actor(s) Solar permit specialist (applicant) Plans Examiner (aka Plan Checker) Building Inspector Supporting Actor(s) AHJ Permit Technician (application intake) PV System Designer Stakeholders and Interests Asset Owner Pre-Conditions PV system is designed in conformance with applicable codes & standards PV system plans and reports are prepared for submittal Post Conditions Success end condition: Success end condition is PV system successfully passes AHJ plan review and inspections, and has AHJ approval for interconnection Failure end condition: Project cannot move forward owing to inability to obtain required permit(s) Trigger: Successful completion of design process (next step in fulfillment of sales agreement) Data Required: Page 12 Orange Button Market Requirements Document -

13 Site Address Assessor s Parcel Number (APN) PV panel/module make & model number PV panel (module) Type Rating (according to UL 1703) PV panel/module quantity Inverter make & model number Inverter quantity Selected components qualified for incentive programs Mounting system parameters Conductor sizing and routing indicated on plans Line-side tap or Load-side tap, in conformance with AHJ and utility policy Conformance with applicable product/system standards: UL 1703 for panels/modules UL 2703 for mounting systems (portions are optional) UL 1741 for inverters Manufacturers Installation Instructions For rooftop mounted PV systems: Required fire access pathways for rooftop ventilation Required fire setback from ridge(s) Required Fire Classification of Building Fire Classification of PV System (per UL 1703 & UL 2703) Requirements for Rapid Shutdown Systems (RSS) For ground mount systems: Type of foundation system (e.g., driven steel piles, ground screws, helical anchors) Soil Classification per USCS (or use default soil classification) Required setbacks from buildings and property lines (if applicable) Extensions: Variations: Frequency: Once per phase Assumptions: 4.4 Utility Interconnection Page 13 Orange Button Market Requirements Document -

14 Use Case: Utility Interconnection (Plan Approval; Permission to Operate) Id: MR-DEP.004 Description: This use case encompasses Phase I and Phase II utility interconnection processes. Phase I typically occurs prior to construction and Phase II typically occurs after construction and after the AHJ has granted approval of final inspection. Phase I includes: Plan approval Interconnection Agreement Phase II includes: Inspection Corrections (if applicable) Permission to Operate (PTO) Priority: 3 Primary Actor(s) PV Integrator Interconnection Specialist Utility Interconnection Specialist Supporting Actor(s) PV System Designer Stakeholders and Interests Asset Owner Utility Pre-Conditions Phase I pre-condition is PV system has been successfully designed Phase II pre-condition is PV system successfully passes AHJ plan review and inspections, and AHJ has approved final inspection Page 14 Orange Button Market Requirements Document -

15 Post Conditions Success end condition: Phase I success end condition is execution of Interconnection Agreement (pre-construction) Phase II success end condition is successful Utility Interconnection and Permission to Operate (PTO) Failure end condition: Phase I failure end condition is inability to deploy PV system owing to inability to execute Interconnection Agreement, owing to missing or inadequate data. Phase II failure end condition is inability to activate PV system and generate power owing to failure to pass inspection or failure to satisfy Interconnection Agreement. Trigger: Phase I trigger is successful completion of design process (Interconnection Agreement is next step in fulfillment of sales agreement) Phase II trigger is completion of PV system installation and AHJ approval of final inspection Data Required: Site Address Generation standard power unit value with a timestamp in Unix Epoch Time stating when that generation value was experienced. For example: 3000, System Size - AC nameplate size of the PV system in standard power unit value AC Voltage - (optional) of the PV system along with a timestamp in Unix Epoch Time stating when that value was experienced. *The Area A did not have volunteer resources with the expertise needed to identify all of the data types required for use cases MR-DEP.004, MR-DEP.006, and MR-DEP.007. The team will interface with Team B resources and identify the data types needed to meet the requirements as defined in those use cases. Extensions: Variations: Page 15 Orange Button Market Requirements Document -

16 Frequency: Once per phase Assumptions: 4.5 Construction Installation Use Case: Construction/Installation Id: MR-DEP.005 Description: This use case addresses the data needs of all deployment activities that facilitate the physical deployment of the solar asset in the field. Activities include: 1. Construction Scheduling 2. Job Safety Analysis (JSA) 3. Review of project plans and specifications 4. Material handling (supply chain) 5. System Deployment 6. Required inspections Priority: 3 Primary Actor(s) For Residential DG installations: Crew lead Installation Crew For Commercial & Industrial installations: Project Manager Construction Manager Installation crew, including subcontractors Supporting Actors Project Scheduler Supply Chain Page 16 Orange Button Market Requirements Document -

17 Stakeholders and Interests Solar Integrator/contractor Financial Institution Pre-Conditions Required construction permits issued; Interconnection Agreement executed; Installation scheduled with property owner and/or occupant Post Conditions Success end condition: PV System installed and passes AHJ final inspection. Failure end condition: PV system cannot be installed, owing to errors and/or omissions in project plans PV system fails inspections (requiring recirculation for re-work) Trigger: Required approvals successfully obtained, and project scheduled with asset owner Data Required: Site Address Approved plans; reports; specifications Manufacturer s installation instructions for components and systems Locally adopted codes (i.e., which codes and which editions) Utility Interconnection parameters Bill of Materials (BOM) Installer Safety needs (for example, locations of fall arrest anchors) Data carried over from use cases: MR-DEP.002 PV System Design MR-DEP.003 AHJ Plan Review, Permitting, Inspection Extensions: Page 17 Orange Button Market Requirements Document -

18 Variations: Frequency: Once per phase Assumptions: 4.6 Commissioning Testing Use Case: Commissioning and Testing Id: MR-DEP.006 Description: This use case addresses the data needs for all post-deployment processes for commissioning and testing. Solar Commissioning is part of the Field Acceptance Test. Solar commissioning is performed in order to establish an as-built baseline for the system as well as ensure that the system is safe and built to code. Testing of the solar asset involves identifying the data needed to assure safety and reliability requirements are met, as well as the performance and regulatory requirements. Priority: 3 Primary Actor(s) Third-party Commissioning Agent Supporting Actor(s) Solar Integrator EPC Stakeholders and Interests Asset Owner Investors and financiers Pre-Conditions Page 18 Orange Button Market Requirements Document -

19 System is deployed and required inspections are approved Post Conditions Success end condition: Success end condition is solar asset acceptance and successful commissioning Failure end condition: Failure end condition results from failed commissioning owing to unsubstantiated deviations from plans or inadequate performance during Field Acceptance Test (requiring correction and recirculation) Trigger: System is deployed and required inspections are approved Data Required: Site Address Meter AC Power Measurement accuracy Calibration Plane of array irradiance Meter AC energy Average Irradiance Average module temperature Expected performance ratio Expected energy production based on pro forma Expected meteorological data for period in question *The Area A did not have volunteer resources with the expertise needed to identify the data types required for use cases MR-DEP.004, MR-DEP.006, and MR-DEP.007. The team will interface with Team B resources and identify the data types needed to meet the requirements as defined in those use cases. Page 19 Orange Button Market Requirements Document -

20 Extensions: Variations: Frequency: Once per phase Assumptions: 4.7 Initial Incentive Reporting Use Case: Initial Incentive Reporting Id: MR-DEP.007 Description: This use case addresses the data needs for all post-deployment verification of system characteristics and system performance, in conformance with incentive program requirements. Priority: 3 Primary Actor(s) Incentive team for solar integrator Supporting Actor(s) Incentive reporting agency SREC or local/state utility Stakeholders and Interests Asset Owners Investors and financiers Page 20 Orange Button Market Requirements Document -

21 Incentive reporting agency SREC or local/state utility Pre-Conditions System is a deployed asset in operation and producing power Post Conditions Success end condition: Required data is received by asset owner and necessary third party Failure end condition: Required data is not received by asset owner and necessary third party Trigger: System is deployed and producing power Data Required: Site Address Permit parameters System characteristics, as listed in previous use cases Power production parameters *The Area A did not have volunteer resources with the expertise needed to identify the data types required for use cases MR-DEP.004, MR-DEP.006, and MR-DEP.007. The team will interface with Team B resources and identify the data types needed to meet the requirements as defined in those use cases. Extensions: Variations: Frequency: Once per period Assumptions: Page 21 Orange Button Market Requirements Document -

22 5 Supporting Data The use cases are appended to this document in separate files. 5.1 MRD Assumptions Page 22 Orange Button Market Requirements Document -