High Traffic Sample Clauses

High Traffic remove dust with mop – or disposable cloth sweeper three times weekly. Damp mop for soilage as necessary. Spray clean or burnish using a mechanized system three times weekly. Light scrub and apply maintenance coat as necessary. Strip clean and reseal as required.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
High Traffic. Remove dust with mop – or disposable cloth sweeper daily. Damp mop for spillage as necessary. Strip floor monthly to remove old buildup wax in preparation for re-coating. Apply a non-slip and fully buffed water based wax. Buff monthly to achieve high gloss finish.
Sample 1
High Traffic. Remove dust with dust control mop or dust absorbent cloth daily. Damp mop with lukewarm water to remove dirt daily and buff these floors monthly to achieve high gloss finish.
Sample 1

Related to High Traffic

  • Transit Traffic The following rates will apply:

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Traffic The provisions in this Section apply regardless how the ISP-bound traffic is determined.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

  • Internet Traffic Any traffic that is transmitted to or returned from the Internet at any point during the duration of the transmission.

  • 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):

  • Tandem Transit Traffic 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on CBB's network, and is transported through Verizon’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Verizon, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Verizon. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). Switched Exchange Access Service traffic is not Tandem Transit Traffic.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Traffic Signals Based upon the results of the Traffic Warrant Studies, the Engineer shall identify and prepare Traffic Signal Plans for all warranted traffic signals. The Engineer shall confirm the power source for all signals and coordinate with the appropriate utility agency. Traffic Signal Plans must be signed and sealed by a Texas Registered Professional Engineer. The Engineer shall develop all quantities, general notes, specifications and incorporate the appropriate agency standards required to complete construction. Traffic signal poles, fixtures, signs, and lighting must be designed per the Green Ribbon Report recommendations and standards. The Engineer shall provide the following information in the Traffic Signal Plans:

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