Suction Case Sample Clauses

Suction Case. Suction case shall securely fasten the suction piping to the bowl assembly. It shall be heavily reinforced with streamlined fluid passages and it shall contain a sleeve bearing for the pump shaft which is effectively plugged at the bottom to form a grease container. A sand collar shall prevent sand from entering the suction case bearing.
AutoNDA by SimpleDocs

Related to Suction Case

  • Usual case If the Issuer is an emerging issuer (as defined in section 3.3 of the Policy) and you have not sold any escrow securities in a permitted secondary offering, your escrow securities will be released as follows: On , 2 , the date the Issuer’s securities are listed on a Canadian exchange (the listing date) 1/10 of your escrow securities 6 months after the listing date 1/6 of your remaining escrow securities 12 months after the listing date 1/5 of your remaining escrow securities 18 months after the listing date 1/4 of your remaining escrow securities 24 months after the listing date 1/3 of your remaining escrow securities 30 months after the listing date 1/2 of your remaining escrow securities 36 months after the listing date your remaining escrow securities *In the simplest case, where there are no changes to the escrow securities initially deposited and no additional escrow securities, the release schedule outlined above results in the escrow securities being released in equal tranches of 15% after completion of the release on the listing date.

  • Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.

  • Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.

  • Interconnection Customer Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,

  • DISCHARGE CASES 10.01 In the event of an Employee who has attained seniority being discharged from employment, and the Employee feeling that an injustice has been done, the case may be taken up as a grievance.

  • Assets Reserved and Pending Claims (a) If, upon the occurrence of a Dissolution Event, there are any assets that, in the judgment of the Liquidating Trustee, cannot be sold or distributed in kind without sacrificing a significant portion of the value thereof or where such sale or distribution is otherwise impractical at the time of the Dissolution Event, such assets may be retained by the Company if the Liquidating Trustee determines that the retention of such assets is in the best interests of the Members. Upon the sale of such assets or a determination by the Liquidating Trustee that circumstances no longer require their retention, such assets (at their Fair Value) or the proceeds of their sale shall be taken into account in computing Capital Account on winding up and amounts distributable pursuant to Section 6.2(b), and distributed in accordance with such value.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

  • Interconnection Customer Payments Not Taxable The Parties intend that all payments or property transfers made by the Interconnection Customer to the Participating TO for the installation of the Participating TO's Interconnection Facilities and the Network Upgrades shall be non-taxable, either as contributions to capital, or as a refundable advance, in accordance with the Internal Revenue Code and any applicable state income tax laws and shall not be taxable as contributions in aid of construction or otherwise under the Internal Revenue Code and any applicable state income tax laws.

  • Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None

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