PROJECT NUMBER: PAGE 1

Transcription

1 PROJECT NUMBER: PAGE 1 DATE: 07/01/2016 WHO: Registered List of Bidders HOW: ORIGINAL TO: COPIES TO: Via Project File Todd Tipton Culver City BY: Jonathan Wicks PROJECT NAME: Culver City PARCS RFP # 1602 PROJECT NUMBER: SUBJECT: Addendum # 2 To All, Attached below are the questions submitted and the answers provided by the City of Culver City with regard to the captioned Request for Proposal. All currently available drawings have been posted to the City website at: No further questions will be answered at this time. One original, one electronic and two copies of the proposal must be submitted to the CITY CLERK at CITY HALL, 9770 Culver Boulevard, Culver City, California, 90232, not later than 3:00 p.m. on Thursday, July 28, Facsimile proposals will not be accepted. The electronic copy should be submitted on a USB stick drive or CD/DVD in PDF format. Hard copies of Addendum # 2 will not be issued. Thank you, Jonathan Wicks Walker Parking Consultants Page 1 of 12

2 PROJECT NUMBER: PAGE 2 General Questions: 1. Will there be any further information provided concerning the Metro TAP card tie in? What system and specs is the Metro using? Response: PARCS vendor to provide an interface that verifies ridership via the Metro TAP database to provide a discounted parking rate to qualified parkers. Metro has successfully interfaced with their pay station provider through an interface with the METRO TAP card identifier engine software that included the following: 1. Have the ability to save a TAP card holder s registered plate detail 2. Ability to access the World Wide Web 3. Have the ability to retrieve a TAP card holder s registered plate details so they do not need to re-enter plate details every time they park 4. Have the ability to produce an optional paper receipt or downloadable electronic receipt. 5. Ability to handle, send and consume JSON data structures. 6. Communication speeds of at least 2.0 mbs (wireless communication preferable) 7. Ability to handle SSL authentication, using the latest standard protocols, with the ability to update if standards change. 8. Read TAP Card in the near field (when presented) NFC Card reader specs as below: ISO/IEC Type A compliant smart cards and hardware shall be able to read/ Mifare Classic cards 9. Decline transactions based on Business Processing Rule software program (BPR) black list data 10. Communicate TAP Card data, Credit card data or payment data to the BPR API 11. Accept web based responses from BPR API 12. Handle exception processing from the BPR, such as alternative rates and unpaid transactions. 2. Will you put the drawing on line for the garages to be built in the next year? Response: See the City website for additional drawings 3. Is the city going to do any of the civil work or is that part of the contractor s responsibility? Response: The City is requesting proposers include all civil and other infrastructure work required to support the proposed PARCS, in conjunction with City approval and permitting. The City understands the infrastructure requirements and lane layouts are unique to each proposer s PARCS so it is the responsibility of the proposer to determine what infrastructure work will be required to accommodate their PARCS. Page 2 of 12

3 PROJECT NUMBER: PAGE 3 4. Who is responsible for the power and data infrastructure in the new future garages (Market hall and Parcel B) Response: Combined properties will be responsible for the power and data infrastructure in the Parcel B garage and the City will be responsible for the Market Hall garage. The successful PARCS vendor will be required to provide the power and data infrastructure requirements for their PARCS to allow the responsible parties to install the infrastructure necessary to support the proposed PARCS. 5. Will the City be providing network communication from City hall to each of the garages (Fiber or point 2 point T1) Response: Currently, City provided DSL lines are available at each garage. Proposals should include any additional communication infrastructure or lease lines needed to accommodate the proposed PARCS. All costs, including any reoccurring costs, to be outlined in the proposal. Reoccurring costs to be passed through to the City. The City is in the process of a City-wide fiber project that may accommodate connectivity to the garages in the future but the PARCS proposals should assume that fiber connections will not be available prior to the implementation of the new PARCS. 6. Are we to provide pricing to GC s bidding the construction of the new garages? Response: Yes, but it must be consistent with pricing provided to the City. 7. We respectfully request a two (2) week extension to the bid due date, allowing reasonable time to define, plan, and price the civil components of the project. Please confirm if an extension will be granted. Response: The City is agreeable to a two week extension. 8. Please provide relevant architectural and parking system drawings for the facilities included in the RFP. These to include the as-builts provided as part of the previous installation. Response: See City website for available drawings 9. AUP 11 indicates an interface with the METRO transit system to confirm ridership for discounted parking. Please provide a detailed explanation as to the operational intentions and the data that will be provided by the METRO system. For example, is the ridership requirement based on an anniversary or calendar day? Is the ridership status stored on the card, back-end, or both? Is discount to be a function of time or money? For same calendar/anniversary day? What of riders that may work night shift? Response: The Transit Program will offer a discounted daily parking rate to parkers that can verify use of the Metro system as well as related municipal providers within a 96-hour period. Verification will be provided by linking the automobile to a valid TAP card. Non-transit riders will pay a regular daily parking rate, set to be higher without transit users discount to discourage non-transit use. Monthly transit parking will be available for patrons that maintain a minimum of ten (10) daily ridership transactions per month, using their TAP card. Monthly transit parking customers that have six (6) or less daily ridership transactions at the fifteenth (15th) of the month will be notified via reminder that they must maintain the minimum of ten (10) daily transactions to purchase the monthly transit parking for the following month. Customers can complete the minimum Page 3 of 12

4 PROJECT NUMBER: PAGE 4 transactions requirement through the last day of each month. If the minimum ridership transaction requirement is not met, the parking permit will be invalid the following month. Ridership status is stored on the back-end with Metro TAP card identifier software Discount is to be an alternative rate schedule based on a dollar value discount for the different rate increments 10. Project Requirements 8 indicates power conditioning to be provided by vendor. Please provide all relevant electrical drawings for the intended facilities inclusive of the current load specifications Response: See the City website for available drawings. The intent is for the PARCS vendor to provide power conditioning at the lane/equipment level as part of the UPS units. Power conditioning at each panel is not required. 11. If additional power is required at the locations, exceeding the current panel allocation, will the City provide additional power panels? Response: Although not anticipated, the PARCS vendor will be responsible for providing and installing additional panels if needed. Because this is not anticipated, this would be handled as a change order and not part of the base pricing. 12. Project Requirements 16 indicates connection to owner supplied equipment. Please provide a list and location of what is considered owner supplied equipment and include any relevant operational intentions associated with the owner supplied equipment. Response: See 2.1 of Section for Owner Supplied and Existing Products 13. Project Summary, System Design Characteristics, 4 indicates the desire for EMV capability. Please confirm the City s desired operation with regard to CVM (Cardholder Verification Method) as this will significantly impact the hardware to be bid. In addition, the specifications indicate a 4 second authorization process. This will be impacted by the EMV functionality desired. Response: The requirements state that the equipment and software have the ability to be upgraded to enable EMV compliant credit card processing. EMV readers are not required at this time but are acceptable if they are the proposer s preferred method of credit card processing. If proposing EMV readers please provide anticipated average credit card processing transaction times. 14. Product Data Submittals, 2e indicates pinhole cameras. Please provide the detail as the specifications for the requested cameras, where the CCTV head end is located, and the brand and specifications of the CCTV head end. Response: Pinhole cameras are not required at this time but the City may elect to add pinhole cameras to PARCS devices in the future. Proposers to provide an affirmative statement of their ability support the use of pinhole cameras and ability retrofit the PARCS devices with pinhole cameras. Proposers should also provide and install any spare communication cabling, if necessary, to support the future installation of pinhole cameras in the entry stations, exit stations, and POF. Page 4 of 12

5 PROJECT NUMBER: PAGE POF Equipment. Please confirm the cash and credit card POF units are not to accept or issue coins. Response: Confirmed, no coin acceptors needed. 16. The AVI option is inclusive of the desire to provide 500 transponders. Please detail the type of transponders requested: active passive form factor. Response: Passive tags are preferred but the PARCS vendor should propose their best value solution for transponders that meet the requirements of 2.6.Q How do you want to have the two undeveloped garages (Parcel B & Market Hall) bid, equipment only - no infrastructure, or equipment and infrastructure? a. If infrastructure is to be bid, will plans be timely furnished? Response: Combined properties will be responsible for the power and data infrastructure in the Parcel B garage and the City will be responsible for the Market Hall garage. The successful PARCS vendor will be required to provide the power and data infrastructure requirements for their PARCS to allow the responsible parties to install the infrastructure necessary to support the proposed PARCS. Bid equipment only for these locations. 18. Will plans be furnished for the existing 4 garages (City Hall, Ince, Cardiff and Watseka)? a. If, so how and when? Response: See City website for available drawings 19. Will the security roll gates need to be controlled by the PARCS? a. By schedule or credentialed, or both b. Does the gate have a high capacity/cycle spec? Response: The security gates need to be controlled by the PARCS system via a credential. The gates will otherwise be controlled by the parking manager and/or a timer. The gate does not have a high capacity/cycle spec. Accommodating after hours parkers will require additional PARCS hardware to activate the gate for authorized after hours users, as there is not currently PARCS equipment outside the security gates. The City currently has a contractual arrangement with a downtown hotel to allow valet parking in the Ince structure. This valet parked cars will not be equipped with AVI technology, requiring proximity card readers. Additional PARCS hardware required includes 5 AVI readers and 3 proximity card readers at the following locations: One (1) AVI reader at the Watseka Garage installed outside of the entry side of the security gate. One (1) AVI reader at the Cardiff Garage installed outside of the entry side of the security gate. Total of three (3) AVI readers and three (3) proximity card readers at the Ince Garage. One (1) AVI reader and one (1) proximity card reader outside of the entry side of each security gate. Use cases for the interface with the existing rolling security gates are as follows: Watseka and Cardiff Garages - One rolling gate controls the single entry and exit point. Authorized users access the structure after hours via AVI transponder that is used to operate the gate and then used again to gain entry through the PARCS entry lane. Upon exiting, the user s AVI transponder is used at the Page 5 of 12

6 PROJECT NUMBER: PAGE 6 PARCS exit lane to vend both the PARCS barrier gate and the rolling security gate (when closed). Ince Garage - Three entry rolling gates and three exit rolling gates in total. Two entry and one exit gate on Culver Boulevard and one entry and two exit gates on Washington Boulevard. Authorized users access the structure after hours via AVI transponder or proximity card that is used to operate the gate and then used again to gain entry through the PARCS entry lane. Upon exiting, the user s AVI transponder or proximity card is used at the PARCS exit lane to vend both the PARCS barrier gate and the rolling security gate (when closed). Proposers to adjust the quantity of equipment on the Price Proposal form and add any additional software cost, if necessary, to accommodate the functionality described above. Proposers may additionally provide an alternative solution to support the required valet parking access at Ince that does not require proximity cards, but must include the proximity card solution in base pricing. 20. Are all booths removed at Ince garage? a. If all are removed, where is the requested CT (Cashier Terminal) be located? Response: Yes, cashier booths to be removed. Cashier Terminal will be located in the parking office. City desires the rights to salvage any equipment before the booths are removed. 21. Who is your preferred credit card processor? Response: Per 1.6.E.8 in Section the Proposer is to submit a list of credit card processors with which the Proposer s PARCS has existing interfaces. PARCS vendor shall assist the City with coordinating use of the City s selected credit card processor. 22. Can GPR (Ground Penetrating Radar) be substituted for X-ray? Response: Yes, GPR is acceptable 23. Are pin hole cameras to be bid for the entry/exit/pof s? Response: Pinhole cameras are not required at this time but the City may elect to add pinhole cameras to PARCS devices in the future. Proposers to provide an affirmative statement of their ability support the use of pinhole cameras and ability retrofit the PARCS devices with pinhole cameras. Proposers should also provide and install any spare communication cabling, if necessary, to support the future installation of pinhole cameras in the entry stations, exit stations, and POF. 24. Is the city aware that using an EMV solution will increase credit card transactions beyond 4 seconds? Response: The requirements state that the equipment and software have the ability to be upgraded to enable EMV compliant credit card processing. EMV readers are not required at this time but are acceptable if they are the proposer s preferred method of credit card processing. If proposing EMV readers please provide anticipated average credit card processing transaction times. 25. Can validations be used for just the garage where the ticket originates from? Response: Validations created by the PARCS to be configurable to be used in one specific garage or multiple garages. Offline validators to be programmed to validate tickets from one garage or multiple garages. Configuration of offline validators to be determined after contract award. Page 6 of 12

7 PROJECT NUMBER: PAGE Is there a requirement for the AVI to be either passive or active? Response: Passive tags are preferred but the PARCS vendor should propose their best value solution for transponders that meet the requirements of 2.6.Q Please clarify the type of data infrastructure that will be provided to connect to the main control center. Please also confirm that this will be provided by the City of Culver City. Response: Currently, City provided DSL lines are available at each garage. Proposals should include any additional communication infrastructure or lease lines needed to accommodate the proposed PARCS. All costs, including any reoccurring costs, to be outlined in the proposal. Reoccurring costs to be passed through to the City. The City is in the process of a City-wide fiber project that may accommodate connectivity to the garages in the future but the PARCS proposals should assume that fiber connections will not be available prior to the implementation of the new PARCS. 28. Please confirm that the parking attendant booths will be removed and hauled away by the successful bidder. (Confirm that the city does not want to retain them). Response: Yes, Contractor to remove and dispose of cashier booths. PARCS vendor to coordinate with the City to give the City the opportunity to salvage any equipment before the booths are removed. 29. Please confirm that the required concrete to fill in the cavity left over from the removal of the attendant booths including conduit modifications and electrical enclosures will be provided by the successful bidder. Response: Confirmed. Contractor is responsible for any required infrastructure modifications. 30. Please confirm whether all garages will be operational and accessible 24/7. Are there security gates and when would they be used? Should the bidders also provide afterhours access to monthly parkers and visitors via proximity access cards and barcode readers? Response: The security gates need to be controlled by the PARCS system via a credential. The gates will otherwise be controlled by the parking manager and/or a timer. Accommodating after hours parkers will require additional PARCS hardware to activate the gate for authorized after hours users, as there is not currently PARCS equipment outside the security gates. The City currently has a contractual arrangement with a downtown hotel to allow valet parking in the Ince structure. This valet parked cars will not be equipped with AVI technology, requiring proximity card readers. Additional PARCS hardware required includes 5 AVI readers and 3 proximity card readers at the following locations: One (1) AVI reader at the Watseka Garage installed outside of the entry side of the security gate. One (1) AVI reader at the Cardiff Garage installed outside of the entry side of the security gate. Total of three (3) AVI readers and three (3) proximity card readers at the Ince Garage. One (1) AVI reader and one (1) proximity card reader outside of the entry side of each security gate. Use cases for the interface with the existing rolling security gates are as follows: Page 7 of 12

8 PROJECT NUMBER: PAGE 8 Watseka and Cardiff Garages - One rolling gate controls the single entry and exit point. Authorized users access the structure after hours via AVI transponder that is used to operate the gate and then used again to gain entry through the PARCS entry lane. Upon exiting, the user s AVI transponder is used at the PARCS exit lane to vend both the PARCS barrier gate and the rolling security gate (when closed). Ince Garage - Three entry rolling gates and three exit rolling gates in total. Two entry and one exit gate on Culver Boulevard and one entry and two exit gates on Washington Boulevard. Authorized users access the structure after hours via AVI transponder or proximity card that is used to operate the gate and then used again to gain entry through the PARCS entry lane. Upon exiting, the user s AVI transponder or proximity card is used at the PARCS exit lane to vend both the PARCS barrier gate and the rolling security gate (when closed). Proposers to adjust the quantity of equipment on the Price Proposal form and add any additional software cost, if necessary, to accommodate the functionality described above. Proposers may additionally provide an alternative solution to support the required valet parking access at Ince that does not require proximity cards, but must include the proximity card solution in base pricing. 31. Should the bidders provide the recommended equipment protection bollards where required? Response: Yes. 32. Please confirm that all civil work - electrical and low voltage conduit (including electrical service where non-existent and needed to support the proposed upgrades) and concrete island/concrete modifications will be provided by the successful bidder. Response: Confirmed. Contractor is responsible for any required infrastructure modifications. 33. A. Agreed Upon Procedures (AUP), System Characteristics 10. Provide an interface that allows the occupancy data recorded by the PARCS to be disseminated to City websites, 3rd party websites, and the City s PGS. Question: What type of file would these systems require to import and display the occupancy count statistics? Please provide names and details of the systems that the PARCS should interface with. Response: All use cases related to occupancy data are not defined at this time. As described in Section the Contractor is to provide a system that uses standard APIs. Proposers should include a description of their API and the available methods for exporting data (including available file formats) from the PARCS database. 34. A. Agreed Upon Procedures (AUP), System Characteristics 11. Provide an interface that verifies METRO transit ridership for discounted parking sessions at a cap of 235 parkers per day. Question: What is the media to be used to validate Metro parkers? Is there a mag-stripe/barcode/proximity card that will be present for this transaction? Would this be issued in the form of a chaser coupon or other validation method? Please provide specifics of this feature desired, and how it should work. Response: Page 8 of 12

9 PROJECT NUMBER: PAGE 9 Media used to validate Metro ridership is the Metro TAP card. ISO/IEC Type A compliant smart cards and hardware shall be able to read/ Mifare Classic cards. At this time no chaser tickets or other validations are intended to be used for verification of Metro ridership A parking patron is considered a transit user if they use the system, or transit provided by other systems using a TAP card, within 96 hours of parking at a Metro Transit Parking facility. The time period of 96 hours can occur prior to or after the patron parks their vehicle. TAP card readers will be installed on the pay machines and will allow the automated parking management system to verify transit ridership. Transit patrons can simply present their TAP card at the pay machine. Once the TAP card is read, the last transaction will be identified. If that transaction happened within the last 96 hours, the patron is eligible for the transit patron parking rate. Metro has successfully interfaced with our pay station provider. Here are specs needs to interface with METRO TAP card identifier engine software: 1. Have the ability to save a TAP card holder s registered plate detail 2. Ability to access the World Wide Web 3. Have the ability to retrieve a TAP card holder s registered plate details so they do not need to re-enter plate details every time they park 4. Have the ability to produce an optional paper receipt or downloadable electronic receipt. 5. Ability to handle, send and consume JSON data structures. 6. Communication speeds of at least 2.0 mbs (wireless communication preferable) 7. Ability to handle SSL authentication, using the latest standard protocols, with the ability to update if standards change. 8. Read TAP Card in the near field (when presented) NFC Card reader specs as below: ISO/IEC Type A compliant smart cards and hardware shall be able to read/ Mifare Classic cards 9. Decline transactions based on Business Processing Rule software program (BPR) black list data 10. Communicate TAP Card data, Credit card data or payment data to the BPR API 11. Accept web based responses from BPR API 12. Handle exception processing from the BPR, such as alternative rates and unpaid transactions. 35. B. Project Requirements 26. X-Ray All Lanes before saw-cutting. Question: Is radar an acceptable substitution for X-ray? Response: Yes, GPR is acceptable Page 9 of 12

10 PROJECT NUMBER: PAGE Proposal Submittals E. Product Data Submittals 11. System Fault Tolerance Description Question: What specifically is required for this section? Are there specific statistics that you are looking for? Response: Proposer to provide a narrative, statistics, diagrams, or any other relevant information describing the characteristics of the proposer s PARCS design that limits the risk of single point of failure from an equipment and software perspective. 37. Will a static IP internet connection be provided at each of the parking facilities for the new PARCS use? Response: Yes, there is a static IP address for each structure provided via a DSL line. If additional connectivity is needed it will be the responsibility of the PARCS vendor to provide the appropriate connectivity and pass along the cost to the City Equipment and Subsystems, L. Uninterruptible Power Supplies (UPS) Questions: Would gates with Power Fail Operation be sufficient for ingress/egress during a power failure? Would emergency power be available at any of the parking facilities? If a UPS battery is required for each entry/exit lane and POF, wouldn t there be a total of 39? Response: UPS is required at each lane and POF for a total of 35. The four reversible lanes have two sets of equipment that share one UPS. If the proposed POF contain an internal UPS then the proposer may modify the quantity of UPS in the price proposal form as needed. Emergency power via a generator exists at the Ince parking structure Equipment and Subsystems, N. Multi-Space Meter, 9. Card Reader, b. Credit Card Approval System 7) Confirm and provide record formats required by Owner s financial institution. Question: What record formats are required by Owner s financial institution? Please specify. Response: Record format will depend on the City s selected credit card processor 40. For Cardiff, Watseka, Ince and City Hall garages, please provide drawings. Response: See City website for available drawings 41. RFP, III B.4 & B9 6 & 7 III B.4 calls for design of infrastructure modifications and III B.9 calls to provide infrastructure modifications. This specification is extremely open-ended and raises the potential for huge discrepancies in bid amounts. Can the City provide more direction in terms of locations, requirements and or specifications for this item? Response: The City is requesting proposers include all civil and infrastructure work required to support the proposed PARCS, in conjunction with City approval and permitting. The City understands the infrastructure requirements and lane layouts are unique to each proposer s PARCS so it is the responsibility of the proposer to determine what infrastructure work will be required to accommodate their PARCS. 42. RFP, II B 4 How is the PARCS system to integrate with the PGS and DMS? What functions need to be integrated? Response: All use cases related to occupancy data and the PGS are not defined at this time. As described in Section the Contractor is to provide a system that uses standard APIs. Proposers should include a description of their API and the available methods for exporting data (including available file formats) from the PARCS database. Page 10 of 12

11 PROJECT NUMBER: PAGE RFP, III A.3 5 Are the costs for software upgrades to keep the system in PCI DSS compliance a part of this proposal? Response: Yes. The PARCS application should be PCI compliant through the life of the system. Per 2.6.C.1 of Section no Contractor provided product or solution will prevent the Owner from achieving PCI compliance in its parking operation 44. RFP, III B.4 & B9 6 & 7 III B.4 calls for design of infrastructure modifications and III B.9 calls to provide infrastructure modifications. This specification is extremely open-ended and raises the potential for huge discrepancies in bid amounts. Can the City provide more direction in terms of locations, requirements and or specifications for this item? Response: The City is requesting proposers include all civil and infrastructure work required to support the proposed PARCS, in conjunction with City approval and permitting. The City understands the infrastructure requirements and lane layouts are unique to each proposer s PARCS so it is the responsibility of the proposer to determine what infrastructure work will be required to accommodate their PARCS. 45. RFP, III B.5 & B.6 6 & 7 What are the locations at each site from which power and communications wiring will be derived? Plans of the various sites would be helpful. Response: See City website for available drawings 46. RFP, III B.16 7 What Owner supplied equipment will we be required to interconnect with? Response: See 2.1 of Section for Owner Supplied and Existing Products 47. Spec, E1.e & f 5 When is the pending construction for the Parcel B Garage and the Market Hall Garages scheduled. Will these installations proceed as part of the initial installation or will they be installed as part of a second phase? Response: Construction of the Parcel B garage is expected to commence in the next days so the PARCS installations will occur prior to the completion of construction. Construction of the Market Hall garage is expected to commence in nine to 12 months so the PARCS installation will occur as part of a second phase. 48. Spec, E What structures are post-tensioned, that will require GPR prior to installation? Response: For any PARCS equipment locations that require cutting or penetrating any non-grade level deck structure the Proposers should anticipate utilizing X-ray or GPR to detect potential obstructions in the slab, including post tension cables. 49. Spec, F1 8 What PGS system will be deployed by the City? Response: The City is in the process of selecting a PGS vendor with the anticipation that the selection process will be complete by 7/11/ Spec, E.2b 10 Are there any special features required for the barrier gates? ie. lighted arms, breakaway options, audible alarms etc.? Response: See 2.6.J in Section for required barrier gate features and functionalities 51. Spec, E.2h 10 Pinhole cameras are indicated. Are cameras required at equipment locations? Response: Pinhole cameras are not required at this time but the City may elect to add pinhole cameras to PARCS devices in the future. Proposers to provide an Page 11 of 12

12 PROJECT NUMBER: PAGE 12 affirmative statement of their ability to support the use of pinhole cameras and ability retrofit the PARCS devices with pinhole cameras. Proposers should also provide and install any spare communication cabling, if necessary, to support the future installation of pinhole cameras in the entry stations, exit stations, and POF 52. Spec, E.2n & o 10 AVI readers and transponders are indicated as ADD/ALTERNATES but appear on the PARCS Price Proposal Form as a Base item. Are the AVI readers and transponders to be included in the Base proposal or as an ADD/ALTERNATE item? Response: AVI system to be part of the base proposal. 53. RFP, III A.11 6 Please provide more specific detail and description of integration required for METRO cards. Response: Please refer to response Nos. 9 and 34 above. End of Addendum #2 Page 12 of 12