AS-BUILT DOCUMENT CLASSIFICATION Sample Clauses

AS-BUILT DOCUMENT CLASSIFICATION. Contractor shall develop a procedure describing the process for the management of Progress As- Built documents and Record As-Built documents (collectively, “As-Builts”), which shall include: · identification of deliverables to be As-Built · the handover of As-Builts · the approach that shall be used to verify the technical correctness and completeness of the information in relation to the As-Builts · criteria used to determine whether any particular document categorized as As-Built in Schedule B-1 shall be revised to represent the observed as-built condition. Such procedure shall be submitted to Owner within [***] ([***]) Days after issuance of NTP, for Owner’s review. Contractor shall utilize the following two (2) criteria to define the completed status of documents: 4.1. As-Built (“AB”) 4.2. Latest Issue Revision (“LR”)
Sample 1
AutoNDA by SimpleDocs
AS-BUILT DOCUMENT CLASSIFICATION. Contractor shall use the procedure describing the process for the management of Progress As-Built documents and Record As-Built documents (collectively, “As-Builts”) that was developed during Phase 1 Work, which included: identification of deliverables to be As-Built the handover of As-Builts the approach that shall be used to verify the technical correctness and completeness of the information in relation to the As-Builts criteria used to determine whether any particular document categorized as As-Built in Schedule B-1 shall be revised to represent the observed as-built condition. Contractor shall utilize the following two (2) criteria to define the completed status of documents: 4.1. As-Built (“AB”) 4.2. Latest Issue Revision (“LR”)
Sample 1

Related to AS-BUILT DOCUMENT CLASSIFICATION

  • Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Project Documents In addition to any other pertinent and necessary Project documents, the following documents shall be used in the development of the Project: A. TxDOT 2011 Texas Manual of Uniform Traffic Control Devices for Streets and Highways, including latest revisions B. Texas Department of Transportation's Standard Specifications for Construction of Highways, Streets, and Bridges, 2014 or 2024, as applicable and as amended

  • Closet I Urinal Requirements Employees Closets Urinals

  • Procurement documents Languages in which the procurement documents are officially available: English

  • REVIEW OF CONTRACT DOCUMENTS 4.2.1 The Contractor shall carefully study and compare the Contract Documents and shall immediately report in writing to the Architect and the State any error, inconsistency or omission he may discover. The Contractor shall not be liable to the State or the Architect for any damage resulting from any such errors, inconsistencies or omissions in the Contract Documents. The

  • Attachment  C_ CONTRACT AFFIRMATIONS For purposes of these Contract Affirmations, HHS includes both the Health and Human Services Commission (HHSC) and the Department of State Health Services (DSHS). System Agency refers to HHSC, DSHS, or both, that will be a party to this Contract. These Contract Affirmations apply to all Contractors and Grantees (referred to as “Contractor”) regardless of their business form (e.g., individual, partnership, corporation). By entering into this Contract, Contractor affirms, without exception, understands, and agrees to comply with the following items through the life of the Contract:

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

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