Project Vehicles Sample Clauses

Project Vehicles. ‌ 10 Developer shall not permit and shall prevent parking of Project vehicles and vehicles belonging 11 to Developer’s staff on the freeway, freeway on-/off-ramps, crossroads, work zones, under any 12 tree’s defined dripline, local streets, and outside the ADOT ROW, unless authorized by ADOT. 13 Developer shall not park any Project vehicles or staff vehicles in locations that damage existing 14 or proposed landscaped areas or impair the installation or maintenance of the temporary 15 irrigation systems to the landscaped areas. In addition, Developer shall not park or store any 16 equipment within the dripline of any tree. The dripline of a tree is defined as the line created by 17 the tree’s outermost branches that form the tree’s canopy and refers to the extent of the outer 18 layer of a trees leaves and branches. If Developer damages any irrigation systems or 19 landscaped areas, or parks or stores any equipment within any tree dripline, Developer shall 20 repair or replace the damaged area or system. Repair of any compaction or fluid spill under or 21 associated with any tree’s dripline that is a result of equipment or vehicle storage requires that 22 Developer shall bring the impacted area back to its pre-construction soil chemistry and 23 density/compaction through the use of a method that does not harm the tree’s root system 24 through removal and replacement of soil for fluid spills, or mechanical tillage or soil injection 25 methods to relieve the compaction; and, prior to commencing any repair or replacement, 26 Developer shall obtain ADOT’s approval of any and all such methods. If the tree(s) impacted by 27 such action show any signs of decline or stress during the Work, Developer shall replace such 28 trees with like kind, size, and character. 29 Developer’s light duty on-road vehicles that are on-site must have the Vehicle Project Logo and 30 Developer’s name visibly displayed on both sides of the vehicle. Developer’s Project vehicles 31 must be equipped with appropriate safety equipment and warning lights according to all Laws.
AutoNDA by SimpleDocs
Project Vehicles. ‌ 19 Developer shall not permit and shall prevent parking of Project vehicles and vehicles belonging 20 to Developer’s staff on the freeway, freeway on-/off-ramps, crossroads, work zones, under any 21 tree’s defined dripline, local streets, and outside the ADOT ROW, unless authorized by ADOT. 22 Developer shall not park any Project vehicles or staff vehicles in locations that damage existing 23 or proposed landscaped areas or impair the installation or maintenance of the temporary 24 irrigation systems to the landscaped areas. In addition, Developer shall not park or store any
Project Vehicles. ‌ 13 Project vehicles used by Developer shall comply with all vehicle registration, load restriction, and vehicle 14 delineation requirements when used on roads open to the public. Developer shall establish adequate 15 parking for Project staff personal vehicles as needed at the collocated office location. Developer may 16 provide parking specific staging areas away from work activities within Project ROW that shall be directly 17 accessible from public roads as approved by ADOT. Parking specific staging areas shall be constructed 18 of a hard surface temporary asphalt pavement or xxxxxxxx and parking stalls defined with pavement 19 markings. Parking specific staging areas shall be maintained through Substantial Completion as required 20 for work activities. 21 Storage of construction vehicles and parking of personal vehicles belonging to Developer staff will not be 22 permitted on public roadway, shoulders, or private parking lots without the owner’s approval. Parking of 23 personal vehicles belonging to Developer staff will not be permitted in any work zone. 24 Developer’s light duty on-road vehicles that are on-site shall have the Vehicle Project Logo and 25 Developer’s name visibly displayed on both sides of the vehicle. As a condition precedent to ADOT’s 26 issuance of NTP 2, Developer shall prepare and submit a full-size sample Vehicle Project Logo that is to 27 be affixed to all Developer’s Project vehicles to ADOT for approval in ADOT’s good faith discretion.
Project Vehicles a. The Developer shall, within 30 Calendar Days after NTP1, provide 0- 0000-0000 (110 cu. ft. EPA passenger volume or greater) five-passenger, four-wheel drive, Crossover sport utility vehicles, 0- 0000-0000 (150 cu. ft. EPA passenger volume or greater) seven-passenger, four-wheel drive, Crossover sport utility vehicles, and 0- 0000-0000 four-wheel drive Crew Cab (full-size class) pickups, including delivery charges, full service, all applicable taxes, and full coverage insurance, license plate fees, all maintenance, and all other cost inherent to provisions of said vehicles, excluding fuel expense. The vehicles shall be used exclusively by the Department’s staff until Final Acceptance; b. The Project Vehicles shall: i. Be new, white in color, and complete with all standard equipment; ii. Comply with the Motor Vehicle Safety Standards, as established by the U.S. Department of Transportation; iii. Have Developer maintained ownership and title of the vehicles during the period they are in the possession of the Department; and iv. In case of fire, theft, accident, or breakdown, be repaired or replaced within 48 hours of such occurrence. c. General equipment for the vehicles shall include: i. Four Door; ii. Engine – standard available for each identified model type; Central 70 Project: Project Agreement Schedule 8 (Project Administration) Schedule 8-45 iii. Tires and wheelsstandard size for each identified model type, with all season steel-belted radial tires; iv. Power anti-lock brakes and power steering; v. Automatic transmissions; vi. Vinyl floor mats; vii. Rear window wiper and defroster – electric type (Crossover sport utility type only); viii. Directional signals with 4-way flasher; ix. Inside rear view mirror – day/night type; x. Exterior mirrors – left and right mounted, power adjustable; xi. Air conditioner/heater;
Project Vehicles. SMART shall lease to Grantee for Xxxxxxx’s use SMART vehicle(s) as indicated in “Exhibit A” hereinafter referred to as “Project Vehicle(s),” in accordance with the terms and conditions of this Agreement. The forms making up Exhibit A shall be updated prior to delivery of the Project Vehicle(s) to include VIN number(s) and the acknowledgement that the Grantee has taken possession of the Project Vehicle(s). The Parties further agree that Exhibit A will be updated as necessary to reflect any changes to the Project Vehicle(s). All updates to Exhibit A shall become a part of this Agreement. SMART shall retain title to Project Vehicles. As a direct Recipient of §5310 funds, SMART is authorized to reassign and/or replace Project Vehicles as SMART deems necessary to achieve the desired outcome of §5310 grant funding. No Project Vehicles shall be disposed of or reassigned without prior written approval by XXXXX. Project Vehicles are provided on an “As Is” basis.

Related to Project Vehicles

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Office Space, Equipment and Facilities Provide such office space, office equipment and office facilities as are adequate to fulfill the Adviser’s obligations hereunder.

  • Capital Equipment Collaborator’s commitment, if any, to provide ICD with capital equipment to enable the research and development activities under the Research Plan appears in Appendix B. If Collaborator transfers to ICD the capital equipment or provides funds for ICD to purchase it, then ICD will own the equipment. If Collaborator loans capital equipment to ICD for use during the CRADA, Collaborator will be responsible for paying all costs and fees associated with the transport, installation, maintenance, repair, removal, or disposal of the equipment, and ICD will not be liable for any damage to the equipment.

  • Office Equipment The Client must not install any cabling, IT or telecom connections without the Provider’s consent, which the Provider may refuse at its absolute discretion.

  • Project Location [Insert the location of the Project, if applicable]

  • Critical Infrastructure Subcontracts For purposes of this Paragraph, the designated countries are China, Iran, North Korea, Russia, and any countries lawfully designated by the Governor as a threat to critical infrastructure. Pursuant to Section 113.002 of the Business and Commerce Code, Contractor shall not enter into a subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business and Commerce Code, in this state, other than access specifically allowed for product warranty and support purposes to any subcontractor unless (i) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is majority owned or controlled by citizens or governmental entities of a designated country; and (ii) neither the subcontractor nor its parent company, nor any affiliate of the subcontractor or its parent company, is headquartered in a designated country. Contractor will notify the System Agency before entering into any subcontract that will provide direct or remote access to or control of critical infrastructure, as defined by Section 113.001 of the Texas Business & Commerce Code, in this state.

  • Project Site The “Project Site” is the place where the Work is being carried on.

  • Property Locations (a) Provide to Administrative Agent at least 10 days’ prior written notice before adding any new offices or business or Collateral locations, including warehouses (unless such new offices or business or Collateral locations qualify as Excluded Locations). (b) With respect to any property or assets of a Loan Party located with a third party, including a bailee, datacenter or warehouse (other than Excluded Locations), Borrowers shall use commercially reasonable efforts to cause such third party to execute and deliver a Collateral Access Agreement for such location, including an acknowledgment from each of the third parties that it is holding or will hold such property, subject to Collateral Trustee’s security interest. (c) With respect to any property or assets of a Loan Party located on leased premises (other than Excluded Locations), Borrowers shall use commercially reasonable efforts to cause such third party to execute and deliver a Collateral Access Agreement for such location.

  • Leased Equipment The risk of loss or damage to leased equipment, goods or property shall not transfer to the University except as provided in §680.219, Florida Statutes. Any security interest in the leased equipment, goods or property granted to the Contractor contrary to AGO 79-72 and AGO 80-9 is null and void. Limitations of remedies provisions, which are unconscionable under applicable Florida law, are void. MATERIAL SAFETY DATA SHEET (MSDS). In compliance with Florida Statutes, Ch. 442, a Material Safety Data Sheet (MSDS) must accompany any applicable item delivered under this Agreement.

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!