San Francisco Municipal Transportation Agency RFP No. SFMTA Transit Vehicle Farebox System Questions for SFMTA DATE: 9/28/2015

Transcription

1 San Francisco Municipal Transportation Agency RFP No. SFMTA Transit Vehicle Farebox System Questions for SFMTA DATE: 9/28/ Page 9 of 40 Under normal circumstances, the fare table shall be maintained via the data system and automatically downloaded to the Farebox whenever the Farebox is probed. - > For clarification, please confirm that it is acceptable if data upload and download are managed via wireless LAN communications at the garages, as opposed to via probing. (page 10 confirms wireless uploads only.) Answer: Yes, the SFMTA prefers that data transfer between the fareboxes/vehicles and the garage computers (both directions) via wireless LAN communications at the garages. Please note that page 13 also states the requirement: Any data contained within the Farebox compu[t]er that is not successfully transmitted via WiFi shall be retrievable through a hard-wired connection. 2. Page 10 - printed receipt from a roll of paper such as those found in cash registers. If this option is elected, for pricing, can you please confirm whether metallic striping is necessary on the transfer paper to prevent fraud, or is watermark-only paper acceptable? Answer: Vendors may propose any anti-fraud solution that allows SFMTA Transit Fare Inspectors to visually assess the authenticity of the fare receipt. 3. Page 11 To track the level of non-compliance and alert SFMTA Transit Fare Inspectors that the customer has not paid the appropriate fare, the Transit Operator must be able to key in an underpayment into the Farebox. Please confirm that a shortfare button is acceptable, if the farebox automatically determines the short fare amount. Answer: Yes, a shortfare/underpayment button would be acceptable. Because it is possible that a fare citation could be issued for an underpayment, it is extremely important that the farebox count all cash deposited accurately. 4. Page 13 Vaulting Is there full WLAN coverage across all garages? If not, is there full WLAN coverage across the fuel islands in each location? Answer: The SFMTA is currently upgrading its wireless system to improve coverage at all parts of its divisions. At a minimum, there will be reliable wireless coverage at locations where fareboxes are emptied and replaced. (At our light rail and trolley coach divisions, there are no fuel islands because these vehicles are electrically-powered.) 5. Page 13 Vaulting Is there existing power and Ethernet run to the vault locations or should the vendor provide this?

2 Answer: There is existing power and Ethernet connectivity at vault locations. 6. Page 14 - The Contractor shall ensure that this transactional level data is provided to the SFMTA in XMLformatted files. The Contractor shall work with SFMTA Technology staff to determine the XMLfile definition. How often does SFMTA expect to receive the formatted XML file (daily, weekly, monthly, etc.)? Answer: The SFMTA will need to receive this XML format on a daily basis as cash receipts need to be reconciled each day. 7. Page 15 upon integration with a CAD/AVL system, the location of the vehicle and Farebox. -Is the intention of this requirement to provide GPS location of when probing occurred (When probing occurs, routinely the CAD system has not booted completely or obtained GPS)? Answer: Yes, the intention of this requirement is to be able to track the location when probing occurred. If there are technical limitations that preclude this, please note them in your proposal and feel free suggest other ways locational information could be obtained if possible. 8. Page 15 If a garage computer is not required for a vendor s farebox solution, does SFMTA still want a vendor to propose a garage computer based solution? If so, can the garage computer be virtual? If SFMTA requires a garage computer Is it acceptable if a garage computer is only used for translating and forwarding data? As for reporting for one or more years worth of data, that may be achieved by allowing an access control web interface to the central data system. Answer: Yes, vendors may propose alternatives to having a physical garage computer so long as those solutions provide the same functionality as described in the RFP. The SFMTA must be able to receive transactional-level data from individual fareboxes to store in an Oracle database. For reconciliation purposes, the vendor solution should enable the SFMTA to associate individual transactions on specific vehicles with the garages where revenue collection occurs. 9. CAD Integration Is there existing data transfer on a J1708 network on the vehicles (i.e. Destination sign integration.) If so, can SFMTA provide the specification? Answer: If the SFMTA exercises the CAD/AVL option, the SFMTA will provide the specification for the interface. 10. If a vendor has verifiable evidence of multiple farebox system deployments that meet or exceed the ridership and quantity requirements internationally (including Canada,) can this be considered to meet minimum requirements for proposal submittal, if the vendor also has US deployments?

3 Answer: Yes, vendors may include international deployments that meet or exceed the ridership and quantity requirements. Because fareboxes in some countries accept coin currency only (such as selected transit systems in Canada), vendors will need to provide evidence that their equipment can also successfully accept bills. 11. Can you please provide the pricing form in Excel format? Answer: Yes, the pricing form in Excel format has been included on the City s Procurement website ( 12. Can we please request an extension for questions of two (2) weeks and a proposal due date of four (4) weeks? Answer: We are extending the submission deadline to Friday, October 23, Yes, the pricing form in Excel format has been included on the City s Procurement website (see response to Question 11). 13. What is the expected NTP date of the project (for purposes of providing a project schedule?) Answer: NTP will depend on the duration of final contract negotiations and approvals from the Civil Service Commission, the SFMTA Board of Directors and the San Francisco Board of Supervisors. NTP could possibly take place in late winter/early Spring of Please provide the list of garages, and quantity/type of vehicles at each garage. Answer: Here is the current list of SFMTA divisions with the number of active vehicles. Please note that the SFMTA is currently receiving new buses on a weekly basis and often redeploys vehicles to different divisions. Therefore, these numbers are subject to change and will likely be different by the time Notice to Proceed is issued. Cable cars do not have onboard fareboxes and are not part of this procurement. Division Motor Coach Trolley Coach LRV (2 fareboxes each) Woods Neoplan Orion Hybrid Orion Hybrid New Flyer Hybrid Kirkland Neoplan Flynn Neoplan New Flyer Hybrid 60 20* Islais Creek Neoplan Presidio - ETI Potrero - ETI ETI New Flyer Historic Streetcar

4 Green - - Breda- 149*** Muni Metro East **** Cameron Beach ***** * Contract allows for purchase of up to 163 New Flyer 60 articulated motor coaches. ** Contract includes purchase of 60 New Flyer 60 articulated trolley coaches. *** A total of 149 Breda Light Rail Vehicles are shared between the Green and Muni Metro East facilities. Cars are not specifically assigned to one shop. **** In addition, there are 3 historic streetcars off-site under rehabilitation ***** There are also 12 historic streetcars with antique fareboxes that would not be subject to this RFP Does SFMTA have existing enterprise licenses for SQL and Microsoft Server? Answer: Yes 16. Does SFMTA have any requirements for redundancy or backup? Answer: Yes. SFMTA requires a cluster server. 17. Can SFMTA provide virtual server infrastructure/virtual machines for deployment of backend systems? Answer: Yes 18. Does SFMTA have any preference as to whether the vendor uses open source software for server-based applications (i.e. Linux, Open SQL, etc.?) Answer: The SFMTA already has databases licenses for Oracle and SQL Server. The SFMTA must approve any open source software the vendor proposes, and this open source software must be vendor supported and have a maintenance plan. 19. What section of the proposal shall the vendors place the project schedule and implementation plan? Answer: Vendors shall place the project schedule and implementation plan in the section 3. Describe the features of the complete Farebox System. 20. All proposals must include unit costs for transfers/fare receipts assuming bulk supply purchases. A Proposal must explain options for purchasing transfers/fare receipts supplies beyond the duration of the Contract. - Please provide line items on the pricing table with requested quantity pricing for the four types of optional transfer stock. Answer: The pricing sheet in Excel format contains line items for each transfer/fare receipt option. Proposers should enter unit prices per transfer/fare receipt at different stated quantities.

5 21. Please provide the desired quantities to be priced for the transfer tickets/paper. Answer: The pricing sheet in Excel format asks vendors to provide unit prices per transfer/fare receipt at different stated quantities. 22. Is there an existing mobile router with WiFi in the SFMTA Revenue Collection trucks that can be used for the purposes of transferring data? Answer: No; however, there is already an existing GPS tracking system on all SFMTA nonpassenger vehicles that can be used for this purpose. 23. Does the Revenue Collection Facility have WiFi coverage that can be backhauled to the Central System? Answer: The Revenue Collection Facility will have either WiFi or Ethernet coverage. 24. Is real-time communication regarding mobile vault status in Revenue Collection trucks required (i.e. 4G communication to central system?) Answer: No; however, there is already an existing GPS tracking system on all SFMTA nonpassenger vehicles that can be used for this purpose. 25. Is there an existing mobile router/ WLAN device on-board the SFMTA vehicles that can be used to transfer data? If so, please provide the make and model. Answer: There is currently no existing mobile route/wlan device on-board SFMTA vehicles. 26. Can you please provide the latest fare table information, including any required passenger boarding information (such as recording day pass count, transfers, etc.)? Answer: Here are SFMTA s current cash fares. Adult Base Fare with 90-minute transfer - $2.25 Youth Base Fare with 90-minute transfer - $1.00 Senior, Disabled, Medicare with 90-minute transfer - $ Day Visitor Passport (all customers) - $17.00 (Note: This 1-day passport is primarily geared towards visitors and is currently not sold aboard vehicles. However, the farebox should be programmable to accommodate different types of 1- day passes should the SFMTA elect to sell them for example, one valid on all vehicles and adult, youth, senior/disabled day passes valid on all vehicles except cable cars.) 27. Please clarify whether SFMTA would like a magnetic card swipe reader as an option if a magnetic card solution is exercised.

6 Answer: Yes, please include a magnetic card swipe reader in that option. 28. Application Programming Interface (API): Does Muni intend to integrate the data from the farebox system to the Clipper Central System? Answer: The SFMTA currently imports transactional level Clipper data into an Oracle database and intends to do the same for fareboxes. It is possible that the two data sources will be integrated on the back-end, but the vendor will not be responsible for managing or integrating with Clipper data. 29. There s a typo on page 6 of the PDF under Site Acceptance Test (SAT) there s a mention of parking facility s equipment, that s not described anywhere else Answer: The Site Acceptance Test should refer to the Farebox System. Acceptance criteria are detailed in Section F on page 18 of 41 of the RFP. 30. What is the go-live date for the Xerox/ACS OrbStar CAD/AVL upgrade? Answer: In Autumn 2015, the SFMTA expects to begin conducting mini-fleet testing. Currently, the project completion and final system acceptance is scheduled to be March Are SFMTA tokens available to general public or only through non-profit/government organizations? Also, is there only one type of token (single ride) with the initials SF punched through? Answer: SFMTA tokens are not available to the general public. They are distributed through non-profit/social service agencies. There is only one type of token. As noted below in question 51, vendors may purchase tokens can be purchased for testing purposes. 32. What is your definition of a service day for fare collection (reporting, etc.? Is it a full 24-hour cycle? Or is there a different End of Day definition such as 3:00 am, etc.? Answer: The definition for the End of the Day is 3:00 am. 33. Please confirm that there are two types of transfers as listed below. Are there any exceptions to transfer validity, e.g. riding from bus/rail and transferring to cable car or vice versa: a. Regular transfer that is good for 90 minutes of travel, whether it be on a single route, or a trip with multiple transfers across buses and light rail. b. Late Night Transfer for any transfer that is issued after 8:30 pm and becomes extended until 5:00 am

7 Answer: Transfers are valid for 90 minutes on all Muni modes (motor coach, trolley coach, light rail vehicle and historic streetcars) with the exception of cable cars. Cable cars have their own ticketing system and transfers are neither issued nor accepted on them. 1-Day passes, 3-Day and 7-Day passes are valid on all Muni modes, including cable cars. Late night transfers issued by drivers on surface vehicles after 8:30 pm are valid until 5:00 am the following day. 34. Transfers are automatically issued on payment of the full amount such as $2.25. If a customer overpays (e.g. $3), do you wish to have that overpayment automatically printed on the transfer? Or do you prefer that only a transit operator can issue an overpayment receipt upon tapping a button on the Operator Control Unit (OCU)? Answer: The vendor s farebox should be flexible enough such that customers can pay for multiple fares together. For example, two adults shall be able to pay for separate $2.25 base fares (with two transfer/fare receipts issued) with $4.50 exact change or a single $5.00 bill. The vendor may propose a solution that prints out how much a customer actually paid, including overpayments. Current SFMTA fare policy states that customers do not receive change or credit for overpayments. 35. You have requested a unique ticket number to be printed on the transfer/fare receipts. Is this going to be a sequential number? Is it going to be unique throughout the system? Are SFMTA Transit Fare Inspectors required to visually validate this number as an anticounterfeiting measure? Answer: We must have different ticket numbers to help deter illegal duplication of transfers/fare receipts. Transit Fare Inspectors will look at that number, in conjunction with other information such as date, time and route of issuance, to determine the validity of the transfer/fare receipt. For each calendar day, these numbers must be unique but do not have to be sequential. 36. Inter-agency Transfers: How would a 50% discount work for a cash-paying adult single ride customer, transferring to Muni from the following agencies, or is it a function of Clipper card only: a. Alameda/Oakland Ferry b. Harbor Bay Ferry c. Golden Gate Ferry d. Golden Gate Transit e. Bay Area Rapid Transit District f. Vallejo Ferry

8 Answer: At this time, the vendor is not expected to accommodate interagency transfer discounts, which are available on the Clipper Card only. Nevertheless, in their proposals, Proposers may wish to demonstrate the extent to which their Farebox Systems could accommodate different types of fare policies and structures. 37. Will there be a DBE / SBE / LBE goal for the project now that it uses Federal funds? Answer: There is no DBE, SBE or LBE goal for this particular project. 38. Will SFMTA remove the current fareboxes, or will you expect the Contractor to remove the units? a. If the units are to be removed by Contractor, are we responsible for the disposition of the units? b. If responsible for the disposition, does SFMTA require the salvage proceeds to be returned? Answer: The SFMTA has not yet determined whether vendors or internal staff will be responsible for disposing of existing Cubic fareboxes. Proposers shall provide an option for their staff to remove the fareboxes. If Proposer disposes of the fareboxes, the salvage proceeds shall be returned to the SFMTA. 39. What CAD / AVL providers does SFMTA specifically expect to have integration quotes from? Answer: The SFMTA expects integration quotes from Clever Devices (CleverCAD), INIT (MOBILE-ITCS), Trapeze (Transit Master) and Xerox/ACS (OrbStar) systems. 40. Would SFMTA accept / review / consider a proposal for an integrated fare box with a CAD / AVL solution built in? Answer: SFMTA will accept, review and consider a proposal for an integrated farebox with a CAD/AVL solution built as long as the Proposer also provides integration quotes for the specified Clever Devices (CleverCAD), INIT (MOBILE-ITCS), Trapeze (Transit Master) and Xerox/ACS (OrbStar) systems. As stated in the RFP, the SFMTA may exercise the option to have Contractor integrate with any (or none) of the CAD/AVL systems. 41. Would SFMTA accept / review / consider a proposal for a hosted back-office solution? Answer: We cannot answer the question. Please provide more details as to what constitutes a hosted back-office solution. 42. Will SFMTA be providing a description of the interface with OrbStar that includes hardware, system overview, physical interface and or protocol description?

9 Answer: Should the SFMTA select this or any other CAD/AVL option, we will provide a technical description of the interface to the Proposer. 43. Is the expectation to run two systems simultaneously during the transition period? a. If so, will an interface be needed between the legacy system and new system for reporting needs? b. Would SFMTA be open to a data warehouse solution for holding all data during this period? Answer: The SFMTA will be maintaining two systems in terms of revenue accounting during the transition period. However, the Contractor will not be responsible for maintaining or interfacing with the legacy farebox system. 44. Will the RFP due date be extended based upon the issuance of a new document? Answer: Yes, we are extending the submission deadline to Friday, October 23, Requirement: If the coin or bill verification functionality is not available due to a jam or equipment malfunction, the vehicle operator shall have the ability to place the coin or bill module into bypass mode without verification using the Operator Control Unit. a. Q-> Is it acceptable for the operator to use a physical lever to put the farebox in bypass mode (prevents accidental pushing of farebox into bypass mode?) Answer: Yes 46. Requirement: The Contractor shall provide a portable data probe system which will allow the updating of Fareboxes and collecting Farebox data from buses, as well as testing and repairing Farebox equipment in the field. a. Q -> If maintenance, testing and troubleshooting can be completed on the OCU, is it acceptable for this functionality if it is confined to the farebox and the portable probe is used for probing (security issue if someone is troubleshooting the farebox and doesn t need to be able to probe the farebox?) Answer: Vendors may propose alternative solutions so long as the design enables SFMTA staff to retrieve data, update fareboxes, diagnose/test and repair farebox equipment issues in the field. Please fully describe how the design limits access of currency to the authorized technician and records each access occurrence. 47. Due to connector size/input, will SFMTA allow an OCU with a depth of 3.54?

10 Answer: Yes; however, please consider that the size of the Farebox and Operator Control Unit (OCU) is a scored selection criterion under Interface & Usability by Transit Operators. 48. As discussed during the pre-proposal meeting, is this procurement bound by the Buy America requirements typical of fare collection procurements? If so, please provide forms to be submitted with the proposal. Answer: Yes, this procurement is subject to Buy America requirements. We have provided a certification sheet for vendors to complete. 49. The RFP says the farebox is to transmit data via a wireless local area network (LAN) at each operating division or maintenance yard. Please confirm that SFMTA has existing wireless infrastructure at each facility suitable for this purpose and that the contractor is not required to provide additional wireless equipment at these locations. Answer: The SFMTA is currently upgrading its wireless system to improve coverage at all parts of its divisions. At a minimum, there will be reliable wireless coverage at locations where fareboxes are emptied and replaced. 50. Please clarify whether pricing for As-Needed Preventative Maintenance and the Extended Annual Warranty as listed in Appendix G will be included in SFMTA s evaluation of the cost proposal. Answer: Yes, pricing for As-Needed Preventative Maintenance and the Extended Annual Warranty will be included in the cost proposal evaluation 51. Can tokens be purchased for testing? Answer: Tokens can be purchased for testing purposes. Token price is $2.25. Please contact the SFMTA directly at revenue.sales@sfmta.com or call Please make sure to indicate that the tokens are being purchased for testing purposes related to responses for RFP No. SFMTA Orders will be processed within five business days. There are no discounts available for bulk purchases. 53. If we do not have references from all four of the SFMTA prescribed CAD / AVL providers - due to no other reason than not having existing customer requirements to do so - how will that be scored and will it count against any possible bidder? o In addition, can we provide references for a CAD / AVL provider that is not included in SFMTA s list? Answer: The SFMTA recognizes that vendors may not necessarily have integrated with all four listed CAD/AVL providers. The selection committee will take that into consideration when

11 scoring. A Proposer may list other CAD/AVL providers with which it has integrated its farebox system. 54. Please elaborate on the proposed schedule for delivery. The current RFP statement says that the fareboxes must be delivered / installed immediately upon issuance of NTP. Under that premise, that will provide SFMTA will NO time for a sufficient design review nor any time for testing of the equipment in a factory setting. Please advise if the RFP is correct in regards to immediate installation. Please confirm SFMTA s intentions to have the project completed (read as finished base install ) within or on 12 months from NTP. This again is a rather aggressive schedule that may not work in the favor of SFMTA. Implementation approach (p. 17 of 40) states "Contractor must assume that installation of the Farebox System will commence immediately upon receipt of NTP. Can you please clarify if the design review will be completed before award or if design phases will be completed post award. Answer: The SFMTA will issue an amendment clarifying that installation of the Farebox System will not commence immediately upon receipt of a Notice to Proceed. Vendors shall include a testing and installation schedule in their Proposals. Due to the age and condition of SFMTA s existing Fareboxes and ongoing delivery of new vehicles, however, the SFMTA needs to expedite installation; The SFMTA expects the selected Proposer to begin developing a prototype and configuring back-end systems immediately upon receipt of a Notice to Proceed. 55. Can you please clarify the statements related to warranty repair and the use of SFMTA staff. o How are we to include the use of this staff in our pricing model? o Can the Contractor provide staff for this project to cover warranty. o If the Contractor can provide staff, are they required to be Union / bargained for staff? Can you please confirm that you are asked for a flat fee for repair over the term of the agreement. Can you please clarify who s responsibility Preventative Maintenance will be. If it is not the Contractor, how will that impact the defined failure rates identified within the project if the Contractor is not able to ensure quality of work. For the pricing of the Software System, do you want to include the 5yr maintenance / warranty cost and do you want it included in the out years?

12 Answer: SFMTA staff will be responsible for routine day-to-day farebox maintenance. As noted in question 55 above, there are three types of maintenance that are the responsibility of the vendor: Warranty Compliance Warranty compliance shall be provided at no extra charge to the SFMTA for the first five years. The SFMTA does not consider as selection criteria whether a vendor s employees are subject to a collective bargaining agreement. Vendor expenses to offer warranty compliance should be included in the unit prices of the fareboxes. If the contract is extended for years 6-10 and years 11-15, the vendor should provide unit warranty prices on an annual incremental basis. Preventative maintenance procedure Each vendor shall propose a complete preventative maintenance procedure, which includes inspection of all farebox components, for all vehicles using its own or subcontracted staff. The vendor shall conduct the preventative maintenance procedure given three months advance notice from the SFMTA. The SFMTA may request preventative maintenance multiple times, or not at all, during the contract as necessary. Vendors should price one preventative maintenance procedure per farebox for years 1-5, 6-10 and On-Call Maintenance Vendors shall provide an hourly on-call maintenance rate (inclusive of all salaries, benefits and overhead). If this contract is extended for years 6-10 and 11-15, the SFMTA will permit Contractor each year to increase hourly On-Call Maintenance rates by a level no greater than inflation, as measured by the Consumer Price Index (CPI) for the San Francisco area. 56. Are negotiation / exceptions to the contract conditions allowed? o And if so, what format would you like them in and how would you like them submitted? Answer: By taking exceptions to the terms and conditions stated in the form contract, a Proposer risks rendering its Proposal non-responsive. Whether an exception renders a Proposal nonresponsive generally depends on whether the exception would amend a material term of the contract or seek to amend a requirement established by City ordinance or other law. The SFMTA requests that vendors communicate their proposed exceptions to the SFMTA prior to the close of the communications period so that the Agency may respond appropriately. The SFMTA will provide its responses to all Proposers. 57. Will Wi-Fi in bus garages / depots be provided by SFMTA? o If not, would SFMTA like a network provided / included? Answer: SFMTA will provide Wi-Fi. 58. Can you please provide commentary / clarification on of "software upgrades" to be provided at no charge during the term of the agreement?

13 Answer: A software update is a correction, debug, work around or other repair or improvement to the existing functionality of the software. A software upgrade is additional system functionality that is part of the vendor s system generally offered to the vendor s customers as part of the base system (i.e., is not customized for another transit agency). The SFMTA requires that during the term of the Agreement and any Maintenance Agreement, Contractor shall provide both software updates and upgrades. 59. Are you requiring any other CAD/AVL system integration pricing beyond OrbStar throughout the fleet? o Would you consider a proposal for an integrated farebox that includes a CAD / AVL solution? Answer: SFMTA will accept, review and consider a proposal for an integrated farebox with a CAD/AVL solution built as long as the Proposer also provides integration quotes for the specified Clever Devices (CleverCAD), INIT (MOBILE-ITCS), Trapeze (Transit Master) and Xerox/ACS (OrbStar) systems. As stated in the RFP, the SFMTA may exercise the option to have Contractor integrate with any (or none) of the CAD/AVL systems. 60. Front page and I. B. state September 30 submission due date, section III. A. states the 20th - which one is correct? Answer: We are extending the submission deadline to Friday, October 23, Do you require that each bus garage / depot have individual data systems or one overarching as well? o Can this system be hosted for SFMTA by the Contractor? Answer: Each bus garage does not need to have an individual data system. Rather, for reconciliation purposes, the vendor solution should enable the SFMTA to associate individual transactions on specific vehicles with the garages where revenue collection occurs. There does not necessarily have to be a physical garage computer at each individual division, as long as SFMTA is able to obtain the same functionality for data as described in the RFP. As described on page 14 of the RFP, the primary purpose of the data system is for the SFMTA to obtain transactional level data from the farebox. The SFMTA will have its own back-end system to receive this data. As noted in the answer to question 63, Proposers may offer additional services such as hosting a back-end system (listed under Other Enhancements on the pricing sheet) but the SFMTA is under no obligation to purchase these services. 62. Please clarify that there is NO LBE requirement for this project. Answer: There is no LBE goal for this particular project.

14 63. Would you be open to a vendor hosting the back end system? Where would you like us to price options (those not required for the base delivery of the system) on the scoring sheet (e.g. farebox with built in / integrated CAD / AVL solution vs expensive interfacing with third party partners)? Answer: Proposers may offer additional services, such as hosting a back-end system or an integrated CAD/AVL system. Proposers should explain how these services achieve the same or enhanced functionality over the base system described in the RFP. Please note: (a) If the Proposer is selected, the SFMTA is under no obligation to purchase these services. (b) Proposers must still provide price quotes and demonstrate functionality for base system requirements. On the pricing sheet, there is a section called Other Enhancements (beyond the requirements not listed in the Request for Proposals). Vendors should add the pricing for these options in this section. To evaluate all proposals consistently, vendor-provided options that are not required for the base delivery of the system will not contribute to the total price for scoring purposes. However, other evaluation criteria will take into consideration the entirety of the Proposal as it relates to meeting or exceeding base requirements. 64. Can vendors observe how revenue collection from fareboxes takes place at a garage? Answer: Proposers are invited to attend a demonstration of how revenue is collected from fareboxes as vehicles arrive at a division. This event will take place on Wednesday, October 7, 2015 from 6:15 pm to 7:15 pm at the Potrero Trolley Coach Division. Potrero is located at 2500 Mariposa Street (at Hampshire St.). This site accessible by Muni routes 9/9R, 22, 27 and 33. If vendors drive to the site, they will be responsible for finding on-street parking; no parking is available on SFMTA property. Proposers are requested to budget extra time in arriving as the demonstration will begin promptly at 6:15 pm as trolley coaches begin to pull in for the evening. 65. Page 7: SFMTA indicates that the Provider needs to use the existing mounting provisions. Please provide details on those mounting points. Photos, schematics and or drawings would be very helpful. Answer: Please see the following diagram of our mounting plate. At the 4 cross intersections, the farebox is bolted to the floor using hold a 3/8 diameter thread that has a 16 threads per inch pitch which has 3/8-16 threaded holes approximately. Many of the holes were created with a loose tolerance; hence, a guaranteed fit with vendor-provided fareboxes would require the same slotted footprint or a floating hole. The SFMTA would prefer a floating hole arrangement over the cross because the cross is very limiting (only 1 degree of freedom at a time (forward-back or side-to-side, not both).

15 66. Please provide a current fleet list of all vehicles and vehicle types to be installed with fareboxes. Answer: Please see the answer to question Page 6: The Farebox shall also accept Muni tokens. Please provide samples and more details about the tokens to understand how these are made. Answer: Please see the answer to question The current proposal due date is only 5 business days removed from final submission of questions. Would SFMTA please consider a 4 week extension in order for venders to have an opportunity to incorporate question responses and new information into the final proposal? Answer: SFMTA is rescheduling the deadline for final sumbissions to questions to Thursday, October 8. The deadline for submissions is Friday, October 23 (15 days later). To maximize time for Proposers, the SFMTA will be releasing answers to questions as soon as they have been prepared and will not wait until after the question submission deadline.