Loading...
HomeMy WebLinkAbout508060 CLEVER DEVICES LTD - CONTRACT - RFP - 7381 ADVANCED TRAVELER INFORMATION SYSTEMSERVICES AGREEMENT THIS AGREEMENT made and entered into the day and year set forth below by and between THE CITY OF FORT COLLINS, COLORADO, a Municipal Corporation, hereinafter referred to as the "City" and Clever Devices, Ltd, hereinafter referred to as "Service Provider". WITNESSETH: In consideration of the mutual covenants and obligations herein expressed, it is agreed by and between the parties hereto as follows: 1. Scope of Services. The Service Provider agrees to provide services in accordance with the scope of services attached hereto as Exhibit "A", consisting of fifty-seven (57) pages and incorporated herein by this reference. 2. Contract Period. This Agreement shall commence October 15, 2012, and shall continue in full force and effect until October 14, 2017, unless sooner terminated as herein provided. Pricing changes shall be negotiated by and agreed to by both parties. The Denver Boulder Greeley CPIU published by the Colorado State Planning and Budget Office will be used as a guide. 3. Delay. If either party is prevented in whole or in part from performing its obligations by unforeseeable causes beyond its reasonable control and without its fault or negligence, then the party so prevented shall be excused from whatever performance is prevented by such cause. To the extent that the performance is actually prevented, the Service Provider must provide written notice to the City of such condition within fifteen (15) days from the onset of such condition. 4. Early Termination by City/Notice. Notwithstanding the time periods contained herein, the City may terminate this Agreement at any time without cause by providing written notice of termination to the Service Provider. Such notice shall be delivered at least fifteen (15) days prior to the termination date contained in said notice unless otherwise agreed in writing by the parties. All notices provided under this Agreement shall be effective when mailed, postage Services Agreement 7381 Advanced Traveler Information System the City Project Manager. Change of the Service Provider Project Manager after Contract Acceptance shall only be permissible with City's written approval. B. Initial Activities Meeting (CDRL 100, "Initial Activities Meeting") The initial activities meeting shall take place no later than 20 days after Notice To Proceed and shall be subject to the City's approval. City personnel will be introduced to the Service Provider's management team at the City's facilities. During these meetings, the Service Provider shall present the project control methodology and convey the plans for the initial activities prior to formal progress reporting. The objectives of the initial activities meeting shall be to familiarize the City with the Service Provider's intended design and procurement activities, resolve external interfaces, and provide the basis for proceeding to Preliminary Design Review. The initial activities meeting shall cover the following: 1. Schedule review 2. Confirm the Service Provider's management team and the scope for each subcontractor 3. Provide a functional block diagram of the system and equipment to be provided 4. Provide narrative descriptions of the major subsystems proposed by the Service Provider, including identification of components supplied by subcontractors for each equipment type 5. Provide preliminary device layouts 6. Identify all interfaces between the major subsystems, provide a schedule, and identify responsibilities for completion of detailed definition of the interfaces 7. Confirm that the Service Provider is familiar with the intended operations and maintenance environment 8. Provide outline and format of customer interface messages 9. Provide physical dimensions of each equipment type 10. Identify power and other facility requirements for each equipment type 11. Identify information needs and decisions required from the City 12. Provide description of problem tracking, resolution and reporting process. C. Project Management Plan - (CDRL 101, "Project Management Plan") The Service Provider shall submit a Project Management Plan that describes the organization, controls, planning, and schedules. The Project Management Plan (PMP) shall be submitted no more than 30 days following the Notice to Proceed and shall be subject to the City's review and approval. The plan shall include the following: 1. An organization chart identifying managers for all organization departments of the Service Provider and Subcontractors 2. The methodology to control program schedule 3. A master program schedule, emphasizing key milestones and events 4. A schedule for the items of design and manufacture that require approval 5. A configuration management plan for all submittals and subsequent revisions Services Agreement 7381 Advanced Traveler Information System 6. A Risk Register identifying areas of risk for the project, assign a level of risk and mitigation techniques to minimize the identified risk. 7. A subcontractor management and communications plan outlining the Service Provider's methods and procedures for organizing and communicating with the subcontractor. This shall include an outline of activities to be performed by DBE firms, an identification of the portion of the Contract revenues to be allocated to such firms for these activities, and the means of encouraging, tracking and controlling DBE participation throughout the duration of the Contract. 8. Procedures and processes to be followed for the replacement of any DBE subcontractor throughout the duration of the Contract. D. Progress Reviews, Schedules and Project Control - (CDRL 102, "Project Schedule") Progress reviews shall be held on a monthly basis at City's facilities, as appropriate. Other meetings may be scheduled as necessary. The Service Provider shall prepare and maintain a detailed progress schedule, which shall be the working schedule and shall be used to: 1. Plan 2. Organize 3. Execute the work 4. Record and report actual performance and progress 5. Forecast remaining work The Service Provider must fully comply with the schedule submission requirements specified herein to ensure the timely processing of progress payments. Work shall be scheduled so that any specified intermediate milestone dates and completion dates are met. The Project Schedule shall be submitted no more than 30 days following the Notice to Proceed and shall be subject to the City's review and approval. The Service Provider shall submit to the City a detailed progress schedule addressing Contract activities for the period from Notice to Proceed to completion of the warranty period. Activities shall also include the design reviews. Critical path method analysis shall be used to approve the baseline schedule of key milestones and events. One hard copy and one electronic copy in Microsoft Project 2007 shall be delivered. The hard copy of the progress schedule may be in the form of a Gantt bar chart. In preparation of the progress schedule, the Service Provider may propose, for the City's approval, alternative dates if the specified dates are not consistent with their sequence of work. This schedule shall be updated on a monthly basis according to the status of events and presented to the City at the status review meeting. E. Weekly Conference Calls The Service Provider shall participate in weekly conference calls with the City Project Manager, other City staff and outside consultants as determined by the City Project Manager. Services Agreement 7381 Advanced Traveler Information System The agenda for these meetings will be to discuss the most current status of and plans related to all identified issues. City reserves the right to identify for discussion any additional issues beyond those identified. A status report shall be issued to the City at least two days prior to each conference call, including: 1. Agenda for the upcoming conference call highlighting key discussion items; 2. Updated action item list with the updates incorporating the discussions of the previous bi-weekly conference call as well as other subsequent developments since the previous action item list release. The Service Provider shall be represented in these conference calls by at minimum their designated Project Manager, as well as any additional Service Provider staff necessary to properly address the current issues and project status. The City will be represented by their designated implementation management representatives. The call -in procedures for the conference call will be arranged by the Service Provider. The Service Provider shall submit minutes to the City Project manager within two business days of each conference call. F. Monthly Progress Status Updates - (CDRL 103, "Monthly Progress Reports") The Service Provider shall submit to the City monthly progress reports on planned progress and deviations, if any. Progress Reports will be provided in Service Provider standard reporting format. The first monthly progress Status report is due the Second Calendar month after Notice to Proceed and shall be subject to the City's review and approval and will continue through the end of the project. Special reports may be requested and topical reviews held to address problem areas. Progress reports shall also include: • A summary of completed, pending and upcoming Service Provider and City activities during the previous and the next two reporting periods, along with required completion dates • The status of unresolved Contract questions and change requests • A description of current and anticipated project problem areas and steps to be taken to resolve each problem • Updates to the Risk Register G. Design and Configuration Control The Service Provider's program for design and configuration control shall meet the requirements in the following subsections. The Service Provider shall conduct a Preliminary Design Review and a Final Design Review. H. Design Principles and Reviews Commonly accepted industrial design principles shall be employed throughout the design and manufacturing processes. Design calculations, layouts, and other documentation summarizing Services Agreement 7381 Advanced Traveler Information System the human factors engineering considerations shall be submitted during the design reviews. Industrial design aspects of ATIS shall be reviewed during the scheduled design review meetings. A formal design review process shall be conducted to evaluate the progress and technical, functional and programmatic adequacy of the design in accordance with the performance requirements of the Contract. In addition to formal design reviews, informal meetings to address key issues shall be held as needed. Prior to each review, a design review package shall be submitted to the City that includes items required for the review. Design review packages shall be provided at least 15 days before a design review meeting. Design reviews shall consist of the following key activities: 1. Design review package will be reviewed by City staff. 2. An Issues List will be created as a result of the review and will be provided to the Service Provider at least ten days prior to the scheduled design review meeting. 3. The design review meeting, or series of meetings, will be held between Service Provider and City staff where the Service Provider shall explain their design and the City shall confirm the requirements. When possible, issues will be resolved during the design review meetings. 4. Issues not resolved during the meetings will be identified and documented. City will determine the appropriate action to close the issue, giving consideration to where the project is in the overall design review process. This may require resubmission of design review items. 5. The submittal will be approved, upon the City's determination that there are no open issues. I. Preliminary Design Review - (CDRL 104, "PDR Package") The objective of the PDR is to review the progress of the project and evaluate specification compliance of the completed work and/or work in progress. The Preliminary Design Review shall be submitted no more than 90 days following the Notice to Proceed and shall be subject to the City's review and approval. The specific submittals shall be provided prior to PDR by the Service Provider in electronic format such as Microsoft Office 2010, Microsoft Project and Visio 2007 or Adobe PDF when appropriate and one reproducible on regular paper. The PDR shall cover the following: 1. Schedule compliance review and discussion of variances or delays 2. Detailed technical descriptions of ATIS system major components 3. Detailed interface descriptions, including hardware mounting arrangements and installation methods 4. Single -line power diagrams and functional block diagrams for each device, including a functional overview 5. Detailed network diagram including all wiring and communications interfaces 6. Software menus 7. Software system -level flow charts Services Agreement 7381 Advanced Traveler Information System 8. Software data backup and recovery procedures 9. Software version and configuration control system 10. Computer configurations for desktop and mobile access 11. Standards Package - The Service Provider shall prove that the City project is compatible with these standards to the best degree possible 12. a. The system(s) delivered as part of this project must be in compliance with nationally relevant standards such as the National Transportation Communications for ITS Protocol (NTCIP) and the Transit Communications Interface Profiles (TCIP). b. The proposed system must also conform to the Colorado Department of Transportation Region 4 ITS Plan. All equipment will meet all Local, State, and Federal regulations for safety and environmental control. Service Provider is encouraged to categorize the PDR information into logical topics. Ideally, the formal PDR meetings should be limited to confirmation of previously reviewed, commented on, and approved -in -principle submittals and resolution of open items. J. Final Design Review - (CDRL 105, "FDR Package") The FDR shall be conducted when detailed design is complete and production drawings are ready for release. The Final Design Review shall be submitted no more than 150 days following the Notice to Proceed and shall be subject to the City's review and approval. The objective of the FDR is to determine whether the detailed design will satisfy the design requirements established in the Contract. The specific submittals shall be provided prior to FOR by the Service Provider in electronic format such as Microsoft Office 2010, Microsoft Project and Visio 2007 or Adobe PDF when appropriate and one reproducible on regular paper. Data submitted for the PDR shall be updated to a level of detail consistent with the completed design and submitted for the FOR. The FDR shall cover the following: 1. Schedule compliance review and discussion of variances or delays 2. Latest revisions of the drawings and documentation submitted for the PDR 3. Assembly drawings down to the lowest replacement unit level 4. Electrical schematic drawings, down to the individual signal or wire level, for each external electrical circuit 5. Software documentation consisting of structured data flow diagrams, including Entity Relationship Drawing with software module descriptions (or elemental process descriptions) in structured narrative format. Input and output data definitions 6. Program parameters 7. Data dictionary 8. ERD — Entity Relationship Diagram The Service Provider may propose suitable confidentiality agreements. Services Agreement 7381 Advanced Traveler Information System For the purposes of change control, the design baseline shall be established at the FDR. The Service Provider shall submit to City for approval changes beyond FDR that affect the design characteristics agreed to at FDR. K. Data Communications Data transfer from the transit vehicles' to the City data center is currently provisioned using a Cisco wireless solution. Data currently being transferred involves recorded and live video and smart card data from onboard smart card readers. All data transfer operations are automated and do not require intervention by City personnel. L. Operating Environment ATIS shall be able to operate, without degradation in performance, under the following environmental conditions: • Humidity range of 20% to 100% • Temperature range of 20' F to 150' F • Direct or Indirect Sunlight • City requires that any system proposed must allow for 50% fleet growth ability within the specified limits of the proposal during the life of ATIS. • The ATIS solution must be able to provide a vehicle location determination anywhere in Larimer County and Boulder County and up to 10 miles inside the adjoining counties. Provided appropriate Cellular coverage is available. M. Protocols ATIS must include the ability to send an email via an email server to anyone, or any group, based upon an event. The use of protocols or methods of communications such as ICMP, SMTP, SMS, paging, etc. must be supported. The events must include, but not necessarily limited to, the following: 1. System Event 2. Generated Alarm 3. Any Filter Alarm 4. Any Input Alarm N. Anti -Virus and Security The VMS shall be compatible with the leading brands of anti -virus software in order to detect and deactivate malicious software that may attempt to attack the system. The option to set up ATIS in advanced security mode shall enable both IT and security managers to collectively integrate the unit into existing Microsoft Windows networks without compromising the existing security protocols. Services Agreement 7381 Advanced Traveler Information System O. Data Information and Ownership The ATIS solution shall have sufficient capacity to store the real-time data from the buses for at least five (5) 24-hour periods of data for all routes covered. Real-time data shall be archived on a daily basis. The database shall be capable of keeping ATIS data, standard reports, and other related information for a minimum period of one (1) year in a single standard database. In addition, back up and retrieval procedures shall be in place to be able to use archived data as needed. Data must be indexed by date and time in which the data was collected. All data generated and used by the ATIS system shall remain the property and for the exclusive use of the City with no limitations on any or all aspects of the data. P. Data Analysis and Report Generation — (CDRL 106 "Report Generation" The Service Provider shall perform all data processing and report generation from data collected until all accuracy testing and relevant City staff training have been successfully completed. The Report Generation shall be submitted no more than 60 days following the Pilot Testing and shall be subject to the City's review and approval. The reports will be submitted in hard copy and electronic format by the Service Provider to City within five (5) calendar days from the last date that data was collected from ATIS. Hardcopy and electronic reports will be produced for Weekday, Saturday, Weekly, Monthly and Annual service. The report formats submitted are subject to approval by City and will include the following: 1. Summary of all events observed for each vehicle and route assignment. 2. Summary of events by Geographic Location. 3. Schedule adherence utilizing specified parameters that can be adjusted over time, for early, on -time, and late bus arrivals from designated stops or time points along a route. 4. Running times by end -user specified route segment, time interval, and direction of travel. 5. Deadhead Running Times. 6. Schedule Adherence statistics: median, average, standard deviation, percentiles, etc. 7. On -Time performance summaries at different levels of detail, including system -wide, route, and time point levels. 8. Summary of all samples observed for each vehicle and route assignment. 9. NTD Report — Defined by Title 49 USC 5335. 10. Trip reports by route with stops in sequential order, including ID, description, Boarding, Alighting, Loads, Distance, and Passenger Miles. 11. Boarding, Alighting, and Load profiles by route, day of the week, month of year, stop location and time of day (variables are end -user specified). 12. Vehicle loads by time of day (end -user specified intervals). 13. Bus loads by end -user specified route segment, time interval and direction of travel. 14. Passenger Activity by stop, segment, route, and time period. 15. Location specific passenger activity (end -user selected location). 16. Dwell times. 17. Report on type of errors and adjustments. Services Agreement 7381 Advanced Traveler Information System 18. Time used in wheelchair lift operation (i.e., lowering, raising, and total time). 19. Wheel -chair lift usage by route by day and direction of travel. 20. Daily Status report from each vehicle including status on MDT, IVN, APC, GPS, including last time reporting in, last time transmitting data. etc. Q. Database Information The Service Provider shall provide network access to the raw database as well as standard reports for staff assigned to work with the data from the ATIS system. The database shall be able to be accessed, using standard ODBC protocols. City currently utilizes Microsoft SQL 2008 R2 as its enterprise database engine. The Service Provider database is to be installed at the City's main data center with oversight and approval of the City Project Manager assigned to this project. R. Software and License Model The Service Provider shall grant City the right to use all software and firmware used in the equipment provided under the Contract as follows: For Commercially Available Software, the Service Provider shall provide a license for each copy used in the equipment as well as the distribution media. The Service Provider shall provide for version updates of these applications during the warranty period as required to be compatible with the Service Provider's system. For Service Provider Proprietary Software, the Service Provider shall establish an escrow account with a third party, acceptable to City, for a period of no less than ten years, in which the same data as for the Project Specific Software will be deposited. The Service Provider shall pay all initial and future costs related to the escrow account. The data shall immediately be obtainable and usable by City should the Service Provider agree to release the data; should the Service Provider fail to satisfactorily respond to or support a written request for modification of the software by City in a reasonable amount of time during the term of the active escrow agreement; or, the term of the escrow has expired within a mutually agreed Software License agreement. The Service Provider shall notify City's current Project Manager of the intended closure of the escrow account. This notification must be made a minimum of 60 days prior to the closure. For software required for City ATIS operations, the Service Provider shall grant City a royalty -free right to use the software. City will have the right to modify all project -specific software settings and parameters that configure City's application, including: • Operating data (machine numbers, network numbers, and up/download parameters) • Display and voice text and graphics • Other configurable parameters as described in this document. The software and user's manual together with the training shall ensure that City personnel are able to modify the above listed parameters without system interruption of more than thirty minutes. S. Licensing Model The following license methodology will be used: Services Agreement 7381 Advanced Traveler Information System Product Description CleverCAD Server Single site license based on quantity of vehicles CleverCAD Client Unlimited install quantity BusTime Server Single site license based on quantity of vehicles BusTime User Access Web Based and unlimited DCC Server Single site license based on quantity of vehicles BusLink Single site license based on quantity of vehicles BusLink Client Unlimited install quantity BusTools data management Single Site License Clever Reports Server Single site license based on quantity of vehicles Clever Reports User Access Web based and unlimited Optional — Future AVM Server Single site license based on quantity of vehicles AVM User Access Web based and unlimited A breakdown in the Appendix B shows the licensing costs. T. Software Requirements - The Service Provider shall furnish all software fully debugged and documented. The Service Provider shall work with City to develop the Software Design and Documentation at the Preliminary and Final design reviews (PDR, FDR). The Service Provider shall provide for City approval the full up-to-date documentation, including flow diagrams, data structures, parameter tables, restoration plans, full restoration procedures, and all other design and development documentation, with each software package. Such documentation shall be accompanied by a functional description of the software as applicable to the City's ATIS system. A list of commercially available software to be employed in the system, including a description of the capabilities and proposed functionality of such software shall be submitted to City for review at PDR and approval at the FDR. All software documentation and licenses shall be provided by the date of delivery of the first equipment. Updated versions of such documentation, reflecting any prior changes made in the system, shall be provided within 21 days of any applicable system change. Final versions of such documentation shall be provided at the end of the warranty period. U. Interface Requirements Google Transit Feed Specification (GTFS) The Service Provider shall provide an export that meets the Google Transit Feed Specification (GTFS) for City to make available to Google. The intention is to use the Google based trip planning system in lieu of purchasing an independent trip planning system. The ATIS website shall link to the Google trip planning system and appear as a single seamless system. Services Agreement 7381 Advanced Traveler Information System AVL Data Export The Service Provider shall provide a fully integrated AVL data export capable of providing real- time information that enhances both en -route and pre -trip planning for City customers and City personnel. As part of this contract the Service Provider shall integrate all VMS and paging systems to support displays and sound systems at City specified locations, a new web site application that displays real-time arrival and departure information using both maps and textual displays. The Service Provider shall provide an open source application programming interface that includes real-time vehicle location updates for access by developers of web sites or mobile devices. Trapeze Software Interface The CAD software shall have an interface to Trapeze software that allows for seamless synchronization of payroll information as well as incident management. Incidents may be managed in either Trapeze Software or the CAD solution, however, the interface will ensure that data is reflected in both solutions "on save". Trapeze OPS will remain system of record for most items and lookup data such as employees, vehicles, incident types and investigation action types will be derived from Trapeze Software. The interface between OPS and the CAD system shall operate in an automated and virtually real-time fashion. The City updates scheduling based on special circumstances such as Holiday Service, and other special events. Schedule changes are typically exported three times annually from Trapeze. Daily vehicle and operator changes are made in Trapeze OPS. The interface shall have a log file that will allow monitor and management of the interface for troubleshooting purposes. The City will manage the interface between CleverCad and Trapeze Software Group. The Service Provider shall provide an interface tool set including documentation to determine what data is being transmitted and what data is received via software and / or reporting tools. V. Pilot Project Acceptance Test - (CDRL — 107 "Mini -Fleet (Pilot Phase) Deployment") The following section has multiple requirements that will be tested and require demonstration to be signed off during the pilot project phase. The Pilot Phase Deployment shall start within two weeks after Final Design Review (considered a grace period after receiving the FDR for questions or corrections) and completed within 90 days and shall be subject to the City's review and approval. The pilot project will consist of multiple system implementations including: • Computer Aided Dispatch • Vehicle Systems • Automatic Announcements • Passenger Information Systems • Information Displays and Paging Systems • Internet Information Services Agreement 7381 Advanced Traveler Information System prepaid and sent to the following addresses: City: Copy to: Service Provider: City of Fort Collins City of Fort Collins Clever Devices, Ltd Attn: Purchasing Attn: Dean Erickson, Senior 300 Crossways Park Drive PO Box 580 Database Analyst, Transfort Woodbury, NY 11797 Fort Collins, CO 80522 PO Box 580 Attn: William Duckett, Project Fort Collins, CO 80522 Manager In the event of early termination by the City, the Service Provider shall be paid for services rendered to the date of termination, subject only to the satisfactory performance of the Service Provider's obligations under this Agreement. Such payment shall be the Service Provider's sole right and remedy for such termination. 5. Contract Sum. The City shall pay the Service provider for the performance of this Contract, subject to additions and deletions provided herein, per the attached Exhibit "A", Appendix B; consisting of seven (7) pages, and incorporated herein by this reference. 6. City Representative. The City will designate, prior to commencement of the work, its representative who shall make, within the scope of his or her authority, all necessary and proper decisions with reference to the services provided under this agreement. All requests concerning this agreement shall be directed to the City Representative. 7. Independent Service provider. The services to be performed by Service Provider are those of an independent service provider and not of an employee of the City of Fort Collins. The City shall not be responsible for withholding any portion of Service Provider's compensation hereunder for the payment of FICA, Workmen's Compensation or other taxes or benefits or for any other purpose. 8. Personal Services. It is understood that the City enters into the Agreement based on the special abilities of the Service Provider and that this Agreement shall be considered as an agreement for personal services. Accordingly, the Service Provider shall neither assign any responsibilities nor delegate any duties arising under the Agreement without the prior written consent of the City. Services Agreement 7381 Advanced Traveler Information System • Application Server Environment • Data information and Ownership • Technical Overview • Interface Requirements The City will setup configure and implement the virtual server environment as specified in the Service Provider response to the proposal. Confirmation of the specifications by the Service Provider will ensure a successful deployment of technology. The applications can be installed once the City notifies the Service Provider that the servers are ready to be used. Installation can occur remotely through VPN connectivity or onsite. The technology systems and their implementation as determined in the preliminary and final design reviews shall be in place as part of the Pilot Project. The Service Provider shall provide documentation of verification methodology for each section prior to acceptance. The in -vehicle technology will be placed on five representative transit vehicles as selected by the City. The appropriate systems and equipment will be installed, configured and tested by the Service Provider prior to the start of the 45 day trial of the vehicles in revenue service. The length of time to implement the systems prior to the Pilot Project trials will be determined as parl of the design review. The City will provide to the Service Provider, a Paging System and LED message sign from the spare parts inventory of the MAX BRT contract for integration into the ATIS deployment. The City will receive them from the MAX BRT general contractor as part of the MAX BRT contract. IV. ATIS COMPONENTS AND PILOT PROJECT SYSTEM DETAILED REQUIREMENTS A. Computer Aided Dispatch (CAD) CAD technology is the foundation for accurate bus arrival information to be displayed. The CAD software shall include all necessary tools to enhance the dispatchers' ability to monitor and manage the transit fleet. The software shall utilize a user-friendly graphical interface that includes mapping capabilities and displaying of messages, events, and alarms as well as other functionality needed for the efficient management of the fleet. CAD will provide data for the downstream data systems such as Automatic Announcements, Interactive Voice Response, Message Notification systems and Mobile Applications. The software shall be capable of displaying the AVL software in tabular format. The tabular display shall provide the capability to display windows that contain the following information: 1. Vehicle, Run, Route, Block and Operator information synchronized with data generated from City Trapeze modules 2. Vehicles / Operators currently logged into the system 3. Vehicles not logged into The ATIS System 4. Vehicles that have not logged a successful wheelchair lift/ramp cycle 5. Early, On Time and Late vehicles with different colors 6. Off route vehicles 7. Characteristics of vehicles that have actuated a silent alarm condition. Services Agreement 7381 Advanced Traveler Information System 8. Passenger Count Information 9. Transfer protection requests between vehicles B. Automatic Vehicle Location (AVL) The Automatic Vehicle Location (AVL) subsystem shall provide location using an onboard Global Positioning Satellite (GPS) receiver as required reaching location accuracy within ten (10) meters location of actual vehicle location to support ATIS throughout the City's service area. Vehicle location shall be determined by a navigation algorithm that collects inputs from multiple sources and calculates a solution based on the reported reliability and weighting of each input device. The location determination device(s) shall automatically calibrate and require no operator or maintenance personnel intervention for daily usage. The GPS system shall have a cold acquisition time of no more than two (2) minutes, warm acquisition time of no more than fifteen (15) seconds and update the current position at least every five (5) seconds. The GPS system shall include multi -path rejection capabilities to help eliminate inaccurate signals caused by reflections off of buildings or other structures. Vehicle location shall be transmitted at least twice every one (1) minute to ATIS for display and storage purposes and every fifteen (15) seconds during an Emergency Alarm. GPS delay time from location acquisition to formatting for transmission shall not exceed one (1) second. The GPS system shall store the most recent location to provide as the "last known good" location in the event that location reporting is interrupted. Location messages transmitted to dispatch shall indicate messages status as current or "last known good". C. Real-time Prediction Accuracy City considers ATIS accuracy to be of the utmost importance. As such, accuracy and repeatability of results shall play a prominent part in system testing. The Service Provider shall confirm accuracy requirements are met during Functional System Testing. City's "real-time" arrival prediction accuracy goals are as follows: • 85% of all predictions within 60 seconds of predicted arrival time • 95% of all predictions within 90 seconds of predicted arrival time • 99% of all predictions within 120 seconds of predicted arrival time When real-time information is unavailable to serve a customer request for information due to a communications failure ATIS shall revert to providing schedule information clearly identified as schedule information until such time that the communications with the vehicle(s) is reestablished. A failure to receive vehicle update messages for five polling cycles shall constitute a communications failure. Accuracy shall remain consistent during changing conditions such as morning and afternoon pull-out, transition to off-peak operation, etc. The system shall indicate the vehicle is "Arriving" (or other equivalent message) to arrive if the real-time arrival prediction is one (1) minute or less. Services Agreement 7381 Advanced Traveler Information System The system shall process last minute corrections ("clear -down") to electronic message signs to reflect reality, e.g. the bus is due, has arrived, or has just departed. In no case shall the system indicate that the bus is due to arrive as it is departing the stop. Clear -down would take precedence over predicted arrival and departure times. D. AVL Data Accuracy and System Reliability Data accuracy and reliability shall fall within the following ranges: • Overall reliability of AVL hardware and software (excluding on -board vehicle hardware) system is expected to be 98% or better (System and all components are fully functional at least 98% of the time); • Overall reliability of AVL on -board bus hardware is expected to be 95% reliable, (based on a peak pull-out of 30 buses, we expect no more than 1 bus would have non- functioning AVL hardware); • Vehicle location information is expected to be 98% accurate based on a GPS accuracy of +/- 30 feet or less; • Schedule Adherence information is expected to be 95% reliable based on a +/- of two (2) minutes; • Real-time information system is expected to be 95% reliable based on a +/- of two and a half (2.5) minutes; • Any hardware component with a failure rate in excess of 10% or greater during the first twelve (12) months of the original warranty will be considered as a 100% failure. E. User Interface Configuration The map, textual, and tabular displays shall be designed such that functionality based upon access rights and permissions are either hidden or clearly identifiable as not accessible. The map, textual, and tabular displays shall be designed such that unavailable functionality based upon access rights and permissions does not impede ease of navigation within and between applications. The system administrator shall have the ability to configure profiles to be used for different classes of users through defined groups. The profiles shall permit the administrator to define access rights to applications as well as functions within applications. The system administrator shall be able to set permissions including any combination of read, write, change, and delete to applications and functions within applications. The Microsoft Active Directory Services (MADS) integration will allow for use of MADS security groups to allow functionality within CleverCAD. The system administrator shall have the ability to configure profiles to be used for different classes of users through defined groups. The profiles shall permit the administrator to define access rights to applications as well as functions within applications. The system administrator shall be able to set permissions including any combination of read, write, change, and delete to applications and functions within applications. The Microsoft Active Directory Services (MADS) integration will allow for use of MADS security groups to allow the user to logon to the CleverCAD system using the same Username/Password used for Workstation Logon. The user access and permissions, to the CAD features, will be managed within the CleverCAD Administration Utility Services Agreement 7381 Advanced Traveler Information System F. Schedule Adherence ATIS shall monitor Schedule Adherence by comparing real schedule versus the published schedule for all vehicles logged on. Schedule adherence data shall be stored and include parameters for analysis such as, but not limited to, vehicles, routes, time points, block/runs, and Operator ID. Both the time of arrival and departure at all scheduled time points shall be accurately recorded and stored. It shall be noted that City maintains multiple schedules for Weekday, Saturday, Sunday and maintains different schedules for schooldays, early out's etc. Based on AVL and the stored run and/or block logon, the on -board system shall constantly calculate the schedule adherence and present it to the vehicle operator. Schedule adherence shall be reported to ATIS via the cellular data network with every location update. Adherence tracking shall support multiple patterns per route and accurately report adherence for route and blocking techniques including route interlining, mid -trip and end -of -line layovers, revenue deadheads, and non -revenue deadheads. The City shall be responsible for providing the schedule data from the Trapeze FX and Trapeze Blockbuster software for use by ATIS. The Service Provider shall perform any stop and route geo-surveys required using Service Provider supplied tools and include a designated City employee in the process. The Service Provider shall provide adequate training prior to the start of this activity in accordance with the project schedule for the City designated employee. The Service Provider supplied tools for route/schedule maintenance shall be delivered to the City as a part of this process. Real-time (predictive to the next time point) schedule adherence shall be displayed for dispatchers and made available to the real-time customer information applications. In real-time, ATIS shall be capable of identifying vehicles that are predicted to be running early by more than a predefined number of minutes or late by more than a predefined number of minutes at the next scheduled time point on both graphical and tabular displays. Schedule adherence parameters shall be able to be set differently by route with separate early and late user supplied values. The onboard TCH display shall be configurable to either inhibit display or display the predicted status relative to schedule shown in one minute increments. If the TCH display is configured in the display mode the schedule adherence display will be shown to the Operator regardless of dispatcher selectable parameters. Schedule adherence from the vehicle shall be calculated, transmitted, and stored regardless of the onboard display setting. ATIS shall support multiple service types such as school in, school out, early school dismissal, Weekday, Saturday, Sunday, and holiday to accommodate service variations at the route and trip level. Each schedule day shall permit assignment of multiple service types. Schedule deviations for bus arrivals and departures at time points shall be recorded at the time when it occurs and independent of the poll rate. Information shall include: 1. Vehicle number 2. Operator number 3. Route number 4. Block number 5. Run number Services Agreement 7381 Advanced Traveler Information System 6. Direction 7. Geographic location 8. Date and time G. Route Adherence The onboard ATIS solutions shall provide off -route status to the Operator and transmit a notification to be displayed at the dispatch workstation. The off -route notification shall identify and display the name of the next stop when a vehicle is further than a pre -defined distance from the assigned route. The off -route distance value shall be a user definable parameter. The Service Provider shall identify whether the off -route distance is the total distance traveled from the assigned route or a deviation from the corridor of travel. H. ATIS System Time The ATIS system time shall be based on GPS time. The ATIS system shall display Mountain Time and provide automatic correction for daylight savings time. If a vehicle's GPS is not operating ATIS shall provide GPS time updates. GPS time shall be accessible for use throughout City's data network. Time on all ATIS components shall never be more than five (5) seconds different from GPS time. The TCH shall display time consistent with all other ATIS components throughout the City data network in a user specified format derived from the GPS sub -system. I. Data Messaging ATIS shall enable dispatchers to transmit text messages to an individual vehicle, a group of vehicles, a specific route, fleet, or all vehicles, an operator name, or operator ID. Text messages shall either be keyed in as free -form text or selected from a pre -defined text message list (canned). Text length shall support at least 256 characters. Pre -defined text messages shall be user definable. The dispatcher shall have the option to require an operator acknowledgement or response upon viewing the text message and shall be able to monitor the status of text message acknowledgements or responses. ATIS shall enable dispatchers to send any text messages designated as store -and -forward. Store -and -forward message duration shall be defined by a user defined time period. J. Textual and Tabular Displays Configurable multiple message queues for Data Messages, Schedule/Headway Adherence, Request to Talk, Emergency Alarms, text messages, maintenance alarms, system health, and other event messages shall be provided. Dynamic column filter and sorting shall be provided. The following tabular displays shall be provided: 1. Canned and ad hoc text messaging to the TCH or onboard vehicle displays with store and forward capability 2. Emergency alarm listen in, audible alarms, and downgrade capabilities 3. Schedule and route information by block and/or run including real time status 4. Pull -in and Pull-out status from garage(s) for late and missed pull -ins and pull-outs Services Agreement 7381 Advanced Traveler Information System 5. Capability for dispatchers to log in operators with optional requirement for operator acknowledgement 6. Off route monitoring including both off route and back on route notification 7. Display of operator generated transfers requests and capability to intervene in the transfer process as operationally required 8. Provide safety tool that will not allow the operator to send text messages while the vehicle is in motion. K. Map Display The ATIS map display shall be compatible with ESRI shape files and map layers that can be shared by all the City GIS enabled systems including Trapeze FX, trip planners, GIS tools and applications, and other public web based real-time information systems. City requires that the GIS solution be capable of supporting existing industry interface standards and provide the architecture to support future interface standards. The Map Display shall have the following characteristics: 1. Continuous refreshed real-time location of all vehicle location updates 2. Filtered map views based upon parameters such as vehicles by user definable groups, route, line group and login status 3. Options to display different vehicle icon labels including vehicle number, adherence, route, driver, and run per map view 4. Quick find tool to locate vehicles and routes 5. Automated focus and continuous vehicle tracking during Emergency Alarm condition L. Emergency Alarm (EA) When a dispatcher receives an EA the following events shall occur, in sequence: An audio alarm is triggered and the vehicle is continuously traced on the AVL work station map display in a separate window. The refresh rate for location reporting shall be at least every fifteen (15) seconds. An emergency alarm acknowledgment message is sent and discreetly displayed on the Transit Control Head (TCH). A Dispatcher responds to the emergency by listening in on the vehicle audio through a microphone integrated into the TCH or installed within the Operator work area. Emergency Alarms shall have the highest priority of all data messages. The EA event shall be transparent to anyone on the vehicle except the driver. The EA circuitry shall incorporate power -on -self -test features with the capability to detect open and short circuit conditions. The EA switch shall be a normally open switch to guard against accidental activation due to vibration, and shall be designed to preclude accidental activation by the operator (i.e. within a collar). Services Agreement 7381 Advanced Traveler Information System M. Historical Data (Playback Mode) ATIS users shall have quick and easy access to an historical event display or Playback application accessible agency -wide. The historical event display shall playback all pertinent historical messages (e.g., messages sent and received by: vehicle mobile data terminal and dispatch). The display shall be by a sequence of events on a geographic map. Playback of these events shall include the capability to perform the following functions: 1. Allow selection by vehicle(s), route(s), fleet(s), or run(s) for specific time frames through a query action window. 2. Configurable speed of replay for moving forward and backward through events 3. Graphical representation of event data on the ATIS system map 4. Selectable display of map layers including but not limited to stops, streets, routes, points of interest, and geographical attributes 5. Text display of attributes of each vehicle event message including messages related to other onboard systems 6. Step forward, step backward and pause the historical display of events 7. Zoom, move, center, and fit to window views within the map window 8. Measuring distance tool 9. Vehicle label by number, adherence, route, driver, run, and block 10. Locate vehicles, routes, intersections or objects 11. Display route traces 12. Date and time messages are logged 13. Print the historical display Automatic query for a selected vehicle in the real-time CAD system shall be available for dispatcher playback of all historical messages for a user -defined period of time prior to the current incident time for the dispatcher to assess the current conditions leading up to an event. V. VEHICLE SYSTEMS Vehicle systems will consist of onboard computers and operator consoles, VMS signs, integrated paging systems and automatic passenger counter systems. The integration of the Onboard Mobile Gateway will be considered a critical component of the received proposal. A. Clever Devices' Intelligent Vehicle Network (IVN) The On -board ATIS subsystem shall include an IVN as a central processing unit, including memory, input and output capabilities, data storage and system software residing on each vehicle. The IVN shall be the center of the on -board components, integrating the data communications for the information level applications included in this specification. The IVN shall be capable of real time updates and messaging to and from the vehicle. The IVN shall meet communication requirements for wireless network, as well as interfaces for current and future onboard ITS systems. Provided interfaces shall include RS232, RS485 with busy line, TTL, SAE J1708, SAE J1939, USB, Ethernet, TCP/IP, discrete inputs and outputs, odometer, spare 1/0 pins, audio inputs and outputs. Services Agreement 7381 Advanced Traveler Information System The IVN shall meet environmental and vibration standards (MIL-STD-81OD, NEMA-4) as well as appropriate electromagnetic immunity standards (SAE 1455) and protect against surge, and reverse polarity. The IVN shall be of proven design and easy to install and replace. In case the cellular data network is not available, all on -board functions with the exception of vehicle location and schedule adherence reporting to the central system shall be functioning. Event data will be stored locally until the communication link is restored. Data storage capacity shall be sufficient to store at least five operating days' worth of event messages in the case where data communications are disrupted and event messages are stored locally. Sufficient data storage capacity shall be included to store the complete current route schedules, pending route schedules, five days of operating data, and associated announcement files with 50% spare capacity for long-term growth. Configuration settings related specifically to the vehicle shall be stored in the vehicle's configuration module installed in the vehicle such that the IVN unit can be swapped out and the unique vehicle information automatically associated with the replacement IVN. Each IVN shall have a unique IF address for purposes of participating in the vehicle network and for remote monitoring. B. Data Transfer The On -board equipment shall be capable of sending real-time AVL data and APC data wirelessly using cellular technology as well as via Wi-Fi technology (802.11 b/g/n), at the City Facilities. Further, the wireless data transfer for both the AVL and APC systems shall not require any human intervention, input, or monitoring for its daily operation. Yet, the Service Provider shall supply a means to transfer data by manual methods using a portable device such as a laptop or other form of manual data retrieval. C. Transit Control Head (TCH) The TCH shall be connected to the IVN. The TCH shall provide visual messages and beep tone signals to the operator, if so configured by a system administrator of the City. The TCH shall be capable as serving as the single point of logon for the ATIS system and its subcomponents. The logon shall also capture the employee number and run and/or block number that can be shared with other future systems through industry standard interfaces and communication protocols. The TCH shall be a color graphical screen capable of displaying fonts of variable size. The TCH shall be designed with appropriate functional buttons capable of controlling other onboard ITS systems (e.g. fareboxes, head signs, card readers) including numeric input. There is no preference to touch -screen or hard key user interface. For a hard key user interface the TCH buttons shall provide tactile feedback for positive recognition of signal processing. For a touch - screen user interface the virtual keys shall not require additional cleaning and provide positive recognition of signal processing. The TCH shall provide contrast and brightness controls to provide for clear and easy viewing in day, night, or high glare conditions. The TCH shall be easy to install and replace, be durable and meet SAE ruggedness standards. The TCH shall be capable of providing status and setup capabilities to the system administrator of all integrated onboard systems including GPS, communications network and other on -board integrated ITS systems such as but not limited to Automatic Passenger Counters, Headway Signs and Fareboxes. Services Agreement 7381 Advanced Traveler Information System The TCH shall display the bus' actual progress related to schedule and route adherence. The TCH shall display vehicle status including data transmission, pending messages, and communication mode. The TCH shall be capable of providing unique aural tones to identify incoming messages to keep the operator's attention on the road while driving. The TCH shall be capable of providing onboard information and interface to onboard systems during operation of the vehicle including: 1. Logon 2. Emergency Alarm 3. Data Messaging 4. Transfer Assistance and Notification 5. Schedule Adherence 6. Trip/Schedule Status 7. Current Route and Direction 8. Maintenance Mode 9. Current GPS Time 10. Fare Box Control 11. Head sign Control 12. Map Display When the power is turned on, the TCH software shall automatically perform a power -on -self test, followed by configuring and initializing the TCH to the user -specified default values. The TCH shall be self -restarting and shall not become unresponsive and require manual restarts to continue operations. The TCH shutdown process will be controlled by the TCH software and shall only be possible when the ignition is in the off position. A user specified shutdown delay shall be provided to continue operations and to initiate the shutdown procedure that shall automatically close all files, save values, and send a shutdown message. Wheelchair lifts and ramps shall be monitored and data recorded for each cycle. If a wheelchair lift or ramp is not cycled prior to leaving a garage/storage area at startup, after the vehicle has moved a user configurable predefined distance then the TCH shall display a warning to the operator and transmit the warning to the central ATIS system for storage and display at the dispatcher work station. The TCH shall display a warning if a logon has not occurred after a vehicle is moved a user configurable predefined distance. This warning shall be transmitted to the ATIS system for storage and display at the dispatcher workstation. A logon process shall be provided for maintenance purposes to enable a vehicle to be moved through -out a facility for servicing and maintenance purposes without triggering alarms. D. Text Messaging The TCH shall allow the operator to send a message to dispatch from a set of pre -defined messages. Messages shall be capable of being grouped into categories for quick selection. Message categories and message text shall be user definable. The TCH shall support the Services Agreement 7381 Advanced Traveler Information System display of text messages longer than can fit on one line of the display. A minimum of twenty-four (24) messages shall be supported. The TCH shall store multiple messages received from dispatch and indicate those text messages that are unread. A distinct aural tone and visual notice shall alert the Operator of an arriving data message to be read when the vehicle is not in motion. A text message shall support a required Operator initiated acknowledgement message back to dispatch once the driver has viewed a message if flagged by dispatch as requiring Operator acknowledgement. Text messages shall be either deleted or saved by the Operator after viewing. Storage for saved text messages shall support a minimum of eight (8) stored messages. E. Transfer Requests ATIS shall provide an automated process to protect the transfer of passengers at designated transfer points designed primarily for transit centers, hubs and major transfer points. An Operator may select a time point along their trip and be presented with intersecting routes to "hold" after receiving a customer request for a transfer. Upon selection ATIS shall evaluate the request and either approve or deny the request based upon allowable parameters. The parameter values that define allowable hold times shall be user definable. The sending vehicle shall receive notification of the ATIS decision and if the request is approved the target vehicle shall receive a hold notification indicating the location and route to complete the transfer. The transfer process shall not require dispatcher intervention. However, the dispatcher shall have the capability to review transfer requests and intervene as appropriate. F. Automatic Passenger Counter (APC) APC systems will be installed on board each transit revenue vehicle and have the passenger counts stored on board and or transferred to the data center. The APC data must be compliant with the Federal Transit Administration ridership data requirements. APC collection equipment shall be installed at vehicle door entries. The equipment will enable complete ridership data collection, storage and transfer. APC data transfer will be enabled to occur automatically through the wireless infrastructure. The equipment shall not require any human input or monitoring for its daily operation. In addition, the Service Provider shall also supply a means to transfer data by manual methods using a portable data storage device such as a laptop or other form of manual data retrieval. The computer used for processing and analyzing the data must be able to accept and process the manually transferred data. The Service Provider must attain an accuracy of 95%. The Service Provider shall provide assistance in producing an APC benchmarking plan and APC maintenance plan or other process or plan as required by the Federal Transit Administration for certifying and maintaining certification of APCs for NTD reporting. Below are excerpts from: A Guidebook for Using Automatic Passenger Counter Data for National Transit Database (NTD) Reporting Prepared by National Center for Transit Research at CUTR University of South Florida, Tampa December 2010 ------------------------------------------------------------------------------- Services Agreement 7381 Advanced Traveler Information System 9. Acceptance Not Waiver. The City's approval or acceptance of, or payment for any of the services shall not be construed to operate as a waiver of any rights or benefits provided to the City under this Agreement or cause of action arising out of performance of this Agreement. 10. Warranty. a. Service Provider warrants that all work performed hereunder shall be performed with the highest degree of competence and care in accordance with accepted standards for work of a similar nature. b. Unless otherwise provided in the Agreement, all materials and equipment incorporated into any work shall be new and, where not specified, of the most suitable grade of their respective kinds for their intended use, and all workmanship shall be acceptable to City. C. Service Provider warrants all equipment, materials, labor and other work, provided under this Agreement, except City -furnished materials, equipment and labor, against defects and nonconformances in design, materials and workmanship/workwomanship for a period beginning with the start of the work and ending twelve (12) months from and after final acceptance under the Agreement, regardless whether the same were furnished or performed by Service Provider or by any of its subcontractors of any tier. Upon receipt of written notice from City of any such defect or nonconformances, the affected item or part thereof shall be redesigned, repaired or replaced by Service Provider in a manner and at a time acceptable to City. 11. Default. Each and every term and condition hereof shall be deemed to be a material element of this Agreement. In the event either party should fail or refuse to perform according to the terms of this agreement, such party may be declared in default thereof. 12. Remedies. In the event a party has been declared in default, such defaulting party shall be allowed a period of ten (10) days within which to cure said default. In the event the default remains uncorrected, the party declaring default may elect to (a) terminate the Services Agreement 7381 Advanced Traveler Information System These requirements for the use of APCs in obtaining UPT and PMT for motorbus also are valid for the use of APCs on other modes such as light rail service. 2.2.1 Benchmarking Plan The benchmarking plan must contain procedures for conducting the benchmarking study during the first year for which an agency wants to use APC data for NTD reporting. These procedures cover three aspects: 1. Selecting a random sample of one-way vehicle trips covering a full year according to a sampling plan. This sampling plan must be designed for the resulting annual PMT and UPT data from both APCs and ride checkers to meet FTA's minimum 10% precision and 95% confidence levels. 2. Testing the statistical equivalence in the sample APTL between the parallel APC data and manual ride -check data from the same sample. 3. Adjusting the APC data for UPT and PMT to replicate the data produced by the manual ride -check data. 2.2.2 Maintenance Plan The maintenance plan must include procedures for calibrating APCs every year after the first year of using APC data for NTD reporting. These procedures cover three aspects: 1. Selecting a sample of at least 100 vehicle trips using ride checkers to collect the UPT and PM data. The trips in the sample do not need to be randomly distributed by route, by day, and time of day. 2. Estimating and comparing the UPT and PMT data collected by ride checkers to APC derived UPT and PMT data and the statistical variance between the two data sets. 3. Regularly checking and reconciling UPT counts from APCs against trip counts and fares from registering fare boxes. The City desires to have FTA APC certification for the MAX BRT service scheduled to start in 2014. G. Automatic Announcements (AA) Automatic announcement systems consist of three main areas: • In Vehicle Systems • Transit Centers • Platforms and Stops H. In Vehicle Systems In vehicle systems will consist of Service Provider installed Variable Message Sign (VMS) mounted to the ceiling and integration with the existing onboard paging system. There will be two VMS on forty (40) foot length and smaller buses and three VMS on sixty (60) foot length buses. The exact location for the VMS to be installed will be approved by the City prior to installation. The bus manufacturer and paging system types are noted in Appendix C Vehicles. Services Agreement 7381 Advanced Traveler Information System VI The AA shall announce and display information determined by City staff as the vehicle passes through geo-fences or other GPS triggered methodology created by the proposed system. The announcements and displays must meet ADA requirements. Canned messages and dynamic messages generated from the CAD system will be playable over the AA in each vehicle. Transit Centers Transit Center AA will consist of integration of existing paging systems and VMS at each transit center. The AA shall announce and display information determined in collaboration with City staff as the vehicle passes through geo-fences created by the proposed system. The announcements and displays must meet ADA requirements. Details of current equipment are in Appendix D - Transit Centers J. Platforms and Stops Platforms and stops AA will consist of VMS and paging systems along the Mason Corridor BRT line. The AA shall announce and display information determined in collaboration with City staff as the vehicle passes through geo-fences created by the proposed system. The announcements and displays must meet ADA requirements. Canned messages and dynamic messages generated from the CAD system will be playable over the AA to each platform or stop. All VMS and paging systems are being installed by the General Contractor building the MAX BRT line. Integration into those devices will be required as part of this project. All hardware required for interface at each BRT Stop or Platform must be installed by the BRT General Contractor. The appropriate interface equipment (if required) will be provided by the Service Provider with installation instructions. Software configuration and final testing will be completed by the Service Provider. PASSENGER INFORMATION SYSTEMS Passenger information systems consist of external facing or public facing ATIS systems: • An interactive voice response system for telecommunication callers. • A series of information displays such as variable message signs (LED) and digital signage systems (LCD) and paging systems. • An internet information web site with a mobile ready version • Mobile device application and development • Mobile SMS/Email component A. Interactive Voice Response (IVR) The IVR system shall provide for user supplied numeric bus stop identification for automated delivery of bus stop level real-time and schedule information. The IVR system shall incorporate the City's bus stop numeric identification system. Using the unique stop identification number the IVR system shall provide the most current information related to all routes and vehicles providing service at that stop location. The IVR system shall interface with ATIS for service bulletins, scheduled, and real-time bus information. Services Agreement 7381 Advanced Traveler Information System The IVR shall be capable of providing computer Telephony Integration. The City has a Cisco VOIP phone system that will be used for the IVR system. The IVR shall include technology integrated with the input from touch -tones phones and not use voice activated interaction. The IVR shall provide management tools for authorized City personnel to configure the system without experiencing system down -time. Reports shall be available to monitor usage statistics. The IVR will be used in conjunction with two dial in phone lines and a phone tree that will roll over the third line to a customer service representative. B. Information Displays and Paging Systems The Service Provider shall provide a data input to existing or planned LED and LCD signs and paging systems. Information provided to the signs and paging systems shall include scheduled and real-time transit vehicle arrival / departure information, text messages, vehicle location, bay assignments, maps, and other multi -media content. Layout capabilities shall be user definable and capable of supporting alternate purposes other than transit scheduling notification including multimedia capabilities. A user interface shall provide easy setup, configuration, diagnostic, and messaging status at each Passenger Information Display location. Displays shall be capable of showing multiple routes, ATIS system time, ad hoc messages, sponsor advertising, and scheduled messages. A system administrator user interface shall provide diagnostic information, messaging status, setup, configuration, and messaging capabilities for all locations. The following list identifies the locations in City's operating area that are the primary candidates for real-time traveler information displays and are provided for sizing of the ATIS design: South Transit Center 1. Will consist of Eleven (11) bus bay Variable Message Displays (LED) (displays will be purchased and installed by the MAX Bus Rapid Transit General Contractor) — Outdoor 2. Will consist of Two (2) 40" LCD displays using a digital signage software (displays will be purchased and installed by the MAX Bus Rapid Transit General Contractor) 3. Will consist of bus bay specific paging system and internal paging system (paging system will be purchased and installed by the MAX Bus Rapid Transit General Contractor) Downtown Transit Center 1. Consists of an existing 40" LCD display using Four Winds Interactive digital signage software. 2. Consists of existing internal and external paging system Colorado State University Transit Center 1. Consists of an existing 40" LCD display using Four Winds Interactive digital signage software. 2. Consists of an existing 46" LCD display using Four Winds Interactive digital signage software. Services Agreement 7381 Advanced Traveler Information System 3. Consists of existing internal and external paging system MAX Bus Rapid Transit Stops and Platforms 1. Will consist of thirty seven (37) Variable Message Displays (LED) (displays will be purchased and installed by the MAX Bus Rapid Transit General Contractor) — Outdoor 2. Will consist of Stop and Platform specific paging system (paging system will be purchased and installed by the MAX Bus Rapid Transit General Contractor) C. Internet Information (Web Site) The Service Provider shall provide a dynamic geographical view of City's system routes, stops, and vehicles with up-to-date real time information using web services. The web interface will show route and stop information, scheduled departure times, next estimated arrival and departure times shall be provided. Information from the web services shall be published to personal computers, cell phones, personal internet enable devices, and other wireless devices. Customers shall be able to place subscriptions to real-time alerts for routes, stops, system wide alerts, and specific trips that will be published by the City web service prior to a configurable period of time to the event's occurrence. Options that are user definable shall be provided that integrate the real-time display of information into the look and feel of the existing City web site. Such options should include graphics, logos, backgrounds, page layout, and icons. Map displays shall include configurable colors, routes, map layers, backgrounds and refresh rates. The web site application shall permit the user to enter a stop id and select a route and direction. The system will then display the arrival times of the next two buses. The application shall also permit the user to identify one or more routes on a map display. All vehicles on the route(s) shall be displayed at the last known location if communications with the vehicle are active otherwise scheduled locations shall be displayed and clearly labeled as scheduled. Each vehicle shall display route, direction, next time point, and bus ID when the cursor is placed or clicked on the vehicle. The map shall display bus stops on the route(s) when the zoom level is close enough to support this level of detail. Each stop shall provide the street location, route(s) and direction(s) served, and unique bus stop ID when the cursor is placed or clicked on the stop. The web site application shall permit the user to identify a route, direction, and stop to display the next two scheduled buses and their real-time estimated time of arrival for that stop. When the real-time estimated time of arrival is unknown the web site will clearly state that the scheduled time only is being provided. All web services configurations, applications and public facing information shall be approved by a City representative prior to final design and deployment. D. Mobile Device Applications and Web Site The Service Provider shall provide a mobile application in support of the (phone and Droid operating systems on smart phones. The application will be developed and maintained by the Service Provider and made available on the ATIS website and other mobile app websites. The Service Provider will coordinate content and features with City prior to each release to the general public. Services Agreement 7381 Advanced Traveler Information System 1. Plan your itinerary using the Google Trip Planner. 2. Find fare, safety rules and help information. 3. Get latest news and rider alerts. 4. The mobile app allows customers to locate the nearest lines and stations based on the smart phone's GPS capabilities. 5. The application is integrated with Google Maps, displaying the nearest stations and lines based on your smart phone's GPS location. Platforms, stops or transit centers are represented with a pin and a popup displaying the Line information. 6. Ability to register or change your transit alerts. 7. Ability to put a City disclaimer banner or use agreements into Mobile app prior to use. The mobile ready version of the ATIS web site shall be developed and made available for use on mobile devices. The Service Provider will coordinate content and features prior to release to the general public. In addition to the requirements listed above, the mobile ready version will also require: 1. The mobile web site allows customers to locate the nearest lines and stations based on their interest. 2. The mobile web site integrated with Google Maps, displaying the stations and lines based on your interest. Platforms, stops or transit centers are represented with icons or other designated symbols. 3. All web services configurations, applications and public facing information shall be approved by a City representative prior to final design and deployment. E. Mobile SMS/Email The proposed ATIS solution will include the capability for passengers to access rider alert information, real-time and schedule time information via SMS and email messaging. At a minimum, the system will allow passengers to subscribe to SMS and email messages as described earlier in this section. Subscriptions will allow passengers to receive this information in the following manner: • Real-time arrival information • Real-time rider alerts At a minimum, the proposed solutions will also include the capability for passengers to receive these updates using the following context: • Day of week • Time of day • Route • Bus stop The proposed ATIS solution will include the ability to deliver default schedule information and/or canned messages with alerts when the system is unable to calculate a prediction to send via SMS or email. Services Agreement 7381 Advanced Traveler Information System The system will allow passengers to place subscriptions to SMS and email messaging through public facing website. The system will also allow passengers to request real-time arrival, real- time rider alert and scheduling arrival information by entering a stop number via a mobile application. F. The SMS Texting Plan The SMS texting plan will be administered by the Service Provider. The SMS texting plan can be changed at any time for effect the following month. The initial scope will be the 45,000 SMS text messages a month as provided by TextMarks.. The City shall require a way to monitor the usage and have a limited texting plan. This can be done by running one of two reports; Daily Informational Alerts Traffic Summary or Traffic Detailed. These reports will give the City Personnel the usage numbers they need to monitor the activity for any time period they require in order to tweak their message credits contract with TextMarks if necessary. The Admin User would choose the appropriate report type, date range and additional options for having it run automatically at desired intervals and delivered through email if desired. Reports cover outbound and inbound traffic. G. Upgrade Tools The Service Provider shall provide upgrade protection in the following areas to ensure in system customizations will continue with new versions of the software: 1. Customized tables and fields 2. The Trapeze Software Interface VII. MAINTENANCE AND SUPPORT The Service Provider shall provide complete details addressing the following minimum requirements: 1. Maintenance coverage for routine services on a periodic basis, including software updates, patches, and upgrades. 2. Emergency response service with a guaranteed response time, location of dispatch by responding party and process to be followed for the following events: a. System outage b. Network control and monitoring center outage 3. Period of maintenance coverage (i.e., number of hours or days of maintenance coverage) 4. Equipment replacement procedures (onsite and depot parts repair and replacement) 5. Describe response procedure for: a. Escalation calls b. First-time response to service calls 6. Provide breakdown report of all maintenance costs for all equipment, software, network response and services including warranty periods. 7. The Service Provider shall have the ability to connect remotely to ATIS to provide needed support. The remote connectivity will be through approved City VPN security software and procedures. Services Agreement 7381 Advanced Traveler Information System 8. Communication between the Service Provider and the City shall be on an ongoing basis. Advanced notification shall occur when any work is to be performed remotely or on site at any City facility or station / stop. Any work being performed on the construction sites of transit facilities must be approved by the City before the work can begin. Vill. TRAINING A. Training Program Plan - (CDRL 108, "Training Program Plan") The Service Provider shall submit a Training Program Plan in accordance with the criteria outlined below. The Training Program Plan shall be submitted no more than 90 days following the Notice to Proceed and shall be subject to the City's review and approval. City staff or its representatives shall have the right to request and receive instruction regarding the operations and maintenance of all provided equipment, from the Service Provider, at any time as part of the training process. B. Description A narrative description that documents the training of City staff shall be delivered during the Pilot Phase deployment and prior to the training. City staff to be trained includes operations managers, dispatch operators, shift supervisors, drivers, repair personnel, IT, marketing specialists, and trainers. The description for each training program shall include the following: 1. Performance objectives that state the expected behavior, the conditions under which performance will occur, and the measures and standards to be applied 2. The sequence of learning activities 3. An outline of the content 4. Learning strategies to be used (e.g., classroom presentation, hands-on practice, paper and pencil exercises, etc.) 5. Methods and criteria for evaluating performance, including an objective grading system to report progress of trainees during the training 6. Resources required, such as equipment, shop space, projectors, screens, etc. 7. Approximate hours required for training, including classroom and hands-on instruction. C. Training Delivery Schedule A schedule based on the number of hours of instruction shall be developed. The training delivery schedule shall include the following information: 1. Title of the program 2. General description of the program 3. Intended audience 4. Size of the audience 5. City facilities required (e.g., classroom size) 6. Sequence of classroom and hands-on instruction and estimated hours required for both 7. Number of sessions 8. Any other information that will facilitate planning for and delivery of the training programs. Services Agreement 7381 Advanced Traveler Information System D. Service Provider's Training Experience The Service Provider Trainers shall consist of field experienced personnel who have hands on knowledge of the provided system. Resumes of all trainers shall be provided to City no later than 60 days prior to training commencement. City reserves the right to request changes in the proposed training staff with no extra expense to City. E. Training Materials - The Service Provider shall submit the training materials required for each course discussed in the Training Program Plan in accordance with the following requirements. The Service Provider shall provide a list of training materials required for each course discussed in the Training Program Plan. The Service Provider shall reflect all changes and revisions to the installed ATIS systems in all training materials, whether supplied to City personnel, or used in Service Provider -conducted training courses. At a minimum the following training materials shall be provided for each course in sufficient quantities: Instructor guides, including the following: 1. Course agenda and objectives 2. Resources and facilities required for the course 3. Detailed lesson plans or outlined presentations and discussion guides 4. Pre- and post -training assignments 5. Instructions for using any audiovisual support and equipment 6. Student handouts 7. Operational ATIS equipment Two copies of draft training materials shall be submitted at FDR. Final training materials shall be submitted 20 days before classes are scheduled to begin for City approval. The above deliverables shall be in addition to a master copy of each final version that shall be furnished to City. F. Training Courses The Service Provider shall provide a series of courses designed to train operators, dispatchers, operations supervisors, customer service representatives, system administrators, maintenance, and IT personnel on the ATIS operations and simple maintenance. The Service Provider shall provide the City a course description of each course as part of the training program deliverable. All provided training courses shall be accompanied by training manuals, guides, training aids, student and instructor workbooks, and operator and maintenance manuals. All training classes will be scheduled by City and will not take place before the CAD systems are installed on site. A plan for training the City staff to deliver the training shall be included. It shall describe the Service Provider's approach, resources and hours required, and any training aids that might be included. Services Agreement 7381 Advanced Traveler Information System G. Vehicle Equipment Training and Maintenance Module The Service Provider shall supply one (1) portable ATIS module, or "bus -in -a -box" for a training period of one month before go -live and one month after go -live, that can be used for training simulation and system maintenance purposes (see Training Section). The "bus -in -a -box" shall be designed and constructed to be portable and include all ATIS vehicle equipment. The "bus - in -a -box" shall be able to communicate with the central system and operate like any other ATIS equipped vehicle using simulated motion through any run/block file loaded after a successful logon. The purchase of the bus -in -a box is included in the pricing. The bus -in -a -box can be used as a test bed after training is completed. H. Fleet Deployment — (CDRL 109 "Fleet Deployment Complete") The following section has multiple requirements that will be tested and require demonstration to be signed off during the fleet deployment phase. The fleet deployment phase shall start within 20 days after a successful Pilot Phase Deployment and shall be subject to the City's review and approval. The fleet deployment phase will consist of multiple system implementations including: • Vehicle Systems o IVN deployment o TCH deployment o VMS deployment o Paging integration o Farebox integration o Headsign integration The in -vehicle technology will be placed on the remaining transit vehicles. The appropriate systems and equipment will be installed, configured and tested by the Service Provider. The length of time to install the In -Vehicle systems will be as shown below: Bus Manufacturer Size in Feet Time to install, configure, implement and test in Hours. NABI 35,40 10-14 Man Hours NABI 60 12-16 Man Hours Gillig 30, 35, 40 10-14 Man Hours An installation schedule based on the information has been determined to be 6-8 hours per type of vehicle and the completion of the fleet deployment will be completed within 40 days of Successful pilot phase. Each vehicle must be tested and accepted by the City representative to be fully ATIS operational. Any vehicle not deemed fully ATIS operational must be corrected before Fleet deployment is considered complete and before moving into the System Acceptance Phase. Services Agreement 7381 Advanced Traveler Information System System Acceptance — (CDRL 110 "System Acceptance" The Service Provider shall provide proof through documentation and demonstration that all aspects of the ATIS system as defined in the section under Pilot Phase Acceptance Test have been signed off on. When the fleet deployment has been certified as.complete and all vehicles are deployed with ATIS equipment a state of GO Live will be issued by the City. All vehicles shall have been tested and demonstrated to the City representative that the ATIS system is fully functional and has been running without error for 60 days. The GO Live date may move if there are errors and or ongoing technical problems with any of the ATIS components, subsystems or deployed technology. Any discrepancies that arise during the 60 day period must be recorded and assessed by the City and Service Provider for impact on System Acceptance. The System Acceptance Chart is included in Appendix A and must be filled out by a City representative prior to System Acceptance being completed. J. Project Closeout — (CDRL 111 "Project Closeout Phase" The Project Closeout Phase will start immediately after the formal System Acceptance. The transition into the warranty period will start and the Service Provider will continue to provide technical support as part of the warranty period. The Service Provider shall provide technical support for both hardware and software in an ongoing basis until at which time the City decides not to pursue a support contract, typically at end of life for the technology. The Project Closeout phase shall include delivery of documentation that includes the following: 1. Updated system documentation 2. Updated training information for future training sessions 3. Project management plan 4. Risk Register 5. Status reports 6. Memos 7. Change Orders 8. Lessons Learned The document shall contain information pertaining to methodology or best practices when deploying transit related technology. All documentation shall be reviewed and approved by a City representative before the Project Closeout Phase is complete. K. Professional Services Professional Services can be purchased from the Service Provider using the table in Appendix 8 for specific labor categories. Professional Services shall be used for integration or expansion of ATIS technology to other transit related systems and subsystems. Services could also include but not limited to consulting, studies, application programming or interface integration. Services can also include installation and removal of related hardware from transit vehicles. Services Agreement 7381 Advanced Traveler Information System Agreement and seek damages; (b) treat the Agreement as continuing and require specific performance; or (c) avail himself of any other remedy at law or equity. If the non -defaulting party commences legal or equitable actions against the defaulting party, the defaulting party shall be liable to the non -defaulting party for the non -defaulting party's reasonable attorney fees and costs incurred because of the default. 13. Binding Effect. This writing, together with the exhibits hereto, constitutes the entire agreement between the parties and shall be binding upon said parties, their officers, employees, agents and assigns and shall inure to the benefit of the respective survivors, heirs, personal representatives, successors and assigns of said parties. 14. Indemnity/Insurance. a. The Service Provider agrees to indemnify and save harmless the City, its officers, agents and employees against and from any and all actions, suits, claims, demands or liability of any character whatsoever brought or asserted for injuries to or death of any person or persons, or damages to property arising out of, result from or occurring in connection with the performance of any service hereunder. b. The Service Provider shall take all necessary precautions in performing the work hereunder to prevent injury to persons and property. c. Without limiting any of the Service Provider's obligations hereunder, the Service Provider shall provide and maintain insurance coverage naming the City as an additional insured under this Agreement of the type and with the limits specified within Exhibit B, consisting of one (1) page, attached hereto and incorporated herein by this reference. The Service Provider before commencing services hereunder, shall deliver to the City's Director of Purchasing and Risk Management, P. O. Box 580 Fort Collins, Colorado 80522 one copy of a certificate evidencing the insurance coverage required from an insurance company acceptable to the City. d. The Service Provider's damages under this provision shall not exceed the Services Agreement 7381 Advanced Traveler Information System L. Transit Vehicles Installation at the Factory The City shall occasionally purchase new transit vehicles and will have the ATIS equipment installed at the factory. The Service Provider shall provide a complete package of equipment per vehicle to be installed at the factory by the factory installation teams. The Service Provider shall provide a complete set of documentation on installation of the ATIS equipment for the manufacturer to install on the vehicle. The cost for each ATIS equipment package for new vehicles is shown in Appendix B. The timing on the MAX BRT buses is a critical item and high priority for the City. The Service Provider shall provide the information required by the bus manufacturer within 30 days or sooner of the notice to proceed. The City shall occasionally purchase replacement transit vehicles and will want the equipment swapped out from the current vehicle to the new vehicle at the City facilities after receiving the replacement vehicles at the City facility. The cost for each ATIS equipment package and the removal and installation cost for replacement vehicles is shown in Appendix B. M. Automatic Vehicle Monitoring (AVM) Module (Optional) The City shall purchase the AVM module to be integrated into the fleet of transit vehicles at its discretion. Once the decision and funding is available the module shall be installed in each transit vehicle up to the fleet size as described in the table in Appendix B. Services Agreement 7381 Advanced Traveler Information System Appendix A Pilot Phase Acceptance Chart ATIS Section Acceptable es/no Date City Representative Computer Aided Design Automatic Vehicle Location Real-time Prediction Accuracy AVL Data Accuracy and System Reliability User Interface Configuration Schedule Adherence Route Adherence ATIS System Time Data Messaging Textual and Tabular Displays Map Display Emergency Alarm EA Historical Data (Playback Mode Vehicle Systems Intelligent Vehicle Network Transit Control Head Data Transfer with Manual Transfer Mobile Data Terminal Text Messaging Transfer Requests Automatic Passenger Counter APC Automatic Announcements AA In Vehicle Systems Transit Centers Platforms and Stops Passenger Information Systems Interactive Voice Response IVR Information Displays and Paging Systems Internet Information Web Site Mobile Device Applications and Web Site Mobile SMS/Email Information Displays and Paging Systems South Transit Center Downtown Transit Center Colorado State University Transit Center MAX Bus Rapid Transit Stops and Platforms Internet Information Web Site Services Agreement 7381 Advanced Traveler Information System Mobile Device Applications and Web Site Mobile SMS/Email Application Server Environment BusLink BusTime BusTime Web CleverCAD Clever Reports IVR Data Information and Ownership Data Analysis and Report Generation Technical Overview Data Communications Operating Environment Software and License Model Software Requirements Protocols, Anti -virus and Security Interface Re uirements Google Transit Feed Specification GTFS AVL Data Export Trapeze Software Interface Services Agreement 7381 Advanced Traveler Information System Fleet Deployment Chart # Unit Year Make -Model VIN Status Acceptable Date City Representative 1 29 1993 GILLIG 15GCB1214P1084887 Active PHANTOM 2 30 1993 GILLIG 15GCB1216P1084888 Active PHANTOM 3 31 1993 GILLIG 15GCB1218P1084889 Active PHANTOM 4 39 1997 GILLIG 15GCB2119V1087482 Active PHANTOM 5 40 1997 GILLIG 15GCB211OV1087483 Active PHANTOM 6 41 1997 GILLIG 15GCB2112V1087484 Active PHANTOM 7 42 1997 GILLIG 15GCB2114V1087485 Active PHANTOM 8 43 1997 GILLIG 15GCD2113V1087486 Active PHANTOM 9 45 1998 GILLIG 15GCB2112W1088958 Active PHANTOM 10 46 1998 GILLIG 15GCB2114W1088959 Active PHANTOM 11 47 1998 GILLIG 15GCB2110W1088960 Active PHANTOM 12 48 1998 GILLIG 15GCB2113W1089259 Active PHANTOM 13 49 2001 GILLIG LOW 15GGE181411090423 Active FLOOR 14 50 2001 GILLIG LOW 15GGE181611090424 Active FLOOR 15 51 2001 GILLIG LOW 15GGE181811090425 Active FLOOR 16 53 2001 GILLIG LOW 15GGE181111090427 Active FLOOR Services Agreement 7381 Advanced Traveler Information System Page 43 of 78 17 54 2001 GILLIG LOW 15GGE181311090428 Active FLOOR 18 55 2006 ELDORADO BUS 1 N9MNA8G36C08405 Active LOWFLOOR 6 19 60 2008 NABI 1 N90351048A140271 Active 35LFW3510.01 20 61 2008 NABI 35LFW3510.01 1 N90351068A140272 Active 21 62 2008 NABI 35LFW3510.01 1N90351088A140273 Active 22 63 2009 NABI 40' BUS 1 N94045009A140137 Active 23 64 2009 NABI 40' BUS 1 N94045289A140257 Active 24 65 2009 NABI40' BUS 1N940452X9A140258 Active 25 66 2009 NABI 40' BUS 1 N94045219A140259 Active 26 67 2009 NABI 40' BUS 1 N94045289A140260 Active 27 68 2009 NABI 40' BUS 1 N940452MA140261 Active 28 69 2009 NABI 40' BUS 1 N94045219A140262 Active 29 72 2009 INTERNATL 4DRASAAL49H042758 Active 3200 30 73 2011 NABI 40' BUS 1 N9404530BA140316 Active 31 74 2011 NABI 40' BUS 1 N9404532BA140317 Active 32 75 2011 NABI 40' BUS 1 N9404534BA140318 Active 33 76 2011 NABI 40' BUS 1N9404536BA140319 Active 34 77 1 2011 NABI 35' BUS 1N9351025BA140337 Active 35 78 2011 NABI 35' BUS 1N9351027BA140338 Active 79 2013 TBD TBD TBD Replacement Vehicles 80 2013 TBD TBD TBD Replacement Vehicles 81 2013 TBD TBD TBD Replacement Vehicles 82 2013 TBD TBD TBD Replacement Vehicles 83 2013 TBD TBD TBD Replacement Vehicles Services Agreement 7381 Advanced Traveler Information System Page 44 of 78 84 2013 TBD TBD TBD Replacement Vehicles 85 2013 TBD TBD TBD Replacement Vehicles 36 86 2014 NABI 60' ARTIC TBD on order Additional BRT ROUTE Vehicles 37 87 2014 NABI 60' ARTIC TBD on order Additional BRT ROUTE Vehicles 38 88 2014 NABI 60' ARTIC TBD on order Additional BRT ROUTE Vehicles 39 89 2014 NAB] 60' ARTIC TBD on order Additional BRT ROUTE Vehicles 40 90 2014 NAB[ 60' ARTIC TBD on order Additional BRT ROUTE Vehicles 41 91 2014 NABI 60' ARTIC TBD on order Additional BRT ROUTE Vehicles Fixed Route Coaches Total 41 1 2000 1998 CHEVROLET 0 BLAZER 2 2000 1998 CHEVROLET 1 BLAZER 3 2000 2008 DODGE GRAND 2 CARAVAN 4 2608 2000 FORD FLATBED F350 5 2630 1998 CHEVROLET ASTRO VAN 6 2682 1999 CHEVROLET VAN Supervisor Maintenance Vehicles Total 6 Total Number of Revenue Vehicles 41 Services Agreement 7381 Advanced Traveler Information System Page 45 of 78 System Acceptance Chart ATIS Section Acceptable es/no Date City Representative Computer Aided Design Vehicle Systems Automatic Announcements AA Passenger Information Systems Information Displays and Paging Systems Internet Information Web Site Application Server Environment Data Information and Ownership Technical Overview Interface Requirements Fleet Deployment Training 60 days error Free Discrepancies Services Agreement 7381 Advanced Traveler Information System Page 46 of 78 Appendix B Milestone and Payment Table 1 Contract Deliverables Requirements List Description Percent of Amount CDRL Payment Completion of Requirements 15 % $164,392.15 Review 104 Preliminary Design Review Package 5 % $54,797.38 105 Final Design Review Package 20 % $219,189.53 107 Mini Fleet Deployment 20 % $219,189.53 110 Fleet Deployment Complete 20 % $219,189.53 111 Systems Acceptance 10 % $109.594.77 112 Project Closeout Package 10 % $109,594.77 Total 100 % $1,095,947.65 Cost Summary Table 2(Cost detailed tables below) Description Table Number Costs Project Management Costs 7 $423,727.07 Site License (SW and Vehicle) 8 $324,016.22 Base items Escrow -Spare parts 9 $38,000.00 Text Messaging 10 $ 7,185.60 Vehicle Hardware Table 11 $247,336.80 BRT Platforms Table 12 $ 0 Transit Centers Table 13 $31,376.65 Training and Implementation Table 14 $24,305.31 Clever Devices Total Costs $1,095,947.65 Support Costs Year 2* Product Support 7 $33,140.00 In Vehicle Software Support 7 $12,177.00 In Vehicle Systems Support 11 $8,674.17 Transit Center Support 13 $3,581.25 Total $57,572.42 * Annual support costs of Clever Devices systems for each year after 1 year warranty. 3% annual escalation based on 2nd year of warranty cost. Services Agreement 7381 Advanced Traveler Information System Professional Services Table 3* Title Rate Project Manager $98.40 Systems Engineer $120.00 Applications Engineer $88.80 IT Deployment $105.38 Technician $67.20 Schedule Integration $121.63 Mobile App Developer $159.77 *Professional Services to be used for additional technical services based on a quote that is received from the Service Provider for specific tasks. This work to be completed in the future. New Transit Vehicle installation Package Table 4 Manufacturer of Vehicle Size System Package Cost Shipping Total Cost per Vehicle NABI or other 35 $5,830.00 $125.00 $5,955.00* 40 $5,830.00 $125.00 $5,955.00* 60 $7,301.01 $125.00 $7,426.01* Does not include Software, Installation or Project Labor costs Replacement Transit Vehicle Installation Package Table 5 Manufacturer of Vehicle Size System Package Cost Removal from and Reinstallation Cost Total Cost per Vehicle NABI or other 35 NIA $1,050.00** $1,050.00*** 40 NIA $1,050.00** $1,050.00*** 60 NIA $1,500.00** $1,500.00*** ** Labor rates are valid for 2013. After 2013 current labor rates will apply. ***Does not include Software or Project Labor Costs Automatic Vehicle Monitoring (AVM) Module (Optional) Table 6 AVM Module CITY of vehicles Cost Installation in BRT Vehicles 6 $14,515.54 Installation in Fleet 35 $84,673.99 Server Application - Additional Vehicles (additional) $850.00 per vehicle plus Data Dictionary Configuration labor**`* **** This cost does not include labor for AVM Data Dictionary Configuration. Services Agreement 7381 Advanced Traveler Information System Project Management and Product Support Costs Table 7 Labor Categories Cost License Costs Year 2 n Vehicle SW Support Costs Year Computer Aided Dispatch $214,479.12 $12,000.00 $4,182.00 Map Update (Larimer and Boulder County, Colorado) $36,051.67 $6,000.00 Goo le Transit Feed Specification $5,767.98 $3,000.00 $492.00 AVL Data Export $17,165.13 $1,200.00 $1,599.00 Trapeze Interface $28,839.90 $0 Automatic Announcements Vehicles $102,476.31 $0 $1,722.00 Automatic Announcements Transit Centers $11,911.83 $0 Automatic Announcements Platforms / Stops $11,911.83 $0 Passenger Information Displays IVR $15,177.20 $4,940.00 Information displays and paging systems $8,651.97 $6,000.00 Internet Information Web Site $12,759.74 $0 $4,182.00 Mobile Applications and Web Site $5,767.98 $0 Digital Si na a Interface $13,871.58 $0 OEM Vehicles $19,891.50 $0 Subtotal $512,945.64 $33,140.00 $12,177.00 Discount $89,218.57 Total` $423,727.07 $33,140.00 $12,177.00 'This total reflects the 15% management discount that was applied. ATIS Software License Table 8 Licenses Site License Vehicle License 6 OEM Vehicles IVR Totals Costs $231,975.00 $53,025.00 $9,090.00 $40,750.00 $334,840.00 Discount $34,796.25 $7,953.75 $1,363.50 $6,112.50 $50,226.00 Total Costs $197,178.75 $45,071.25 $7,726.50 $34,637.50 $284,614.00 Services Agreement 7381 Advanced Traveler Information System amount of the agreement and any subsequent additions to the agreement. 15. Entire Agreement. This Agreement, along with all Exhibits and other documents incorporated herein, shall constitute the entire Agreement of the parties. Covenants or representations not contained in this Agreement shall not be binding on the parties. 16. Law/Severability. The laws of the State of Colorado shall govern the construction interpretation, execution and enforcement of this Agreement. In the event any provision of this Agreement shall be held invalid or unenforceable by any court of competent jurisdiction, such holding shall not invalidate or render unenforceable any other provision of this Agreement. 17. Prohibition Against Employing Illegal Aliens. Pursuant to Section 8-17.5-101, C.R.S., et. seq., Service Provider represents and agrees that: a. As of the date of this Agreement: 1. Service Provider does not knowingly employ or contract with an illegal alien who will perform work under this Agreement; and 2. Service Provider will participate in either the e-Verify program created in Public Law 208, 104th Congress, as amended, and expanded in Public Law 156, 108th Congress, as amended, administered by the United States Department of Homeland Security (the "e-Verify Program") or the Department Program (the "Department Program"), an employment verification program established pursuant to Section 8-17.5-102(5)(c) C.R.S. in order to confirm the employment eligibility of all newly hired employees to perform work under this Agreement. b. Service Provider shall not knowingly employ or contract with an illegal alien to perform work under this Agreement or knowingly enter into a contract with a subcontractor that knowingly employs or contracts with an illegal alien to perform work under this Agreement. c. Service Provider is prohibited from using the e-Verify Program or Department Program procedures to undertake pre -employment screening of job applicants while this Agreement is being performed. Services Agreement 7381 Advanced Traveler Information System Base Items Escrow -Spare parts Table 9 Additional Base Items Quantity Costs Software Escrow 10 ears 1 $22,055.00 Spares 5% IVN's with AVA HW 35ft 2 $5,415.63 IVN's with AVA HW 60ft 1 $3,387.23 APC's-2 door config 2 $3,921.53 APC's-3 door config 1 $2,457.76 Wayside signs 1 $8,034.75 Cellular Modem w/GPS Antenna 1 $729.00 Total Additional Base Items $46,000.90 Discount -$8000.90 Grand Total Additional Base Items $38,000.00 Additional Optional Items Automatic Vehicle Monitoring (See Table 10 In Vehicle Systems/Engine Monitoring Option) 41 $107,269.28 On -Board Maps 42 $3,192.00 Monthly Text Messaging Plan from TextMark Table 10 Text Messaqin-q Plan # of months Cost per month Total Cost 45,000 Messages 12 months' $598.90 1 $7,185.60" 'After 1 year there will be an adjustment to any new rates. The cost will be based upon actual plan usage and billed monthly Services Agreement 7381 Advanced Traveler Information System In Vehicle Systems Table 11 Description 30,35, and 40 Buses 30,35, and 40 Buses Support 6 OEM Vehicles 6 OEM Vehicles Support Supervisors /Pool Vehicles VMS LED Signs Quantity 35 12 0 Costs $23,779.70 $8,152.99 Manufacturer Sunrise Systems Sunrise Systems Support Costs Year 2 $475.65 $163.08 Paging System Integration Quantity 35 6 Costs $9,917.95 $1,700.22 Manufacturer Clever Devices Clever Devices Support Costs Year 2 $198.45 $34.02 APC Devices Quantity 70 18 0 Costs $68,626.60 $14,746.58 Manufacturer Clever Devices Clever Devices Support Costs Year 2 $5,042.81 $546.93 On -board Computer Unit Quantity 35 6 6 Costs $107,646.70 $14,608.32 $4,374.00 Manufacturer Clever Devices Clever Devices Blue Tree Support Costs Modems Year 2 $1,410.50 $258.18 Mobile Data Terminal Quantity 35 6 1 Costs $23,243.15 $3,984.54 $859.38 Manufacturer Clever Devices Clever Devices Installation of Blue Tree Support Costs Modems in Year 2 $ 464.86 $79 69 the Pool Vehicles Headway Sign Integration No costs ro proposed No costs proposed No Headway Si ns Cost $ $ Manufacturer Services Agreement 7381 Advanced Traveler Information System Support Costs Year 2 $ $ GFI Genfare Cents -a -Bill Integration No fareboxes No fareboxes Cost $ 17,775.00 $ - Support Costs Year 2 $ $ Wheelchair ramp deployment No costs proposed No costs proposed NSA Cost $ Support Costs Year 2 $ $ Engine Monitoring (Option) NSA Cost $84,673.99 $14,515.54 Support Costs Year 2 $6,839.70 $1,172.52 Totals Section Vehicle Quantity 35 6 6 Total In Vehicle Hardware Costs $250,989.10 $43,192.65 $5,233.38 Total Year 2 Support Costs $7,592.27 $1,081.90 Discount -$43,655.48 -$7.512.66 -$910.26 Discount Total In Vehicle Costs $207,333.62 $7,592.27 $38,515.19 $1,081.90 $4,323.11 In Vehicle Hardware Costs $247,336.80 Vehicle Hardware Support Costs $8,674.17 Services Agreement 7381 Advanced Traveler Information System MAX BRT Platforms / Stops Table 12 Costs ID Station Variable Message Sign Costs for Paging for Number Display System CITY VMS System Paging Integration Zones Integrate on 1 South Transit Center Monument 1 N/A N/A Sign 2 South Transit Center Pull - Ins 11 11 3 Harmony Station - Northbound and 2 1 Southbound 4 Troutman Station - Northbound and 2 1 Southbound 5 Horsetooth Station - Northbound 2 1 and Southbound 6 Swallow Northbound Stop 1 1 7 Swallow Southbound Stop 1 1 8 Drake Station - Northbound and 2 1 Southbound 9 Bay Farm Northbound Stop 1 1 10 Bay Farm Southbound Stop 1 1 11 Prospect Station - Northbound and 2 1 Southbound 12 University Station - Northbound and 2 1 Southbound 13 Laurel Northbound Stop 1 1 14 Laurel Southbound Stop 1 1 15 Mulberry Northbound Stop 1 1 16 Mulberry Southbound Stop 1 1 17 Olive Northbound Stop 1 1 18 Olive Southbound Stop 1 1 19 Mountain Northbound Stop 1 1 20 Mountain Southbound Stop 1 1 21 Downtown Transit Center Stop 1 1 Subtotal 37 30 Total MAX BRT Costs 0.00 0.00 Services Agreement 7381 Advanced Traveler Information System Transit Centers Table 13 Transit Centers Integration into paging system Downtown Transit Center $12,912.35 CSU Transit Center $12,912.35 South Transit Center $12,912.35 Subtotal $38,737.04 Discount $5,616.87 Total $33,120.17 Support Costs Year 2 $3,581.25 Training and Implementation Table 14 Training 8Implementation Length, (Hours/ Days) of onsite training Remote Training Cost Bus in a Box(training materials $12,180.00 Dispatch Training 10 $2,352.10 System Administration Training 32 $7,526.72 Go Live'Training 2 days $3,130.20""' Refresher Training ( one year after o live) 18 $4,233.78 Training and Implementation Costs $29,422.80 Discount $4,280.39 Total Training and Implementation Costs $25.142.41 This cost is for 2 days of onsite support for "Go -Live" Session. Services Agreement 7381 Advanced Traveler Information System APPENDIX C Transit Vehicles Table Destination Networ Fare k Collection Unit YR-Make-Model VIN Status Engine Torn Ra Signs PA Seats Length Type Mfg/Model Ramp System 29 1993 GILLIG 214P1 Active Cummins VOITH3 G3- Lift-Lift- U LU 0- Luminator Mobile 36 35' J-1708 GFI PHANTOM 084887 084887 L10 3 speed speed Page Centsabill 51 12 30 1993 GILLIG 15GCB1216P1 Active Cummins VOITH G3- Lift-Lift- U LU 0- Luminator Mobile 36 35' J-1708 GFI PHANTOM 084888 L10 3 speed Page Centsabill 51-12 31 1993 GILLIG 218P1 Active Cummins G3- OITspeed Lift-Lift- U LU 0- Luminator Mobile 36 35' J-1706 GFI PHANTOM 084689 084889 L10 3 3 speed Page Centsabill 51 12 39 1997 GILLIG 15GC62119V1 Active Cummins Allison 5 Lift -Lift - U 0- Luminator Mobile 36 35' J-1708 GFI PHANTOM 087482 M11 Page Centsabill eed s eed 51-0-03 40 1997 GILLIG 10V1 Active Cummins Allison B400R-5 Lift-Lift- U LU 0- Luminator Mobile 36 35 ' J_1708 GFI PHANTOM 087483 087483 M71 Page Centsabill speed 51-03 41 1997 GILLIG 15GCB2112V1 Active Cummins Allison B400R-5 Lift -Lift - U LU 0- Luminator Mobile 36 35' J-1708 GFI PHANTOM 087484 M11 speed 51-03 Page Centsabill 42 1997 GILLIG 15GCB2114V1 Active Cummins Allison B400R-5 Lift-Lift- U LU 0- Luminator Mobile 36 35' J-1708 GFI PHANTOM 087485 M11 Page Centsabill speed 51-03 43 1997 GILLIG PHANTOM 15GCD2113 Active Cummins Allison B400R-5 Lift-Lift- U LU 0- Luminator Mobile 42 40' J 1708 GFI V1087481087486 M71 speed 51-03 Page Centsabill 45 1998 GILLIG PHANTOM 15GCB2112 Active Cummins Allison B400R-6 Lift-Lift- U LU 0- Luminator Mobile 36 35' J-1708 GFI W1088958 M11 speed 51-12 Page Centsabill 4 Cummins Allison Lift-Lift- Mobile GFI 46 1998 GILLIG PHANTOM W1088959068959 Active M11 B400R-6 U LU 0- Luminator Page 36 35' J-1708 Centsabill s eed 51-12 47 1996 GILLIG PHANTOM 15GCB2110 Active Cummins Allison Lift -Lift- Luminator Mobile 36 35' J-1708 GFI W1088960 M11 B400R-6 U LU 0- Pa a Centsabill Services Agreement 7381 Advanced Traveler Information System Page 55 of 78 speed 51-12 15GC Cummins Allison Lift -Lift - Mobile GFI 48 1998 GILLIG PHANTOM W70892 259 Active M71 6400R-6 U LU 0- Luminator Page 36 35' J-1708 Centsabill speed 51-12 Allison Ramp - 49 2001 GILLIG LOW 15GGE1814 Active Cummins 6300R-5 Lift-U Luminator Mobile 27 29 J-1708 GFI FLOOR 11090423 ISC speed LU-6-03- LED Page Centsabill 02 Allison Ramp- 50 2001 GILLIG LOW 15GGE7616 Active Cummins B300R-5 Lift-U Luminator Mobile 27 29 J-1708 GFI FLOOR 11090424 ISC LU-6-03- LED Page Centsabill speed 02 Allison Ramp- 51 2001 GILLIG LOW 15GGE1818 Active Cummins 6300R-5 Lift-U Luminator Mobile 27 29 J-1708 GFI FLOOR 11090425 ISC LU-6-03- LED Page Centsabill speed 02 Al n so Ramp- 53 2001 GILLIG LOW 15GGE1811 Active Cummins sLift-U B300R- Luminator Mobile 27 28 J-1708 GFI FLOOR 11090427 ISC LU-6-03- LED Page Centsabill speed 02 Allison Ramp- 54 2001 GILLIG LOW 15GGE1813 Active Cummins 5 Lift-U Luminator Mobile 27 29 J-1708 GFI FLOOR 11090428 ISC LU-6-03- LED Page Centsabill epee speed 02 55 2006 ELDORADO BUS 1N9MNA8G John Allison Ramp- Luminator Mobile GFI LOWFLOOR 36C084056 Active Deere B300R-5 Eldorad LED Page 32 28' J-1939 Centsabill speed o Cummins Allison Ramp- 60 2008 NABI 1N90351048 Active ISL-G 6 Lift-U Luminator REI 30 35' J-1939 GFI 35LFW3510.01 A140271 LU-6-03- LED Centsabill 280hp speed speed 02 Cummins Allison Ramp- 61 2008 NABI 1N90351068 Active ISL-G B400R-6 Lift-U Luminator REI 30 35' J-1939 GFI 35LFW3510.01 A140272 LU-6-03- LED Centsabill 280hp speed 02 Cummins Allison Ramp- 62 2008 NABI 1N90351088 Active ISL-G B400R-6 Lift-U Luminator REI 30 35' J-1939 GFI 35LFW3510.01 A740273 280hp speed LU-6-03- LED Centsabill 02 Cummins Allison Ramp- 63 2009 NABI40' BUS 1N94045009 Active ISL-G B400R-6 Lift-U Luminator REI 36 40' J-1939 GFI A140137 280hp speed LU-11- LED Centsabill 06-02 64 2009 NABI40' BUS 1N94045289 Active Cummins Allison Ramp- Luminator REI 36 40' J-1939 GFI Services Agreement 7381 Advanced Traveler Information System Page 56 of 78 A140257 ISL-G B40OR-6 Lift-U LED Centsabill 280hp speed LU-11- 06-02 Cummins Allison Ramp- 65 2009 NABI 40' BUS 1N940452X Active ISL-G B40OR-6 Lift-U Luminator REI 36 40' J-1939 GFI 9A140258 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 66 2009 NABI 40' BUS 1N94045219 Active ISL-G B40OR-6 Lift-U Luminator REI 36 40' J-1939 GFI A140259 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 67 2009 NABI 40' BUS 1N94045289 Active ISL-G 6 Lift-U Luminator REI 36 40' J-1939 GFI A140260 280hp speed speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 68 2009 NABI 40' BUS Active B400R-6 Lift-U Luminator REI 36 40' J-1939 GFI 9N940452X A140261 280h 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 69 2009 NA6140' BUS 1N94045219 Active ISL-G 8400R-6 Lift-U Luminator REI 36 40' J-1939 GFI A140262 280hp speed LU-11- LED Centsabill 06-02 4D IHC AlliRASAAson Lift' GFICentsabill 2009 INTERNATL 3200 ggHO42758 42758 Active Maxforce 6300-5 Braun Twin Vision 25 26' J-1939 DT-366 seed Vista Cummins Allison Ramp- 73 2011 NABI 40' BUS Active ISL-G B40OR-6 Lift-U Luminator REI REI 36 40' J-1939 GFI BA140316 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 74 2011 NABI 40' BUS 1N9404532 Active ISL-G 6 Lift-U Luminator REI 36 40' J-1939 GFI BA140317 280hp speed speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 75 2011 NABI 40' BUS 1N9404534 Active ISL-G B40OR-6 Lift-U Luminator REI 36 40' J-1939 GFI BA140318 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 76 2011 NAB[ 40' BUS 1N9404536 Active 6400R-6 Lift-U Luminator REI 36 40' J-1939 GFI BA140319 280h 280hp speed LU-11- LED Centsabill 06-02 77 2011 NABI 35' BUS 1N9351025 Active Cummins Allison Ramp- Luminator REI 30 35' J-1939 GFI Services Agreement 7381 Advanced Traveler Information System Page 57 of 78 BA140337 ISL-G B400R-6 Lift-U LED Centsabill 280hp speed LU-11- 06-02 Cummins Allison Ramp- 78 2011 NABI 35' BUS 1N9351027 Active ISL-G 6 Lift-U Luminator REI 30 35' J-1939 GFI BA140338 280hp speed speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 79 2013 NABI 35' BUS TBD TBD ISL-G B400R-6 Lift-U Luminator REI 30 35' J-1939 GFI 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 80 2013 NABI 35' BUS TBD TBD ISL-G 6 Lift-U Luminator REI 30 35' J-1939 GFI 280hp speed speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 81 2013 NABI 35' BUS TBD TBD ISL-G B400R-6 Luminator REI 30 30 35' J-1939 GFI 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 82 2013 NABI 35' BUS TBD TBD 6400R-6 Lift-U Luminator REI 30 35' J-1939 GFI 280hp 280h speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 83 2013 NABI 35' BUS TBD TBD ISL-G 6 Lift-U Luminator REI 30 35' J-1939 GFI 280hp speed speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 84 2013 NABI 35' BUS TBD TBD B400R-6 Lift-U Luminator REI 30 35' J-1939 GFI 280h 280hp speed LU-11- LED Centsabill 06-02 Cummins Allison Ramp- 85 2013 NABI 35' BUS TBD TBD 6400R 6 Lift-U Luminator REI 30 35' J-1939 GFI 280h 280hp speed LU-11- LED Centsabill 06-02 NABI 60' ARTIC on Cummins Allison Luminator 86 2014 BRT ROUTE TBD order ISL-G 6 TBD LED TBD 44 60' J-1939 TBD 330h speed NABI ARTIC on Cummins Allison Luminator 87 2014 BRT ROUTE O TBD order ISL-G BSOOR-6 TBD LED TBD 44 60' J-1939 TBD 330hp seed I 88 2014 NABI 60' ARTIC TBD on Cummins Allison TBD Luminator TBD 44 60' J-1939 TBD BRT ROUTE order ISL-G B500R-6 LED Services Agreement 7381 Advanced Traveler Information System Page 58 of 78 330hp speed NABI ARTIC on Cummins Allison Laminator 89 2014 BRT ROUTE TBD order ISL-G 8500R-6 TBD LED TBD 44 60' J-1939 TBD 330hp speed NABI 60' ARTIC on Cummins Allison Laminator 90 2014 BRT ROUTE TBD order ISL-G 6 TBD LED TBD 44 60' J-1939 TBD 330hp seed eed speed p NABI ARTIC °n Cummins Allison Laminator 91 2014 BRT ROUTE TBD order ISL-G B500R-6 TBD LED TBD 44 60' J-1939 TBD 330hp I speed I I Services Agreement 7381 Advanced Traveler Information System Page 59 of 78 d. If Service Provider obtains actual knowledge that a subcontractor performing work under this Agreement knowingly employs or contracts with an illegal alien, Service Provider shall: 1. Notify such subcontractor and the City within three days that Service Provider has actual knowledge that the subcontractor is employing or contracting with an illegal alien; and 2. Terminate the subcontract with the subcontractor if within three days of receiving the notice required pursuant to this section the subcontractor does not cease employing or contracting with the illegal alien; except that Service Provider shall not terminate the contract with the subcontractor if during such three days the subcontractor provides information to establish that the subcontractor has not knowingly employed or contracted with an illegal alien. e. Service Provider shall comply with any reasonable request by the Colorado Department of Labor and Employment (the "Department') made in the course of an investigation that the Department undertakes or is undertaking pursuant to the authority established in Subsection 8-17.5-102 (5), C.R.S. f. If Service Provider violates any provision of this Agreement pertaining to the duties imposed by Subsection 8-17.5-102, C.R.S. the City may terminate this Agreement. If this Agreement is so terminated, Service Provider shall be liable for actual and consequential damages to the City arising out of Service Provider's violation of Subsection 8-17.5-102, C.R.S. g. The City will notify the Office of the Secretary of State if Service Provider violates this provision of this Agreement and the City terminates the Agreement for such breach. 18. Special Provisions. Special provisions or conditions relating to the services to be performed pursuant to this Agreement are set forth in Exhibit "C", consisting of twelve (12) pages, attached hereto and incorporated herein by this reference. Services Agreement 7381 Advanced Traveler Information System Supervisor and Maintenance Vehicles Table Vehicle Number Radio Year Make and Model 20000 M0960 1998 CHEVROLET BLAZER 20001 M0960 1998 CHEVROLET BLAZER 20002 M0960 2008 DODGE GRAND CARAVAN 2608 M0960 2000 FORD FLATBED F350 2630 M0960 1998 CHEVROLET ASTRO VAN 2682 M0960 1999 CHEVROLET VAN Services Agreement 7381 Advanced Traveler Information System Page 60 of 78 Appendix D — Transit Centers City Maintenance Facility (TMF) 6570 Portner Road Downtown Transit Center (DTC) 250 North Mason Street Existing Displays • 40' LCD Samsung display internal • Dell Optiplex 620 computer running Windows XP Pro • Digital signage currently using Four Winds Interactive software Existing paging equipment • TOA 900 series II Amplifier A-912MK2 • Internal and external speakers on a 70 volt line • Volume controls and microphones • Dell Optiplex 280 computer running windows XP pro • Automatic announcements currently using BMS Business Music System Colorado State University Transit Center (CTC) North End of the Lory Student Center, lower level Existing Displays • 40" LCD Samsung display internal • 46" LCD Samsung display internal • (1) Dell Optiplex 620 computer - Windows XP Pro • (1) Medius Digital Engine -Windows Professional 7 • Digital signage currently using Four Winds Interactive software Existing paging equipment • TOA 900 series II Amplifier A-912MK2 • TOA Integrated Amplifier • Crown Integrated Amplifier • CSVX 9620 Amplifier • Internal and external speakers on a 70 volt line • Volume controls and microphones • Dell Optiplex 620 computer running windows XP pro • Automatic announcements currently using BMS Business Music System South Transit Center (STC) Fossil Blvd - Construction to start 2012 Services Agreement 7381 Advanced Traveler Information System Page 61 of 78 Appendix E Definitions Acceptance Testing: A formal process of proving to City that all Work, or a specified portion thereof, under Contract has been completed to the specification requirements and submitted to City for approval. Acceptance: Written documentation attesting to the act of an authorized representative of City, by which all Work or specified portion thereof, under the Contract has been identified as complete to the specification requirements. Alarm: An audible and/or visual indication of a faulty condition. Approved/Approval: Written approval by the Project Manager unless contract document specifically states otherwise. Assembly: A combination of subassemblies or components that form a subset of equipment. Audit: An examination of records or accounts to verify accuracy and status. Authentication: A technique to confirm the identity of a computer system. Baseline Design: The design of the Advanced Traveler Information System or any of its assemblies, components, devices, systems, subsystems, or materials that has received both drawing approval and First Article approval by City. All design modifications made past the establishment of the design baseline shall be considered design changes. Service Provider(s) Drawings: Items such as detail drawings, graphs, diagrams, and sketches which are prepared by the Service Provider to detail its work. Service Provider Quality Assurance/Quality Control: The quality assurance and control program established and maintained by the Service Provider that ensures compliance with the Contract requirements. Calculation: Numerical computations based on actual field conditions performed to demonstrate compliance with the Technical Specification. Contract Deliverables Requirements List (CDRL): List of all Contract Deliverables Certified Inspection Reports: Reports signed by the Service Provider inspector(s) attesting that items inspected meet the specification requirements other than any exceptions included in the report. The Service Provider shall also have inspection reports that are certified as true by the Service Provider Project Manager. Certified Test Reports: Reports of test signed by a qualified professional or the City employee attesting that tests were performed in accordance with the test method specified. The test results reported are accurate, and that items tested meet or fail to meet the stated minimum requirements. Comment: Written critiques of the Service Provider's submittals to the City. Services Agreement 7381 Advanced Traveler Information System Page 62 of 78 Commercially Available: All Service Provider supplied equipment, subsystems, assemblies and/or components that do not require any modifications to meet the functional and performance requirements of this Contract and that are available from more than two sources. Commercially Available Software: Any software or firmware product that is commercially available from software developers, distributors or retailers (i.e. Windows, Word, Excel). Component: A piece or part of an Assembly such as a mechanical part, electrical part, or support structure that is combined with other components to form an Assembly. Contracting Administrator: An official of the City authorized and empowered to execute contracts, modifications, and agreements on behalf of the City. Days Working: Those calendar days during which regular business is conducted, excluding Saturdays and Sundays and all Authority -observed federal, state, and municipal holidays. Design baseline: See Baseline Design Equal: Whenever the words "equal" or "approved equal" are used in connection with make or quality of material or equipment in these Contract Documents, the Contracting Officer's decision as to whether any material or equipment proposed is equal to that specified shall be binding and final on both the Service Provider and the City. Equipment: All equipment required to be furnished by the Service Provider under the Contract, including, but not limited to vehicle logic units, mobile display terminals, mobile radios, radio consoles, base stations, displays, display controllers, the management hardware and software, and all related and appurtenant items. Failure: The inability of a component, assembly or a piece of equipment to function as designed and/or specified. Failure Rate: The frequency of failure, expressed as failures per unit of time (in hours). First Article: The first one of any production component of the Advanced Traveler Information System equipment that is produced. The Technical Specification provides that production components not be manufactured prior to drawing approval, so the First Article shall have been made to approve drawings. First Article Testing: The process of testing under the supervision of the City or the City's representative an initial part, assembly, subassembly, subsystem, system or material, manufactured or assembled by either the Service Provider or sub Service Providers. The first article inspection shall be completed prior to the first article testing. Indicated: As used in the Technical Specification, "Indicated" shall be understood to mean "as shown in the Technical Specification Drawings," or "as described in the Technical Specification." Inspection: Examining, analyzing, or sampling products or workmanship, including appropriate raw materials, components, and subassemblies, to determine conformance to stated requirements. Services Agreement 7381 Advanced Traveler Information System Page 63 of 78 Installation Inspection and Testing: Inspection that takes place after all installation activities are complete. Installation test is the process of confirming that the equipment functions at the same level as prior to shipping. Maintainability: The ability of the Automatic Vehicle Location and Real-time Information Equipment to be maintained by maintenance staff, including equipment and components that require maintenance. Module and/or Modular: A standardized, interchangeable, self-contained unit(s), designed to facilitate maintenance, repair(s), and extensions. Off-line: Not connected to a telephone or other communications network. On-line: Connected to a telephone or other communications network Product Data: Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, instructions, warnings, and other information furnished by the Service Provider to illustrate or explain the fabrication, assembly, installation, maintenance, or operation of materials, equipment, or some portion of the work. Production baseline: The design and fabrication specifications of the Advanced Traveler Information System equipment or any of its components, subassemblies or materials of which the First Article Testing has been approved by the City. Any modifications made to production units after the production baseline has been established will be considered a design/construction change. Production Inspection and Testing: The Inspection activities that occur during the production process of the Advanced Traveler Information System equipment and testing activities that occur prior to shipment of the equipment to the City's work site. Project Specific Software: Any software or firmware product that contains any element of characteristic design feature or coding developed by the Service Provider or any one of its Subcontractors in whole or in part specifically for or use in conjunction with equipment delivered under this Contract. Proof (used as suffix): Apparatus is designated as dustproof, waterproof, etc., when so constructed, protected, or treated that its successful operation is not interfered with when subjected to the specified material or condition. Proprietary Software: Any software or firmware product developed and copyrighted by the Service Provider or any of its Subcontractors, but not commercially available, and which is used by the Service Provider in any way as part of the Service Provider's development effort or end product. Quality Assurance Audit: Audit performed by the City or its representative to ensure the elements of the Service Provider's Quality Assurance plan are being followed. Quality Control Inspection and Tests: Inspections and tests performed for the purpose of monitoring the quality of products and performance of the Service Provider. Services Agreement 7381 Advanced Traveler Information System Page 64 of 78 Reliability: The probability of performing a specified function without failure and within design parameters for the period of time under actual service conditions. Service Proven: Identical or near identical equipment which has demonstrated successful operation in a transit industry environment similar to that anticipated for the City. Shop Drawings: Drawings or sketches prepared by the Service Provider for use in its manufacturing facility, assembly facility, or shop to fabricate, assemble, and/or install parts of the Advanced Traveler Information System equipment, whether manufactured from raw materials or purchased from others in a ready -to -use condition. Specialized shop -level test equipment: Diagnostic and test equipment furnished by the Service Provider for the purpose of testing, troubleshooting, and calibrating electrical, mechanical, and electromechanical components of Advanced Traveler Information System in a shop environment. Such equipment is not intended for use in the field. State: The State of Colorado Subassembly/Subsystem: Two or more components combined into a unit for convenience in assembling or servicing equipment. A subsystem comprises functional elements interconnected within a system to perform a specific function, such as a display, display controller, or control system. System: When used alone, all Advanced Traveler Information System equipment, data processing system, and computer equipment to be procured under this Contract. Tamperproof: Items are designated as tamperproof when they cannot be easily loosened, opened, or penetrated by hand or with commonly available tools such as a flat blade or Phillips screwdriver or pliers. Tight (used as suffix): Apparatus or enclosures are designated as watertight, dust -tight, etc., when so constructed that the enclosing case will exclude the specified material and is manufactured and rated according to an industry standard such as NEMA. Time-out: When a prescribed amount of time has elapsed during which a specified action has not occurred. Upgrades: Performance improvements or enhancements to hardware, software, or firmware. Upgrades include both hardware and software, as long as fit, form, and function can be complied with. Upgrades that require design changes necessitate a change order. Work Site: The area identified as the City Right of Way necessary for the installation of the equipment being provided under the contract. Services Agreement 7381 Advanced Traveler Information System Page 65 of 78 EXHIBIT "B" INSURANCE REQUIREMENTS 1. The Service Provider will provide, from insurance companies acceptable to the City, the insurance coverage designated hereinafter and pay all costs. Before commencing work under this bid, the Service Provider shall furnish the City with certificates of insurance showing the type, amount, class of operations covered, effective dates and date of expiration of policies, and containing substantially the following statement: "The insurance evidenced by this Certificate will not be cancelled or materially altered, except after ten (10) days written notice has been received by the City of Fort Collins." In case of the breach of any provision of the Insurance Requirements, the City, at its option, may take out and maintain, at the expense of the Service Provider, such insurance as the City may deem proper and may deduct the cost of such insurance from any monies which may be due or become due the Service Provider under this Agreement. The City, its officers, agents and employees shall be named as additional insureds on the Service Provider's general liability and automobile liability insurance policies for any claims arising out of work performed under this Agreement. 2. Insurance coverages shall be as follows: A. Workers' Compensation & Employer's Liability. The Service Provider shall maintain during the life of this Agreement for all of the Service Provider's employees engaged in work performed under this agreement: Workers' Compensation insurance with statutory limits as required by Colorado law. 2. Employer's Liability insurance with limits of $100,000 per accident, $500,000 disease aggregate, and $100,000 disease each employee. B. Commercial General & Vehicle Liability. The Service Provider shall maintain during the life of this Agreement such commercial general liability and automobile liability insurance as will provide coverage for damage claims of personal injury, including accidental death, as well as for claims for property damage, which may arise directly or indirectly from the performance of work under this Agreement. Coverage for property damage shall be on a "broad form" basis. The amount of insurance for each coverage, Commercial General and Vehicle, shall not be less than $500,000 combined single limits for bodily injury and property damage. In the event any work is performed by a subcontractor, the Service Provider shall be responsible for any liability directly or indirectly arising out of the work performed under this Agreement by a subcontractor, which liability is not covered by the subcontractor's insurance. Services Agreement 7381 Advanced Traveler Information System Page 66 of 78 CLEVE-1 OP ID: AH a` o�Ro CERTIFICATE OF LIABILITY INSURANCE 10/04112 YV) DAT/04/12 THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CERTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURER(S), AUTHORIZED REPRESENTATIVE OR PRODUCER, AND THE CERTIFICATE HOLDER. IMPORTANT: If the certificate holder is an ADDITIONAL INSURED, the policy(ies) must be endorsed. If SUBROGATION IS WAIVED, subject to the terms and conditions of the policy, certain policies may require an endorsement A statement on this certificate does not confer rights to the certificate holder in lieu of such endorsements . PRODUCER Phone: 516465-0200 NAMEACT Selma Miller INSIGHT COMPANIES INC. Fax: 516-065-0201 125 East Bethpage Road Plainview, NY 11g03 John R. Keane PHG� 516-065-0200 nlc No: 516-065-0201 AIC No Est: E-MAIL :smiller@insightins.com -ADDRESS INSURER(S) AFFORDING COVERAGE NAICIF INSURER a: Netherlands Insurance Co. 24171 INSURED Clever Devices, Ltd. INSURER B: Peerless Insurance Company 24198 ' 300 Crossways Park Drive Woodbury, NY 11797 INSURER C: Valley Forge Insurance Co. 20508 INSURER : Excelsior Insurance Com pang 11045 INSURER E INSURER F COVERAGES CERTIFICATE NUMBER: REVISION NUMBER: D THIS IS TO CERTIFY THAT THE POLICIES OF INSURANCE LISTED BELOW HAVE BEEN ISSUED TO THE INSURED NAMED ABOVE FOR THI INDICATED. NOTWITHSTANDING ANY REQUIREMENT, TERM OR CONDITION OF ANY CONTRACT OR OTHER DOCUMENT WITH RESPECS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLICIES DESCRIBED HEREIN IS SUBJECT TO, EXCLUSIONS AND CONDITIONS OF SUCH POLICIES. LIMITS SHOWN MAY HAVE BEEN REDUCED BY PAID CLAIMS. INSR TR TYPE OF INSURANCE OOL SUB POLICY NUMBER POLICY EFF MMMDIYYYV POLICY EXP MMMDNYYY LIMIT GENERAL LIABILITY EACH OCCURRENCE 000 PREMISES Ee..urronce ,000 A X COMMERCIAL GENERAL LIABILITY X CBP8524008 10/07/12 10107113 CLAIMS MADE a OCCUR MED DIP (Any one person) ,000 PERSONAL B ADV IN JURY $ ,,000 X PERPROJECT/LOCH GENERAL AGGREGATE $ 2,000,00 GENT AGGREGATE LIMIT APRL IES PER PRODUCTS - COMP/OP AGG $ 2,000,00 POLICY PR0 LDC Emp Ben. $ 1,000,00 AUTOMOBILE LIABILITY COMBINED(Ea S INGLE LIMIT $ 1,000,00 BODILY INJURY (Per person) if B X ANY AUTO BA8524708 10107/12 10/07/13 ALL OWNED SCHEDULED AUTOS AUTOS BODILY IN.4IRY (Per ecadenD $ accident PAAP. $ HPREDAUTOS AUTOS X UMBRELLAPer UMBRELLA LIAR X OCCUR EACH OCCURRENCE $ 10,000,000 AGGREGATE $ 10,000,000 D EXCESSLIAB CLAIMS -MADE CU8524808 10/07/12 10/07/13 DIED I X I RETENTION$ 10,000 $ WORKERS COMPENSATION WC STAT U- OTH- C A!ID EMPLOYERS' LIABILITY Y ANY PROPRIETORIPARTNEREXECUTIVE C414285746 10/07/12 10/07/13 EL EACH ACCIDENT $ 500,00 ❑N OFFICERIMEMBER EXCLUDED? (Mandatary In NH) N/A E. L. DISEASE - EAEMPLOYEE $ 500,00 If yes desaibo under DESCRIPTION OF OPERATIONS Uelm E. L. DISEASE -POLICY LIMIT If 500,000 DESCRIPTION OF OPERATIONS I LOCATIONS I VEHCLES (Attach ACORD 101, ALdiGonal Remarks Schedule, If more space Is requimIII The certificate holder is included as an additional insured. CERTIFICATE HOLDER CANCELLATION COFFORT SHOULD ANY OF THE ABOVE DESCRIBED POLICIES BE CANCELLED BEFORE City of Fort Collins THE EXPIRATION DATE THEREOF, NOTICE WILL BE DELIVERED IN ACCORDANCE WITH THE POLICY PROVISIONS. 215 North Mason Street Fort Collins, CO 80521 AUTHORIZED REPRESENTATIVE f4.,— ©1988-2010 ACORD CORPORATION. All rights reserved. ACORD 25 (2010105) The ACORD name and logo are registered marks of ACORD No Text EXHIBIT C FEDERAL CONTRACT REQUIREMENTS FEDERAL TRANSIT ADMINISTRATION Federally Required and Other Model Contract Clauses 1. NO GOVERNMENT OBLIGATION TO THIRD PARTIES No Obligation by the Federal Government. (1) The Purchaser and Contractor acknowledge and agree that, notwithstanding any concurrence by the Federal Government in or approval of the solicitation or award of the underlying contract, absent the express written consent by the Federal Government, the Federal Government is not a party to this contract and shall not be subject to any obligations or liabilities to the Purchaser, Contractor, or any other party (whether or not a party to that contract) pertaining to any matter resulting from the underlying contract. (2) The Contractor agrees to include the above clause in each subcontract financed in whole or in part with Federal assistance provided by FTA. It is further agreed that the clause shall not be modified, except to identify the subcontractor who will be subject to its provisions. 2. PROGRAM FRAUD AND FALSE OR FRAUDULENT STATEMENTS AND RELATED ACTS Program Fraud and False or Fraudulent Statements or Related Acts. (1) The Contractor acknowledges that the provisions of the Program Fraud Civil Remedies Act of 1986, as amended, 31 U.S.C. § 3801 et seq. and U.S. DOT regulations, "Program Fraud Civil Remedies," 49 C.F.R. Part 31, apply to its actions pertaining to this Project. Upon execution of the underlying contract, the Contractor certifies or affirms the truthfulness and accuracy of any statement it has made, it makes, it may make, or causes to be made, pertaining to the underlying contract or the FTA assisted project for which this contract work is being performed. In addition to other penalties that may be applicable, the Contractor further acknowledges that if it makes, or causes to be made, a false, fictitious, or fraudulent claim, statement, submission, or certification, the Federal Government reserves the right to impose the penalties of the Program Fraud Civil Remedies Act of 1986 on the Contractor to the extent the Federal Government deems appropriate. (2) The Contractor also acknowledges that if it makes, or causes to be made, a false, fictitious, or fraudulent claim, statement, submission, or certification to the Federal Government under a contract connected with a project that is financed in whole or in part with Federal assistance originally awarded by FTA under the authority of 49 U.S.C. § 5307, the Government reserves the right to impose the penalties of 18 U.S.C. § 1001 and 49 U.S.C. § 5307(n)(1) on the Contractor, to the extent the Federal Government deems appropriate. (3) The Contractor agrees to include the above two clauses in each subcontract financed in whole or in part with Federal assistance provided by FTA. It is further agreed that the clauses shall not be modified, except to identify the subcontractor who will be subject to the provisions. Services Agreement 7381 Advanced Traveler Information System Page 67 of 78 ATTES�&',),e'. CORPOR SECRETARY CITY OF FORT COLLINS, COLORADO a municipal corporation By: of Darin Atteberry, City Manager By: James P. O Neill II, CPPO, FNIGP Directo f urchasing and Risk Management Date: ( ( I `a IT� PRINT NAME CORPORATE PRESIDENT OR VICE PRESIDENT Date: 10 /i—.1 /i,4— (C rpora a Seal) Services Agreement 7381 Advanced Traveler Information System 3. ACCESS TO RECORDS AND REPORTS Access to Records - The following access to records requirements apply to this Contract: A. Where the Purchaser is not a State but a local government and is the FTA Recipient or a subgrantee of the FTA Recipient in accordance with 49 C.F.R. 18.36(i), the Contractor agrees to provide the Purchaser, the FTA Administrator, the Comptroller General of the United States or any of their authorized representatives access to any books, documents, papers and records of the Contractor which are directly pertinent to this contract for the purposes of making audits, examinations, excerpts and transcriptions. Contractor also agrees, pursuant to 49 C.F.R. 633.17 to provide the FTA Administrator or his authorized representatives including any PMO Contractor access to Contractor's records and construction sites pertaining to a major capital project, defined at 49 U.S.C. 5302(a)1, which is receiving federal financial assistance through the programs described at 49 U.S.C. 5307, 5309 or 5311. B. The Contractor agrees to permit any of the foregoing parties to reproduce by any means whatsoever or to copy excerpts and transcriptions as reasonably needed. C. The Contractor agrees to maintain all books, records, accounts and reports required under this contract for a period of not less than three years after the date of termination or expiration of this contract, except in the event of litigation or settlement of claims arising from the performance of this contract, in which case Contractor agrees to maintain same until the Purchaser, the FTA Administrator, the Comptroller General, or any of their duly authorized representatives, have disposed of all such litigation, appeals, claims or exceptions related thereto. Reference 49 CFR 18.39(i)(11). D. FTA does not require the inclusion of these requirements in subcontracts. Requirements for Access to Records and Reports by Types of Contract Contract Characteristics Operational Service Contract Turnkey Construction Architectural Engineering Acquisition of Rolling Stock Professional Services I State Grantees None Those None None None None a. Contracts below SAT imposed on ($100,000) state pass None thru to Yes, if non- None unless None unless None unless non- b. Contracts above unless' Contractor competitive non- non- competitive $100,000/Capital non- award or if competitive competitive award Projects competitive funded thru2 award award award 5307/5309/531 1 II Non State Grantees Those a. Contracts below SAT Yes' imposed on Yes Yes Yes Yes ($100,000) non -state b. Contracts above Yes' Grantee pass Yes Yes Yes Yes $100,000/Capital thru to Projects Contractor Services Agreement 7381 Advanced Traveler Information System Page 68 of 78 Sources of Authority: ' 49 USC 5325 (a) 2 49 CFR 633.17 318 CFR 18.36 (i) 4. FEDERAL CHANGES Federal Changes - Contractor shall at all times comply with all applicable FTA regulations, policies, procedures and directives, including without limitation those listed directly or by reference in the Master Agreement between Purchaser and FTA, as they may be amended or promulgated from time to time during the term of this contract. Contractor's failure to so comply shall constitute a material breach of this contract. 5. TERMINATION a. Termination for Convenience (General Provision) The City may terminate this contract, in whole or in part, at any time by written notice to the Contractor when it is in the Government's best interest. The Contractor shall be paid its costs, including contract close-out costs, and profit on work performed up to the time of termination. The Contractor shall promptly submit its termination claim to the City to be paid the Contractor. If the Contractor has any property in its possession belonging to the City, the Contractor will account for the same, and dispose of it in the manner the City directs. b. Termination for Default [Breach or Cause] (General Provision) If the Contractor does not deliver supplies in accordance with the contract delivery schedule, or, if the contract is for services, the Contractor fails to perform in the manner called for in the contract, or if the Contractor fails to comply with any other provisions of the contract, the City may terminate this contract for default. Termination shall be effected by serving a notice of termination on the contractor setting forth the manner in which the Contractor is in default. The contractor will only be paid the contract price for supplies delivered and accepted, or services performed in accordance with the manner of performance set forth in the contract. If it is later determined by the City that the Contractor had an excusable reason for not performing, such as a strike, fire, or flood, events which are not the fault of or are beyond the control of the Contractor, the City, after setting up a new delivery of performance schedule, may allow the Contractor to continue work, or treat the termination as a termination for convenience. c. Opportunity to Cure (General Provision) The City in its sole discretion may, in the case of a termination for breach or default, allow the Contractor [an appropriately short period of time] in which to cure the defect. In such case, the notice of termination will state the time period in which cure is permitted and other appropriate conditions If Contractor fails to remedy to the City's satisfaction the breach or default of any of the terms, covenants, or conditions of this Contract within [ten (10) days] after receipt by Contractor of written notice from the City setting forth the nature of said breach or default, the City shall have the right to terminate the Contract without any further obligation to Contractor. Any such termination for default shall not in any way operate to preclude the City from also pursuing all available remedies against Contractor and its sureties for said breach or default. d. Waiver of Remedies for any Breach In the event that the City elects to waive its remedies for any breach by Contractor of any covenant, term or condition of this Contract, such waiver by the City shall not limit the City's remedies for any succeeding breach of that or of any other term, covenant, or condition of this Contract. Services Agreement 7381 Advanced Traveler Information System Page 69 of 78 6. CIVIL RIGHTS REQUIREMENTS Civil Rights - The following requirements apply to the underlying contract: (1) Nondiscrimination - In accordance with Title VI of the Civil Rights Act, as amended, 42 U.S.C. § 2000d, section 303 of the Age Discrimination Act of 1975, as amended, 42 U.S.C. 6102, section 202 of the Americans with Disabilities Act of 1990, 42 U.S.C. § 12132, and Federal transit law at 49 U.S.C. § 5332, the Contractor agrees that it will not discriminate against any employee or applicant for employment because of race, color, creed, national origin, sex, age, or disability. In addition, the Contractor agrees to comply with applicable Federal implementing regulations and other implementing requirements FTA may issue. (2) Equal Employment Opportunity - The following equal employment opportunity requirements apply to the underlying contract: (a) Race. Color, Creed, National Origin, Sex - In accordance with Title VII of the Civil Rights Act, as amended, 42 U.S.C. § 2000e, and Federal transit laws at 49 U.S.C. § 5332, the Contractor agrees to comply with all applicable equal employment opportunity requirements of U.S. Department of Labor (U.S. DOL) regulations, "Office of Federal Contract Compliance Programs, Equal Employment Opportunity, Department of Labor," 41 C.F.R. Parts 60 et sec., (which implement Executive Order No. 11246, "Equal Employment Opportunity," as amended by Executive Order No. 11375, "Amending Executive Order 11246 Relating to Equal Employment Opportunity," 42 U.S.C. § 2000e note), and with any applicable Federal statutes, executive orders, regulations, and Federal policies that may in the future affect construction activities undertaken in the course of the Project. The Contractor agrees to take affirmative action to ensure that applicants are employed, and that employees are treated during employment, without regard to their race, color, creed, national origin, sex, or age. Such action shall include, but not be limited to, the following: employment, upgrading, demotion or transfer, recruitment or recruitment advertising, layoff or termination; rates of pay or other forms of compensation; and selection for training, including apprenticeship. In addition, the Contractor agrees to comply with any implementing requirements FTA may issue. (b) Acme - In accordance with section 4 of the Age Discrimination in Employment Act of 1967, as amended, 29 U.S.C. § § 623 and Federal transit law at 49 U.S.C. § 5332, the Contractor agrees to refrain from discrimination against present and prospective employees for reason of age. In addition, the Contractor agrees to comply with any implementing requirements FTA may issue. (c) Disabilities - In accordance with section 102 of the Americans with Disabilities Act, as amended, 42 U.S.C. § 12112, the Contractor agrees that it will comply with the requirements of U.S. Equal Employment Opportunity Commission, "Regulations to Implement the Equal Employment Provisions of the Americans with Disabilities Act," 29 C.F.R. Part 1630, pertaining to employment of persons with disabilities. In addition, the Contractor agrees to comply with any implementing requirements FTA may issue. (3) The Contractor also agrees to include these requirements in each subcontract financed in whole or in part with Federal assistance provided by FTA, modified only if necessary to identify the affected parties. Services Agreement 7381 Advanced Traveler Information System Page 70 of 78 7. DISADVANTAGED BUSINESS ENTERPRISE (DBE) a. This contract is subject to the requirements of Title 49, Code of Federal Regulations, Part 26, Participation by Disadvantaged Business Enterprises in Department of Transportation Financial Assistance Programs. The national goal for participation of Disadvantaged Business Enterprises (DBE) is 10%. The City has an overall DBE goal of 9.9%. There is no specific contract goal for this project but the City encourages bids from DBE firms in this project. b. The contractor shall not discriminate on the basis of race, color, national origin, or sex in the performance of this contract. The contractor shall carry out applicable requirements of 49 CFR Part 26 in the award and administration of this DOT -assisted contract. Failure by the contractor to carry out these requirements is a material breach of this contract, which may result in the termination of this contract or such other remedy as City of Fort Collins deems appropriate. Each subcontract the contractor signs with a subcontractor must include the assurance in this paragraph (see 49 CFR 26.13(b)). The successful bidder/offeror will be required to report its DBE participation obtained through race -neutral means throughout the period of performance. d. The contractor is required to pay its subcontractors performing work related to this contract for satisfactory performance of that work no later than 30 days after the contractor's receipt of payment for that work from the City of Fort Collins. In addition, it is required to return any retainage payments to those subcontractors within 30 days after incremental acceptance of the subcontractor's work by the City of Fort Collins and contractor's receipt of the partial retainage payment related to the subcontractor's work. e. The contractor must promptly notify City of Fort Collins whenever a DBE subcontractor performing work related to this contract is terminated or fails to complete its work, and must make good faith efforts to engage another DBE subcontractor to perform at least the same amount of work. The contractor may not terminate any DBE subcontractor and perform that work through its own forces or those of an affiliate without prior written consent of City of Fort Collins. 8. INCORPORATION OF FEDERAL TRANSIT ADMINISTRATION (FTA) TERMS Incorporation of Federal Transit Administration (FTA) Terms - The preceding provisions include, in part, certain Standard Terms and Conditions required by DOT, whether or not expressly set forth in the preceding contract provisions. All contractual provisions required by DOT, as set forth in FTA Circular 4220.1 E, are hereby incorporated by reference. Anything to the contrary herein notwithstanding, all FTA mandated terms shall be deemed to control in the event of a conflict with other provisions contained in this Agreement. The Contractor shall not perform any act, fail to perform any act, or refuse to comply with any (name of grantee) requests which would cause (name of grantee) to be in violation of the FTA terms and conditions. 9. GOVERNMENT -WIDE DEBARMENT AND SUSPENSION (NON PROCUREMENT) Background and Applicability Services Agreement 7381 Advanced Traveler Information System Page 71 of 78 In conjunction with the Office of Management and Budget and other affected Federal agencies, DOT published an update to 49 CFR Part 29 on November 26, 2003. This government -wide regulation implements Executive Order 12549, Debarment and Suspension, Executive Order 12689, Debarment and Suspension, and 31 U.S.C. 6101 note (Section 2455, Public Law 103- 355, 108 Stat. 3327). The provisions of Part 29 apply to all grantee contracts and subcontracts at any level expected to equal or exceed $25,000 as well as any contract or subcontract (at any level) for Federally required auditing services. 49 CFR 29.220(b). This represents a change from prior practice in that the dollar threshold for application of these rules has been lowered from $100,000 to $25,000. These are contracts and subcontracts referred to in the regulation as "covered transactions." Grantees, contractors, and subcontractors (at any level) that enter into covered transactions are required to verify that the entity (as well as its principals and affiliates) they propose to contract or subcontract with is not excluded or disqualified. They do this by (a) Checking the Excluded Parties List System, (b) Collecting a certification from that person, or (c) Adding a clause or condition to the contract or subcontract. This represents a change from prior practice in that certification is still acceptable but is no longer required. 49 CFR 29.300. Grantees, contractors, and subcontractors who enter into covered transactions also must require the entities they contract with to comply with 49 CFR 29, subpart C and include this requirement in their own subsequent covered transactions (i.e., the requirement flows down to subcontracts at all levels). Clause Language The following clause language is suggested, not mandatory. It incorporates the optional method of verifying that contractors are not excluded or disqualified by certification. Suspension and Debarment This contract is a covered transaction for purposes of 49 CFR Part 29. As such, the contractor is required to verify that none of the contractor, its principals, as defined at 49 CFR 29.995, or affiliates, as defined at 49 CFR 29.905, are excluded or disqualified as defined at 49 CFR 29.940 and 29.945. The contractor is required to comply with 49 CFR 29, Subpart C and must include the requirement to comply with 49 CFR 29, Subpart C in any lower tier covered transaction it enters into. By signing and submitting its bid or proposal, the bidder or proposer certifies as follows: The certification in this clause is a material representation of fact relied upon by (insert agency name). If it is later determined that the bidder or proposer knowingly rendered an erroneous certification, in addition to remedies available to (insert agency name}, the Federal Government may pursue available remedies, including but not limited to suspension and/or debarment. The bidder or proposer agrees to comply with the requirements of 49 CFR 29, Subpart C while this offer is valid and throughout the period of any contract that may arise from this offer. The bidder or proposer further agrees to include a provision requiring such compliance in its lower tier covered transactions. Services Agreement 7381 Advanced Traveler Information System Page 72 of 78 10. BUY AMERICA The contractor agrees to comply with 49 U.S.C. 53230) and 49 C.F.R. Part 661, which provide that Federal funds may not be obligated unless steel, iron, and manufactured products used in FTA-funded projects are produced in the United States, unless a waiver has been granted by FTA or the product is subject to a general waiver. General waivers are listed in 49 C.F.R. 661.7, and include final assembly in the United States for 15 passenger vans and 15 passenger wagons produced by Chrysler Corporation, and microcomputer equipment and software. Separate requirements for rolling stock are set out at 49 U.S.C. 53230)(2)(C) and 49 C.F.R. 661.11. Rolling stock must be assembled in the United States and have a 60 percent domestic content. A bidder or offeror must submit to the FTA recipient the appropriate Buy America certification (below) with all bids or offers on FTA-funded contracts, except those subject to a general waiver. Bids or offers that are not accompanied by a completed Buy America certification must be rejected as nonresponsive. This requirement does not apply to lower tier subcontractors. Certification requirement for procurement of steel, iron, or manufactured products Certificate of Compliance with 49 U.S.C. 53236)(1) The bidder or offeror hereby certifies that it will meet the requirements of 49 U.S.C. 5323(j)(1) and the applicable regulations in 49 C.F.R. Part 661.5. Date Signatu Company Name L Title L.[i. a, Certificate of Non -Compliance with 49 U.S.C. 53236)(1) The bidder or offeror hereby certifies that it cannot comply with the requirements of 49 U.S.C. 53230)(1) and 49 C.F.R. 661.5, but it may qualify for an exception pursuant to 49 U.S.C. 53230)(2)(A), 5323(j)(2)(B), or 5323(j)(2)(D), and 49 C.F.R. 661.7. Date Signature Company Name Title Certification requirement for procurement of buses, other rolling stock and associated equipment Certificate of Compliance with 49 U.S.C. 53236)(2)(C). The bidder or offeror hereby certifies that it will comply with the requirements of 49 U.S.C. 5323(j)(2)(C) and the regulations at 49 C.F.R. Part 661.11. Date Signature Services Agreement 7381 Advanced Traveler Information System Page 73 of 78 Company Name Title Certificate of Non -Compliance with 49 U.S.C. 53236)(2)(C) The bidder or offeror hereby certifies that it cannot comply with the requirements of 49 U.S.C. 5323(j)(2)(C) and 49 C.F.R. 661.11, but may qualify for an exception pursuant to 49 U.S.C. 5323(j)(2)(A), 5323(j)(2)(B), or 53230)(2)(D), and 49 CFR 661.7. Date Signature Company Name Title 11. BREACHES AND DISPUTE RESOLUTION Disputes - Disputes arising in the performance of this Contract which are not resolved by agreement of the parties shall be decided in writing by the authorized representative of City's [title of employee]. This decision shall be final and conclusive unless within [ten (10)] days from the date of receipt of its copy, the Contractor mails or otherwise furnishes a written appeal to the [title of employee]. In connection with any such appeal, the Contractor shall be afforded an opportunity to be heard and to offer evidence in support of its position. The decision of the [title of employee] shall be binding upon the Contractor and the Contractor shall abide be the decision. Performance During Dispute - Unless otherwise directed by City, Contractor shall continue performance under this Contract while matters in dispute are being resolved. Claims for Damages - Should either party to the Contract suffer injury or damage to person or property because of any act or omission of the party or of any of his employees, agents or others for whose acts he is legally liable, a claim for damages therefor shall be made in writing to such other party within a reasonable time after the first observance of such injury of damage. Remedies - Unless this contract provides otherwise, all claims, counterclaims, disputes and other matters in question between the City and the Contractor arising out of or relating to this agreement or its breach will be decided by arbitration if the parties mutually agree, or in a court of competent jurisdiction within the State in which the City is located. Rights and Remedies - The duties and obligations imposed by the Contract Documents and the rights and remedies available thereunder shall be in addition to and not a limitation of any duties, obligations, rights and remedies otherwise imposed or available by law. No action or failure to act by the City, (Architect) or Contractor shall constitute a waiver of any right or duty afforded any of them under the Contract, nor shall any such action or failure to act constitute an approval of or acquiescence in any breach thereunder, except as may be specifically agreed in writing. Services Agreement 7381 Advanced Traveler Information System Page 74 of 78 12. LOBBYING Modifications have been made to the Clause pursuant to Section 10 of the Lobbying Disclosure Act of 1995, P.L. 104-65 [to be codified at 2 U.S.C. § 1601, et seq.] - Lobbying Certification and Disclosure of Lobbying Activities for third party contractors are mandated by 31 U.S.C. 1352(b)(5), as amended by Section 10 of the Lobbying Disclosure Act of 1995, and DOT implementing regulation, "New Restrictions on Lobbying," at 49 CFR § 20.110(d) - Language in Lobbying Certification is mandated by 49 CFR Part 19, Appendix A, Section 7, which provides that contractors file the certification required by 49 CFR Part 20, Appendix A. Modifications have been made to the Lobbying Certification pursuant to Section 10 of the Lobbying Disclosure Act of 1995. - Use of "Disclosure of Lobbying Activities," Standard Form-LLL set forth in Appendix B of 49 CFR Part 20, as amended by "Government wide Guidance For New Restrictions on Lobbying," 61 Fed. Reg. 1413 (1/19/96) is mandated by 49 CFR Part 20, Appendix A. Byrd Anti -Lobbying Amendment, 31 U.S.C. 1352, as amended by the Lobbying Disclosure Act of 1995, P.L. 104-65 [to be codified at 2 U.S.C. § 1601, et seq.] - Contractors who apply or bid for an award of $100,000 or more shall file the certification required by 49 CFR part 20, "New Restrictions on Lobbying." Each tier certifies to the tier above that it will not and has not used Federal appropriated funds to pay any person or organization for influencing or attempting to influence an officer or employee of any agency, a member of Congress, officer or employee of Congress, or an employee of a member of Congress in connection with obtaining any Federal contract, grant or any other award covered by 31 U.S.C. 1352. Each tier shall also disclose the name of any registrant under the Lobbying Disclosure Act of 1995 who has made lobbying contacts on its behalf with non -Federal funds with respect to that Federal contract, grant or award covered by 31 U.S.C. 1352. Such disclosures are forwarded from tier to tier up to the recipient. APPENDIX A, 49 CFR PART 20--CERTIFICATION REGARDING LOBBYING Certification for Contracts, Grants, Loans, and Cooperative Agreements (To be submitted with each bid or offer exceeding $100, 000) The undersigned [Contractor] certifies, to the best of his or her knowledge and belief, that: (1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to influence an officer or employee of an agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement. (2) If any funds other than Federal appropriated funds have been paid or will be paid to any person for making lobbying contacts to an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in Services Agreement 7381 Advanced Traveler Information System Page 75 of 78 connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form--LLL, "Disclosure Form to Report Lobbying," in accordance with its instructions [as amended by "Government wide Guidance for New Restrictions on Lobbying," 61 Fed. Reg. 1413 (1/19/96). Note: Language in paragraph (2) herein has been modified in accordance with Section 10 of the Lobbying Disclosure Act of 1995 (P.L. 104-65, to be codified at 2 U.S.C. 1601, et seq.)] (3) The undersigned shall require that the language of this certification be included in the award documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under grants, loans, and cooperative agreements) and that all subrecipients shall certify and disclose accordingly. This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by 31, U.S.C. § 1352 (as amended by the Lobbying Disclosure Act of 1995). Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure. [Note: Pursuant to 31 U.S.C. § 1352(c)(1)-(2)(A), any person who makes a prohibited expenditure or fails to file or amend a required certification or disclosure form shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such expenditure or failure.] The Contractor, L/tic._ 4c"--m. , certifies or affirms the truthfulness and accuracy of each statement of its certification and disclosure, if any. In addition, the Contractor understands and agrees that the provisions of 31 U.S.C. A 3801, et seq., apply to this certification and disclosure, Signature of Contractor's Authorized Official Name and Title of Contractor's Authorized Official fI L Date 13. CLEAN AIR Clean Air — (1) The Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act, as amended, 42 U.S.C. §§ 7401 et seg. The Contractor agrees to report each violation to the Purchaser and understands and agrees that the Purchaser will, in turn, report each violation as required to assure notification to FTA and the appropriate EPA Regional Office. (2) The Contractor also agrees to include these requirements in each subcontract exceeding $100,000 financed in whole or in part with Federal assistance provided by FTA. Services Agreement 7381 Advanced Traveler Information System Page 76 of 78 14. CLEAN WATER REQUIREMENTS Clean Water - (1) The Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Federal Water Pollution Control Act, as amended, 33 U.S.C. 1251 et seg. The Contractor agrees to report each violation to the Purchaser and understands and agrees that the Purchaser will, in turn, report each violation as required to assure notification to FTA and the appropriate EPA Regional Office. (2) The Contractor also agrees to include these requirements in each subcontract exceeding $100,000 financed in whole or in part with Federal assistance provided by FTA. 15. CARGO PREFERENCE REQUIREMENTS Cargo Preference - Use of United States -Flag Vessels - The contractor agrees: a. to use privately owned United States -Flag commercial vessels to ship at least 50 percent of the gross tonnage (computed separately for dry bulk carriers, dry cargo liners, and tankers) involved, whenever shipping any equipment, material, or commodities pursuant to the underlying contract to the extent such vessels are available at fair and reasonable rates for United States -Flag commercial vessels; b. to furnish within 20 working days following the date of loading for shipments originating within the United States or within 30 working days following the date of leading for shipments originating outside the United States, a legible copy of a rated, "on -board" commercial ocean bill -of -lading in English for each shipment of cargo described in the preceding paragraph to the Division of National Cargo, Office of Market Development, Maritime Administration, Washington, DC 20590 and to the FTA recipient (through the contractor in the case of a subcontractor's bill -of -lading.) c. to include these requirements in all subcontracts issued pursuant to this contract when the subcontract may involve the transport of equipment, material, or commodities by ocean vessel. 16. FLY AMERICA REQUIREMENTS The Contractor agrees to comply with 49 U.S.C. 40118 (the "Fly America" Act) in accordance with the General Services Administration's regulations at 41 CFR Part 301-10, which provide that recipients and subrecipients of Federal funds and their contractors are required to use U.S. Flag air carriers for U.S Government -financed international air travel and transportation of their personal effects or property, to the extent such service is available, unless travel by foreign air carrier is a matter of necessity, as defined by the Fly America Act. The Contractor shall submit, if a foreign air carrier was used, an appropriate certification or memorandum adequately explaining why service by a U.S. flag air carrier was not available or why it was necessary to use a foreign air carrier and shall, in any event, provide a certificate of compliance with the Fly America requirements. The Contractor agrees to include the requirements of this section in all subcontracts that may involve international air transportation. 17. ENERGY CONSERVATION REQUIREMENTS Energy Conservation - The contractor agrees to comply with mandatory standards and policies relating to energy efficiency which are contained in the state energy conservation plan issued in compliance with the Energy Policy and Conservation Act. Services Agreement 7381 Advanced Traveler Information System Page 77 of 78 EXHIBIT A SCOPE OF WORK Table of Contents I. Scope................................................................................................................... 9 II. ATIS Contract Deliverables.................................................................................. 9 III. Project Management............................................................................................ 9 IV. ATIS Components and Pilot Project System Detailed Requirements ................. 20 V. Vehicle Systems.................................................................................................26 VI. Passenger Information Systems......................................................................... 31 VII. Maintenance and Support .................................................................................. 35 VIII. Training.............................................................................................................. 36 Services Agreement 7381 Advanced Traveler Information System 18. RECYCLED PRODUCTS Recovered Materials - The contractor agrees to comply with all the requirements of Section 6002 of the Resource Conservation and Recovery Act (RCRA), as amended (42 U.S.C. 6962), including but not limited to the regulatory provisions of 40 CFR Part 247, and Executive Order 12873, as they apply to the procurement of the items designated in Subpart B of 40 CFR Part 247. 19. CONFORMANCE WITH ITS NATIONAL ARCHITECTURE To the extent applicable, the Contractor agrees to conform to the National Intelligent Transportation Systems (ITS) Architecture and Standards as required by SAFETEA-LU § 5307(c), 23 U.S.C. § 512 note, and follow the provisions of FTA Notice, "FTA National ITS Architecture Policy on Transit Projects," 66 Fed. Reg. 1455 et seq., January 8, 2001, and any other implementing directives FTA may issue at a later date, except to the extent FTA determines otherwise in writing. 20. ADA ACCESS Accessibility. Facilities to be used in public transportation service must comply with 42 U.S.C. Sections 12101 et seq. and DOT regulations, "Transportation Services for Individuals with Disabilities (ADA)," 49 CFR Part 37; and Joint ATBCB/DOT regulations, "Americans with Disabilities (ADA) Accessibility Specifications for Transportation Vehicles," 36 CFR Part 1192 and 49 CFR Part 38. Notably, DOT incorporated by reference the ATBCB's "Americans with Disabilities Act Accessibility Guidelines" (ADAAG), revised July 2004, which include accessibility guidelines for buildings and facilities, and are incorporated into Appendix A to 49 CFR Part 37. DOT also added specific provisions to Appendix A modifying the ADAAG, with the result that buildings and facilities must comply with both the ADAAG and amendments thereto in Appendix A to 49 CFR Part 37. 21. CITY OF FORT COLLINS BID PROTEST PROCEDURES The City of Fort Collins has a protest procedure, covering any phase of solicitation or award, including but not limited to specification or award. The protest procedures are available from the Purchasing Department, City of Fort Collins, 215 N. Mason, Street, 2nd Floor, P. O. Box 580, Fort Collins, CO. 80522. You may also request a copy of the procedures by emailing: Purchasing(a)fcgov.com or calling 970-221-6775. Services Agreement 7381 Advanced Traveler Information System Page 78 of 78 SCOPE The ATIS project is a comprehensive Intelligent Transportation System (ITS) solution which consists of several subprojects with a primary goal to increase ridership. Each of the subprojects complements each other to combine for a substantial impact for the City rider. Communication infrastructure systems are already in place and will be leveraged to provide near real-time bus arrival information to the general public. The primary subproject system is the back office Computer Aided Dispatch (CAD) and Automatic Vehicle Location (AVL) system. The data provided by the on -board systems will be used by central database systems and transferred to various application systems. The projects and the order of implementation coincides with both technical logic as well as a management derived priority list. II. ATIS CONTRACT DELIVERABLES A. Contract Deliverables Requirements List The Contract Deliverables Requirements List describes contract deliverables. The deliverables will need to meet the criteria set forth under each section and will need to meet the schedule and milestones as outlined in the agreed upon CDRL 701, "Project Management Plan". Contract Deliverables Requirements List CDRL Description Due Date 100 Initial Activities Meeting 20 days after NTP 101 Project Management Plan 30 days after NTP 102 Project Schedule 30 days after NTP 103 Monthly Progress Reports Second calendar month after NTP 104 Preliminary Design Review Package 90 days after NTP 105 Final Design Review Package 150 days after NTP 106 Report Generation 60 days from Pilot Testing 107 Mini -Fleet (Pilot Phase) Deployment 90 days after Final Design Review 108 Training Program Plan 90 days after NTP 109 Fleet Deployment Complete 90 days after Successful Pilot Phase 110 System Acceptance 30 days after Go Live 111 Project Closeout Package 30 days after Go Live III. PROJECT MANAGEMENT This section defines the management program that is required to provide a process of planning, scheduling, design review, controlling, and reporting. A. Contract Management The Project Manager shall be designated by the Service Provider to manage the work of this Contract. Formal communication shall be between the Service Provider's Project Manager and Services Agreement 7381 Advanced Traveler Information System