Vehicle Types Sample Clauses

The 'Vehicle Types' clause defines which categories or models of vehicles are covered or permitted under an agreement. It typically specifies whether the contract applies to cars, trucks, motorcycles, or other vehicle classes, and may include details such as size, weight, or intended use. By clearly outlining the applicable vehicle types, this clause ensures both parties understand the scope of the agreement and prevents disputes over coverage or permitted use.
Vehicle Types. All new frontline collection vehicles will be provided for this contract. Vehicles will be expertly maintained at CONTRACTOR’s operations base. Vehicle specifications are provided in Exhibit 14. Until new vehicles arrive, new or like-new collection vehicles will be rented and deployed. CONTRACTOR is specifying a new fleet of clean fuel automated sideloaders (ASLs) to provide service to residential/cart customers. Vehicle selection supports the minimization of vehicle miles traveled and provides for routing flexibility. For residential recycling, split sideloaders will be utilized to sync with the designated recycling processing facility.
View Source
Vehicle Types. Government policy requires Authorized Users to use the most economical, fuel-efficient, and 'green' mode of transportation suitable for their needs. Authorized Users are encouraged to rent clean energy and hybrid vehicles wherever available and where servicing is available in the proposed operating area. Further, some ministries may restrict Authorized Users to the use of clean energy, hybrid or compact vehicles unless use of larger vehicles is pre-authorized by an expense authority. In the event an Authorized User reserves a vehicle of a particular type and that type of vehicle is not available at the time of rental, vehicles of alternate types offered will be offered at no additional cost.
View Source
Vehicle Types. Company is required to use low-emission or alternative fueled, state-of-the-art, regenerative air and/or mechanical broom sweepers that are certified to meet all State and Federal Environmental Protection Agency (EPA) and National Pollution Discharge Elimination System (NPDES) compliance mandates. Vehicles must not be over five (5) years in age.
View Source
Vehicle Types. All golf carts operated on AMSCD property or amenities must have standard electric power systems installed as standard equipment by the manufacturer and no after-market modification to that power system shall be permitted. Safe Working Condition. Golf Carts must be in sound and safe working condition. No golf cart may be operated on a path or roadway unless, at a minimum, the golf cart is equipped with the following features: efficient brakes, a reliable steering apparatus, safe tires, a rearview mirror, and red reflectorized warning devices in both the front and rear If authorized for use beyond the hours between sunrise to sunset, the golf cart must also be equipped with headlights, turn signals, and a windshield, and when operated during these times, the golf cart must use an activated headlight. A person who drives or is in actual physical control of a golf cart on a public roadway is subject to all
View Source
Vehicle Types. We reserve the right to substitute vehicles if the booked vehicle is not available at the time of rental, or is damaged during the rental period. The substitute vehicle may be of another type that is equal in size and ability.
View Source
Vehicle Types. Contractor’s Qualifications
View Source
Vehicle Types. 4 door sedans (Sedan) Midsize Sport Utility Vehicles (SUV) Extended Cab pickup trucks (Pickup) The KBI will deliver the vehicles to the vendor’s installation site. KBI will not be required to utilize these contracts if the vehicle is based at a location which is more than 100 miles from the contractor’s installation site. Payment: Payment shall be made after receipt of goods or services in agreement with Kansas Law. Payments shall not be made for costs or items not listed in the bidder's response.
View Source
Vehicle Types. Vehicle types listed herein are subject to availability. Rates for vehicle types not listed above will be provided upon request.
View Source
Vehicle Types 
View Source

Related to Vehicle Types

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between CLEC Party Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g., 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E-911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 CLEC Party shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which CLEC Party originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Meet Point B Interconnection Trunk group, exceeds (a) the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centum Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing Meet Point A One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,