Specifications include, but are not limited to: The system will consist of two components: a back office for management of the system and reporting on usage and a mobile application for use by the riders. The mobile application will be available on the Android and iOS mobile platforms. The procured application and supporting system will be developed in the Software as a Service (SaaS) architecture. That is, the chosen vendor will have a single application and a single instance of the back office across all their installations of the system. User access controls will ensure that each agency using their application will have control over only their system and view only their data. The vendor will manage all payment transactions, with financial settlements clearing into the designated BFT account no less frequently than once a day. A “transaction” is defined as a single payment for the purchase of one or more fare products. As part of the SaaS model, BFT expects to pay for the system on a per transaction basis, with a percentage of the tickets and passes purchased being withheld before the balance clears into the BFT designated account. BFT has a number of discounted and free offerings where a mobile ticket would also be useful and expects to pay low to no cost for these passes. Beyond the cost of non-recurring expenses incurred from specific customizations required, BFT does not expect to pay up front costs.