Specification Deficiencies. If omissions or ambiguities occur in these specifications, requirements of the Texas Department of Transportation and/or the Texas Natural Resources Conservation Commission shall govern that part of the work.
Specification Deficiencies Sample Clauses
Related to Specification Deficiencies
MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.
ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.
Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:
Retainage for Unacceptable Corrective Action Plan or Plan Failure If the corrective action plan is unacceptable to the Department or Customer, or implementation of the plan fails to remedy the performance deficiencies, the Department or Customer will retain ten percent (10%) of the total invoice amount. The retainage will be withheld until the Contractor resolves the performance deficiencies. If the performance deficiencies are resolved, the Contractor may invoice the Department or Customer for the retained amount. If the Contractor fails to resolve the performance deficiencies, the retained amount will be forfeited to compensate the Department or Customer for the performance deficiencies.
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Punchlist Upon completion of the Performance Tests and prior to Substantial Completion, Owner and Contractor shall inspect Subproject 3, and Contractor shall prepare a proposed Punchlist of items identified as needing to be completed or corrected as a result of such inspection. Contractor shall promptly provide the proposed Punchlist to Owner for its review, together with an estimate of the time and cost necessary to complete or correct each Punchlist item. Contractor shall add to the proposed Punchlist any Punchlist items that are identified by Owner within ten (10) Days after Owner’s receipt of the proposed Punchlist from Contractor, and Contractor shall immediately initiate measures to complete or correct, as appropriate, any item on Contractor’s proposed Punchlist (including those items identified by Owner during Owner’s review) that are not of a Punchlist nature. Notwithstanding anything to the contrary in this Agreement, Contractor and Owner are not required as a condition of Substantial Completion to agree upon and identify every Punchlist item and include it on the Punchlist, but Contractor is required to complete as a condition of Substantial Completion all Work that does not meet the definition of Punchlist as provided in Section 1.1. In the event of a dispute regarding whether a specific item of Work meets the definition of Punchlist under Section 1.1, the Parties shall resolve such dispute in accordance with Section 18.1A. Owner shall provide Contractor with access to the Work after Substantial Completion sufficient to enable Contractor to complete all Punchlist items, so long as such access does not unreasonably interfere with operation of Subproject 3 after Substantial Completion or Subproject 1 or Subproject 2 after substantial completion of Subproject 1 or Subproject 2 (as applicable) under the Stage 1 EPC Agreement and subject to any reasonable security or safety requirements of Owner. Upon Contractor’s completion or correction of any items necessary to achieve Substantial Completion, as modified by any Owner additions, such Punchlist shall govern Contractor’s performance of the Punchlist items up to Final Completion. All Work on the Punchlist shall be completed by the date required for Final Completion, as specified in Section 5.3C, or Owner may, in addition to any other rights that it may have under this Agreement, complete such Punchlist Work at the expense of Contractor. In the event Owner elects to complete such Punchlist Work, Contractor shall pay Owner, within ten (10) Days after receipt of written notice from Owner, all reasonable costs and expenses incurred by Owner in performing such Punchlist Work, or, at Owner’s sole discretion, Owner may withhold or offset amounts owed to Contractor or collect on the Letter of Credit in accordance with Section 7.8 in the amount of such costs and expenses. Any Defective Work identified after agreement between the Parties of the Punchlist shall be corrected by Contractor as a Warranty item under Article 12.
DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.
SAFETY CONDITIONS 1.0 The responsibility for providing for safe working conditions that are in conformance with applicable law and which are within fiscal constraints shall be the District’s. Employees shall be responsible for complying with safety procedures and practices and for reporting any unsafe condition, facility, or equipment of which he/she is aware. The District shall be responsible for informing employees of necessary safety procedures and practices. There shall be no reprisal against an employee for reporting any real or potentially unsafe condition, facility, or equipment.
Class Specifications The Human Resources Division shall determine:
