Joint Restraint (MJ Field Lok®, Field Sample Clauses

Joint Restraint (MJ Field Lok®, Field. Lok®) Ductile Iron pipe and fittings (except hydrant branches) may be restrained using Fieldlok or MJ Fieldlok restraint. The Contractor shall submit an option joint restraint application, and document on the ECIP construction plan the proposed location of the alternate joint restraint. Plans and application shall be submitted to Milwaukee Water Works, Engineering Construction Section; DPW Field Headquarters 0000 X 00xx Xx, Xxxxxxxxx, XX 00000, at least ten (10) working days prior to the scheduled start of work on the contract. Alternate joint restraint will not be allowed if the contractor has not submitted an application. Mechanical and push-on joints shall be restrained where required by City specifications or construction plans, either by the use of concrete buttresses, anchors, strapping, Tyton joint restraint gaskets (Field Lok 350®), or MJ Field Lok ® glands and gaskets. (Note: A combination of restraint alternatives may be required to achieve the proper joint restraint at the mechanical joint fittings as well as the specified restrained length.)
AutoNDA by SimpleDocs

Related to Joint Restraint (MJ Field Lok®, Field

  • Sale or License of Custom Products Involving Tax Exempt Financing (i.e., Certificates of Participation - COPS) The Authorized User’s sale or other transfer of Custom Products which were acquired by the Authorized User using third party, tax-exempt financing may not occur until such Custom Products are, or become, useable. In the event that the Contractor wishes to obtain ownership rights to Custom Product(s), the sale or other transfer shall be at fair market value determined at the time of such sale or other transfer, and must be pursuant to a separate written agreement in a form acceptable to the Authorized User which complies with the terms of this paragraph.

  • Geographical Indications 1. Each Party shall recognise that geographical indications may be protected through a trade xxxx or sui generis system or other legal means in accordance with its laws and regulations.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Third Party Technology The Company makes use of third party technology to collect information required for traffic measurement, research, and analytics. Use of third party technology entails data collection. We therefore would like to inform clients the Company enables third parties to place or read cookies located on the browsers of users entering the Company’s domain. Said third parties may also use web beacons to collect information through advertising located on the Company’s web site. Please note that you may change your browser settings to refuse or disable Local Shared Objects and similar technologies; however, by doing so you may be disabling some of the functionality of Company’s services.

  • Patent Marking LICENSEE shall xxxx all Licensed Products made, used or sold under the terms of this Agreement, or their containers, in accordance with the applicable patent marking laws.

  • Territory 43.1 This Agreement applies to the territory in which Verizon operates as an Incumbent Local Exchange Carrier in the Commonwealth of Pennsylvania. Verizon shall be obligated to provide Services under this Agreement only within this territory.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Patent Rights The State and the U. S. Department of Transportation shall have the royalty free, nonexclusive and irrevocable right to use and to authorize others to use any patents developed by the Engineer under this contract.

  • Foreground IP This subparagraph d. shall not apply to unmodified commercial off‐the‐shelf goods. If Services or goods are developed, modified or redesigned pursuant to this Contract then the paragraphs below apply.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

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