RFP 100 25 Automated Bus Lane and Stop Enforcement System v7.pdf

7.1.Lapuyade23

MASSACHUSETTS BAY TRANSPORTATION AUTHORITY

REQUEST FOR PROPOSALS (RFP)

RFP#: 100-25

COMMBUYS BID NUMBER- BD-26-1206-MBTA-MBTA-119428

AUTOMATED BUS LANE AND BUS STOP ENFORCEMENT SYSTEM

Date Issued: August 8, 2025

RFP: 100-25 - 1 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Project Name: Automated Bus Lane and BUS Stop Enforcement System

Contents

1. INTRODUCTION

2. PROGRAM GOALS

3. SCOPE OF WORK

3.1 Bus-mounted Violation Detection System (VDS)

3.2 Central System

3.3 Performance Standards service level agreement (SLA)

3.4 Information Technology

3.5 Project Management

3.6 Expected Contract Duration

3.7 Additional Services

4. BIDDERS' INSTRUCTIONS AND PROCUREMENT PROCESS

Bidders’ Conference

Procurement Method

RFP Calendar and Delivery Instructions

Dissemination of Confidential Information

Examination of RFP

Rules of Contact

Clarifications of Specifications, Questions, and Answers

RFP Addendum

MBTA Standard Contract and Terms & Conditions

Confidentiality / Public Information Act Disclosure Requests

Business Conduct

Collusion

Prices

Eligible Entities

Pre-Contractual Expenses

Tax Exemption

Insurance

5. SUBMISSION OF RESPONSE

Response Submissions

Power of Attorney

RFP: 100-25 - 2 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Acceptance of Response

Incomplete Response

6. MBTA POLICIES

Small, Minority, Women, and Other Disadvantaged Businesses

7. SELECTION PROCESS AND EVALUATION

Response Opening and Confidentiality

Responsiveness Review and Basis of Award

Evaluation Criteria and Notification

Technical Response, Supplier Diversity

Solution Presentation

Price Response Evaluation

Technology Pilot

Basis of Award: Best–Value Proposal

Successful Bidder

MBTA Reserved

Appeal / Protest Procedures

8. CONTRACT STRUCTURE

Enclosure 1 – Bid Cover Letter

Form A: Pre-Award Bidder Evaluation Data Form

Form B: Technical Response

Form C: Small Business Program Attestation Form

Form D: Pricing Response

8.1 MBTA Standard Contract Instructions (Section 8.0)

8.2 MBTA Standard Terms & Conditions Instructions (Section 8.1)

9. Massachusetts Bay Transportation Authority Standard Contract

Standard Terms and Conditions

RFP: 100-25 - 3 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Attn: Bidder/s

Request for Proposals (RFP) # 100-25

RFP Description:

Dear Prospective Bidder:

The Massachusetts Bay Transportation Authority (“MBTA” or “Authority”), a corporate and political subdivision of the Commonwealth of Massachusetts, operates under Mass. Gen. Laws, Ch 161A (as amended). It invites Bidders to participate in the competitive bid process. This bid is for the pilot and potential procurement of Automated Bus Enforcement Systems. The scope of work is described below in

Section 3. The MBTA may award contract(s) to one or multiple Bidders at its discretion. All formal communication with the MBTA during the bidding period shall be only through the MBTA’s designated point of contact (POC). All bidder responses must conform to the requested format or document template(s) provided.

The MBTA’s designated point of contact (POC)for this solicitation will be:

Steven Pelczar

Massachusetts Bay Transportation Authority

10 Park Plaza, Room 2810

Boston, MA 02116

Email: spelczar@mbta.com

The RFP shall be launched through COMMBUYS, and proposals must be submitted electronically no later than 9/10/2025 in full compliance with this RFP, including but not limited to Section 3, Bidders'

Instructions, and the Procurement Process. This RFP shall remain in effect until the Contract is executed or until it is modified or canceled by the MBTA.

Respectfully, Steven Pelczar

Sr. Project Manager, Procurement Operations

Massachusetts Bay Transportation Authority (MBTA)

RFP: 100-25 - 4 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

1. INTRODUCTION

The Massachusetts Bay Transportation Authority (MBTA), often called “The T”, is the public operator of most bus, subway, commuter rail, and ferry systems in the greater Boston Area. It's the largest transit provider in New England and the fifth largest in the United States. The MBTA provides services to 175 communities.

The MBTA Bus Network features over 40 miles of dedicated bus lanes and more than 7,000 bus stops.

Daily, unauthorized vehicles impede the agency’s ability to deliver safe and reliable bus service to its riders by standing or parking at bus stops or in dedicated bus lanes. This can prevent buses from pulling entirely into a bus stop and up to the curb, exposing passengers to traffic and preventing riders in mobility devices from boarding and alighting. Unauthorized vehicles in bus stops and dedicated bus lanes also reduce the efficiency and reliability of the MBTA’s bus service.

In January 2025, Governor Healey signed Bill S.2884 into law, legalizing bus-mounted camera systems and bus stop monitoring cameras to issue tickets to motorists blocking bus lanes and bus stops. The law establishes an escalating fine for blocking lanes, beginning at $25 for the first offense and rising to a maximum of $125, and a flat fine of $100 for blocking stops. It does not permit camera enforcement for operating a vehicle in a bus lane, only for parking or standing in one.

The RFP is comprised of the following documents:

• RFP 100-25, Form and Enclosures including:

o Enclosure 1 – Bid Cover Letter o Form A – Pre-Award Bidder Evaluation Data Form o Form B – Bidder Technical Response o Form C – Small Business Attestation

• Attachments o Exhibit A – VDS Deployment Plan o Exhibit B – MBTA Bus Fleet o Exhibit C – MBTA Bus Lanes List o Exhibit D – MBTA Bus Lane Designs o Exhibit E – MBTA Bus Lanes Map o Exhibit F – Bus Zone Violation Thresholds o Exhibit G – LPR HIT PUSH API o Exhibit H – OpenAPI Spec.yaml o Exhibit I – MBTA Cloud Computing Terms o Exhibit J – MBTA Minimum Insurance Requirements o Exhibit K – MBTA Accessibility Requirements o Form D – Bidder Price Response https://malegislature.gov/Bills/193/S2884

RFP: 100-25 - 5 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

2. PROGRAM GOALS

The purpose of this solicitation is to identify, pilot, and deploy a bus-mounted automated enforcement system that can accurately determine when an unauthorized vehicle is stopped or parked at an MBTA bus stop or dedicated bus lane, transmit evidence data to a cloud-based central storage system for processing, offer a user-friendly platform for MBTA staff to review violation evidence, and securely transfer approved evidence data to the MBTA’s Citation Management Engine (CME) for parking citation management. The

MBTA seeks a Contractor to ensure system compatibility with all current and planned MBTA vehicles, provide ongoing system monitoring and reporting, and provide a system warranty.

The MBTA plans to pilot one or more of these systems simultaneously for approximately 30 days on two bus routes (the SL4 and SL5) to evaluate the potential solutions' effectiveness. Each selected Bidder must install their system on two New Flyer XDE60 buses. After the pilot, the MBTA may decide to implement one or more systems on a portion of its bus fleet.

3. SCOPE OF WORK

The contractor will deliver and operate an automated bus enforcement system, including bus-mounted

Violation Detection Systems (VDS) and a Central System. The Central System processes evidence packages according to MBTA-defined business rules, enabling MBTA staff to review and approve or reject evidence, transfer evidence to the MBTA’s CME, and provide system health monitoring and reporting on key performance metrics.

The MBTA is seeking a base contract of three (3) years, with three options, each to extend the contract by one year. As outlined in the RFP attachment VDS Deployment Plan, the MBTA is looking to procure an estimated 300 VDS systems to be installed at its garages over 11 months to provide automated enforcement coverage on all fixed bus routes that it operates.

The Contractor must comply with the MBTA’s requirements outlined below, organized into the following sections:

• Bus-mounted Violation Detection System (VDS) to collect evidence of potential violations

• Cloud-based Central System for evidence processing, review, transfer, system health monitoring, and reporting on key performance metrics

• Performance Standards for the MBTA’s automated bus enforcement system

• Information Technology requirements

• Project Management requirements

3.1 BUS-MOUNTED VIOLATION DETECTION SYSTEM (VDS)

The MBTA aims to acquire a mobile, bus-mounted Violation Detection System (VDS) that can be configured and installed on any buses in its current or planned fleet. The VDS should include all necessary components to automatically detect, capture, and transmit evidence of bus lane and bus stop violations with high accuracy and reliability. Before the RFP responses are due, the MBTA will set a date and time for interested bidders to visit one of its bus facilities and inspect the bus types under consideration for VDS installation. It remains undetermined whether systems will be installed in “all bus types” (noted below).

RFP: 100-25 - 6 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Installation onto MBTA buses

3.1.1 VDS must be capable of being installed in all MBTA New Flyer bus models: D40LF, DE60LFR, XDE40, XN40, XDE60, XE60, and XE40.

3.1.2 VDS must be installed in a location that meets MBTA Performance Standards (see section

3.3 Performance Standards) while remaining as unobtrusive to operators and riders as possible. The MBTA will have final approval of all equipment placement before installation, and once onboard, it should be removable and replaceable.

3.1.3 VDS must be able to be installed on buses and operate seamlessly without interfering with or being affected by vehicle components or other installed electronics. The bidder must collaborate with New Flyer (bus manufacturer) to ensure that VDS installation and operation do not cause any issues.

Hardware and operation

3.1.4 VDS must include camera(s) to record video and images of vehicles unlawfully parked, standing, or made to stand in MBTA bus lanes or bus stops, and for Automatic License

Recognition (ALPR) to generate machine-readable license plate data.

3.1.5 When a potential violation is observed, in addition to capturing video of the incident and license plate imagery, the VDS must be able to record:

3.1.5.1 Date and time of the observation

3.1.5.2 Vehicle location (GPS coordinates)

3.1.5.3 Route pattern (route-variant and direction, e.g., Inbound or Outbound)

3.1.6 VDS must be capable of starting up and initiating automated enforcement independently when the vehicle powers on, without any human input.

3.1.7 VDS must automatically recognize all enforcement parameters, including the enforcement area (e.g., bus lane or bus stop), enforcement date, and enforcement times.

3.1.8 VDS must be able to use a cellular data connection to automatically upload evidence of each violation observed to a web-based Central System within 24 hours of capture.

3.1.9 VDS must be capable of monitoring system health and automatically reporting any faults or issues.

3.2 CENTRAL SYSTEM

VDS should upload evidence to a cloud-based solution (“Central System”) hosted by the Contractor. The

Central System will be responsible for processing evidence, storing proof, providing a platform for MBTA staff to review evidence, and securely transferring approved evidence to the MBTA’s Citation Management

Engine (CME). The Central System must also push evidence data on a scheduled basis to the MBTA’s database, enable MBTA staff to view system health and performance in real-time, and generate reports on system performance.

Evidence processing, review, and transfer

3.2.1 Provide a web-based portal (a “Central System”) with a user interface accessible through standard web browsers (Internet Explorer, Google Chrome, Firefox).

RFP: 100-25 - 7 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.2.2 The Central System shall receive, process, and store evidence packages uploaded from VDS to fulfill the requirements outlined in the Performance Standards section.

3.2.3 Central System shall have the ability to allow the MBTA to create and maintain a list of authorized vehicles that are exempted from automated enforcement.

3.2.4 The Central System shall be able to eliminate duplicative evidence packages that may result from a vehicle, in violation of program rules, remaining at the same location for an extended period.

3.2.5 Provide an easy-to-use interface for MBTA staff to review and approve or reject violation evidence for traffic citations.

3.2.5.1 Evidence approval/rejection decisions must include a unique identifier for the evidence reviewer.

3.2.5.2 When rejecting an evidence package, MBTA staff should be able to select from a list of customizable values that can be used for reporting and system optimization.

3.2.6 Securely transfer approved evidence package data to the Gtechna Citation Management

Engine (CME) used by the MBTA. For documentation on the Gtechna API, see the RFP attachments for LPR HIT PUSH API.pdf and OpenAPI Spec.yaml. The API and evidence data to transfer to the Gtechna CME will be developed and defined in coordination with the

MBTA and Gtechna.

Reporting

3.2.7 Periodically to be determined in coordination with the MBTA, Contractor must securely transmit evidence data to the MBTA through an automated SQL data export process. Data fields for each evidence package should include:

3.2.7.1 Unique violation ID

3.2.7.2 Violation review outcome (approved/rejected, and if rejected, reason for rejection)

3.2.7.3 Unique ID for MBTA staff evidence reviewer

3.2.7.4 Violation type (bus lane or bus stop)

3.2.7.5 Date/time violation was observed

3.2.7.6 Location (GPS coordinates, block address, and/or nearest intersection if available)

3.2.7.7 Bus route

3.2.7.8 Route pattern (route-variation and direction, e.g., inbound or outbound)

3.2.7.9 Bus stop the violation was observed in (if applicable)

3.2.7.10 Bus lane the violation was observed in (if applicable)

3.2.7.11 Indication if the violation was exempted due to the presence of an authorized vehicle

3.2.7.12 Indication if the violation was exempted due to duplicate violation logic specified by the MBTA

RFP: 100-25 - 8 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.2.8 The Central System must provide a user interface for MBTA staff to generate, view, and customize reports on key program performance metrics such as VDS runtime, observed violations by type (bus lane or bus stop) and by route, repeat offender rate, evidence package processing time, and evidence package approval rate.

3.2.9 Central system must provide a user interface for MBTA staff to monitor VDS health in real time.

Data handling

3.2.10 The Central System and VDS should store evidence data and be able to serve as backups to the MBTA’s CME.

3.2.11 To comply with the program’s regulations, the Central System must automatically delete video evidence, photographic images, and ALPR metadata as follows:

3.2.11.1 For rejected evidence packages: All video and photographic evidence related to that package, along with any metadata that could identify individuals near the time of the violation (such as license plate data), should be deleted within 24 hours of rejection;

all other metadata should be retained for reporting purposes.

3.2.11.2 For approved evidence packages: All video and photographic evidence associated with that evidence package, as well as any metadata that could be used to identify anyone in the vicinity of the violation at the time of the observation (such as license plate data), should be deleted after a configurable amount of time, such as 120 days.

All other metadata should be retained for reporting purposes.

3.2.12 The Central System must be capable of maintaining a data archive for the MBTA that includes all data and reports stored in the system for up to two (2) years after this Contract expires. All systems used for the scheduled automatic and permanent deletion of evidence as outlined in this Scope of Work should remain in place after this Contract ends. No changes or configurations to the Central System should be made unless approved by the MBTA.

RFP: 100-25 - 9 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.3 PERFORMANCE STANDARDS SERVICE LEVEL AGREEMENT (SLA)

This section outlines the performance standards for the Automated Bus Enforcement system that the MBTA aims to meet in its program. The Contractor shall ensure that the MBTA has the data needed to create a monthly report to assess system performance against each performance standard, including data from the

Central System or evidence review platform, such as evidence package delivery and processing times, reject rates, and corrections to inaccurate evidence package metadata. The Contractor shall identify problem areas and proactively investigate them, providing details and reports as needed by the MBTA.

Measurement Period: Monthly

Measured by: MBTA

Vendor Responsibility: Ensure that the system is logging the data needed to calculate the performance standards listed below, and pushing performance data periodically to the MBTA regularly

Financial Penalties: MBTA will deduct from the contractor’s monthly invoice

Performance

Standard

Target Measurement Financial Penalty

System accuracy

(valid, complete evidence packages)

≥ 90% of processed evidence packages delivered to the MBTA for review are approved for enforceable violations and include correct information (violation type, enforcement areas/time, unauthorized vehicle, license plate image that can be matched to contextual video, legible license plate characters, accurate license plate data, location data, and other evidence package metadata)

% of evidence packages that are rejected or that require

ALPR license plate data to be manually corrected

$500 penalty per percentage point below

90%

$750 penalty per percentage point below

80%

Capped at $25,000/month

Evidence processing time

≥ 95% of evidence packages should be processed and ready for review by MBTA staff within 72 hours of observation

Compare timestamps of evidence observation time and when evidence is processed and marked as ready for MBTA review

$500 penalty per percentage point below

95%, capped at

$5,000/month

Evidence package transfer time

≥ 98% of approved evidence packages should be transferred to the MBTA’s CME within 4 hours of approval by MBTA staff

Measured by comparing timestamps of evidence approval by

MBTA and successful transfer to the

MBTA’s CME

$500 penalty per percentage point below

98%, capped at

$5,000/month

Central System availability

≥ 99.5% Central System and evidence review platform uptime (excluding pre-scheduled outages)

Measured by

Contractor

$500 penalty per 0.1% below 99.5%, capped at

$10,000/month

RFP: 100-25 - 10 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.4 INFORMATION TECHNOLOGY

The VDS and Central System must comply with MBTA information technology requirements as outlined in this section, which covers system administration, security, and communication architecture.

3.4.1 The Contractor must use encryption methods compliant with FIPS 140-3, preferably AES-

256-bit encryption or higher. The Contractor is required to apply approved encryption techniques to data both at rest and in transit.

3.4.2 The solution will include built-in data-masking features. The response should also specify any built-in data privacy, compliance, or masking capabilities (PII, NPI, PHI, etc.).

3.4.3 Access controls for services provided by the Contractor must include authentication through

MBTA-managed Entra ID.

3.4.4 All suppliers and subcontractors must abide by the cybersecurity requirements outlined in this SOW. The Contractor and all subcontractors will be subject to all clauses within this section in addition to the standard terms and conditions.

3.4.5 All software must be the latest stable version available for the proposed equipment. The contractor shall supply all necessary updates and upgrades to VDS software required for operations and maintaining security at no extra cost to MBTA during the contract term.

3.5 PROJECT MANAGEMENT

This section outlines the project management requirements for deploying the system, including documentation, project staffing, maintenance, installation, testing, and training.

VDS Installation

3.5.1 The MBTA aims to deploy VDS and start automated enforcement across its service area as quickly as possible. The Contractor must submit an Implementation Plan/Project Schedule outlining their approach and milestones for system installation, integration, route mapping, tuning, testing, and acceptance to meet the proposed schedule in the RFP attachment VDS

Deployment Plan. MBTA will also be exploring “self & 3rd party” installation options.

3.5.2 The Implementation Plan should include the Proposer’s proposed list and order of activities for delivering the complete system according to these specifications, along with milestones for testing and acceptance. At a minimum, the Implementation Plan must detail the sequence and duration of the following activities:

3.5.2.1 Engineering & Design

3.5.2.2 Equipment, procurement and pre-delivery testing

3.5.2.3 Equipment shipping and site arrival

3.5.2.4 First Article Inspections (FAI)

3.5.2.5 Onboard systems installations

3.5.2.6 Operations planning

3.5.2.7 Testing and acceptance tasks and milestones

3.5.2.8 Training

3.5.2.9 Final Acceptance

RFP: 100-25 - 11 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.5.3 MBTA and the Contractor will develop and mutually agree on VDS installation acceptance procedures, which must include written acceptance of the installation by both parties for each unit. The Contractor must work with New Flyer to validate and provide proof that their VDS does not interfere with any existing bus systems or subsystems for each bus type.

3.5.4 As the system installation advances across various vehicle types, the Contractor shall perform first article inspections (FAI) for each new bus model where the VDS is installed.

3.5.5 The Contractor shall submit and follow a quality control plan detailing the steps to ensure the quality of installation, maintenance, and software support, thereby ensuring the overall reliability of the system as specified in this statement of work. The plan shall include checklists for standard maintenance and installation services.

3.5.6 The contractor shall conduct any on-site surveys needed to determine equipment placement and calibrate the pilot equipment.

3.5.7 Prior to beginning installation of equipment onto any bus, Contractor will need to:

3.5.7.1 Document any significant pre-existing damage on the vehicle in a pre-installation checklist, and make sure that after the installation, the bus is returned in the same condition as it was before installation. An MBTA designated representative will be on-site during installation to assess quality control. The MBTA representative has full authority to stop or suspend work if, in their sole opinion, the work is being done unsatisfactorily. Any damage to the vehicle, other components, or newly installed equipment will be the contractor's responsibility to repair or replace, either by a qualified entity chosen by the MBTA or if the work does not meet the MBTA’s standards.

3.5.7.2 The Contractor shall avoid damage to newly installed and existing wiring and equipment. Any damage to the vehicle, other components on the vehicle, or newly installed equipment shall be the Contractor's responsibility to repair or replace, either directly or through an entity chosen by the MBTA if the repairer or replacer is not qualified or if the work does not meet MBTA standards.

3.5.7.3 Submit complete installation schematics for each MBTA bus type the VDS will be installed on, using standard engineering drawings with specified tie points and fusing.

Submit wiring and cabling product information for MBTA review and approval.

3.5.8 Contractor must be able to install VDS when buses are not in service or undergoing routine maintenance, including overnight hours if necessary. The MBTA will provide access to the bus garage and other relevant facilities, including available parking spots and necessary coordination. Installation will occur at a time and location selected by the MBTA. It will be performed under MBTA supervision and must adhere to the installation requirements specified in this solicitation, as practically feasible.

3.5.9 If the Contractor determines that cutting holes in the exterior of the vehicle is necessary, the proposed design must undergo additional review and inspection to ensure that the installation method does not lead to leaks over time. The detailed installation, securing, and sealing of the exterior equipment shall be submitted separately for MBTA review. The vendor shall be required to design and perform a water intrusion test in close collaboration with the MBTA before the proposed design is approved.

3.5.10 The contractor shall supply and install all cables, brackets, and other related materials needed for the pilot installations. All materials and equipment used must be new, unused, and free of defects. Discontinued models are not acceptable.

3.5.11 Contractor representatives must be identified by the Contractor and display proper

RFP: 100-25 - 12 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428 identification while on MBTA property. They must also wear required PPE such as, but not limited to, safety vests, gloves, safety shoes, safety glasses, goggles, and other necessary safety gear based on the task to protect against injuries and accidents.

3.5.12 Contractor’s on-site personnel must complete MBTA safety training before accessing

MBTA facilities and must follow all MBTA Rules and Regulations.

3.5.13 The Contractor shall follow all MBTA work standards, rules, and regulations while on

MBTA property, including any FTA Substance testing requirements.

3.5.14 Contractor staff must sign in and out at the Maintenance Office when arriving and leaving any MBTA bus garage and must have an escort while on MBTA property. MBTA personnel will perform escort services and specific tasks as needed.

3.5.15 The contractor must specify if they plan to use any subcontractors. If yes, they must state what percentage of the work will be done by subcontractors.

Testing

3.5.16 The Contractor shall create and maintain a Requirements Traceability Matrix (RTM) that links all system, functional, and performance requirements from this RFP to the system design, implementation, and testing/validation phases. The RTM shall be reviewed and approved by the MBTA during system design, updated regularly throughout the project, and submitted in final form at project closeout.

3.5.17 After the Technology Pilot and before System Acceptance, Field Testing will be used to verify that the Contractor’s VDS and Central System are properly calibrated and configured for the MBTA’s needs. Field testing will involve driving buses with calibrated and tested

VDS units on the SL4 and SL5 bus routes, or two other routes of the MBTA’s choice that have been configured for automated enforcement. The MBTA will assign employees in vehicles to test evidence package generation and Central System processing (e.g., removal of duplicates and authorized vehicles) in various staged scenarios and at different times of the day.

3.5.18 During Field Testing, the Contractor shall provide the MBTA with full access to system data, including diagnostic data, performance data, and onboard collected data. Within three weeks of contract award, a field-testing plan lasting one to two weeks will be submitted to the

Contractor.

3.5.19 System Acceptance shall be granted when:

3.5.19.1 The Contractor has supplied all necessary equipment, systems, and services needed to carry out a specific rollout phase of the VDS.

3.5.19.2 All functionality is available and demonstrated, meaning all contract requirements have been validated to the MBTA's satisfaction.

3.5.19.3 The Contractor has prepared and submitted all necessary documentation in final or as-built form.

3.5.19.4 Contractor has provided multiple sets of any non-standard or proprietary tools needed to access, perform maintenance, remove, or adjust VDS.

3.5.19.5 The Contractor has finished all training.

3.5.19.6 The Contractor has completed all testing, including resolving all deficiency list items.

RFP: 100-25 - 13 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.5.19.7 Field testing has been conducted on at least two installed vehicles, and the MBTA is satisfied with the results.

Documentation

3.5.20 Contractor shall provide as-built implementation documentation that includes the items below, within three (3) weeks of System Acceptance:

3.5.20.1 An inventory of all equipment supplied, including supplier, model number, serial number, installation location, and planned useful life of each component.

3.5.20.2 An inventory of all spare parts supplied, including supplier, model number, serial number, and storage location.

3.5.20.3 All reference and user manuals for system components, including those components supplied by third parties.

3.5.20.4 All warranties documentation, including components supplied by third parties.

3.5.20.5 A diagram indicating the as-built interconnections between components.

3.5.20.6 The version number of all software and license counts, including that supplied by third parties.

3.5.21 Note that both physical and digital copies of As-Built Documentation should be provided for each bus type the VDS is installed onto, and updated documentation should be provided whenever software or hardware is upgraded.

3.5.22 The Contractor shall provide User Manuals for all system components and relevant applications.

3.5.23 The Contractor shall develop and provide documentation for all internal and external system interfaces and APIs, including ICDs detailing data, data definitions, data formats, communications protocols, and relevant database tables and views being accessed.

3.5.24 The Contractor shall detail the extent to which the solution's architecture is open-source and supports integration and communication with system components using industry-standard

APIs and technologies.

3.5.25 The Contractor shall provide the MBTA with a bill of materials that clearly identifies all known third-party software components contained in the supplier product. This bill of materials shall be provided in a machine-readable format.

3.5.26 The Contractor shall provide software licensing/subscription options with the associated terms and conditions. With this deliverable, provide any potential patent infringement clauses that the MBTA needs to be aware of.

3.5.27 The Contractor shall provide a list of built-in adaptors and existing APIs for integrating with third-party tools, including Splunk SIEM, MS Entre ID, Clever Devices, Trapeze/Vontas, HASTUS, etc.

3.5.28 IT Security Documentation/Artifacts shall include:

3.5.28.1 System Security Plan

3.5.28.2 Patch and Vulnerability Management Plan

3.5.28.3 Network Topology Diagram

3.5.28.4 Interconnection Security Agreement

RFP: 100-25 - 14 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

3.5.28.5 Information Flows/Paths

3.5.28.6 Hardware/Software/Firmware

3.5.28.7 Encryption Techniques

3.5.28.8 System Enterprise Architecture and Information Security Architecture

3.5.28.9 Configuration Management Plan

3.5.28.10 Ports, Protocols, and Services Management

Warranty and Support

3.5.29 The proposed system (both hardware and software components) must be covered by a comprehensive warranty that ensures the functionality, reliability, and performance of the system as specified in this RFP. The warranty must remain valid regardless of whether installation and/or maintenance is performed by the Contractor, the MBTA, or a third party, provided that all installation and maintenance activities follow the Contractor’s written specifications and guidelines. Warranty & Support Services during the term of this Contract must include at least the following:

• Remote health monitoring of all VDS units and timely alerts for any issues detected, including:

(a) An API with VDS health data that the MBTA can query to so that VDS health issues can be integrated into existing alert systems.

(b) Create and maintain a file stored in a secure FTP location for the MBTA to access and that can be imported into Trapeze EAM for the automated creation of VDS service requests; implementation details will be determined in coordination with the MBTA.

• Remote and/or on-site diagnostics to determine the cause of any failed VDS components

• Faulty system components replaced (or replacement parts delivered if Contractor is not providing repairs) within 72 hours

• Software and firmware updates for VDS, Central System, and the evidence review platform are needed to maintain a secure, stable, and up-to-date system

3.5.30 On-demand technical support for the Central System and evidence review platform.

3.5.31 The Contractor’s PM must be easily accessible to schedule and conduct monthly meetings with the MBTA’s PM to discuss needs, changes, upgrades, or further configuration of services during the term of this Contract. The Contractor’s PM must be reachable 24/7 by telephone and email for direct contact in case of emergencies and must promptly notify

MBTA's PM if phone numbers or email addresses change during the contract period.

3.5.32 If the MBTA awards a follow-on contract for automated bus lane and bus stop enforcement to another contractor, the Contractor must cooperate with the MBTA and any successor

Contractor to ensure the program continues smoothly.

RFP: 100-25 - 15 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Training

3.5.33 A Training Plan, including the training schedule and course outlines, must be submitted to the MBTA for review at least four weeks before Contractor-provided training begins. The

Training Plan for each session must include at least the following topics:

• Course objectives

• Topics to be covered

• Training method (in-person, Zoom/Teams, self-guided, etc.)

• Time required to complete each course

• Suggested attendees

• Resources required from the MBTA

• Approach to follow-up training

• Any prerequisites for the course

• Approach to evaluating student learning and retention

3.5.34 The Contractor shall provide additional training if new functionality is delivered after initial training sessions are completed.

3.6 EXPECTED CONTRACT DURATION

The MBTA proposes a base contract of three (3) years, with three optional extensions, each to extend the contract by 1 year. MBTA plans to acquire an estimated 300 VDS systems to be installed over a period of

11 months, as outlined in the deployment schedule in the RFP attachment VDS Deployment Plan. The deployment plan and the number of VDS installations are estimates and may change at any time.

3.7 ADDITIONAL SERVICES

Additionally, directly related services may be added to this Agreement before its start or throughout its duration if the parties agree to this in writing.

4. BIDDERS' INSTRUCTIONS AND PROCUREMENT PROCESS

Bidders’ Conference

The MBTA reserves the right to hold one or more Bidders’ conferences with all Bidders at any time before the Response Date. Bidders’ conferences may be held either in person or by telephonic or electronic means.

If held telephonically or electronically, the Bidders’ conference will permit interactive communication between all Bidders and the MBTA. The MBTA will provide notice of any Bidders’ conference via

COMMBUYS. If a Bidders’ conference is conducted by telephonic or electronic means, the notice will inform Bidders of the manner of the meeting.

By submitting its Response, each bidder acknowledges that the opportunity to attend any Bidders’ conference, if held, was offered to all Bidders and waives any right to challenge this procurement based on its attendance at, or failure to attend, a Bidders’ conference.

RFP: 100-25 - 16 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Each Bidder is encouraged to attend Bidders’ conferences, if held, with appropriate members of its proposed staff, and if requested by the MBTA, senior representatives of proposed team members identified by the

MBTA. Nothing stated at any Bidders’ conference or included in a written record or summary of a Bidders' conference will modify this RFP or any other part of the RFP unless it is incorporated in an addendum issued.

Pre-bid conference MS Teams Link

Procurement Method

This RFP is issued under the following laws and regulations: Mass. Gen Laws, Ch. 161A; 801 CMR

21.00.

Bidder shall be responsible for being fully aware of, complying with, and addressing the impact of and compliance with all applicable laws and regulations in its Response.

This RFP will be launched and managed via COMMBUYS. Instructions for logging in and using

COMMBUYS are described at http://www.mass.gov/anf/docs/osd/forms/instructions-for-vendors-responding-to-bids.docx.

Bidders may also contact the COMMBUYS Helpdesk at COMMBUYS@state.ma.us or the COMMBUYS

Helpline at 1-888-MA-STATE. The Helpline is staffed from 8:00 a.m. to 5:00 p.m. Monday through Friday

(Eastern Time), except on federal, state, and Suffolk County holidays.

It is the responsibility of Bidders to maintain an active registration in COMMBUYS and to keep current the email address of the Bidder’s Designated Representative and to monitor that email inbox for communications from the MBTA, including responses to Bidder questions. The MBTA and the

Commonwealth assume no responsibility if a Bidder’s designated email address is not current, or if technical problems, including those with Bidder’s computer, network, or internet service provider (“ISP”) cause email communications sent to or from Bidder and the MBTA to be lost or rejected by any means including email or spam filtering.

Bidder shall thoroughly review and study all documents and report any discrepancies, omissions, technical queries, or other clarifications via COMMBUYS.

Questions and clarification requests submitted by Bidder will be made available to all Bidders via

COMMBUYS, together with MBTA's responses.

4.1.1 MBTA DESIGNATED REPRESENTATIVE

Unless expressly stated otherwise in this RFP, Bidder must submit changes to Bidder’s designated representative and any other communications to the MBTA’s Point of Contact via COMMBUYS. The

MBTA’s Point of Contact is Steven Pelczar, spelczar@mbta.com.

4.1.2 IDENTIFICATION OF BIDDER DESIGNATED REPRESENTATIVE

When submitting a Bid, the Bidder must identify to the MBTA’s Point of Contact its own Designated

Representative to act on behalf of the Bidder relating to this procurement.

RFP Calendar and Delivery Instructions

Bidder is required to prepare and submit all the necessary documents to MBTA electronically via

COMMBUYS.

https://teams.microsoft.com/l/meetup-join/19%3ameeting_NjZjNDU5MmEtMWYzZC00ZjdlLWE3MTUtNjMyYmIyYTgxZmZk%40thread.v2/0?context=%7b%22Tid%22%3a%227558e599-f006-481f-9717-b189e6730862%22%2c%22Oid%22%3a%227b05458e-051d-4546-9730-c0443c4ab1f3%22%7d http://www.mass.gov/anf/docs/osd/forms/instructions-for-vendors-responding-to-bids.docx http://www.mass.gov/anf/docs/osd/forms/instructions-for-vendors-responding-to-bids.docx mailto:COMMBUYS@state.ma.us mailto:rfpresponse@mbta.com

RFP: 100-25 - 17 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

The MBTA anticipates carrying out the procurement process according to the schedule noted in the table below. All times are local to Boston, Massachusetts, USA, unless otherwise indicated. The schedule is subject to modification at the sole discretion of the MBTA. Bidders will be notified of any change by an addendum to this RFP.

TABLE: RFP CALENDAR

Procurement Activity Date Time

RFP issued 8/8/2025 11:00 PM

Pre-bid conference 8/15/2025 11:00 PM

Bidder Site Visit to Inspect Bus Types

Upon Bidder Request 8/21/2025

TBD

Deadline for submission of Bidder questions via COMMBUYS Q&A

8/27/2025 5:00 PM

Official Answers for Bid Q&A published by MBTA on COMMBUYS 9/3/2025

5:00 PM

Bidder RFP Response Due Date 9/10/2025 5:00 PM

Notification to bidders

(Selected for Solution Presentations) 9/24/2025

5:00 PM

Solution Presentations (Virtual)

(estimated date) 10/1/2025

TBD

Notice to bidder

(Selected for Technology Pilot) 10/8/2025

5:00 PM

Technology Pilot Preparation

(Selected Bidders)

10/8/2025

(start)

11/5/2025

(end)

Technology Pilot

(Selected Bidders)

11/6/2025

(start)

12/06/2025

(end)

Awardee Selection / Contract Execution (estimated) 1/9/2026

Program Start Date (estimated) 1/12/2026

Dissemination of Confidential Information

Pursuant to this RFP, the MBTA will provide to Bidders certain information, which the MBTA deems

Confidential (“Confidential information"). In order to obtain the Confidential Information necessary for the development of Responses, Bidders are required to obtain and execute a Confidentiality and Non-

Disclosure Agreement. Bidders can obtain the Confidentiality and Non-Disclosure Agreement via

COMMBUYS. Please execute and return the Confidentiality and Non-Disclosure Agreement by Click here to enter a date. To the MBTA's Designated Representative by submitting it to confidential@mbta.com, so that the MBTA can provide Bidders with the Confidential Information promptly.

mailto:confidential@mbta.com

RFP: 100-25 - 18 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Not Applicable

Examination of RFP

Each Bidder shall be solely responsible for examining, with appropriate care and diligence, the RFP and any addenda and material made available to Bidders by the MBTA, and for informing itself concerning any conditions that may in any way affect the amount or nature of its Response, or the performance of the

Contractor’s obligations under the Contract with the MBTA. Failure of the Bidder to examine and inform itself shall be at its sole risk, and the MBTA will provide no relief for any error or omission.

The submission of a Response shall be considered prima facie evidence that the Bidder has made the above-described examination and is satisfied with the conditions to be encountered in performing the Work and the requirements of the Contract.

Rules of Contact

Starting on the date the RFP is issued and ending on the earliest of (a) the award and execution of the

Contract, (b) rejection of all Responses by the MBTA, or (c) cancellation of the procurement, the following rules of contact shall apply. These rules are designed to promote a fair and unbiased procurement process.

Contact includes face-to-face, telephone, email, or formal written communication.

The specific rules of contact are as follows:

i. No Bidder or any of its team members may communicate with another Bidder or its team members regarding this RFP or each team’s Response, except that shared subcontractors between two or more Bidder teams may communicate with their respective team members, provided that those

Bidders establish a protocol to ensure the subcontractor does not act as a conduit for information between the teams. This restriction does not apply to public discussions about the RFP at any

MBTA-sponsored Bidders’ conferences.

ii. No Bidder or their representative shall have any ex parte communications regarding the RFP, the

Contract, or the procurement described herein with any member of the MBTA’s Board of Directors, the Massachusetts Department of Transportation (“MassDOT”) Board of Directors, or with any

MassDOT or MBTA staff, advisors, contractors, or consultants involved with the procurement, except for communications explicitly permitted by the RFP or as approved in advance at the sole discretion of the MBTA’s Point of Contact. However, this restriction shall not prevent or limit communications about matters unrelated to the RFP, Contract, or procurement or participation in the MBTA, MassDOT Boards of Directors meetings, or any public or Bidder workshop related to this RFP.

iii. The Bidders shall not contact employees regarding this RFP, the Contract, or the procurement.

iv. Any communications determined by the MBTA, in its sole discretion, to be improper may result in disqualification.

v. Any official information regarding this RFP will be disseminated from the MBTA’s Point of

Contact via COMMBUYS.

vi. The MBTA will not be responsible for or bound by any oral exchange or any other information or exchange that occurs outside the official process specified herein.

vii. The MBTA will not be bound by, and Bidders should not rely on, any oral communications regarding the RFP. Use of any information gathered or received from other agencies or entities shall be at the Bidder’s own risk.

RFP: 100-25 - 19 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428

Clarifications of Specifications, Questions, and Answers

Bidders must review the RFP and any addenda issued by the MBTA before the Response Date. They should request written clarification or interpretation of any perceived discrepancy, deficiency, ambiguity, error, or omission in the documents, or of any provision they do not understand or wish to modify. The Bidder's failure to examine and inform itself will be at its own risk, and the MBTA will not provide any relief for mistakes or omissions. Bidders must submit questions and requests for written clarification as outlined in this Section 3.7, and the MBTA will respond accordingly.

Questions and clarification requests should be minimized or combined whenever possible. Bidders must submit all questions and clarification requests through the “Bid Q&A” tab in COMMBUYS. Such comments and questions may be submitted any time before the date specified in Section 3.3 or any later date stated in an addendum and must: (i) specify the document; (ii) include the relevant section and page number or indicate if it is a general question; and (iii) not mention the Bidder in the question body or include proprietary or confidential information. Questions submitted through any other method or format will not be considered.

Responses to requests for clarification or questions will be provided in writing and issued by the MBTA’s

Point of Contact via COMMBUYS. Additionally, the MBTA reserves the right, at its sole discretion, not to answer all questions submitted by Bidders.

It is the Bidder’s responsibility to verify the MBTA’s receipt of questions and clarification requests.

RFP Addendum

The MBTA reserves the right to issue addenda to the RFP after its initial publication. It is each Bidder’s responsibility to monitor COMMBUYS for any addenda and Bid Q&A records related to this RFP. The

MBTA and the Commonwealth accept no responsibility and will offer no accommodations to Bidders who submit responses based on outdated RFP or information received from sources other than COMMBUYS.

The Bidder must acknowledge in its Technical Proposal Cover Letter (see Enclosure 1) receipt of all addenda and question and answer responses. Failure to acknowledge receipt may result in the response being deemed non-responsive and rejected.

MBTA Standard Contract and Terms & Conditions

The MBTA does not encourage attempts to negotiate the Section 8.0 Massachusetts Bay

Transportation Authority Standard Contract Terms & Conditions. Many of these provisions are required by law; others are longstanding MBTA policy/practice. Accordingly, Bidders/proposers should only redline or object to provisions that they find absolutely unacceptable. Any rejection or modification of these provisions may disqualify a Bid/proposal as non-responsive or non-compliant.

Confidentiality / Public Information Act Disclosure Requests

4.1.3 Disclosure Waiver

Each Bidder, by submitting a Response to the MBTA in response to the RFP, consents to the disclosures described in this RFP, including this Section and all other disclosures required by law, and expressly waives any right to contest, impede, prevent, or delay such disclosure, or to initiate any proceeding that may have the effect of impeding, preventing, or delaying such disclosure, under Mass. Gen. Laws, Ch. 66 (the Massachusetts Public Records Law or “Public

Records Law”) or any other law relating to the confidentiality or disclosure of information.

Under no circumstances will the MBTA be responsible or liable to a Bidder or any other party

RFP: 100-25 - 20 - COMMBUYS #: Bid BD-26-1206-MBTA-MBTA-119428 as a result of disclosing any such materials. Each Bidder hereby further agrees to assist the

MBTA in complying with these disclosure requirements.

4.1.4 Public Disclosure of Response Documents

Subject to applicable law, after execution of the Contract, or in the event that the procurement is cancelled by the MBTA, the MBTA shall have the right to publicly disclose any and all portions of all Responses. The MBTA will not disclose material deemed confidential by the

MBTA in accordance with Section 4.1.5, unless otherwise required by law.

4.1.5 Disclosure Process for Requests Under the Public Records Law

All written correspondence, exhibits, reports, printed material, photographs, tapes, electronic disks, and other graphic and visual aids submitted to the MBTA during this procurement process, including as part of the response to this RFP, become the property of the MBTA upon their receipt by the MBTA and will not be returned to the submitting parties. Except as provided by applicable law, all materials submitted to the MBTA are subject to release as public records.

Bidders shall familiarize themselves with the provisions of applicable law (including the Public

Records Law) pertaining to disclosure of information in the MBTA’s possession. In no event shall the MBTA, or any of its agents, representatives, consultants, directors, officers, or employees, be liable to a Bidder or Bidder team member for the disclosure of all or a portion of a Response or related information submitted during this procurement.

If a Bidder has special concerns about information which it desires to make available to the

MBTA but which it believes constitutes a trade secret, proprietary information, or other information excepted from disclosure, such responding Bidder shall specifically and conspicuously designate that information by placing “TRADE SECRET - PROPRIETARY” in the header or footer of each such page affected and by identifying such trade secret, proprietary information in the Technical Proposal Cover Letter (see Enclosure 1). Nothing in this provision shall modify or amend the requirements and obligations imposed on the MBTA by the Public Records Law or other applicable law.