System Impact Study Agreement Sample Clauses

System Impact Study Agreement. As soon as practicable after receiving the Transmission Developer’s election in the Scoping Meeting in accordance with Section 22.4.2.4 to proceed to a System Impact Study (“SIS”) or simultaneously with the delivery of an Optional Feasibility Study to the Transmission Developer, the ISO shall tender the Transmission Developer and Connecting Transmission Owner a System Impact Study Agreement. Upon tendering the System Impact Study Agreement, the ISO shall provide to the Transmission Developer a non-binding good faith estimate of the cost and timeframe for completing the SIS. The Transmission Developer must provide a $120,000 study deposit to the ISO for the SIS if the ISO is responsible for performing the entire study; provided, however, that if the Transmission Developer is hiring a third-party consultant to perform the analytical portion of the study, pursuant to the requirements set forth in Section 22.13.4 of this Attachment P, the required deposit is $40,000. The System Impact Study Agreement shall specify that the Transmission Developer is responsible for the actual costs incurred by the ISO and the Connecting Transmission Owner for the SIS. The System Impact Study Agreement shall provide that if actual study costs exceed the study deposit, the Transmission Developer shall pay the ISO the amount in excess of the study deposit, and if the actual study costs are less than the study deposit, the ISO shall refund the remaining deposit amount to the Transmission Developer. The System Impact Study Agreement shall also set forth the study schedule based on the study scope.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
System Impact Study Agreement. Unless otherwise agreed, within ten (10) Business Days after the delivery of the Feasibility Study to Interconnection Customer, IPA shall provide to Interconnection Customer a System Impact Study Agreement substantially in the form of Appendix 3 pursuant to which IPA, or a consultant approved by IPA, will conduct a System Impact Study at Interconnection Customer’s sole cost and expense. IPA may draw upon and apply any remainder of the Interconnection Customer’s initial deposit to perform the study or have a consultant approved by IPA perform the study. In the event that the remainder of the initial deposit is not sufficient to cover the actual costs of such study, including any costs for Reassessment in accordance with Section 7.5, upon receipt of an invoice from IPA for a good faith estimate of the costs to complete such study, Interconnection Customer shall pay to IPA the amount of such estimate prior to IPA, or a consultant approved by IPA, proceeding or continuing with such study. Interconnection Customer shall execute the System Impact Study Agreement and deliver the executed System Impact Study Agreement to IPA no later than thirty (30) calendar days after its receipt, along with demonstration of Site Control or the posting of a deposit in addition to that already made in Section 3.2.1(iii) in the amount specified in the Deposit Amount Schedule, which shall be refundable without interest if and when Interconnection Customer demonstrates Site Control or withdraws its application. If Interconnection Customer does not provide all required technical data when it delivers the executed System Impact Study Agreement, IPA shall notify Interconnection Customer of any deficiency within five (5) Business Days of the receipt of the executed System Impact Study Agreement. Interconnection Customer shall have ten (10) Business Days to cure the deficiency; provided, however, that if the deficiency is either a failure to deliver the executed System Impact Study Agreement or a failure to pay any additionally invoiced deposit specified above, the cure period shall not apply. If Interconnection Customer fails to cure the deficiency within the period specified above, IPA may deem the Interconnection Request withdrawn in accordance with Section 3.5. If the System Impact Study discloses any unexpected result(s) not contemplated during the Scoping Meeting or in the Feasibility Study, a substitute Point of Interconnection identified by Interconnection Customer, IPA, or a con...
Sample 1Sample 2Sample 3See All (5)
System Impact Study Agreement. THIS AGREEMENT is made and entered into this day of 20 by and between , a organized and existing under the laws of the State of , ("Interconnection Customer,") and , a existing under the laws of the State of , ("Transmission Provider"). Interconnection Customer and Transmission Provider each may be referred to as a "Party," or collectively as the "Parties."
Sample 1Sample 2
System Impact Study Agreement. THIS AGREEMENT (“Agreement”) is made and entered into this ____ day of _________ 20___ by and between ____________________________________________, a ______________________________ organized and existing under the laws of the State of ________________________________, (“Interconnection Member,”) and Piedmont Electric Membership Corporation, a Cooperative existing under the laws of the State of North Carolina , (“Cooperative”). The Interconnection Member and the Cooperative each may be referred to as a “Party,” or collectively as the “Parties.”
Sample 1
System Impact Study Agreement or the DISIS Agreement (as specified in the Utility’s applicable Appendix CS) has been executed by the Interconnection Customer include only:
Sample 1

Related to System Impact Study Agreement

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Pharmacovigilance Agreement Within [***] after the Effective Date, BMS and the Company (under the guidance of their respective Pharmacovigilance Departments, or equivalent thereof) shall define and finalize the responsibilities the Parties shall employ to protect patients and promote their well-being in connection with the use of the Licensed Compound(s) until such time that all pharmacovigilance responsibilities have transferred from BMS to Company. These responsibilities shall include mutually acceptable guidelines and procedures for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of adverse event reports, pregnancy reports, and any other information concerning the safety of any Licensed Compound(s). Such guidelines and procedures shall be in accordance with, and enable the Parties and their Affiliates to fulfill, local and international regulatory reporting obligations to government authorities. Furthermore, such agreed procedures shall be consistent with relevant International Council for Harmonization (ICH) guidelines, except where said guidelines may conflict with existing local regulatory safety reporting requirements, in which case local reporting requirements shall prevail. Until such guidelines and procedures are set forth in a written agreement between the Parties (hereafter referred to as the “Pharmacovigilance Agreement”), the Party responsible for pharmacovigilance prior to execution of this Agreement shall have sole Pharmacovigilance responsibility for the Licensed Compound(s) subject to all applicable regulations and guidelines. In the event that this Agreement is terminated, the Parties agree to implement the necessary procedures and practices to ensure that any outstanding pharmacovigilance reporting obligations are fulfilled. Certain information marked as [***] has been excluded from this exhibit because it is both (i) not material and (ii) would be competitively harmful if publicly disclosed.

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Quality Agreement If appropriate or if required by Applicable Law, the parties will also agree upon a Quality Agreement containing quality assurance provisions for the Manufacture of Product (“Quality Agreement”), which agreement will also be attached to the applicable Work Order and incorporated by reference in the Work Order.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

Time is Money Join Law Insider Premium to draft better contracts faster.