MECHANICAL JOINT a. Mechanical joints shall conform with the latest revision of ANSI/AWWA C110/A21.
b. Joint material shall be made up with rubber gaskets conforming to ANSI Standard A21.
MECHANICAL JOINT Sample Clauses
Related to MECHANICAL JOINT
Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.
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.
Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.
Appropriate Documentation The Company will have received, in a form and substance reasonably satisfactory to Company, dated the Closing Date, all certificates and other documents, instruments and writings to evidence the fulfillment of the conditions set forth in this Article 6 as the Company may reasonably request.
Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet
ENVIRONMENTAL DOCUMENTATION Each environmental service provided by the Engineer shall have a deliverable. Deliverables shall summarize the methods used for the environmental services, and shall summarize the results achieved. The summary of results shall be sufficiently detailed to provide satisfactory basis for thorough review by the State, The Federal Highway Administration (FHWA), and (where applicable) agencies with regulatory oversight. All deliverables shall meet regulatory requirements for legal sufficiency, and shall adhere to the requirements for reports enumerated in the State’s NEPA MOU. a. Quality Assurance/Quality Control Review For each deliverable, the Engineer shall perform quality assurance quality control (QA/QC) reviews of environmental documents and on other supporting environmental documentation to determine whether documents conform with: 1) Current Environmental Compliance Toolkit guidance published by the State’s Environmental Affairs Division and in effect as of the date of receipt of the documents or documentation to be reviewed; 2) Current state and federal laws, regulations, policies, guidance, agreements, and memoranda of understanding between the State and other state or federal agencies; and 3) FHWA and American Association of State Highway and Transportation Officials (AASHTO) guidelines contained in “Improving the Quality of Environmental Documents, A Report of the Joint AASHTO and American Council of Engineering Companies (ACEC) Committee in Cooperation with the Federal Highway Administration” (May 2006) for: DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 a) Readability, and b) Use of evidence and data in documents to support conclusions. Upon request by the State, the Engineer shall provide documentation that the QA/QC reviews were performed by qualified staff. b. Deliverables shall contain all data acquired during the environmental service. All deliverables shall be written to be understood by the public and must be in accordance with the State’s Environmental Toolkit guidance, documentation standards, current guidelines, policies and procedures. c. Electronic versions of each deliverable must be written in software which is compatible to the State and must be provided in a changeable format for future use by the State. The Engineer shall supplement all hard copy deliverables with electronic copies in searchable Adobe Acrobat™ (.pdf) format, unless another format is specified. Each deliverable shall be a single, searchable .pdf file that mirrors the layout and appearance of the physical deliverable. The Engineer shall deliver the electronic files on CD-R, CD-RW media in Microsoft Windows format, or through the ftp site. d. When the environmental service is to apply for a permit (e.g., United States Coast Guard (USCG) or United States Army Corps of Engineers (USACE), the permit and all supporting documentation shall be the deliverable. e. Submission of Deliverables 1) Deliverables shall consist of reports of environmental services performed in addition to a Categorical Exclusion (CE) determination form and supporting documentation including the required form or Environmental Assessment (EA) document, when applicable. 2) All deliverables must comply with all applicable state and federal environmental laws, regulations and procedures and include all items listed in the Environmental Document Review Checklist and the Administrative Completeness Review Checklist. 3) On the cover page of each environmental assessment (EA), finding of no significant impact (XXXXX), environmental impact statement (EIS), and record of decision (ROD) prepared under the authority granted by this MOU, and for any memorandum corresponding to any CE determination it makes, the Engineer shall insert the following language in a way that is conspicuous to the reader or include it in a CE project record: "The environmental review, consultation, and other actions required by applicable DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 Federal environmental laws for this project are being, or have been, carried-out by TxDOT pursuant to 23 U.S.C. 327 and a Memorandum of Understanding dated December 16, 2014, and executed by FHWA and TxDOT." f. The State shall provide the State’s and other agency comments on draft deliverables to the Engineer. The Engineer shall revise the deliverable: 1) to include any State commitments, findings, agreements, or determinations (e.g., wetlands, endangered species consultation, Section 106, or Section 4(f)), required for the Transportation Activity as specified by the State; 2) to incorporate the results of public involvement and agency coordination; 3) to reflect mitigation measures resulting from comments received or changes in the Transportation Activity; and 4) include with the revised document a comment response form (matrix) in the format provided by the State. g. All photographs shall be 3.5” x 5” color presentation printed on matte finish photographic paper or 3.5” x 5” color presentation printed on matte white, premium or photo quality laser or inkjet paper. All photographs shall be well focused and clearly depict details relevant to an evaluation of the project area. Provision of photographs shall be one original print of each image or electronic presentations of comparable quality. Comparable quality electronic photograph presentations shall be at least 1200 x 1600 pixel resolution. Photographs shall be attached to separately labeled pages that clearly identify project name, project identification (ID) number, address or Universal Transverse Mercator (UTM) of resource, description of the picture and direction of the photographic view. In addition to the hard-copy prints, an electronic version of each will be submitted with the same identification information as the hard-copy.
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
ODUF Packing Specifications 6.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.
Escrow Format Specification 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.
Instrumentation The acceleration shall be recorded during the test, using equipment in accordance with channel frequency class 1000 as specified in the latest version of ISO 6487.
