RFI 17-08-267 September 8, 2017 To: All Interested Bidders RE: Memorandum 1 All vendors are to accept the information contained herein as the official response of IPTC. TO ALL INTERESTED BIDDERS AND TO WHOM IT MAY CONCERN: This Memorandum is being issued prior to the Award Announcement. This memorandum is sent to inform interested bidders of procedural changes for RFI 17-08-267 Modernization of IPTC Fare Vending System. Please review responses to questions presented to IPTC Procurement for RFI 17-08-267. IPTC encourages all interested bidders to participate in this Request for Information by submitting their letter of interest by 10am on Friday, September 29, 2017. If there are any questions or concerns about the request, please send them via email to procurement@indygo.net Thank you for your interest in doing business with IndyGo.
1). We would like to thank you for this opportunity to present our industry-leading solutions to the IPTC. However, our team feels that a short extension would support our efforts in putting forward the quality of response that you are expecting. We respectfully request that the deadline for RFI 17-08-267 Modernization of IPTC Fare Vending System, be moved to September 29, 2017 at 10am? IPTC Response: Confirmed, moved to September 29, 2017 at 10am (est). 2). What is the estimated cost of the Modernization of Fare Vending System project? IPTC Response: This has not been officially determined and, to some degree, may depend upon feedback received through this RFI process. 3). Has the IPTC allocated funding for the Modernization of Fare Vending System yet? If so, through which source (budget, CIP, state/federal grant etc.)? IPTC Response: IPTC has included resources for this solicitation in its draft internal five-year capital plan. IPTC anticipates funding this effort through a mix of resources derived from grants and its Capital fund. 4). How is the IPTC currently meeting this need? Which vendor provides the incumbent Modernization of Fare Vending System? IPTC Response: IndyGo currently uses SPX Genfare Odyssey fareboxes for its fixed route coaches. These fareboxes accept coins, bills, and magnetic fare cards. There have been no adaptations to these fareboxes to accept smartcards or contactless technologies. 5). Would it be possible to name the three greatest challenges the IPTC is having with the current solution? IPTC Response: IPTC has not collectively defined the three greatest challenges with current technologies. Through its fare study, IndyGo articulated a desire that the fare system be modernized in such a way that 1) promotes ease of use for riders; 2) promotes intra-agency coordination across services (rapid, local, paratransit); 3) secures operational efficiencies (e.g., reduce cash collection, minimize coach operator role in fare collection); and 4) improves IPTC data collection capabilities.
6). Should the IPTC decide to proceed past the RFI process, has a time frame been established in which an RFP may be issued? IPTC Response: A final timeline has yet to be determined, but IPTC anticipates moving forward with an RFP toward the end of 2017 or in the first quarter of 2018. 7). Which other systems will have to integrate or interface with the Modernization of Fare Vending System, and will IPTC provide incumbent vendors for each system? IPTC Response: IndyGo currently uses SPX Genfare Odyssey fareboxes for its fixed route coaches. These fareboxes accept coins, bills, and magnetic fare cards. There have been no adaptations to these fareboxes to accept smartcards or contactless technologies. The feedback received through this solicitation will help IPTC determine its course of action as to whether any vendors procured through this solicitation would provide a standalone service and/or whether it might interface or integrate with existing technologies. 8). Which operating platform does the IPTC currently use? / Is desired for the Modernization of Fare Vending System? IPTC Response: IndyGo currently support the Windows 10 Operating System for Clients and Windows Server 2016 for Application hosting. Databases must be compatible with Microsoft SQL Server 2012 v11 and above. It is IndyGo s desire to maintain databases in MS SQL Server 2014 v12 and above.
9). Can the IPTC elaborate on any additional drivers behind this acquisition that may not be addressed in the RFI? IPTC Response: As part of its internal fare study process, IPTC identified the following goals associated with modernization of the fare system: 1) promotes ease of use for riders; 2) promotes intra-agency coordination across services (rapid, local, paratransit); 3) secures operational efficiencies (e.g., reduce cash collection, minimize coach operator role in fare collection); and 4) improves IPTC data collection capabilities. These efforts should be accomplished in such a way that 1) maintains or increases revenue and/or ridership; 2) ensure equity of access and opportunity for all users; 3) be able to be communicated to and accepted by the public (inclusive of policy changes); 4) and ease enforcement of fare policy. 10). What is the number of users anticipated for the Modernization of Fare Vending System? IPTC Response: Due to data collection constraints associated with the current system, IndyGo does not have an accurate estimate of the number of unique individual users of its current system. Therefore it is hesitant to offer an estimate of the unique number of users it anticipates. IndyGo totaled 9.2 million rides on its fixed route service and approximately 300,000 rides on its paratransit service in 2016. With the planned service expansion through 2022, preliminary estimates suggested an anticipated annual ridership of approximately 17 million rides. 11). Who is the technical contact and/or project manager for the Modernization of Fare Vending System? IPTC Response: John Marron, Director of Strategic Planning, is coordinating IndyGo s fare study and its exploration of potential changes to the fare system. This effort includes representatives across IndyGo departments. The IndyGo Procurement office should remain the primary point of contact for anything related to this solicitation
12). Have you had any external assistance preparing this RFI? IPTC Response: NO 13). Does IPTC anticipate procuring any services related to the effort? For example: IV&V, QA, Staff augmentation, integration, solicitation prep, etc. If so, what, when and how? IPTC Response: The need for additional services will be evaluated depending upon responses to the RFI and a final determination of direction of IPTC s fare modernization strategies. Depending upon the complexity of the solution relative to what is currently deployed across IndyGo services today, IndyGo may seek additional services to assist with implementation, verification, quality assurance, and other related services. 14). Whether companies from Outside USA can apply for this? (like, from India or Canada) IPTC Response: Companies outside the US may provide information related to this RFI and may respond to any subsequent solicitations related to fare modernization 15). Whether we need to come over there for meetings? IPTC Response: A respondent does not need to be physically present to respond to this RFI. 16). Can we perform the tasks (related to RFP) outside USA? (like, from India or Canada)? IPTC Response: Companies outside the US may provide information related to this RFI and may respond to any subsequent solicitations related to fare modernization. Depending upon IPTC s selected funding source for any future procurements related to this project, Buy America requirements may be in effect. 17). Can we submit the proposals via email? IPTC Response: Submission Requirements will remain the same as listed inside of RFI.
18). Does ITPC want a Multi-Client system or single client system? IPTC Response: IPTC will entertain responses for either approach. If the respondent has a preferred approach, please outline the benefits of the approach being presented 19). If multi-client system would there be a settlement and/or clearing in case of multiple bus operators? IPTC Response: IPTC will look to vendors to provide input on optimal solutions based on unique configurations. If the respondent has a preferred approach, please outline the benefits of the approach being presented and/or any additional requirements necessary to make the fare system functional based on a proffered configuration 20). Will there be an interface to an existing CAD/AVL-system, e. g. for single driver log on? If so does your CAD/AVL vendor have an open API and/or will vendors need to contract with that vendor directly? IPTC Response: IndyGo is currently in the process of procuring a new CAD/AVL system. Specifications are not yet available. Respondents are encouraged to listed any additional requirements necessary to make the fare system functional based on any system and/or configuration. 21). It is assumed, that fare boxes will not be part of the procurement is this correct? IPTC Response: IPTC has not categorically excluded the purchase of new fareboxes as part of any future procurement; however, it would look favorably upon cost-effective solutions that could be adapted to or with existing infrastructure 22). Will there be an interface to an existing fare box system? If so does that vendor have an open API? IPTC Response: IndyGo currently uses SPX Genfare Odyssey fareboxes for its fixed route coaches. These fareboxes accept coins, bills, and magnetic fare cards. To IndyGo s knowledge the vendor does not have an open API
23). Is the new system separate from the existing system and starts from scratch or will there be somehow a migration from current technology to new technology? (e.g. re-use of existing cards, data). If re-use does that system have open APIs or is it a proprietary system? IPTC Response: IndyGo is interested, through this RFI, in exploring varying approaches to integrating a new system with the existing system. Ideally, the new system would be introduced and be able to operate in manner that is relatively independent of the current system (or seamlessly integrate with the existing system). The existing system could then be replaced in stages as new media and payment options are adopted by ridership. IndyGo understands that there will need to be a transition plan in place for integrating the new technology; however, until a solution is selected, it is premature to define that transition plan. IndyGo currently uses SPX Genfare Odyssey fareboxes for its fixed route coaches. These fareboxes accept coins, bills, and magnetic fare cards. To IndyGo s knowledge the vendor does not have an open API. 24). Will fare policy including rules for electronic fares (e.g. for transfers, capping) available? IPTC Response: It is anticipated that IPTC fare policy will include rules for electronic fares such as transfers and/or fare capping. Final decisions related to fare policy have not yet been reached 25). What is considered for reporting (reports, database)? IPTC Response: IPTC would prefer to have the ability to select predefined reports, import/export functionality, and access to data. IPTC will look to respondents to this RFI for information on capabilities of any system s ability to provide data to IPTC users across formats 26). What is considered for export and import interfaces? IPTC Response: IPTC is interested in understanding what is possible and current with respect to export and import interfaces. At a minimum, IPTC would expect to be able to query the database and export CSV reports of system data.
27). What is considered for accounting and bookkeeping (e.g. Sage)? IPTC Response: IPTC is in the process of implementing a new ERP system that will handle accounting and bookkeeping. Details associated with this system are not yet available. 28). Is hosting for the IT-system considered? IPTC Response: Yes. A hosted solution is acceptable where the vendor can provide a true, geographically distributed data center model and provide stated availability (uptime and performance) SLA s. 29). It is assumed, that 3G/4G coverage is given, where buses operate Is this correct? IPTC Response: Yes, 3G/4G coverage is available where buses operate within Marion County 30). Contactless credit cards for open payment are these for common use easily available in the area? IPTC Response: Contactless credit cards exist within the area; however, the solution would need additional components beyond the use of contactless credit cards to be serviceable. Per IPTC s 2016 Ridership Survey, more than 30 percent of IPTC riders had neither a credit card or a debit card 31). Are there any considerations for closed loop cards? IPTC Response: While IPTC prefers the adaptability of open payment solutions, it will consider closed loop cards. Vendors are encouraged to discuss the benefits of their solution relative to that which was expressed in the RFI, if different. Should a vendor propose a closed loop solution, they are encouraged to discuss how the system could remain adaptable to future partnerships with colleges and universities, workplaces, other transit providers, or other third parties. See response to Question 41 for additional comment on consideration of desirability of open-loop architecture.
32). Any considerations for use of virtual cards on smart phones (e.g. google wallet/apple pay)? IPTC Response: Virtual cards on smart phones will be considered. Per IPTC s 2016 Ridership Survey, 76.9 percent of respondents indicated that they had smartphone. However, IPTC serves a sizeable unbanked or underbanked population as well; and therefore, vendors are encouraged to discuss how virtual cards on smart phones will fit within a broader, more comprehensive fare modernization solution 33). Are there any considerations for 2D Barcodes on paper as a cheap fare media vs. issue from a complex, expensive fare boxes? IPTC Response: 2D barcodes on paper as a cheap fare media will be considered. Vendors are encouraged to discuss the benefits of this approach relative to other approaches. Vendors are also encouraged to discuss ways in which the system can be established to prevent fare evasion or the unauthorized transfer of paper tickets if the issued ticket provides for multiple rides within a time period. Vendors are encouraged to discuss how these fare media will fit with a broader, more comprehensive fare modernization solution. 34). Is it correct, that the following distribution channels will be required? Validators on bus TVMs and validators on platforms Website Kiosk terminal (sales only) Service center terminal (sales and administration) Mobile ticketing APIs for use and product selling by 3rd parties? IPTC Response: At a minimum, the modernization of IPTC s fare system will require TVMs and validators on platforms and service center terminal sales and administration. It is preferred that patrons also be able to service their account through a website and present a mobile ticket (ideally linked to their account) to a coach operator or fare inspector. Depending upon the final configuration of the fare system and selected fare media and technology IPTC anticipates that onboard validators, kiosk terminals, and APIs to enable third party sales may be included to support convenience and ease of access for riders, but such will be depending upon the final configuration of the system
35). It is assumed, that there will be customer accounts on the system where customers can administer their cards? IPTC Response: An account-based solution where customers can access and administer their account(s) is preferred 36). Is post payment for contracted customers considered? IPTC Response: IPTC is considering post payment as a fare policy; however, such is dependent upon the capabilities and configuration of the selected solution. Should such functionality be available within the selected system, it is likely IndyGo would allow accounts to go negative to a certain threshold and/or allow an additional ride before hot listing accounts or front end devices. 37). Would third party retail networks be contracted separately and the selected vendor would need to provide an API to integrate the product? IPTC Response: The need for and scope of the integration of third-party retail networks into the fare system will be determined in part by responses to this RFI. Comprehensive solutions that can serve to modernize IPTC s fare payment system and serve a third-party vendor network is preferable. Joint responses of two vendors who can work together to provide a comprehensive solution may also be serviceable. Absent a comprehensive solution or a joint venture, APIs would need to be provided to integrate these functions. 38). Will ITPC allow vendors to present prior to issuance of RFP their solutions? IPTC Response: IndyGo may engage, ask questions, or request presentations of various respondents or other vendors prior to the issuance of an RFP, either as follow up to this RFI or in search of other information
39). For off-board fare collection, can IndyGo provide further detail on what size TVM footprint they require? Are cashless TVM s required? Or is IndyGo looking for a mixture of cash and cashless TVM s? IPTC Response: TVMs will primarily be installed on the platforms of IndyGo s Bus Rapid Transit network. The stations were designed to house TVMs with the following dimensions: 10 deep by 17 wide by 69 tall; the recessed area for the smallest of the station configurations measures 13 deep and 54 wide (will also need to house the validator within the recess). IndyGo will pursue a uniform set of TVMs at its bus rapid transit stations. The decision of whether the TVMs will universally accept cash or be cashless is pending a fare equity analysis that will be conducted at the conclusion of this RFI. Depending upon the comprehensive fare solution, IndyGo may consider TVMs of greater size and functionality for location at the Julia M. Carson Downtown Transit Center and/or a modest number of other key locations throughout its service area. 40). Can IndyGo provide a timeline for the procurement and implementation schedule for the proposed modernization of the IPTC Fare Vending System? IPTC Response: IndyGo anticipates issuing an RFP to procure a comprehensive fare vending system either later this year or very early in 2018. The implementation of a modernized fare system may be implemented in phases, depending upon the varying dimensions of a selected system (or systems). At a minimum, TVMs to support the operation of IndyGo s BRT system must be operational no later than February 1, 2019, to allow for adequate testing and system startup and to coincide with the opening of the Red Line Bus Rapid Transit system. Ideally, infrastructure that would support the realization of any benefits from a change to IndyGo s fare policies (such as fare capping or transfers within a period of time) would be implemented at the same time. Other components may be phased in over time before, during, and after those milestones. Depending upon the complexity of the solution (or solutions) selected, the degree of integration required between these systems, and phasing of implementation relative to taking legacy systems down (if required), IndyGo may consider project management and oversight associated with this effort as well. IndyGo encourages vendors to propose guidance on the time required to implement solutions as part of this RFI.
41). For an Open Payment architecture, can IndyGo provide further clarification or detail on payment preferences? Is IndyGo looking for use of credit cards as payment onboard the bus? IPTC Response: IndyGo does not envision credit card payments being the sole form of cashless payment on the bus. Open loop systems are preferred for the adaptability of that approach and in that credit cards or mobile payments by phone may be adapted into the system in the future, if desired. Vendors are encouraged to discuss the benefits and drawbacks of the open-loop architecture relative to other approaches that they may proffer. See response to Question 31 for additional comment on consideration of closedloop approaches 42). Please provide a breakdown of pass sales (by pass type) and cash fare payments for the past year? IPTC Response: Per IndyGo s 2016 Ridership survey (available here)
43). Does IPTC currently have a computer aided dispatch (CAD) and/or automated vehicle locator (AVL) system on its fixed route, BRT or paratransit vehicles? If yes, please provide the name(s) of the provider(s)? IPTC Response: Currently IndyGo maintains CAD AVL on Fixed Route and Paratransit fleets. The current provider of those services is Trapeze through Transit Master for Fixed Route and PASS 12 for Paratransit. IPTC currently has a solicitation for Intelligent Transportation Systems to replace its current CAD/AVL system (see RFP here). It is the desire through the current solicitation to move all IndyGo vehicles to an upgraded or new ITS (CAD AVL) solution by Q2 2018. 44). Please provide a list of the fare collection and ITS equipment currently installed on buses and paratransit vehicles and on BRT platforms and the providers of that equipment? IPTC Response: IPTC s first BRT corridor is not yet operational. The selected system would serve as the first fare system to be used in IndyGo s BRT environment, and as such, there is extra consideration being given into how the system is interoperable between the future BRT network and the local fixed route network. IndyGo currently uses SPX Genfare Odyssey fareboxes for its fixed route coaches. These fareboxes accept coins, bills, and magnetic fare cards. There have been no adaptations to these fareboxes to accept smartcards or contactless technologies. Currently IndyGo maintains CAD AVL on Fixed Route and Paratransit fleets. The current provider of those services is Trapeze through Transit Master for Fixed Route and PASS 12 for Paratransit. IndyGo is currently in the process of procuring a new ITS system. 45).Do your fixed route or paratransit vehicles have an onboard, cellular modem? If yes, provide the make and model for that(those) device(s)? IPTC Response: The Cellular devices to be used are currently under contract negotiation. The devices identified at this time for Fixed Route are Paratransit will use the same router, however Wifi will not be provided on Paratransit vehicles
QTY ITEM 5-in-one antenna (WAAV ANT-4006-1 0000) 2 4G LTE-A cellular modems WiFi rubber duck antenna (included 4 with XA router) 1 AirBox X2A router 46).Is there WiFi available to vehicles when they are parked in the depot(s)? at Carson Transit Center? IPTC Response: IndyGo maintain a wireless network at Headquarters throughout the facility, garage and bus storage area as well as the Julia M. Carson Transit Center. Buses today, do not connect to or receive updates through the network at the Transit Center. IndyGo also maintains a wireless network for Paratransit vehicles located at MV Transportation. 47). How many vehicle depots are operated by IndyGo? IPTC Response: IndyGo currently operates one operations and maintenance facility. In the future, IndyGo may expand its operations and maintenance to a second facility 48). What is the current (or planned) number of BRT inspectors? IPTC Response: This has not yet been determined, and may change over time as additional BRT lines commence operations (Red Line, 2019; Purple Line 2021; Blue Line 2022). 49). What technologies, if any, do (or will) the BRT inspectors use to validate passengers tickets and passes? IPTC Response: IndyGo s BRT system is not yet operational. It is anticipated that the inspectors validators would be procured as part of the solicitation that follows this RFI.
50). Does IndyGo intend to do a single RFP for fare collection or will there be multiple procurement opportunities? Example: Mobile Ticketing will be its own separate RFP? IPTC Response: Such will be determined as a result of this RFI process and a conclusion reached by IndyGo management on a preferred direction for a comprehensive solution or a suite of integrated solutions. IndyGo prefers a comprehensive solution and/or a suite of solutions that are designed to be seamlessly integrated and compatible; however, should such not be available in a manner that is deemed preferable, IPTC may pursue separate procurements for the component parts that would comprise a comprehensive solution. 51). What is Indy s timeline for future fare collection procurements? IPTC Response: IndyGo anticipates issuing an RFP to procure a comprehensive fare vending system either later this year or very early in 2018. The implementation of a modernized fare system may be implemented in phases, depending upon the varying dimensions of a selected system (or systems). At a minimum, TVMs to support the operation of IndyGo s BRT system must be operational no later than February 1, 2019 to allow for adequate testing and system startup and to coincide with the opening of the Red Line Bus Rapid Transit system. Ideally, infrastructure that would support the realization of any benefits from a change to IndyGo s fare policies (such as fare capping or transfers within a period of time) would be implemented at the same time. Other components may be phased in over time before, during, and after those milestones. Depending upon the complexity of the solution (or solutions) selected, the degree of integration required between these systems, and phasing of implementation relative to taking legacy systems down (if required), IndyGo may consider project management and oversight associated with this effort as well. IndyGo encourages vendors to propose guidance on the time required to implement solutions as part of this RFI..
52). What level of PCI certification will be required for fare collection vendors? Will the fare collection vendor require this certification directly or through a 3rd party payment processor? IPTC Response: PCI certification/requirements will be defined by IndyGo Finance and Accounting Divisions. These requirements are not yet available and may vary upon selected fare system.