Appendix D - BC Hydro - Transmission
Appendix D - BC Hydro - Transmission Appendix D - BC Hydro - Transmission
3.3 Valid Interconnection Request.Large Generating Facility's interconnection is also studied withTransmission Provider's Transmission System at peak load, under avariety of severely stressed conditions, to determine whether, withthe Large Generating Facility at full output, the aggregate ofgeneration in the local area can be delivered to the aggregate of loadon Transmission Provider’s Transmission System, consistent withTransmission Provider's reliability criteria and procedures. Thisapproach assumes that some portion of existing Network Resourcesareis displaced by the output of Interconnection Customer's LargeGenerating Facility. Network Resource Interconnection Service inand of itself does not convey any right to deliver electricity to anyspecific customer or Point of Delivery.3.3.1 Initiating an Interconnection Request.To initiate an Interconnection Request, Interconnection Customer must submit all of thefollowing: (i) a $10,000an initial non-refundable $15,000 deposit, and (ii) a completedapplication in the form of Appendix 1, and (iii) demonstration of Site Control or a postingof an additional deposit of $10,000.1. Such deposits shall be applied toward anyInterconnection Studies pursuant to the Interconnection Request. If an InterconnectionCustomer demonstrates Site Control within the cure period specified in Section 3.3.3afterfifteen (15) Business Days of submitting its Interconnection Request, the additionaldeposit shall be refundable; otherwise, all such deposit(s), additional and initial, becomenon-refundable.The expected In-Service Date of the new Large Generating Facility or increase incapacity of the existing Generating Facility shall be no more than the process window forthe regional expansion planning period (or in the absence of a regional planning process,the process window for Transmission Provider's expansion planning period) not toexceed seven years from the date the Interconnection Request is received byTransmission Provider, unless Interconnection Customer demonstrates that engineering,permitting and construction of the new Large Generating Facility or increase in capacityof the existing Generating Facility will take longer than the regional expansion planningperiod. The In-Service Date may succeed the date the Interconnection Request isreceived by Transmission Provider by a period up to ten years, or longer whereInterconnection Customer and Transmission Provider agree, such agreement not to beunreasonably withheld.3.3.2 Acknowledgment of Interconnection Request.Transmission Provider shall acknowledge receipt of the Interconnection Request withinfive (5) Business Days of receipt of the request and attach a copy of the receivedInterconnection Request to the acknowledgement.DM_VAN/BCT0007-BCT00132/6213742.16216529.6 - 12 12-
3.3.3 Deficiencies in Interconnection Request.An Interconnection Request will not be considered to be a valid request until all items inSection 3.3.1 have been received by Transmission Provider. If an InterconnectionRequest fails to meet the requirements set forth in Section 3.3.1, Transmission Providershall notify Interconnection Customer within five (5) Business Days of receipt of theinitial Interconnection Request of the reasons for such failure and that the InterconnectionRequest does not constitute a valid request. Interconnection Customer shall provideTransmission Provider the additional requested information needed to constitute a validrequest within ten (10) Business Days after receipt of such notice. Failure byInterconnection Customer to comply with this Section 3.3.3 shall be treated in accordancewith Section 3.6.3.3.4 Scoping Meeting.Within ten (10) Business Days after receipt of a valid Interconnection Request,Transmission Provider shall establish a date agreeable to Interconnection Customer forthe Scoping Meeting, and such date shall be no later than thirty (30) Calendar Days fromreceipt of the valid Interconnection Request, unless otherwise mutually agreed upon bythe Parties.The purpose of the Scoping Meeting shall be to discuss alternative interconnectionoptions, to exchange information including any transmission data that would reasonablybe expected to impact such interconnection options, to analyze such information and todetermine the potential feasible Points of Interconnection. Transmission Provider andInterconnection Customer will bring to the meeting such technical data, including, but notlimited to: (i) general facility loadings, (ii) general instability issues, (iii) general shortcircuit issues, (iv) general voltage issues, and (v) general reliability issues as may bereasonably required to accomplish the purpose of the meeting. Transmission Providerand Interconnection Customer will also bring to the meeting personnel and otherresources as may be reasonably required to accomplish the purpose of the meeting in thetime allocated for the meeting. On the basis of the meeting, Interconnection Customershall designate its Point of Interconnection, pursuant to Section 6.1, and one or moreavailable alternative Point(s) of Interconnection. The duration of the meeting shall besufficient to accomplish its purpose.3.4 OASIS Posting.Transmission Provider will maintain on its OASIS a list of all Interconnection Requests.The list will identify, for each Interconnection Request: (i) the maximum summer andwinter megawatt electrical output; (ii) the location by county and stateOperating Region;(iii) the station or transmission line or lines where the interconnection will be made; (iv)the projected In-Service Date; (v) the status of the Interconnection Request, includingQueue Position; (vi) the type of Interconnection Service being requested; and (vii) theavailability of any studies related to the Interconnection Request; (viii) the date of theInterconnection Request; (ix) the type of Generating Facility to be constructed (combinedcycle, base load or combustion turbinetechnology and fuel type); and (x) forDM_VAN/BCT0007-BCT00132/6213742.16216529.6 - 13 13-
- Page 4 and 5: TABLE OF CONTENTS(continued)PageSec
- Page 7 and 8: TABLE OF CONTENTSPageSection 1.Defi
- Page 9 and 10: Effective Date shall mean the date
- Page 11 and 12: Provider's Transmission System. Int
- Page 13 and 14: sale to third parties or otherwise
- Page 16 and 17: 2.3 Base Case Data.Transmission Pro
- Page 20 and 21: Interconnection Requests that have
- Page 22 and 23: 4.2 Clustering.At Transmission Prov
- Page 24 and 25: 4.4.1 Permitted Modifications Befor
- Page 26 and 27: as of the effective date of this LG
- Page 28 and 29: 6.3 Interconnection Feasibility Stu
- Page 30 and 31: case of Clustering, the Interconnec
- Page 32 and 33: Transmission Provider may invoice I
- Page 34 and 35: interconnection, which cannot be mi
- Page 36 and 37: 11.2 Negotiation.Notwithstanding Se
- Page 38 and 39: completion of Network Upgrades that
- Page 40 and 41: ecomes, publicly known, through no
- Page 42 and 43: a state regulatory body conducting
- Page 44 and 45: of such third party study. Such thi
- Page 46 and 47: Unless otherwise provided in these
- Page 48 and 49: 6. Applicable deposit amount as spe
- Page 50 and 51: FIELD TIME CONSTANT DATA (SEC)Open
- Page 52 and 53: GENERATOR STEP-UP TRANSFORMER DATA
- Page 54 and 55: TABLE OF CONTENTSPageINDUCTION GENE
- Page 56 and 57: Request pursuant to Section 4.4, th
- Page 58 and 59: ASSUMPTIONS USED IN CONDUCTING THEI
- Page 60 and 61: 3.0 The scope of the Interconnectio
- Page 62 and 63: IN WITNESS THEREOF, the Parties hav
- Page 64 and 65: NOW, THEREFORE, in consideration of
- Page 66 and 67: Attachment B To Appendix 3Combined
3.3.3 Deficiencies in Interconnection Request.An Interconnection Request will not be considered to be a valid request until all items inSection 3.3.1 have been received by <strong>Transmission</strong> Provider. If an InterconnectionRequest fails to meet the requirements set forth in Section 3.3.1, <strong>Transmission</strong> Providershall notify Interconnection Customer within five (5) Business Days of receipt of theinitial Interconnection Request of the reasons for such failure and that the InterconnectionRequest does not constitute a valid request. Interconnection Customer shall provide<strong>Transmission</strong> Provider the additional requested information needed to constitute a validrequest within ten (10) Business Days after receipt of such notice. Failure byInterconnection Customer to comply with this Section 3.3.3 shall be treated in accordancewith Section 3.6.3.3.4 Scoping Meeting.Within ten (10) Business Days after receipt of a valid Interconnection Request,<strong>Transmission</strong> Provider shall establish a date agreeable to Interconnection Customer forthe Scoping Meeting, and such date shall be no later than thirty (30) Calendar Days fromreceipt of the valid Interconnection Request, unless otherwise mutually agreed upon bythe Parties.The purpose of the Scoping Meeting shall be to discuss alternative interconnectionoptions, to exchange information including any transmission data that would reasonablybe expected to impact such interconnection options, to analyze such information and todetermine the potential feasible Points of Interconnection. <strong>Transmission</strong> Provider andInterconnection Customer will bring to the meeting such technical data, including, but notlimited to: (i) general facility loadings, (ii) general instability issues, (iii) general shortcircuit issues, (iv) general voltage issues, and (v) general reliability issues as may bereasonably required to accomplish the purpose of the meeting. <strong>Transmission</strong> Providerand Interconnection Customer will also bring to the meeting personnel and otherresources as may be reasonably required to accomplish the purpose of the meeting in thetime allocated for the meeting. On the basis of the meeting, Interconnection Customershall designate its Point of Interconnection, pursuant to Section 6.1, and one or moreavailable alternative Point(s) of Interconnection. The duration of the meeting shall besufficient to accomplish its purpose.3.4 OASIS Posting.<strong>Transmission</strong> Provider will maintain on its OASIS a list of all Interconnection Requests.The list will identify, for each Interconnection Request: (i) the maximum summer andwinter megawatt electrical output; (ii) the location by county and stateOperating Region;(iii) the station or transmission line or lines where the interconnection will be made; (iv)the projected In-Service Date; (v) the status of the Interconnection Request, includingQueue Position; (vi) the type of Interconnection Service being requested; and (vii) theavailability of any studies related to the Interconnection Request; (viii) the date of theInterconnection Request; (ix) the type of Generating Facility to be constructed (combinedcycle, base load or combustion turbinetechnology and fuel type); and (x) forDM_VAN/<strong>BC</strong>T0007-<strong>BC</strong>T00132/6213742.16216529.6 - 13 13-
Change language