Project Specific Agreements Sample Clauses

Project Specific Agreements. 68. The Parties agree that from time to time the Commonwealth or a State may nominate high-priority Project(s) for Project Specific Agreements to be negotiated between the relevant Parties under this Agreement.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Project Specific Agreements. The Parties agree that from time to time the Commonwealth or a State may nominate high-priority Project(s) for Project Specific Agreements to be negotiated between the relevant Parties under this Agreement. Projects may be identified as candidates for a Project Specific Agreement based on project characteristics, such as financial or strategic value, complexity and risk, and that have the potential to deliver broader policy objectives in addition to the provision of new transport infrastructure. Project Specific Agreements may specify additional criteria or objectives for a Project consistent with, but in addition to, this Agreement. Part 6 — governance arrangements Enforceability of the Agreement The Parties do not intend any of the provisions of this Agreement to be legally enforceable. However, this does not lessen the Parties’ commitment to this Agreement. Review of the Agreement In accordance with Schedule E, Clause 23 of the IGA FFR, this Agreement is time limited. To assess the degree to which the agreed objectives and outcomes and/or outputs of this Agreement have been achieved, and inform decisions regarding the appropriate treatment following its expiry, an independent review of this Agreement will be scheduled to be completed approximately twelve months prior to its expiry. Variation of the Agreement The Agreement may be amended at any time by agreement in writing by all the Parties. A Party to the Agreement may terminate their participation in the Agreement at any time by notifying all the other Parties in writing. The Schedules to this Agreement will be varied at least twice a year, following the Commonwealth Budget and mid-year reviews, and at other times when necessary. Variations to the Schedules to this Agreement will be agreed in writing by the relevant Parties. Delegations Commonwealth Minister(s) with portfolio responsibility for infrastructure are authorised to agree and amend Schedules to this Agreement and to certify that milestones specified under this Agreement have been achieved, so that payments may be made. Respective State and Territory Ministers with portfolio responsibility for infrastructure and/or transport are authorised to agree and amend Schedules to this Agreement. Senior Commonwealth and State officials are authorised to agree and vary project milestones. Agreed project milestones are set out in IMS or equivalent system. The Commonwealth Minister(s) may delegate the assessment of project-based performance benchmarks or...
Sample 1Sample 2Sample 3
Project Specific Agreements. 6.1 Where appropriate the Parties may agree to negotiate, in advance, project specific agreements with respect to the coordination of preliminary screening and regulatory processes of projects that fall within the jurisdiction of both the Regulator and the MVLWB.
Sample 1
Project Specific Agreements. Borrowers will not grant a security interest in any of the Project Specific Agreements other than to Lender. Borrowers will perform and discharge in all material respects all of its obligations under the Project Specific Agreements and shall provide Lender with a copy of any notice of default received by a Borrower thereunder.
Sample 1
Project Specific Agreements. Noxious weed management in the Plan Area will be consistent with Washington State law, county weed control regulations and policy, and USDA-FS weed management policy for Region 6 and the MBSNF. Weed management activities in excess of those required by law or policy may be proposed under the Noxious Weed Plan; these measures will be developed and implemented by consensus of the TRIG. Habitat revegetation and restoration activities will include the use of native plant species to meet management objectives, when practicable. Plant species should be native to the area; preference should be given to native plant materials from locations closest in elevation and geographic proximity to the disturbed sites. Each habitat site will be evaluated to determine the appropriate planting plan in keeping with the site’s vegetative condition and future land use, adjacent land uses, habitat management objectives, and site maintenance requirements. Non-invasive, non-native plant species may be used where their use is consistent with current and expected future land uses (e.g., landscaped sites, frequently disturbed sites, managed forest stands) and where necessary to achieve objectives associated with site management/maintenance activities (e.g., forage production, erosion control, temporary cover, soil conditioning, weed suppression, etc.). On NFS lands, weed management will be conducted consistent with best management practices (BMPs) published by the USDA-FS for the MBSNF (USDA-FS, 1999b), current guidance and NEPA authorization for weed management on the MBSNF (USDA-FS, 2005a and 2005b), and current Region 6 guidance (USDA-FS 2005c), or subsequent applicable USDA-FS guidance. In the event of a conflict between state/county BMPs and USDA-FS BMPs/guidance as applied to National Forest System lands, the plan will follow the more restrictive guidelines. Revegetation on NFS lands will follow USDA-FS Pacific Northwest Regional policy regarding native plants (USDA- FS 1994); plant movement and use of non-native species will follow recommendations of Potash and Aubry (1997), or subsequent applicable USDA-FS guidance.
Sample 1
Project Specific Agreements. Project specific agreements to implement the above principles will be negotiated w'ithin 120 days of the time this agreement is entered into. These project specific agreements will be tailored to the - p specific projects to reflect the differences in sites and project - O organizations.
Sample 1

Related to Project Specific Agreements

  • Quality Agreement Concurrently with execution of this Agreement, the Parties will enter into an agreement that details the quality assurance obligations of each Party with respect to the Manufacture and supply of Supplied Products under this Agreement (the “Quality Agreement”). Each Party shall perform its obligations under the Quality Agreement in accordance with the terms and conditions thereof. In the event of a conflict between the terms of the Quality Agreement and the terms of this Agreement, the provisions of the Quality Agreement shall govern.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A, Statement of Work.

  • Supply Agreement During the period of two (2) years following the Trigger Date (the “Tail Period”), if a member of the Newco Group (the “Newco Purchaser”) reduces in any given six-month period (which period starts at any point of time after the Trigger Date) the GE Sourcing Costs Share with respect to any Seller Good that it purchases from a member of the GE Group (the “GE Supplier”) pursuant to the Supply Agreement by thirty percent (30%) as compared to the GE Sourcing Costs Share with respect to such Seller Good purchased from GE Supplier in the most recently completed calendar year prior to the Trigger Date, and the GE Supplier (a) has available capacity to supply such Seller Good pursuant to the Supply Agreement and (b) is not in material breach of the Supply Agreement (which such breach is incapable of being satisfied or cured by the GE Supplier within thirty (30) calendar days following receipt of written notice from the Newco Purchaser of such breach), then Section 1 shall no longer restrict the GE Supplier from selling such Seller Good during the remainder of the Tail Period. Upon reasonable request from the applicable GE Supplier, Newco shall, or shall cause the applicable Newco Purchaser to, provide to the applicable requesting GE Supplier, in reasonable detail, the GE Sourcing Costs Share with respect to applicable time periods. For purposes of this Section 4, “GE Sourcing Costs Share” means the quotient of (a) the amount of the sourcing costs incurred by the Newco Purchaser with respect to any Seller Good (as defined in the Supply Agreement) purchased by the Newco Purchaser from the GE Supplier in any given period of time divided by (b) the aggregate amount of the sourcing costs incurred by the Newco Group with respect to such Seller Good purchased by the Newco Group from the GE Group and third party suppliers in the same period of time.

  • 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.

  • 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 Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!