Transit Mobile Ticketing.pdf
PDF 928 KB Posted
- Attached to
- Regional Transit Mobile Ticketing
- Solicitation number
- 274-TransitMobileTicketing-2026
- Issued by
- North Carolina
About this file
Transit Mobile Ticketing Summary
This is a project description document for a regional transit mobile ticketing system initiative involving multiple transit agencies in North Carolina. The Transit Agencies are seeking proposals for a comprehensive, account-based fare payment solution that supports fixed-route and Bus Rapid Transit (BRT) services. The requested system shall encompass mobile ticketing capabilities, open-loop payment processing, fare validation equipment, optional Ticket Vending Machines (TVMs), comprehensive system management and reporting tools, and integration with existing transit technologies. The solution must demonstrate regional interoperability across participating transit agencies, accommodate future service expansion, and deliver a seamless, secure, and accessible fare payment experience for riders.
The project emphasizes the need for a unified regional approach to fare payment infrastructure that can scale across multiple transit operators. Key requirements include support for both mobile and traditional payment methods, real-time validation and reporting capabilities, and compatibility with current transit management systems. The system must be designed to facilitate long-term operational efficiency while maintaining security standards and accessibility compliance for all ridership segments. The proposed solution should position the regional transit network for technological advancement and support operational growth without requiring significant redesign or replacement of the core fare payment infrastructure.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Addendum #1-274-TransitMobile Ticketing-2026.pdf | ||
| Addendum #2-274-TransitMobile Ticketing-2026 (002).pdf |
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
Request for Proposals # 274-TransitMobileTicketing-2026
Title: Regional Transit Mobile Ticketing
Issue Date: August 14, 2026
Due Date: September 11, 2026 no later than 5:00PM EST
*LATE PROPOSALS WILL NOT BE ACCEPTED*
Issuing Department: Transportation/Transit
Direct all inquiries concerning this RFP to:
Dana Smith Transportation Supervisor Email: dana.smith@raleighnc.gov mailto:dana.smith@raleighnc.gov
Table of Contents
1. Introduction
1.1 Purpose
1.2 Background
1.3 RFP Timeline
1.4 Pre-Proposal Conference
1.5 Proposal Question
1.6 Proposal Submission Requirements & Contact Information
1.7 Business Engagement and Opportunities
1.8 Rights to Submitted Material
1.9 Communications
1.10 Lobbying
1.11 Conflicts of Interest
1.12 Proposer Expenses
1.13 Proposer Acceptance
2. Proposals
2.1 Request for Proposals Required Document Format
2.2 RFP Documents
3. Proposal Evaluation
3.1 Proposal Evaluation Criteria (Stage 1)
3.2 Interview/Demonstration (Stage 2)
3.3 Final Selection
3.4 Notice to Proposers Regarding RFP Terms & Conditions
3.5 Contract Term
3.6 Federal Funding Requirements
4. Scope of Services
Appendix I – Proposal Cost Form
Appendix II – Proposer Questionnaire
Appendix III – Reference Questionnaire (Instructions)
Appendix III – Reference Questionnaire Form
Appendix IV – Sample Contract
Appendix V – Federal Provisions and Requirements
Dana Smith Cross-Out
1 INTRODUCTION
1.1 Purpose
The City of Raleigh (COR) is solicitating proposals from one or more firm(s) with which to contract for the following services:
The Transit Agencies are seeking proposals for a regional, account-based fare payment system that supports fixed-route and Bus Rapid Transit (BRT) services. The system shall provide mobile ticketing, open-loop payments, fare validation equipment, optional Ticket Vending Machines (TVMs), comprehensive system management and reporting, and integration with existing transit technologies. The solution must support regional interoperability, future service expansion, and a seamless, secure, and accessible fare payment experience for riders across participating transit agencies.
A detailed scope of services is provided in Section 4 of this document.
All information related to this solicitation, including any addenda, will be posted to the North Carolina electronic Vendor Portal (eVP) at https://evp.nc.gov/.
All questions related to this solicitation must be submitted in writing (via email) to the following individual – questions submitted via telephone will not be answered:
Contact Name Email Address Dana Smith dana.smith@raleighnc.gov
1.2 Background
The City of Raleigh, the Capital City of North Carolina, remains one of the fastest growing areas in the country. A great economy, top educational institutions, and exceptional health care facilities are some of the characteristics that attract people to the triangle area. The mild climate, diverse work force and proximity to Research Triangle Park combine to make Raleigh a great place to live.
Raleigh is a 21st Century City of Innovation focusing on environmental, cultural, and economic sustainability. The City conserves and protects our environmental resources through best practice and cutting-edge conservation and stewardship, land use, infrastructure and building technologies. The City welcomes growth and diversity through policies and programs that will protect and enhance Raleigh’s existing neighborhoods, natural amenities, history, and cultural and human resources for future generations. The City leads to improve quality of life for neighborhoods and standard of living for all citizens.
The City works with universities, colleges, citizens, and local partners to promote new technology, create new job opportunities, and encourage local businesses and entrepreneurs. The City enlists and prepares 21st Century staff with the skill sets to carry out the duties of the City through transparent civic engagement and by providing the very best customer service to our citizens.
https://evp.nc.gov/
The Transit Agencies are seeking proposals for a regional, account-based fare payment system that supports fixed-route and Bus Rapid Transit (BRT) services. The system shall provide mobile ticketing, open-loop payments, fare validation equipment, optional Ticket Vending Machines (TVMs), comprehensive system management and reporting, and integration with existing transit technologies. The solution must support regional interoperability, future service expansion, and a seamless, secure, and accessible fare payment experience for riders across participating transit agencies.
1.3 Request for Proposal (RFP) Timeline
Provided below is a list of the anticipated schedule of events related to this solicitation.
The City of Raleigh reserves the right to modify and/or adjust the following schedule to meet the needs of the service. All times shown are Eastern Time (EST):
RFP Process Date and Time
RFP Date August 14, 2026
Pre-Proposal Meeting/Site-Visit (if required) August 20, 2026 10am est.
Deadline for Written Questions August 27, 2026 12pm est.
City Response to Questions (anticipated) September 02, 2026 5pm est.
Proposal Due Date and Time September 11, 2026 at 5pm est.
Evaluation Meeting (anticipated) Week of September 21, 2026
Interviews (if required) Week of September 28, 2026
Selection Announced (tentative) Week of October 05, 2026
1.4 Pre-Proposal Conference
The City of Raleigh elects to conduct a Pre-Proposal Conference or Site Visit. Prospective Proposers are encouraged to submit written questions in advance. The pre-proposal meeting will be held via Teams, the Microsoft Teams link is below:
Join: https://teams.microsoft.com/meet/22831307522736?p=EHW9XpyVoUOfQT7tkb Meeting ID: 228 313 075 227 36 Passcode: kh3hZ95i https://teams.microsoft.com/meet/22831307522736?p=EHW9XpyVoUOfQT7tkb
1.5 Proposal Questions
Requests for clarification and questions to this RFP must be received by the City not later than the date shown above in the RFP Timeline (Section 1.3) for the submittal of written inquires. The firm’s failure to request clarification and submit questions by the date in the RFP Timeline above shall be considered to constitute the firm’s acceptance of all City’s terms and conditions and requirements.
The City shall issue addenda reflecting questions and answers to this RFP, if any, and shall be posted to North Carolina electronic Vendor Portal (eVP). No information, instruction or advice provided orally or informally by any City personnel, whether made in response to a question or otherwise in connection with this RFP, shall be considered authoritative or binding. Proposers can only rely on written material contained in an Addendum to this RFP.
It is important that all Proposers submitting to this RFP periodically check eVP for any Addenda. It is the Proposers responsibility to ensure that all addenda have been reviewed and, if required signed and returned.
All questions related to this solicitation must be submitted in writing (via email) to the following individual – questions submitted via telephone will not be answered:
Contact Name Email Address Dana Smith dana.smith@raleighnc.gov
1.6 Proposal Submission Requirements and Contact Information
Proposals must follow the format as defined in Section 2 (PROPOSALS), and be addressed and submitted as follows:
DELIVERED BY US POSTAL SERVICE
MAIL:
DELIVERED BY OTHER DEIVERY
SERVICES:
City of Raleigh City of Raleigh
ATTN: Dana Smith ATTN: Dana Smith
510 W Martin Street 510 W Martin Street
Suite 200 (2nd floor- LM) Raleigh, NC 27601
Suite 200 (2nd floor- LM) Raleigh, NC 27601
RFP No. 274-TransitMobileTicketing-2026 RFP No. 274-TransitMobileTicketing-2026
Proposals must be enclosed in an envelope or package and clearly marked with the name of the submitting company, the RFP number and the RFP Title.
Proposers must submit:
A. one (1) signed original;
B. one (1) electronic version of the signed proposal
The electronic version of the Proposal must be submitted as a viewable and printable Adobe Portable Document File (PDF) on a USB Flash Drive. Both hard copy and https://evp.nc.gov/ https://evp.nc.gov/ electronic versions must be received by the City on or before the RFP due date and time provided in RFP Timeline (Section 1.3). Proposals received after the RFP due date and time will not be considered and will be returned unopened to the return address on the submission envelope or package.
Proposers must respond to the entire Request for Proposals (RFP). Any incomplete proposal may be eliminated from competition at the discretion of the City of Raleigh. The City reserves the right to reject any or all proposals for any reason and to waive any informality it deems in its best interest.
Proposals that arrive after the due date and time will not be accepted or considered for any reason whatsoever. If the firm elects to mail in its response, the firm must allow sufficient time to ensure the City’s proper receipt of the package by the time specified in the RFP Timeline (Section 1.3). Regardless of the delivery method, it is the responsibility of the firm to ensure that their proposal arrives at the designated location specified in this Section by the due date and time specified in the RFP Timeline (Section 1.3).
1.7 Business Engagement and Opportunities
The City of Raleigh maintains processes to conduct business with all business enterprises, including small, emerging, growing, under-capitalized, and under-resourced firms or organizations.
1.8 Rights to Submitted Material
All proposals and supporting materials, as well as correspondence relating to this RFP, shall become the property of the City. The content of all submittals will be held confidential until the selection of the firm is made. Proposals will be reviewed by the Evaluation Team, as well as other City staff and members of the general public who submit public record requests. Any proprietary data must be clearly marked. In submitting a Proposal, each Prospective Proposer agrees that the City may reveal any trade secret materials contained in such response to all City staff and City officials involved in the selection process and to any outside consultant or other third party who serves on the Evaluation Team or who is hired by the City to assist in the selection process.
Proposals marked entirely as “confidential”, “proprietary”, or “trade secret” will be considered non-responsive and will be removed from the evaluation process.
1.9 Communications
All communications of any nature regarding this RFP with any City staff, elected City officials, evaluation committee members, are strictly forbidden from the time the solicitation is publicly posted until award. Questions must be submitted in writing to the individual designated in Section 1.1 (Purpose), prior to the deadline provided in the RFP Timeline (Section 1.3). Violation of this provision may result in the firm’s proposal being removed from consideration.
1.10 Lobbying
By responding to this RFP, the firm certifies that is has not and will not pay any person or firm to influence or attempt to influence an officer or employee of the City or the State of North Carolina, or any elected official in connection with obtaining a contract as a result of this RFP.
1.11 Conflicts of Interest
City of Raleigh contracts are controlled by three conflict of interest provisions.
First, federal procurement standards provide in 2 CFR 200.318 (c)(1), No employee, officer, or agent may participate in the selection, award, or administration of a contract supported by a Federal award if he or she has a real or apparent conflict of interest. Such a conflict of interest would arise when the employee, officer, or agent, any member of his or her immediate family, his or her partner, or a firm which employs or is about to employ any of the parties indicated herein, has a financial or other interest in or a tangible personal benefit from a firm considered for a contract. The officers, employees, and agents of the non-Federal entity may neither solicit nor accept gratuities, favors, or anything of monetary value from contractors or parties to subcontracts.
Similarly, the North Carolina General Statutes provides a criminal statute for conflicts of interest in public contracting. N.C.G.S. § 14-234(a):
(1) No public officer or employee who is involved in making or administering a contract on behalf of a public agency may derive a direct benefit from the contract except as provided in this section, or as otherwise allowed by law. (2) A public officer or employee who will derive a direct benefit from a contract with the public agency he or she serves, but who is not involved in making or administering the contract, shall not attempt to influence any other person who is involved in making or administering the contract. (3) No public officer or employee may solicit or receive any gift, favor, reward, service, or promise of reward, including a promise of future employment, in exchange for recommending, influencing, or attempting to influence the award of a contract by the public agency he or she serves.
City of Raleigh Charter Section 3.9 regulates private transactions between the City and its officials and employees. The Charter states:
No member of the City Council, official, or employee of the City of Raleigh shall be financially interested, or have any personal beneficial interest, either directly or indirectly, as agent, representative, or otherwise, in the purchase of, or contract for, or in furnishing any materials, equipment or supplies to the City of Raleigh, nor shall any official or employee of the City of Raleigh accept or receive, or agree to accept or receive, directly or indirectly, from any person, firm or corporation to whom any contract may be awarded or from whom any materials, equipment or supplies may be purchased by the City of Raleigh, by rebate, gift, or otherwise, any money or anything of value whatsoever, or any promise, obligation or contract for future reward or compensation, for recommending or procuring the uses of any such materials, equipment or supplies by the City of Raleigh; no member of the City Council, official or employee of the City of Raleigh shall for his own personal benefit operate, directly or indirectly, any concession in any building or on any lands of the City of Raleigh, nor shall any official or employee of the City of Raleigh bid for or be awarded any contract granting concessionary rights of any nature or kind from the City of Raleigh; it shall be unlawful for any member of the City Council, official or employee of the City of Raleigh to bid for or to purchase or to contract to purchase from the City of Raleigh any real estate, equipment, materials, or supplies of any nature or kind whatsoever, either directly or indirectly, at either public or private sale, either singly, or through or jointly with any other person.
1.12 Proposer Expenses
The City of Raleigh will not be responsible for any expenses incurred by any Proposer in the development of a response to this Request for Proposal or any other activities associated with this procurement including but not limited to any onsite (or otherwise) interviews and/or presentations, and/or supplemental information provided, submitted, or given to City of Raleigh and/or its representatives. Further, the City of Raleigh shall reserve the right to cancel the work described herein prior to issuance and acceptance of any contractual agreement/purchase order by the recommended Proposer even if the awarding authority for each entity has formally accepted a recommendation.
1.13 Proposer Acceptance
Submission of any proposal indicates a Proposer’s acceptance of the conditions contained in this RFP unless clearly and specifically noted otherwise on Appendix VI Exceptions to RFP and submitted with proposal. Furthermore, the City of Raleigh is not bound to accept a proposal on the basis of lowest price, and further, the City of Raleigh has the sole discretion and reserves the right to cancel this RFP, and to reject any and all proposals, to waive any and all informalities and/or irregularities and reserves the right to re-advertise this RFP with either the identical or revised scope and specifications if it is deemed to be in the best interests of the City of Raleigh to do so.
The City of Raleigh reserves the right to accept or reject any or all of the items in the proposal, and to award the contract in whole or in part and/or negotiate any or all items with individual Proposers if it is deemed in the best interest of the City of Raleigh to do so.
Moreover, the City of Raleigh reserves the right to make no selection if proposals are deemed to be outside the fiscal constraint or not in the best interest of the City of Raleigh.
2 PROPOSALS
Submitted proposals must follow the format outlined below. The City may reject as non-responsive at its sole discretion any proposal that does not provide complete and/or adequate responses or departs in any substantial way from the required format.
2.1 Request for Proposals Required Document Format
Proposals should be on 8-1/2” x 11” (A4-sized) paper, printed on both sides, bound with only removable clips or staples (no 3-ring binders), and divided into sections using tabs to easily identify and separate each section as follows:
2.1.1. Section/Tab 1: Cover Letter
Provide an introduction letter summarizing the unique proposal of your firm to meet the needs of this service requirement. This letter should be presented on the firm’s official letterhead and signed by an authorized representative who has the authority to enter into a contract with the City on behalf of the firm. Additionally, include the name, address, telephone and email address of the individual who serves as the point of contact for this solicitation.
2.1.2. Section/Tab 2: Corporate Background and Experience
Include background information on the firm and provide detailed information regarding the firm’s experience with similar projects. Provide a list of all similar contracts performed in the past three (3) years, accompanied by at least three (3) references (contact persons, firm, telephone number and email address).
Include the total amount invoiced for each listed project, the length of the project, and list of those involved in the project who are also proposed for the subject project named in this solicitation. Failure to provide a list of all similar contracts in the specified period may result in the rejection of the firm’s proposal. The evaluation team reserves the right to contact any or all listed references, and to contact other public entities regarding past performance on similar projects.
2.1.3. Section/Tab 3: Financial Information
Review and provide one of the following three (3) financial statement options:
1. Recent audited or reviewed financial statements prepared by an independent certified public accountant (CPA) that shall include, at a minimum, a balance sheet, income statement (i.e., profit/loss statement) and cash flow statement and, if the audited or reviewed financial statements were prepared more than six (6) months prior to the issuance of this RFP, the Proposer shall submit its most recent internal financial statements (balance sheet, income statement and cash flow statement or budget with entries reflecting revenues and expenditures from the date of the audited or reviewed financial statements to the end of the most recent financial reporting period (i.e., the quarter or month preceding the issuance date of this RFP)).
OR
2. Recent compiled financial statements prepared by an independent CPA that shall include, at a minimum, a balance sheet, income statement (i.e., profit/loss statement) and cash flow statement and, if the compiled financial statements were prepared more than three (3) months prior to the issuance of this RFP, the Proposer shall submit its most recent internal financial statements (balance sheet, income statement and cash flow statement or budget with entries reflecting revenues and expenditures to date), and other evidence of financial stability such as most recently filed income tax return, evidence of a line of credit/loans/other type of financing with statement of amount in use/outstanding balance (e.g., a complete copy commitment letter, loan agreement, billing statement reflecting the line of credit or statement from lender acknowledging the commitment to fund the Proposer’s stated financing), personal guaranty with copies of personal income tax filing and statement of net worth or such other evidence that is accurate, reliable and trustworthy regarding the Proposer’s financial stability.
OR
3. Include a certified, signed statement from a licensed CPA regularly engaged in the review of the firm’s financial information verifying the financial viability of the firm.
All financial information, statements and/or documents provided in response to this solicitation shall be kept confidential provided that EACH PAGE is marked as follows:
“CONFIDENTIAL – DO NOT DISCLOSE EXCEPT FOR THE EXPRESS PURPOSE OF
PROPOSAL EVALUATION.“
“Recent” shall be defined as financial statements that were prepared within the 12 months preceding the issuance date of this RFP.
Consolidated financial statements of the Proposer’s parent or related corporation/business entity shall not be considered, unless: (1) the Proposer’s actual financial performance for the designated period is separately identified in and/or attached to the consolidated statements, (2) the parent or related corporation/business entity provides the State with a document wherein the parent or related corporation/business entity will be financially responsible for the Proposer’s performance of the contract and the consolidated statement demonstrates the parent or related corporation’s/business entity’s financial ability to perform the contract, financial stability and/or such other financial considerations identified in the evaluation criteria; and/or (3) Proposer provides its own internally prepared financial statements and such other evidence of its own financial stability identified above.
The firm’s failure to provide any of the above-referenced financial statements may result in the proposal being removed from consideration. Proposers are also encouraged to explain any negative financial information, and to provide documentation supporting those explanations and demonstrating the financial strength of the firm.
2.1.4. Section/Tab 4: Project Understanding, Approach and Schedule
Provide a comprehensive narrative, outline, and/or graph demonstrating the firm's understanding and approach to accomplishing the tasks outlined in the Scope of Work section of this RFP. A description of each task and deliverable and the schedule for accomplishing each shall be included.
2.1.5. Section/Tab 5: Team Firm, Experience and Certifications
This section must include the proposed staffing, deployment and firm of personnel to be assigned to this project. The Proposer shall provide information as to the Proposals and experience of all executive, managerial, legal, and professional personnel to be assigned to this project, including resumes citing experience with similar projects and the responsibilities to be assigned to each person. A project-specific firm chart which clearly illustrates the roles, responsibilities, and the reporting relationships of each team member should be included.
2.1.6. Section/Tab 6: Cost
In a separate sealed envelope provide a minimum of one (1) complete copy of the Proposal Cost Form and any additional itemized cost breakdown or price schedule.
Hourly rates shall be fully burdened to include all costs, all applicable overhead and profit (including lodging, meals, and transportation). Attach any additional pricing details.
2.2 RFP Documents
This RFP is comprised of the base RFP document, any attachments, and any addenda released before the contract is awarded. All attachments and addenda released for this RFP in advance of any contract award are incorporated herein by reference.
3 PROPOSAL EVALUATION
3.1 Proposal Evaluation Criteria (Stage 1)
This is not a bid. There will not be a public opening. The Proposals received in response to this RFP will be evaluated and ranked, by the Proposal Evaluation Committee in accordance with the process and evaluation criteria contained below. Responses will be evaluated in light of the material and substantiating evidence presented in the response, and not on the basis of what is inferred. After thoroughly reading and reviewing this RFP, each Evaluation committee member shall conduct his or her independent evaluation of the proposals received and grade the responses on their merit in accordance with the evaluation criteria set forth in the following table.
The maximum interview/demonstration points a Proposer can receive is five (5) points.
The Proposers selected for interviews/demonstrations under this section will be notified in writing of the date and time. The Proposers’ interview/demonstrations shall be based solely upon information provided in each Proposer’s original proposal. No new information may be presented.
Criteria (a)
Weight (b)
Score (0-3)
(a) x (b) Weighted
Score
Corporate Background and Experience 15
Firm Financial Stability 10
Project Understanding 20
Project Approach 25
Team Firm Experience 10
Proposed Cost 20
Total Score (without Interview/Demonstrations)
Interview/Demonstration (if applicable) (1-5 points)
Final Score (with Interview/Demonstrations)
Score Points 0- Missing or Does Not Meet Expectation 2- Meets Expectation 1- Partially Meets Expectation 3- Exceeds Expectation
Cost Formula: The cost criterion is rated by giving the proposal with the lowest total cost the maximum number of Cost points available. The remaining proposals are rated by applying the following formula:
1 - B - A x C = D
A A—the lowest Proposer’s cost.
B—the Proposer’s cost being scored.
C—the maximum number of cost points available.
D—Proposer’s cost score (points).
Note: If the formula results in a negative number (which will occur when the Offeror’s cost is more than twice the lowest cost), zero points shall be assigned.
3.2 Interview/Demonstration (Stage 2)
A short-list of firms may be invited to Stage 2, Interview/Demonstration, step of the evaluation process. Interview/demonstrations are an important aspect of the evaluation process that offers the City an opportunity to see how the proposer’s solution meets the critical components of the RFP.
3.3 Final Selection
Proposals will be evaluated and ranked according to the criteria and weighted values set forth in Section 3.1. Either a final selection for recommendation will be made at this time or the short-list of firms will be invited to participate in Stage 2 of the evaluation process.
If Stage 2 is implemented, each firm will be evaluated and assigned a score to determine the best firm for recommendation.
After which negotiations of a contract with the most qualified firm will commence. If negotiations are unsuccessful, the City will then pursue negotiations with the next most qualified firm. All Proposers will be notified of their standing immediately following the City’s decision.
The City shall not be bound or in any way obligated until both parties have executed a contract. The City also reserves the right to delay the award of a contract or to not award a contract.
3.4 Notice to Proposers Regarding RFP Terms and Conditions
It shall be the Proposer’s responsibility to read the RFP Instructions, the City’s contract terms and conditions (within the sample City Service Contract provided in Appendix IV), all relevant exhibits, attachments, and any other components made a part of this RFP and comply with all requirements and specifications herein. Proposers are also responsible for obtaining and complying with all Addenda and other changes that may be issued in connection with this RFP.
3.5 Contract Term
The contract issued by the City to the awarded proposer will define either a completion date by which the services are to be completed and finished, or a term date by which the services will begin and be provided repeatedly over a specific period. The details of the contract term and any options to renew or extend the contract will be stated in the contract issued by the City.
3.6 Federal Funding Requirements
The services and materials to be provided under this contract will be financed in whole or in part with Federal funding. As such, Federal laws, regulations, policies, and related administrative practices apply to this contract. The most recent of such Federal requirements, including any amendments made after the execution of this contract shall govern this contract, unless the Federal Government determines otherwise. The Federal provisions and requirements identified in Appendix V may be applicable to this contract.
The awarded contractor is responsible for complying with all applicable provisions and requirements.
4 SCOPE OF SERVICES
Awarded proposer shall provide services, all as set forth in this RFP and more particularly described in this Section 4.
This Request for Proposals (RFP) is being conducted as a cooperative procurement led by the City of Raleigh on behalf of public transit agencies in the Research Triangle region of North Carolina. The participating agencies include, but are not limited to, GoRaleigh, GoTriangle, GoDurham, and GoCary, hereinafter collectively referred to as the “Transit Agencies.”
The Transit Agencies are seeking to establish a contract with a supplier to provide a regional fare payment system for fixed-route and Bus Rapid Transit (BRT) services. The proposed system shall:
• Include mobile ticketing, open-loop payment capability, and optional pricing for Ticket
Vending Machines (TVMs).
• Support current and future fixed-route bus operations, as well as planned BRT services.
• Simplify fare payment for riders, reduce boarding delays, support future fare policy changes, and facilitate coordination with regional transit partners across both fixed-route and BRT services.
Background
GoRaleigh operates approximately 135 fixed-route buses that provide over 8 million trips annually. GoTriangle operates approximately 76 fixed-route buses providing 1.7 million trips annually.
While GoDurham and GoCary are participating in this RFP, both systems currently operate fare-free.
The Transit Agencies seek a fare payment technology system that will accommodate and improve upon our GoPass Program. Desired functionality includes:
• Easy GoPass sign up for riders and GoPass Partners
• The ability for riders to manage and view their GoPass benefit on a mobile app
• Robust reporting, including ridership by pass type, by route, by stop, and a reporting
API
• Easy-to-use tools for creating and monitoring GoPass (low administration costs)
The current fare structure in the region is as follows:
Fare Type
GoRaleigh GoTriangle
Full Fare
Reduced Fare
Full Fare
Discount Fare
One- Way Fare
$1.25
$0.60
$2.50
$1.25
Day Pass $2.50 $1.25 $5.00 $2.50
7-Day Pass $12.00 $6.00 $20.00 $10.00
31-Day Pass $40.00 $20.00 $80.00 $40.00
Fare Payment and Ticket Options
The system shall support multiple methods for riders to purchase and use fares for fixed route and Bus Rapid Transit (BRT) services, including mobile applications, agency fare cards, contactless bank cards, mobile wallets, Ticket Vending Machines, and cash options where applicable.
Fare options must include single ride fares, daily and multi day passes, monthly passes, reduced fares, transfers, and promotional fares. All fare options, including transfers where provided, must be interoperable across separate agencies.
The system must support daily, weekly, and monthly fare capping as well as regional compatibility with fare capping on neighboring transit agencies.
Cross agency transfers are currently provided between some of the Transit Agencies’ service, with differing fare rules between agencies.
Transit Agency system shall include appropriate security features to protect customer accounts and payment data and must incorporate tools to monitor, track, and report potential fare evasion, misuse, or fraudulent activity.
Contractor must describe their cybersecurity framework (NIST, ISO 27001, SOC2), as well as other systems and processes in place to promote security and payment compliance.
Account Based and Open-Loop Fare System
The system must support open-loop payment using debit and credit cards and mobile wallets, without the creation of a transit agency account.
The system must also support reduced fare programs and fare media management, as well as fare capping across all applicable fare products. The system must support future service changes, including BRT implementation, fare policy adjustments, and regional fare coordination.
On Board Fare Validation Equipment must accept mobile tickets, agency fare cards, open-loop payments and support fare products issued through Ticket Vending Machines. Fare validation equipment must be ADA compliant, reliable, and suitable for standard buses and BRT vehicles, including higher passenger volumes and all door boarding where applicable.
The equipment must be capable of operating in offline mode and securely storing transaction and validation data if a vehicle temporarily loses connectivity, with automatic synchronization once connectivity is restored.
Ticket Vending Machines (TVMs) The Contractor must provide the option for purchase and/or integration of Ticket Vending Machines that allow riders to purchase fare products for fixed route and BRT services, and be interoperable across all agencies. TVMs must support cashless payments, including credit and debit card, mobile wallets, along with cash acceptance with secure bill, coin handling, and change dispensing capabilities including exact change. Machine must be ADA compliant, support multiple languages, and be suitable for indoor or outdoor installation, including at BRT stations, transit centers, and high ridership locations. TVMs shall be designed for durability in high traffic public environments and include tamper resistant and vandal resistant features. GoRaleigh and GoTriangle must be able to manage fare products and pricing across all TVMs for fixed route and BRT services through a centralized system.
The Contractor may partner with TVM vendors to meet this requirement.
System Management and Reporting The Contractor shall provide a secure system that allows the Transit Agencies to manage fare products, customer accounts, TVMs, payments, and reporting for fixed route and BRT services. The system must include standard financial, boardings-by-route, and boardings-by-stop performance reports and allow data export for planning, Title VI, and reporting purposes. Reporting must allow data to be separated and analyzed by service type and by fare program, including reduced fare categories, fare capping activity, promotional fares, and regional transfers. The Transit Agencies shall retain ownership of all system data.
System must enable the Transit Agencies to administer and report on the regional GoPass program with minimal staff resources. Agency staff report program usage to GoPass partners like universities and employers including boardings by rider, by route, and by program. The Contractor should detail how the GoPass program would be administered under their system, and what reporting tools are available.
The Contractor must provide documented APIs or similar systems allowing the agency access to fare transaction, customer account, and system performance data.
Integration with Existing Systems and Hardware (Exhibit)
The system must integrate with GTFS and GTFS-RT data standards currently used by the Transit Agencies. The Contractor shall support data sharing needed for trip planning, real time information, and performance reporting.
Proposers shall provide information on existing integrations, and where these integrations are currently deployed.
Proposers shall clearly identify existing equipment that can be reused for fixed route and BRT services, any required equipment upgrades, and any equipment that would require replacement. The system must support phased implementation across fixed route and BRT services to ensure continuity of operations during transition.
The Contractor shall provide details on how their proposed system avoids future vendor lock-in and allows integration with third-party systems through open standards and APIs.
Regional Compatibility The system must support coordination and integration with other transit agencies in the region providing fixed route and BRT services, including but not limited to GoRaleigh, GoTriangle, GoCary, GoDurham, and other Wake Transit partners. The system must be capable of supporting shared fare products, cross agency transfers, regional fare capping, and compliance with current or future regional payment standards.
The Contractor must provide information on potential fare integration with rail services including Amtrak, North Carolina Railroad, and the S-Line (currently under development).
Accessibility and Customer Experience The system must meet ADA requirements and support riders with varying needs across fixed route and BRT services, including riders with disabilities, limited English proficiency, and those without access to banking services. Mobile applications, fare validators, and TVMs must be easy to use and clearly communicate fare information.
The system must have the ability to allow riders to add value to their accounts at retail locations (GoTriangle currently uses the InComm retail network for this purpose).
Multimodal Integration The system should be designed to support multimodal integration, including microtransit services, paratransit services, and emerging micromobility options. The system should have the ability to integrate with Via (used by GoRaleigh) and Spare (used by GoDurham) for microtransit payment integration. The system should allow for incorporation and integration of these modes into a unified payment experience, whether through direct fare integration, account-based payment, or interoperability with third-party mobility providers.
Implementation, Training, and Support The Contractor shall provide an implementation plan that supports fixed route and BRT services, including system configuration, testing, staff training, and public launch support. Ongoing maintenance, software updates, and customer and agency support must be included.
Scalability and Future Growth
The system must be scalable and capable of supporting future growth for fixed route and BRT services, including additional vehicles, stations, TVMs, fare products, payment options, and new regional partners without requiring replacement of the core system. The Contractor shall provide details on scalability in reference to the growth proposed in Wake Transit Plan. Information on tiered pricing shall be provided if applicable.
Bus List & Fare Equipment Exhibits
GoRaleigh Equipment Bus List Unit # Service Type Modem DVR Model IVN Farebox
PASSENGERS 0-WC / 1-
WC / 2-WC3 VEHICLE TYPE
1319 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1321 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1322 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1323 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1324 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1325 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1326 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1327 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1328 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1329 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1330 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1331 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1332 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1333 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1334 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1335 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1336 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1337 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1338 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1339 Revenue Digi WR44 MRH8 IVN 4 GFI FastFare 38 / 35 / 31 14 Gillig Low Floor, 40' x 102' 1601 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 16 Gillig Low Floor, 40' x 102' 1603 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 16 Gillig Low Floor, 40' x 102' 1604 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 16 Gillig Low Floor, 40' x 102' 1605 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 16 Gillig Low Floor, 40' x 102' 1606 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 16 Gillig Low Floor, 40' x 102' 1607 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 16 Gillig Low Floor, 40' x 102' 1609 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 26 / 23 / 20 16 Gillig Low Floor, 29' x 102' 1610 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 26 / 23 / 20 16 Gillig Low Floor, 29' x 102' 1611 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 26 / 23 / 20 16 Gillig Low Floor, 29' x 102' 1701 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 17 Gillig Low Floor, 40' x 102' 1702 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 17 Gillig Low Floor, 40' x 102' 1703 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 17 Gillig Low Floor, 40' x 102' 1704 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 17 Gillig Low Floor, 40' x 102' 1801 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1802 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1803 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1804 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1806 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1807 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1808 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1809 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1810 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1811 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1812 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1813 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1814 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1815 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1816 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1817 Revenue Digi WR44 HDR 16/12 IVN 4 GFI FastFare 38 / 35 / 31 18 Gillig Low Floor, 40' x 102' 1901 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1902 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1903 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1904 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1905 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1906 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1907 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1910 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1911 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1912 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1913 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1914 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1915 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1916 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1917 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1918 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102"
1919 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 38 / 35 / 31 19 Gillig Low Floor, 40' x 102" 1920 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 26 / 23 / 20 19 Gillig Low Floor, 29' x 102" 1921 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 26 / 23 / 20 19 Gillig Low Floor, 29' x 102" 1922 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 26 / 23 / 20 19 Gillig Low Floor, 29' x 102" 1923 Revenue Digi WR44 HDR4k 16/12 IVN 4 GFI FastFare 26 / 23 / 20 19 Gillig Low Floor, 29' x 102" 2106 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 21 Gillig Low Floor, 40' x 102" 2107 Revenue cradlepoint ibr1700 HDR 16/12 IVN 5 GFI FastFare 37 / 34 / 31 21 Gillig Low Floor, 40' x 102" 2108 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 21 Gillig Low Floor, 40' x 102" 2109 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 21 Gillig Low Floor, 40' x 102" 2110 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 21 Gillig Low Floor, 40' x 102" 2111 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 24 / 22 / 18 21 Gillig Low Floor, 29' x 102" 2112 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 24 / 22 / 18 21 Gillig Low Floor, 29' x 102" 2113 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 21 Gillig Low Floor, 40' x 102"
2201 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2202 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2203 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2204 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2205 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2206 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2207 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2208 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102"
2209 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2210 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2211 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2212 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2213 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2214 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2215 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2216 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2217 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2218 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2219 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2220 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2221 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2222 Revenue cradlepoint ibr1700 MRH8 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2223 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2224 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2225 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2226 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2227 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2228 Revenue cradlepoint ibr1700 HDR4k 16/12 IVN 5 GFI FastFare 37 / 34 / 31 22 Gillig Low Floor, 40' x 102" 2401 Revenue cradlepoint ibr1700 RR-HDRN4K16 IVN 5 GFI FastFare 37 / 34 / 31 24 Gillig Low Floor, 40' x 102" 2402 Revenue cradlepoint ibr1700 RR-HDRN4K16 IVN 5 GFI FastFare 37 / 34 / 31 24 Gillig Low Floor, 40' x 102" 2403 Revenue cradlepoint ibr1700 RR-HDRN4K16 IVN 5 GFI FastFare 37 / 34 / 31 24 Gillig Low Floor, 40' x 102" 2404 Revenue cradlepoint ibr1700 RR-HDRN4K16 IVN 5 GFI FastFare 37 / 34 / 31 24 Gillig Low Floor, 40' x 102" 2501 Revenue cradlepoint ibr1700 RR-Pro IVN 5 GFI…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .