RFI 49 25 Bidders Questionnaire.xlsx
XLSX spreadsheet 26 KB Posted
- Solicitation number
- BD-24-1206-40000-40000-114821
- Issued by
- Massachusetts
About this file
This document is a Request for Information (RFI) Bidders Questionnaire issued by the Massachusetts Bay Transportation Authority (MBTA) for an automated bus lane and bus stop enforcement system. The questionnaire seeks detailed information from potential vendors about their technological capabilities for detecting and documenting bus lane and bus stop violations through automated enforcement systems. The comprehensive document covers multiple aspects of potential deployment, including technology operation, installation requirements, product features, data handling, artificial intelligence capabilities, maintenance, warranty, support, and pricing models.
The RFI requires vendors to provide in-depth responses across 56 specific questions covering technological specifications, data security, privacy protections, system interoperability, and implementation details. Key areas of focus include system accuracy rates, hardware requirements, data transmission and storage protocols, integration capabilities with existing systems, AI utilization, maintenance procedures, and potential pricing structures. The questionnaire indicates the MBTA is seeking a sophisticated automated enforcement solution that can be retrofitted to existing vehicles or integrated into new bus purchases, with robust data management, strong privacy protections, and comprehensive reporting capabilities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI 49 25 Automated Bus Lane Bus Stop Enforcement System March 2025.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
Sheet1 Section # Question Answer (type in your answer) Clarification (select from drop down) Hakuta, Akira: Please select the best-fitting value from the dropdown on all yellow cells
| Relevant experience and references | 1 | What cities have you deployed your automated enforcement systems in, and for what customers? Please specify the size of each deployment by city (number of vehicles/fixed locations installed, number of bus stops and routes covered), the violation types your system currently enforces in each city, the type of installation (retrofit or part of a new bus purchase and the nature of each deployment (e.g. contract or no-cost pilot), and the installation dates. | N/A |
| 2 | Please provide three references at past or existing transit agency customers, including phone number and email. | N/A | |
| 3 | Please describe the timeline from contract signing to full implementation for these other customers. | N/A | |
| Automated enforcement technology | 4 | What is your system’s theory of operation? How does it automatically capture, process, identify, and transmit violation data on unlawfully parked or standing vehicles in bus lanes and at bus stops with high degree of accuracy? Please explain the way your technology works as clearly and simply as possible, as if you were explaining it to an 8th grader. | N/A |
| 5 | Does your system operate autonomously to generate violation packages, or does it require operator intervention using buttons or controls? | ||
| 6 | What is the accuracy rate of your system when it comes to the following automated enforcement use cases: |
a) Determining whether a motor vehicle is standing in a bus lane.
b) Determining whether a motor vehicle is moving in a bus lane.
c) Determining whether a motor vehicle is standing in a bus stop.
d) Determining whether a motor vehicle is moving in a bus stop.
e) Determining the exact location of a vehicle.
| f) Reading a vehicle’s license plate characters and state. | N/A | |
| 7 | Please include for each scenario specified in 6.1 through 6.6 the following information: |
a) Rates of false positives for your solution in each of the use cases.
b) Rates of false negatives for your solution in each of the use cases.
c) A description of how your system’s accuracy in these scenarios may or may not be affected in different weather such as fog, rain, and snow, and in different lighting conditions such as dawn, dusk, and in the dark.
| d) A detailed description of the methodology used to determine the rates of accuracy cited for each of the use cases above. | N/A | |||
| 8 | Who are your top competitors for automated bus lane and bus stop enforcement, and what makes your automated enforcement technology solution better than your competitors? | N/A | ||
| Installation requirements and initial configuration | 9 | Can your system be retrofitted to current fleet vehicles? Are there any limitations that would prevent a retrofit from being possible? | ||
| 10 | Can your system be integrated into new bus purchases? Have you integrated your on-vehicle solution with any bus OEM’s? If so, which ones? | |||
| 11 | What does your camera-based enforcement system require to function correctly? Please detail the following for both on-vehicle and fixed installation systems: |
a) Physical dimensions and weight of each system component.
b) Power requirements (including specs on the power consumed by your system).
c) Line of sight/placement/orientation requirements.
d) Ventilation requirements and high-temperature auto shutoff protection mechanisms.
e) Shock, vibration, bump, electromagnetic immunity and emissions, and weather sealing ratings for all equipment.
f) Operating and storage temperature ranges, as well as IEC 60068-2-1 test results indicating system performance in cold temperatures.
g) Any CAN bus, GPS, CAD/AVL, cellular data, and Wi-Fi connectivity requirements.
| h) Mounting configurations. | N/A | |||
| 12 | Does your on-vehicle solution require any permanent modifications (drilling holes, etc.) to the vehicle? | N/A | ||
| 13 | What data types do your on-vehicle and stationary automated enforcement systems require to detect bus lane and bus stop violations automatically? | |||
| 14 | On average, how long does it take to install your system to detect bus lane and bus stop violations automatically on one vehicle? | N/A | ||
| 15 | On average, how long does it take to install your system to detect bus lane and bus stop violations automatically into one fixed location? | N/A | ||
| 16 | On average, how long does it take to configure your system to detect bus lane and bus stop violations automatically per bus route? | N/A | ||
| 17 | Does your solution adhere to safety FTA safety protocols? | N/A | ||
| Product features | 18 | Once your automated enforcement system is on a vehicle or installed at a fixed location, what, if anything, needs to be done to it at the start of the day or the end of the day to ensure its correct operation? How does your system handle disruptions to power, such as when a bus is turned off and restarted or if power at a fixed installation goes out? | ||
| 19 | How does your ticket management software interface look and work? Please provide a video or screenshot-based demonstration of your ticket management software interface and how administrators can use it to review, manage, and report on automated violation data. Describe your system’s reporting capabilities and provide examples of available reports and explain any features that minimize the amount of time it takes to review a potential violation. |
a) Can all the actions and data available in your system be integrated into another ticket management system?
| 20 | How long on average does it take someone to review and process a violation package using your ticket management system? | N/A |
| 21 | Is your on-vehicle automated enforcement system able to change its enforcement business logic based on the jurisdiction the vehicle is currently in? If so, how does this work? | |
| 22 | The MBTA will have program administrators that will be responsible for reviewing violation packages and processing violations and appeals. |
Please:
a) List all program administrator actions that are logged in your software.
b) Explain how a program administrator could audit these logs.
c) Describe any controls that are in place to prevent the modification of these system logs, and if and how access to audit logs can be restricted to certain users.
| Interoperability and data inputs/outputs | 23 | Is your automated enforcement system designed to integrate seamlessly with other ticket management systems? If so, how? Do you use a REST API, Webhooks, etc.? |
| 24 | Does your system support integration with corporate Active Directory (AD) accounts for staff single sign on? The MBTA prefers OpenID Connect (OIDC) or SAML integrations with Microsoft EntraID or Keycloak for applications integrating with AD. | |
| 25 | Please provide documentation of your system’s Application Programming Interfaces (APIs) that allow customer systems to interact with your product. | |
| 26 | Can administrative actions be accomplished via a documented API? What actions in your software can only be accomplished via a graphical interface rather than a machine API? | |
| 27 | Describe how your solution makes diagnostic data available to customers (e.g., device connectivity, failure codes, content versioning). Does this include a provided graphical interface as well as APIs or other machine-readable endpoints? | |
| Infrastructure and information security | 28 | Please describe the following aspects of how your system handles data transmission and storage: |
a) How and when your system transmits and stores violation evidence (list all types of data that are transmitted).
b) How encryption is handled (both in transit and at rest).
c) How long the data is stored, what cloud provider you use for storage, and if that data resides in the United States.
d) If and how your system minimizes unnecessary data transmission into storage for efficiency and privacy.
e) Does your system handle and respond to interruptions in cellular or Wi-Fi data connectivity?
f) Please describe your information security response process including leadership and your security team.
g) Describe the networking requirements for your solution – e.g., cellular data, first-responder cellular data networks. Do you have a preferred vendor of cellular routers? Is deploying these routers part of your solution?
h) Do you share any customer data with any third parties including cellular or wifi service providers?
i) How do you share incidents with third parties your organization contracts with that could potentially impact customer data ?
29 Please provide a security overview of your platform, detailing:
a) Current compliance standards.
b) Information security controls and processes.
d) What types of Information Security certifications/attestations does your platform support/provide, such as SOC 2 Type II, ISO 27000-1 or GDPR.
e) How your solution adheres to data privacy protocols for PII.
| 30 | Does your system do anything to protect the privacy of pedestrians, cyclists, drivers, and vehicles that do not violate predefined business rules? Please detail specifically how your product will comply with the privacy requirements detailed in the authorizing legislation (link to legislation here for reference). | ||
| 31 | Do your customers retain full ownership of all of the data generated from your systems? How is data removed upon separation of business relationships? | ||
| Artificial intelligence | 32 | Please describe your artificial intelligence (AI) stack for your organization. | |
| 33 | Please provide a description of any AI services used as part of your product, include model/s used, and how MBTA data is handled throughout the process. | ||
| 34 | Do you use AI or automation tools that interact with sensitive customer data? If yes, how do you ensure these tools are secure? | ||
| 35 | Do you plan to implement and/or use AI within your environment during the length of this proposed contract? (Yes/No) If yes, please explain. | ||
| 36 | List your policies or other documentation that provides guidance on data privacy, bias, and exposure/breach/corruption when working with AI models? | ||
| 37 | Please describe how MBTA information assets are handled and stored in relation to vendor AI capabilities. | ||
| 38 | Do your AI capabilities need to integrate with other MBTA information assets? If yes, please describe the nature of access, and how that impacts the sharing and use of MBTA data. | ||
| 39 | Do you contract out work to sub-vendors who utilize AI tools when working with MBTA data. If yes, please explain. | ||
| 40 | Describe the tools used, the vendor review process for those tools, and how MBTA information assets could be handled by those tools. | ||
| 41 | Please describe the monitoring process for any AI tools that could impact MBTA information assets regarding data drift and data bias. | ||
| Maintenance, warranty, and support | 42 | What are preventative maintenance requirements for you on vehicle and fixed location systems? Please be sure to specify the preventative maintenance details and the recommended frequency. | N/A |
| 43 | What are the common/known corrective maintenance issues that apply to you on vehicle and fixed location systems? Please describe them in detail. | N/A | |
| 44 | Do you provide maintenance services, or are customers required to maintain their own systems? | N/A | |
| 45 | What type of help/IT support system is in place if clients or users experience issues with the ticket management software, or with the automated enforcement hardware? | N/A | |
| 46 | What warranties apply to your system's hardware? And what is the Mean Time Between failure (MTBF) specifications for all components? | N/A | |
| 47 | Is there any bench testing equipment required to operate and maintain your solution? If so, would that equipment be provided? | N/A | |
| 48 | What is the cost model associated with your software and firmware and feature upgrades? For example, is there continuous deployment of new firmware and features? If so, is that done seamlessly in the background, or does that require staff to manually update software unit by unit? Are there costs associated with security updates and new features? How is firmware version control managed? | N/A | |
| Pricing | 49 | Please provide indicative pricing models for hardware costs per bus-vehicle and per fixed location installation, including replacement costs for damaged or faulty system components, estimated hardware lifecycle and replacement costs, preventative and corrective maintenance, and any hardware warranty details applicable. | N/A |
| 50 | Please provide pricing models for administrative costs, software, ongoing operational needs on a per bus-vehicle scalable rate (i.e. cost for administering program on a per-bus vehicle rate). | N/A | |
| 51 | Please provide pricing information for one-time and any ongoing/recurring costs associated with integrating your system’s hardware with a separate ticket management platform. | N/A | |
| 52 | What is your model for implementation and training, and what are representative implementation and training costs? | N/A | |
| 53 | Please describe the ownership and licensing model for your system, including software code, hardware, and the data the MBTA would store in your system. | N/A | |
| 54 | Is your solution available through software resellers? If yes, please indicate the resellers that you currently work with. If no, please indicate if you would consider working with a reseller. | N/A | |
| Software accessibility | 55 | Is your solution and included documentation compliant with the following: Web Content Accessibility Guidelines (WCAG) version 2.1, levels A and AA? If not, in what areas is the solution noncompliant? | |
| 56 | Does your solution have a completed Accessibility Compliance Report (ACR) from the latest version of the VPAT 2.1 (Voluntary Product Accessibility Template) or equivalent? If so, does the ACR include reporting for WCAG 2.1 levels A and AA (AAA optional) and Functional Performance Criteria (Section 508 requirements)? |
File details come from the government source that posted it. Updated .