Mechanical Joints Sample Clauses

Mechanical Joints. 1) When using mechanical joints, thoroughly wash bell sockets, spigots, gland, gasket, nuts, and bolts with soapy water before assembly. Keep these parts wet until the jointing operation is complete.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Mechanical Joints a. Where specified, mechanical joints for above or below ground service shall meet the requirements of ANSI/AWWA A21.10/C110 and ANSI/AWWA A21.11/C111. b. Gaskets and bolts and nuts as specified in this Section.
Sample 1
Mechanical Joints a. Where specified, restrained mechanical joints shall be the positive restraint type. Mechanical
Sample 1
Mechanical Joints. The socket, plain end of each pipe and gasket shall be cleaned of dirt before jointing and shall be jointed according to manufacturer's recommendations. Bolts shall be tightened alternately at top, bottom and sides so pressure on gasket is even.
Sample 1
Mechanical Joints. Many comments stated that for mechanical joints, once a joining procedure has been shown to meet the requirements of the proposed qualification tensile test, the joining procedures are so simple that persons making joints should only need to show that they have followed the procedures to be qualified. MTB has reviewed the joining procedures for various mechanical joints and has found that they are consistently simple and straightforward and do not require a high level of skill to implement. As a result of these findings, the final rule for qualifying persons to make sound mechanical joints requires the person to be qualified by training or experience in the use of the joining procedure, and to make a specimen joint from pipe sections joined according to the. procedure that is visually examined and found to have the same appearance as a specimen joint or photographs of a specimen joint that m eets the applicable test requirements of § 192.283. Further, physical testing of the joint is not —required.
Sample 1

Related to Mechanical Joints

  • Mechanical a. Heating and cooling load calculations as required and major duct or pipe runs sized to interface with structural.

  • Mechanical Breakdowns 15.1 Any mechanical problems associated with the Vehicle must be reported to Apollo as soon as possible in order to give Apollo the opportunity to rectify the problem during the rental period. Equipment failure must also be reported to Apollo.

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

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Mechanical Rights The Licensor hereby grants to Licensee a non-exclusive License to use Master Recording in the reproduction, duplication, manufacture, and distribution of phonograph records, cassette tapes, compact disks, internet downloads, other and miscellaneous audio and digital recordings, and any lifts and versions thereof (collectively ,”Recordings”) worldwide for up to the pressing or selling a total of 10000 copies of such Recordings or any combination of such Recordings. Additionally, Licensor shall be permitted to distribute unlimited internet downloads for non-profit and non-commercial use.

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

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • EODUF Packing Specifications 7.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.

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

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