Loading...
HomeMy WebLinkAboutRFP - 7381 ADVANCED TRAVELER INFORMATION SYSTEM (2)Addendum 1 – 7381 ATIS Page 1 of 6 ADDENDUM No. 1 SPECIFICATIONS AND CONTRACT DOCUMENTS Description of BID 7381: Advanced Traveler Information System OPENING DATE: 3:00 PM (Our Clock) June 1, 2012 To all prospective bidders under the specifications and contract documents described above, the following changes/additions are hereby made and detailed in the following sections of this addendum: Exhibit 1 – Additions and Clarifications Exhibit 2 - Questions & Answers Please contact Ed Bonnette, CPPB, CPM, Buyer, Buyer at (970) 416-2247 with any questions regarding this addendum. RECEIPT OF THIS ADDENDUM MUST BE ACKNOWLEDGED BY A WRITTEN STATEMENT ENCLOSED WITH THE BID/QUOTE STATING THAT THIS ADDENDUM HAS BEEN RECEIVED. Financial Services Purchasing Division 215 N. Mason St. 2nd Floor PO Box 580 Fort Collins, CO 80522 970.221.6775 970.221.6707 fcgov.com/purchasing Addendum 1 – 7381 ATIS Page 2 of 6 EXHIBIT 1 – ADDITIONS AND CLARIFICATIONS 1. NOTE: Word version of 7381 Advanced Traveler Information System RFP document has been posted on City of Fort Collins BuySpeed system. Bidders can use it to cut & paste portions of their proposals. 2. NOTE: An Excel spreadsheet with modifications of bus quantities, Door Widths for the buses listed, and information on the radio systemhas been posted on City of Fort Collins BuySpeed system. THIS REPLACES THE 7381 ATIS APPENDIX SPREADSHEET THAT WAS ON THE ORIGINAL RFP POSTED. MAKE SURE YOU USE THIS REVISED VERSION FOR YOUR PROPOSAL 3. NOTE: Deadline for submission of any additional questions is by end-of-business Tuesday May 15; so that the due date for proposals remains 3:00 PM (Our Clock) June 1, 2012. 4. NOTE: The RFP states heading of 7.2.4 Weekly Conference Calls should state 7.2.2 Weekly Conference Calls 5. NOTE: The RFP states heading 7.2.5 Monthly Progress Status Updates should state 7.2.3 Monthly Progress Status Updates Addendum 1 – 7381 ATIS Page 3 of 6 EXHIBIT 2 – QUESTIONS & ANSWERS 1.Q. Do you want the answers to the questions under each section to be answered together or under each section? 1.A. For readability the preference would be to have the scope of work and the responses under each section that requests information or compliance. 2.Q. Is there a limit to the number of pages the proposal can be? 2.A. There is no limit as this is a rather complex proposal, we want to afford you the opportunity to include the information you want to provide so we may give your proposal a full evaluation. Please do not include large filler documents such as ADMIN or USER Guides. 3.Q. Is there a word document version of the PDF file that will be available for ease of cutting and pasting? 3.A. Yes; check on the City of Fort Collins BuySpeed system. It was made available on there to coincide with this Addendum. 4.Q. Do you want the cost proposal in a separate binder? 4.A. No that is not necessary, just include it using the excel spreadsheet template in a section within your submitted proposal. 5.Q. How does the Appendix B matrix work with the proposal? 5.A. The Appendix B is a way to verify you have completed your responses in each section and to give the evaluators the ability to quickly see where any exceptions might be identified. Once the exceptions are identified, then there will be an evaluation as to the severity or impact these exceptions will have on the overall goals of the project. 6.Q. Do the section requirements and the Appendix B match up with each other? 6.A. The match up will be re-verified to make sure that each section is identified with the requirement for information, compliance or CDRL. If there is a difference an update will be provided in the addendum issued. The revised spreadsheet will include the correct Appendix B. 7.Q. What is the deadline for asking questions? 7.A. We have established a deadline by end-of-business Tuesday May 15 (see Note #4, above). Please send in questions as soon as you can. We do not anticpate a need to push the due date of the project after June 1. Addendum 1 – 7381 ATIS Page 4 of 6 8.Q. Can you provide the configuration of the vehicles in Appendix C, can you provide the dimensions of the doors and whether they open in or out? 8.A. Yes; the revised spreadsheet contains the most up to date information including door dimensions. 9.Q. Table 16, there are 6 supervisor vehicles, can I assume we will provide pricing for them? 9.A. Yes, please refer the components listed in the revised spreadsheet. 10.Q. How many buses should there be pricing for as there are multiple references to various types of buses and quantities? 10.A. In the spreadsheet it includes 20 users, 40 vehicles and 100 employees. This is used to provide uniform pricing between proposals. There are other parts of the costing spreadsheet that require different quantities. 11.Q. What engine metrics are being requested for the vehicle monitoring system? 11.A. We would like to know what types of options are available and the cost associated with them. Indicate if it is an integrated system built into the CAD system. 12.Q. Is the City providing hardware (servers/workstations)? 12.A. Yes, the preference is to use virtual servers and enterprise database systems. Please include the minimum and optimum hardware requirements and database requirements. 13.Q. Is the City providing the wayside signage? 13.A. The General Contractor will be providing all the variable message signs along the BRT and the STC. However there is pricing for VMS signs at each of the transit centers. 14.Q. Qualifications and experience (Pg 55). Are you looking for design documents? 14.A. A pdf or other documentation that shows a description of the project or weblink of the project should be provided. These need to be successfully implemented and completed projects. 15.Q. Have you considered making the mobile section of this come later in the project? 15.A. CAD and In Vehicle systems must be in place in order to provide an external feed to other applications such as websites, mobile apps, etc. The order of implementation will be part of the project plan that is developed. 16.Q. The requirements for this section are all available through mobile websites, so what is the intent of the mobile app? 16.A. We have done a fair amount of research on this and the mobile website is a requirement. The mobile application is still under discussion and the costs associated Addendum 1 – 7381 ATIS Page 5 of 6 with the development and ongoing maintenance will be considered. Colorado State University has requested access to the AVL data in order to build a transit app into their suite of mobile apps. 17.Q. Is there additional functionality that is requested in an app? 17.A. Please include functionality that you have incorporated into other transit related mobile apps. Please include the links to download and install the mobile apps for review. 18.Q. In the section on SMS, it describes day of week and time of day, is that just the filtering system that you would like to use? 18.A. Yes, the filters as shown in the order liste dis the intended order of filtering for the rider. 19.Q. In the price sheet in appendix A, the number of buses is confusing. Can you add the quantities that you want to see in each section? For example, in Appendix A, table 10, it shows the various types but no quantities. It would be helpful if these had the quantities for costing. 19.A. The quantities where appropriate have been updated in the revised spreadsheet. 20.Q. In Appendix C, for 1708 and 1939, what do they refer to on that particular vehicle? 20.A. These are the native bus systems for those vehicles. 21.Q. You requested information on integration for the fareboxes and headsigns. Could you provide information on the systems? 21.A. The GFI Cents-A-Bill (farebox) does have the required cabling for the integration. But if there is a specific requirement for the head signs, we use both Twin Vision and Illuminator, please provide any information you need to integrate them successfully. 22.Q. Are the sound systems in good working order? 22.A. Yes all sound systems work within each transit bus, this is a requirement of the ADA regulations. 23.Q. Is the GFI firmware update in place for integration (for single sign on)? 23.A. Firmware from GFI is easy to install and will be done by Transfort if it is needed. Please list the requirements that you have for integration with the farebox, both hardware and software. 24.Q. On the question regarding budgets, is there additional funding for the project? 24.A. The budget is derived from multiple funding sources. One grant is a congestion Mitigation and Air Quality grant for $600000.00. The MAX BRT project is also providing funding for this project. Addendum 1 – 7381 ATIS Page 6 of 6 25.Q. Is there an estimated timeline for completion? 25.A. Yes, the project is key to our MAX BRT project which must be completed by January 1st 2014. This project must be done before then. 26.Q. Will there be any integration to your two way radio system in the vehicles? 26.A. We have not considered it a priority for the project, however it can be an option included in the submitted proposal, I have included the 2 way radio system information in the revised spreadsheet. 27.Q. Who is the manufacturer of the radio system? P25, analog etc 27.A. Motorola, 800 MHZ Trunking System. Please refer to the revised spreadsheet for specific information. 28.Q. Who should questions be sent to? 28.A. Purchasing. Ed Bonnette, CPM, CPPB, Buyer, at ebonnette@fcgov.com. 29.Q. Section 4.4.2 (Transit Centers) and Section 4.4.3 (Platforms and Stops) Are these sections dealing with announcements made on the bus coupled with coordinated signage, or are they trying to say that the transit centers themselves will have automated announcements? 29.A. The intent is to have the automatic announcments made at the transit centers and platforms and stops to be triggered by the movement of the transit buses as recognized by the CAD system or however the proposed solutionis designed to work. The announcements on the transit buses will be independent of the announcments at the transit centers and platforms and stops. 30.Q. Section 4.4.2 (Transit Centers) and Section 4.4.3 (Platforms and Stops) Are they only interested in geofences here, or would they be amendable to other potential solutions that achieve the same thing (like what we currently have with our IVN- driven announcements based on GPS and odometer pulses)? 30.A. Geofences are one known GPS technology but is not a required technology. However, the proposed solution accomplishes the same goal and as long as it works well will be acceptable. 31.Q. Section 4.4.2 (Transit Centers) and Section 4.4.3 (Platforms and Stops) What kind of PA systems are they currently using? 31.A. The transit center PA systems are listed in Appendix D Transit Centers page 100. The platform and stops are not built yet; the RFP for the MAX BRT is currently on the street. The final draft specs are shown in the Appendix E Platforms and Stops. The final rfp and addendum1 is located on the fcgov.com/purchasing website under BID # 7332. https://secure3.fcgov.com/bso//external/bidDetail.sdo?bidId=7332