Specifications include, but are not limited to: A. Contractor shall provide a web-based cloud hosted system as a SaaS. B. Contractor shall provide support based on Section 6.0. C. Contractor shall provide training on the system either in-person or remotely to METRO. D. Contractor shall provide periodic updates to all software components. E. Contractor shall provide bug fixes on a regular basis, or when notified by METRO per Section 6.0. F. The System shall provide the currently available (consolidated) arrival predictions, vehicle locations for all vehicles, routes and stops, and alerts, (as well as make available the current routes/configurations) to third party application developers via a separate GTFS, GTFS-RT Alerts and GTFS-RT feeds. G. Alerts System shall integrate with GovDelivery, Facebook, Twitter, and provide an alerts API for websites and mobile applications to utilize. H. System shall provide Security roles at a system level and a transit agency level. I. Contractor shall define and apply security roles defined by job function (ex. agency GTFS read only, agency GTFS modification, agency service alert read only, agency service alert modification, etc.). J. Contractor shall provide the System for three (3) years beginning from the date of System Acceptance. A 90-day period shall precede System Acceptance and be used for Contractor’s implementation and testing of System. K. Contractor shall provide all necessary personnel, tools, test equipment, transportation, hardware and software for the successful implementation of the System and for its continued operations for the duration of the contract. L. Contractor shall locate all System software and hardware in Contractor (or Contractor controlled) facilities, unless otherwise authorized in writing by the METRO Project Manager.