Explanations; Omissions and Mis-descriptions Sample Clauses

Explanations; Omissions and Mis-descriptions. Maintenance Contractor shall not take advantage of or benefit from any apparent Error in the COMA Documents. Should it appear that the Maintenance Services to be done or any matter relative thereto is not sufficiently detailed or explained in the COMA Documents, Maintenance Contractor shall request in writing such further written explanations from TxDOT as may be necessary and shall comply with the explanation provided. Maintenance Contractor shall promptly notify TxDOT in writing of all Errors which it may discover in the COMA Documents, and shall obtain specific instructions in writing from TxDOT regarding any such Error before proceeding with the Maintenance Services affected thereby. The fact that the COMA Documents omit or mis-describe any details of any Maintenance Services that are necessary to carry out the intent of the COMA Documents, or that are customarily performed, shall not relieve Maintenance Contractor from performing such omitted Maintenance Services (no matter how extensive) or mis-described details of the Maintenance Services, and they shall be performed as if fully and correctly set forth and described in the COMA Documents, without entitlement to a Change Order hereunder except as specifically allowed under Section 10.
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs

Related to Explanations; Omissions and Mis-descriptions

  • Modifications and Add-ons Subject to the licensing of the required development rights under separate agreement, Provider shall be entitled to develop Modifications and Add-ons for the Software and shall be permitted to Use Modifications and Add- Ons with the Software in accordance with the license grant to the Software set forth in Section 3.1 herein. Provider shall promptly notify SAP if and when Provider is planning to develop Modifications or Add-ons to the Software. The notification provided by Provider shall include a high level description of the intended functionality and of the timeframe planned for such development. In addition, any Modifications or Add-ons must not i) unreasonably impair, degrade or reduce the performance or security of the Software; ii) enable the bypassing or circumventing of SAP license restrictions and/or provide users with access to the Software to which such users are not directly licensed; and/or iii) permit mass data or metadata extraction from an SAP software to a non-SAP software for the purpose of replacing the Software as the data’s system of record. With regards to the aforementioned item iii), Provider shall refer any Customer requiring such information to SAP.

  • ERRORS AND OMISSIONS RELATED TO DATA 11.1.0 Board errors and retroactive adjustments shall be the responsibility of the Board.

  • Captions and References The captions and headings in this Agreement are for convenience of reference only, and shall not be used to interpret, define, or limit its provisions. All references in this Agreement to sections (whether spelled out or using the § symbol), subsections, exhibits or other attachments, are references to sections, subsections, exhibits or other attachments contained herein or incorporated as a part hereof, unless otherwise noted.

  • GEOGRAPHIC AREA AND SECTOR SPECIFIC ALLOWANCES, CONDITIONS AND EXCEPTIONS The following allowances and conditions shall apply where relevant: Where the company does work which falls under the following headings, the company agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

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