Schedule for Dual Inverted Sewer Siphon Design Sample Clauses

Schedule for Dual Inverted Sewer Siphon Design a. Within one (1) month following the acquisition of the aforementioned Pre-Design survey and operational data; the retention of a qualified Engineering Firm, and a fully executed Right of Entry Agreement with Somerset County, Xxxxxx Xxxxxx will produce a Conceptual Design drawing illustrating the general layout of the dual inverted sewer siphon, its approximate length and depth below the Raritan River, and the manner in which it will tie into the existing 54-inch sewer on both sides of the river, and attend a meeting to review the conceptual design with the Township of Bridgewater. This conceptual design must be reviewed and approved by the Township of Bridgewater before proceeding.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Schedule for Dual Inverted Sewer Siphon Design

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • Unbundled Subloop Distribution (USLD) 2.8.2.1 The USLD facility is a dedicated transmission facility that BellSouth provides from an End User’s point of demarcation to a BellSouth cross-connect device. The BellSouth cross-connect device may be located within a remote terminal (RT) or a stand-alone cross-box in the field or in the equipment room of a building. The USLD media is a copper twisted pair that can be provisioned as a 2-wire or 4-wire facility. BellSouth will make available the following subloop distribution offerings where facilities exist: USLD – Voice Grade (USLD-VG) Unbundled Copper Subloop (UCSL) USLD – Intrabuilding Network Cable (USLD-INC (aka riser cable))

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters).

  • Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame (MDF) to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (DAMLs), and may have up to 6,000 feet of bridged tap between the End User’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For Loops less than 18,000 feet and with less than 1300 Ohms resistance, the Loop will provide a voice grade transmission channel suitable for Loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point.

  • Ownership, Use and Return of Offering Materials The Offering Materials shall continue to be the property of the Owner and HFF. The Offering Materials will be used by the Potential Investor solely for the purpose of evaluating the possible acquisition of the Property and not for any purpose unrelated to the possible acquisition of the Property. The Offering Materials may not be copied or duplicated without the Owner's and HFF’s prior written consent, and must be returned to HFF (or with HFF’s permission, destroyed by Potential Investor and any Related Party, and in such instance Potential Investor shall certify in writing to HFF and Owner that such information has been so destroyed) immediately upon request or when the Potential Investor declines to make an offer for the Property or terminates any discussions or negotiations with respect to the Property.

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

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

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

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