My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Transit- Meeting Agenda (12/18/1997)
>
CS_Courthouse Square
>
Transit- Meeting Agenda (12/18/1997)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/20/2012 7:49:34 AM
Creation date
8/18/2011 2:50:31 PM
Metadata
Fields
Template:
Building
RecordID
10291
Title
Transit- Meeting Agenda (12/18/1997)
BLDG Date
1/1/1999
Building
Courthouse Square
BLDG Document Type
Committee
Project ID
CS9801 Courthouse Square Construction
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
154
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
(b) Reporting Format: CONTRACTOR is responsible for properly maintaining separate records and <br />summaries for this senrice as deemed necessary by the DISTRICT. The foilowing are the types of <br />information which the DISTRICT requires CONTRACTOR to maintain: <br />1. Annual Federal Transit Administration (FTA) National Transit Database (formerly Section 15) <br />Report: The CONTRACTOR will be responsible for supplying to the DISTRICT, in a timely <br />fashion, any inforrnation required to cor~plete this required report. <br />2. Tumdown(s) - CONTRACTOR is required to record daily tum-downs of eligible trip requests at all <br />times. DISTRICT may require CONTRACTOR to forward this trip tumdown/denial recording at <br />anytime. <br />3. Fare revenue shortaqes - Contractor is required to attach fare shortaqe explanations to the <br />Monthlv CherrvLift Reimbursement Request The District mav repuire CONTRACTOR to provide a <br />written action ~,fan to correct fare recorded fare shortages <br />3.4 Application Solicitation <br />CONTRACTOR is required to distribute eligibility applications for program participant registration. <br />DISTRICT will approve contents contained in program application. <br />3.5 Identification Cards for Program Participants <br />CONTRACTOR drivers are required to inspect the eligibility (identification) cards of all program <br />participants prior to each trip. <br />3.6 Ineligible Program Participants <br />If a driver observes or suspects that a program participant does not meet the DISTRICTs eligibility <br />criteria, CONTRACTOR must report the program participant along with all supporting findings to the <br />DISTRICT. <br />3.7 Display of Driver I.D. <br />CONTRACTOR shall ensure that drivers prominently display a photo identification card, in clear view, <br />on board the vehicle they are driving at all times. <br />3.8 Complaints <br />CONTRACTOR is required to respond orally or in writing to all rider complaints received from <br />DISTRICT or from CherryLift program participants. CONTRACTOR is required to notify DISTRICT of <br />the corrective action that was taken to prevent re-occuRence of the problem. If DISTRICT requests a <br />written response to a complaint CONTRACTOR must respond in writing within 10 calendar days. <br />Section 4.0 PERSONNEL <br />~ <br />CHERRYLIFT CONTRACT 112 ' AGREEMENT #1296. LIFf <br />
The URL can be used to link to this page
Your browser does not support the video tag.