RVP Vanpool Sample Clauses

The RVP Vanpool clause establishes the terms and conditions under which a vanpool program, typically organized by a Regional Vanpool Program (RVP), operates within the context of an agreement. This clause outlines eligibility requirements for participants, responsibilities for vehicle maintenance, scheduling, and cost-sharing arrangements among riders. By clearly defining the operational framework and participant obligations, the clause ensures smooth coordination of shared transportation and helps prevent disputes related to usage, costs, or liability.
RVP Vanpool. For purposes of this Agreement, the term “RVP Vanpool” means the nonprofit mode of prearranged commuter transportation in a RVP Vehicle that is owned by UTA and leased to Lessee and consists of a relatively fixed group of at least six persons, including the driver, that travels between fixed route bus stops and rail stations (“Transit Stops”) and the workplace. Lessee is prohibited operating the RVP Vanpool Vehicle in excess of a ten mile distance each way, a twenty-mile round trip, or 440 miles in each month. The number of individuals in the RVP Vehicle at any one time shall not exceed the RVP Vehicle manufacturer's design capacity for group occupancy. The RVP Vanpool is intended to provide incentives to persons to make the commute to and from work by a mode other than a single-occupant motor vehicle. The driver and passengers are employees at or near a common location and fees charged, if at all, are designed to recover operating, maintenance, insurance, administration, and reasonable depreciation costs related to the RVP Vanpool.
View Source

Related to RVP Vanpool

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • EPP Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730, 5731, 5732 (if using host objects), 5733 and 5734. If Registry Operator implements Registry Grace Period (RGP), it will comply with RFC 3915 and its successors. If Registry Operator requires the use of functionality outside the base EPP RFCs, Registry Operator must document EPP extensions in Internet-­‐Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.