Required Demonstration for Schedule Relief Sample Clauses

Required Demonstration for Schedule Relief. Without limiting any other requirement of this Article, the Design-Builder shall not be entitled to any adjustment to the Scheduled Substantial Completion Date, the number of days allowed for the achievement of Final Completion or any other schedule adjustment under this Design-Build Contract, unless the Design-Builder demonstrates:
AutoNDA by SimpleDocs

Related to Required Demonstration for Schedule Relief

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

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

  • Accurate and Timely Submission of Reports a) The reports and administrative fees shall be accurate and timely and submitted in accordance with the due dates specified in this section. Vendor shall correct any inaccurate reports or administrative fee payments within three (3) business days upon written notification by DIR. Vendor shall deliver any late reports or late administrative fee payments within three (3) business days upon written notification by DIR. If Vendor is unable to correct inaccurate reports or administrative fee payments or deliver late reports and fee payments within three

  • Deadlines for Providing Insurance Documents after Renewal or Upon Request As set forth herein, certain insurance documents must be provided to the OGS Procurement Services contact identified in the Contract Award Notice after renewal or upon request. This requirement means that the Contractor shall provide the applicable insurance document to OGS as soon as possible but in no event later than the following time periods:  For certificates of insurance: 5 business days  For information on self-insurance or self-retention programs: 15 calendar days  For other requested documentation evidencing coverage: 15 calendar days  For additional insured and waiver of subrogation endorsements: 30 calendar days Notwithstanding the foregoing, if the Contractor shall have promptly requested the insurance documents from its broker or insurer and shall have thereafter diligently taken all steps necessary to obtain such documents from its insurer and submit them to OGS, OGS shall extend the time period for a reasonable period under the circumstances, but in no event shall the extension exceed 30 calendar days.

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

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

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.

  • 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

  • Notice of Changes If a Party makes a change in its network which it believes will materially affect the interoperability of its network with the other Party, the Party making the change shall provide at least ninety (90) days advance written notice of such change to the other Party.

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