Scope Changes Due to DB Contractor Error Sample Clauses

Scope Changes Due to DB Contractor Error. Notwithstanding anything in this Section 14.05 to the contrary, no Scope Change Order shall be issued and no adjustment of the Contract Sum, any Scheduled Substantial Completion Date, the Payment and Values Schedule or the Long Stop Date shall be made in connection with any correction of errors, omissions, deficiencies, or improper or defective work on the part of the DB Contractor or any Subcontractor in the performance of the DB Work hereunder, or correction of any improper, defective or deficient equipment supplied by the DB Contractor or any Subcontractor.
AutoNDA by SimpleDocs

Related to Scope Changes Due to DB Contractor Error

  • Amendments - Changes/Extra Work The Subrecipient shall make no changes to this Contract without the County’s written consent. In the event that there are new or unforeseen requirements, the County has the discretion with the Subrecipient’s concurrence, to make changes at any time without changing the scope or price of the Contract.‌ If County-initiated changes or changes in laws or government regulations affect price, the Subrecipient’s ability to deliver services, or the project schedule, the Subrecipient will give County written notice no later ten (10) days from the date the law or regulation went into effect or the date the change was proposed and Subrecipient was notified of the change. Such changes shall be agreed to in writing and incorporated into a Contract amendment. Said amendment shall be issued by the County-assigned Contract Administrator, shall require the mutual consent of all Parties, and may be subject to approval by the County Board of Supervisors. Nothing herein shall prohibit the Subrecipient from proceeding with the work as originally set forth or as previously amended in this Contract.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Attachment A, Scope of Services The scope of services is amended as follows:

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • SCOPE CHANGES The Commissioner reserves the right to require, by written order, changes to the scope of the Contract, by altering, adding to or deducting from the Bid Specifications, such changes to be within the general scope of the Contract. If any such change causes an increase or decrease in the cost of, or the time required for, performance of any part of the work under the Contract, whether or not changed by the order, the Commissioner shall, upon notice from Contractor as hereafter stated, make an equitable adjustment in the Contract price, the delivery schedule or both and shall modify the Contract. The Contractor must assert its right to an adjustment under this clause within thirty days from the date of receipt of the written order. However, if the Commissioner decides that the facts justify it, the Commissioner may provide an adjustment without receipt of a proposal. Failure to agree to any adjustment shall be a dispute under the Disputes clause, provided, however, that nothing in this clause shall excuse the Contractor from proceeding with the Contract as changed.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Effect of Addenda, Bulletins, and Change Orders No special implication, interpretation, construction, connotation, denotation, import, or meaning shall be assigned to any provision of the Contract Documents because of changes created by the issuance of any (1) Addendum, (2) Bulletin, or (3) Change Order other than the precise meaning that the Contract Documents would have had if the provision thus created had read originally as it reads subsequent to the (1) Addendum, (2) Bulletin, or (3) Change Order by which it was created.

  • CONTRACTOR RESPONSIBILITY FOR SYSTEM AGENCY’S TERMINATION COSTS If the System Agency terminates the Contract for cause, the Contractor shall be responsible to the System Agency for all costs incurred by the System Agency and the State of Texas to replace the Contractor. These costs include, but are not limited to, the costs of procuring a substitute vendor and the cost of any claim or litigation attributable to Contractor’s failure to perform any Work in accordance with the terms of the Contract.

  • Authorized User’s Statement of Work A competitive Mini-Bid is required for every transaction under this Centralized Contract. An Authorized User must prepare a detailed Statement of Work using Appendix F, Attachment 1, Mini-Bid Template. The Authorized User must distribute the Mini-Bid to all qualified Vendors per Lot(s) (unless a Vendor has removed itself from consideration via the Appendix F, Attachment 5, Mini-Bid Participation Interest Template). Contact information, organized by Lot, will be available on the OGS website for this Contract. An Authorized User shall conduct its Mini-Bid in accordance with the requirements set forth in Appendix F, Attachment 2, How to Use this Contract. The following terms and conditions shall apply to each Mini-Bid issued by an Authorized User:  An Authorized User may require the execution of unique forms, such as Confidentiality Non- Disclosure agreements; and  An Authorized User is required to make tentative award and non-award notifications to each Contractor who submitted a response to the Mini-Bid. Additionally, the minimum time, excluding the date of release, between issuance of the Mini-Bid by the Authorized User to the Mini-Bid Opening is as follows:  Xxx 0 Xxxx-Xxxx: Xxxx (0) Xxxxxxxx Xxxx  Xxx 0 Mini-Bids: Ten (10) Business Days

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