Driving Distance Clause Samples

The Driving Distance clause defines the maximum allowable distance that can be traveled by a vehicle or driver under the terms of an agreement. Typically, this clause sets a specific mileage limit for a rental car, company vehicle, or delivery service, and may outline consequences or additional charges if the limit is exceeded. Its core function is to control usage, manage costs, and prevent excessive wear and tear on vehicles by clearly establishing boundaries for acceptable travel.
Driving Distance. At the discretion of Management, employees shall be scheduled to minimize the amount of driving necessary to fulfill their work obligations.
Driving Distance. Surcharge Within Martin County $0 per pay period 0-5 miles driving distance (outside Martin County) $20 per pay period 6-10 miles driving distance (outside Martin County) $30 per pay period 11 - 15 miles driving distance (outside Martin County) $40 per pay period For bargaining unit members who reside outside of Martin County, the fuel surcharge shall be calculated based on the “shortest distance” total driving mileage between the employee’s place of residence and the Martin County line. These two points shall be rounded down to the closest whole number. Bargaining unit members assigned take home vehicles shall be responsible for submitting a take home vehicle form to the Sheriff’s Office identifying the address of his or her residence, which shall list the calculated mileage. This form shall be updated and submitted to Human Resources anytime there is a change of address. The take home vehicle fuel surcharge shall be deducted from each bargaining unit member’s monthly paycheck.
Driving Distance. The use of the Shared Car will be limited to a specific cumulative driving distance as separately agreed upon by GL and the Member in advance. If the Shared Car is driven in excess of this limitation, a 20% surcharge on the base kilometer rate will be applied for the excess distance.

Related to Driving Distance

  • Interoperability MCP must make available to Members their electronic health information held by MCP pursuant to 42 Code of Federal Regulations Section 438.10 and in accordance with APL 22-026 or any subsequent version of the APL. MCP must make available an application program interface that makes complete and accurate Network Provider directory information available through a public-facing digital endpoint on MCP’s website pursuant to 42 Code of Federal Regulations Sections 438.242(b) and 438.10(h).

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

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

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.