NEORide_SaaS_Price_Sheet_Addendum_11022026.xlsx
XLSX spreadsheet 19 KB Posted
- Solicitation number
- 2026-RFP -3
- Issued by
- Summit County, Ohio
About this file
This price sheet addendum is related to NEORide's Regional Council of Governments procurement for a Software-as-a-Service (SaaS) Mobility Platform supporting microtransit, paratransit, and turnkey transportation services across 13 states. The document establishes pricing structures for core system components including a central dispatch and administration application, vehicle and rider-facing applications, reporting platform, demand response transit systems, specialized ADA/paratransit functionality, and required integrations with EZFare, GTFS Flex, and EZConnect mobility center. For evaluation purposes, proposers must price implementation for one participating agency with 50 active vehicles across a 36-month period following final system acceptance, with the NEORide-wide fleet totaling 210 active vehicles that determines the applicable Tier 2 pricing rate. All proposals are due November 20, 2026 at 4:00 p.m. EST, and the contract term is three years commencing in 2027 with up to two one-year renewal options.
Pricing must be submitted as fixed one-time implementation costs and recurring monthly SaaS fees per active vehicle calculated at the Tier 2 rate (101–300 total vehicles across all NEORide participating agencies), with tier rates ranging from Tier 1 (1–100 vehicles) through Tier 4 (601+ vehicles). The price sheet specifies that all required recurring costs—including software, licensing, hosting, maintenance, support, integration maintenance, training, and disaster recovery—must be bundled into the per-active-vehicle monthly fee, with the contractor bearing all third-party service costs and usage risk. Optional services available at additional cost include refresher training, test environment access, custom reports, alternative payment processing, and usage-based telephony and SMS. Annual price adjustments are governed by the Master Service Agreement Section 5 and capped at the lesser of 3% or the USA Consumer Price Index average. Services are funded through a 1% administrative fee on actual contractor sales to participating agencies, with billing flowing directly between contractors and customer agencies rather than through NEORide.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Microtransit,_Paratransit_and_Turnkey_Transportation_Services_(Addendum_#3_Revision).pdf | ||
| NEORide_MSA_w_Tracked_Changes_Addendum_.docx | DOCX document | |
| NEORide_Turnkey_Price_Sheet_Addendum_11022026_FleetSize.xlsx | XLSX spreadsheet | |
| Microtransit,_Paratransit_and_Turnkey_Transportation_Services.pdf | ||
| NEORide_SaaS_Requirements.xlsx | XLSX spreadsheet | |
| NEORide_Tunkey_Service_Price_Sheet.xlsx | XLSX spreadsheet | |
| NEORide_SaaS_price_sheet.xlsx | XLSX spreadsheet | |
| NEORide_microtransit_turnkey_Requirements.xlsx | XLSX spreadsheet | |
| NEORide_Mobility_Platform_and_Turnkey_SOW.pdf | ||
| Sample_Participation_Agreement.pdf | ||
| Sample_MSA_.pdf |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
One Time Costs
| Core System Components | |||||
| # | Cost Items | Fixed One-Time Costs | |||
| (NTP to System Acceptance) | Allocated 3-year SaaS price for the Evaluation Agency | ||||
| 50 active vehicles × 36 months at Tier 2 | Notes | ||||
| 1 | Core Mobility Platform | ||||
| Central dispatch and administration application | |||||
| Vehicle/Operator application | |||||
| Rider facing applications (mobile and web) | |||||
| Reporting platform | |||||
| 2 | Demand Response Transit/Microtransit System | ||||
| Microtransit service configuration | |||||
| Microtransit trip booking and management | |||||
| Microtransit trip brokerage and third-party provider management | |||||
| 3 | Specialized ADA/Paratransit System | ||||
| Eligibility application automation | |||||
| Registration and customer database | |||||
| Operations management | |||||
| Funding source and billing code management | |||||
| Same day paratransit scheduling capability | |||||
| 4 | Integration | ||||
| EZFare Integration | |||||
| GTFS Flex and Trip Planning Integration | |||||
| EZConnect mobility center integration (Amazon Connect telephony and Salesforce CRM) – shared NEORide-level work, priced once | |||||
| 5 | Project Implementation | ||||
| Project Management | |||||
| Design | |||||
| Configuration and Testing | |||||
| Documentation and Training | |||||
| Data Migration | |||||
| Grand Total | $0.00 | $0.00 | |||
| Evaluated Mobility Platform price (3-year) | CALCULATED: fixed one-time Grand Total + Tier 2 monthly fee × 50 active vehicles × 36 months. This is the figure used for evaluation. | ||||
| Notes | |||||
| A | Fixed Implementation Prices include all required work and platform access from the applicable written Notice to Proceed through written Final System Acceptance, including project management, design, configuration, integrations, migration, documentation, initial training, acceptance testing and burn-in testing. No recurring SaaS fee is charged before acceptance. | ||||
| B | Year 1 is the twelve-month period beginning on each Participating Agency’s written Final System Acceptance; the evaluation covers the 36 months following that date. All required recurring software, applications, licenses, hosting, test environments, maintenance, support, integration maintenance, configuration, reporting, data access and required recurring training shall be included in the per-active-vehicle fee. | ||||
| C | Three-year SaaS pricing is requested to provide evaluators with a complete and comparable recurring cost of ownership for the required Mobility Platform over the 36 months following written Final System Acceptance, using the stated evaluation assumptions. It shall include all required recurring costs within the bundled per-active-vehicle fee. | ||||
| D | The 3-year SaaS price is requested to help NEORide evaluators understand and compare the total cost of providing the required Mobility Platform during the 36 months following written Final System Acceptance. | ||||
| E | For evaluation, assume one Participating Agency with 50 active vehicles and 210 active vehicles across NEORide. The NEORide-wide count determines the applicable Tier 2 rate; the agency’s 50 active vehicles determine its evaluated cost. | ||||
| F | Proposers shall calculate the evaluated SaaS price by multiplying the quoted Tier 2 monthly fee per active vehicle by 50 agency active vehicles and 36 months. | ||||
| G | Fixed implementation costs shall be reported separately and shall not be included again in the SaaS price. Evaluators will combine the fixed implementation total and the 36-month SaaS total to determine the cost of implementation and the first three years of system operation following Final System Acceptance (see the Evaluated Mobility Platform price below the Grand Total). | ||||
| H | The component allocations shall represent portions of the quoted bundled price, including all required recurring costs, and shall sum to the evaluated 3-year SaaS price (Tier 2 monthly fee × 50 × 36). They are not separately billable charges and need not represent the Proposer’s internal accounting costs. | ||||
| I | The Contractor bears the cost and usage risk for all required third-party services, including mapping, routing, geocoding, messaging, telephony and other APIs. Increased usage or changes in third-party pricing do not authorize additional charges beyond the contracted per-active-vehicle fee and expressly permitted contractual escalation. No separate trip, user, API-call or transaction-volume overages apply to required functionality. This does not apply where a Participating Agency elects the usage-based telephony/SMS pricing offered under Options. Telephony on NEORide’s EZConnect Amazon Connect instance is NEORide’s cost and is excluded. | ||||
| J | NEORide reserves the right to add or delete services or equipment quantities at the specified prices as needed throughout the term of the contract. | ||||
| K | Component allocations and underlying unit rates are provided for evaluation and transparency only. They do not authorize separate license, module, hosting, integration, user, trip, API or other recurring charges. Each cost shall be priced once. Actual SaaS invoices use agency active vehicles, the applicable NEORide-wide tier and agreed partial-month rules. | ||||
| L | No escalation is entered on this price sheet. Annual price adjustments are governed by MSA Section 5 and apply to all Participating Agencies on each anniversary of the MSA Effective Date. All prices are firm for the MSA term. | ||||
| Options | |||||
| S/N | Cost Item | Installed Quantity | Recurring cost | ||
| (per active vehicle / month) | Installed Unit Cost | Installed Total Cost | Notes | ||
| Refresher Training (beyond any required annual sessions) | 1 | ||||
| Test Environment | 1 | ||||
| Integration with TappPay Ride | 1 | ||||
| Custom Reports (per new report) | 1 | ||||
| Contractor-provided payment processing service (per transaction), if offered. Native payment functionality is core and included in the per-active-vehicle fee; third-party processor fees are passed through at cost (requirement 820). | 1 | ||||
| Usage-based telephony and SMS for IVR and AI-assisted booking (per minute and per message). State included usage and any minimum charge in Notes. Elective alternative to bundled pricing; see Note I. | 1 |
Options are not evaluated. Option prices are binding for Participation Agreements for the MSA term.
Operating Costs
| Operating Costs | ||||
| Tier | Total active vehicles across all Participating Agencies using the Contractor’s Mobility Platform, including vehicles operated under Turnkey Services (recalculated monthly) | Monthly Cost per Active Vehicle | Annual Cost per Active Vehicle | Vendor Assumptions or Exclusions |
| Tier 1 | 1–100 | $0.00 | ||
| Tier 2 | 101–300 | $0.00 | ||
| Tier 3 | 301–600 | $0.00 | ||
| Tier 4 | 601+ | $0.00 | ||
| An active vehicle is a vehicle that logs into the Contractor’s Vehicle Application for revenue service at least once during the billing month. The applicable tier is determined monthly and applies to all of the Contractor’s Participating Agencies for that month. Each Participating Agency is invoiced for its own active vehicles at the applicable tier rate. |
Evaluation Assumptions
| NEORide common SaaS evaluation assumptions |
| Use 50 active vehicles for one agency and 210 active vehicles across NEORide. The same active-vehicle definition applies to both counts. Vendors shall use these common quantities and disclose underlying usage assumptions in Price Breakdown. |
| Evaluation assumption | Common value | Unit | Instruction / basis |
| Agency active vehicles | 50 | Active vehicles | Use this agency count for the evaluated Year 1 SaaS price. |
| NEORide active vehicles | 210 | Active vehicles | Determines the applicable NEORide-wide tier: Tier 2 (101–300). |
| Participating agency deployments | 1 | Agency | Price one 50 active vehicle agency. Identify shared and per-agency implementation work. |
| Evaluation period | 36 | Months | Thirty-six months from each Participating Agency’s written Final System Acceptance, costed at the Tier 2 monthly fee on the Operating Costs tab. |
| Required test environments per agency | 1 | Instances | Required base environment. Options cover additional environments only. |
| Required production environments per agency | 1 | Instances | One production instance for each Participating Agency. |
| Required integrations | EZfare; GTFS Flex and trip planning; EZConnect | Base scope | Include implementation and ongoing integration maintenance. |
| Year 1 commencement | Written Final System Acceptance | Per agency | Implementation, acceptance testing and burn-in occur before recurring SaaS billing. |
| Implementation period | Applicable written NTP through Final System Acceptance | Per agency | All required platform access and support during this period are included in the fixed implementation price. |
| Vehicle count basis | Active vehicles | Same definition | Use active vehicles consistently at agency and NEORide levels; do not introduce a separate vehicle-count basis. |
| Underlying usage assumptions | Vendor disclosure | Price Breakdown | Vendor discloses trips, users, API calls and other usage assumptions underpinning its allocations. Required recurring charges remain bundled and the vendor bears usage risk. |
| Active vehicle definition | Logged into Vehicle Application for revenue service in the month | Per vehicle, per month | A vehicle counts as active for a billing month if it logs into the Contractor’s Vehicle Application for revenue service at least once in that month. The NEORide-wide count includes all Participating Agencies on the Contractor’s platform, including vehicles operated under Turnkey Services, and is recalculated monthly. |
File details come from the government source that posted it. Updated .