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

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.

  • 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 EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (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 EveryCall. 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 EveryCall (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.

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

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • ISP-Bound Traffic 7.3.6.1 The Parties agree that ISP-bound traffic is Interstate traffic and governed by the FCC’s Order on Remand and Report and Order (Intercarrier Compensation for ISP-bound Traffic) CC Docket 01-131 (FCC ISP Order), effective June 14, 2001. However, the Parties agree to exchange ISP-bound traffic utilizing the xxxx and keep compensation mechanism. Xxxx and keep will apply to both end office call termination and tandem switched transport of ISP-bound traffic.

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