SFMTA-2026-43-LOC_-_Attachment_3_-_FR___CC_Matrix.xlsx

XLSX spreadsheet 28 KB Posted

Attached to
EXT MTA | Traffic Signal Central Management
Solicitation number
SFGOV-0000012216
Issued by
San Francisco County, San Francisco City, California

About this file

This is a Functional Requirements and Capabilities Compliance Matrix for Invitation for Bids (IFB) No. SFMTA-2026-43-LOC issued by the San Francisco Municipal Transportation Agency (SFMTA) for Traffic Signal Central Management Software. The SFMTA seeks to procure a centralized Traffic Signal Central Management Software (CMS) solution to replace its current system for monitoring, controlling, and managing the Agency's traffic-signal infrastructure. Bidders are required to complete the compliance matrix in its entirety for each functional requirement listed, indicating whether their proposed CMS solution is compliant, non-compliant, or requires configuration or customization. A virtual Pre-Bid Conference is scheduled for November 12, 2026, at 1:00 PM PT via Microsoft Teams. Any bid marked as non-compliant may result in the bid being deemed non-responsive, and the SFMTA will award the contract to the lowest responsive bid that meets the Minimum Qualifications outlined in IFB Section V.

The functional requirements encompassed in the compliance matrix include controller integration with D4 firmware versions 1.7 and above, real-time monitoring at one-second polling intervals with display of phase status, detector status, and signal indications, Signal Phase and Time (SPaT) logging with historical data storage, intersection map view capabilities, alert logging with export functionality to spreadsheet formats and email or text message notifications, user profile customization, and comprehensive data and communication requirements. Security and data management requirements mandate that the CMS be fully hosted in a commercial cloud environment within the United States, maintain SOC 2 Type II certification at minimum, support encryption at rest and in transit using TLS 1.2 or higher, role-based access control, and multi-factor authentication for administrative access. The contractor must also maintain documented disaster recovery and business continuity plans with a Recovery Time Objective (RTO) and Recovery Point Objective (RPO) of 24 hours each, implement a formal incident response program with 24-hour notification requirements for security incidents, and provide the ability to export data in standard, non-proprietary formats upon request or contract termination.

View the file

Other files

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

Instructions

SFMTA-2026-43-LOC: Traffic Signal Central Management Software
Attachment 3: Functional Requirements and Capabilities Compliance Matrix
Functional Requirements and Capabilities Compliance Matrix – INSTRUCTIONS
Bidders must complete the 'Functional Requirements and Capabilities Compliance Matrix' sheet in its entirety.
For each requirement listed, indicate compliance and provide a clear description of how the proposed CMS solution meets the requirement.
Information regarding the requirements can be found in Attachment 1: Scope of Work
Compliance Definitions:
- Compliant: The requirement is met out-of-the-box without modification.
- Non-Compliant: The requirement is not met.
Notes:
- Any 'Non-Compliant' response may result in the Bid being deemed non-responsive.
- Identify any configuration, customization, or third-party components required.
- Provide references to product documentation, module names, or screenshots where applicable.
Do not modify the 'Req. No.', 'Functional Requirement Description', and 'Mandatory functional requirement at execution or initial deployment' or columns

Compliance Matrix Attachment 1, Section 4: Req. No. Functional Requirement Description Mandatory functional requirement at execution or initial deployment tc={2192DE38-4EE7-4822-A052-6758FA72B578}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

PM: Addition per Sid’s email on 9/16.Compliance (Select)Description of ComplianceConfiguration / Customization Required (Yes/No)Reference (Documentation / Screenshot / Module)
IV.1: Controller IntegrationCMS shall integrate with existing traffic signal controller software, including D4 or equivalent.
IV.1.iCMS shall support D4 firmware versions 1.7 and above.
IV.1.iiCMS shall maintain compatibility with future firmware updates.
IV.2: Real Time MonitoringCMS shall poll controllers at a rate of one (1) second.
IV.2.iCMS shall display Phase Status.
IV.2.iiCMS shall display Detector Status.
IV.2.iiiCMS shall display Phase Next.
IV.2.ivCMS shall display Min and Max Green Times for vehicles and pedestrians.
IV.2.vCMS shall display Clearance Times.
IV.2.viCMS shall display Ring Status Screen.
IV.3: Signal Phase and Time (SPaT) LoggingCMS shall log second-by-second traffic signal controller data (SPaT) and store historical data.
IV.4: Intersection Map ViewCMS shall provide a detailed map view.
IV.4.i.aCMS shall display Signal status for Vehicles (Green, Yellow, and Red Indications).
IV.4.i.bCMS shall display Signal status for Transit Signals (Red and White Lunar Bar Indications).
IV.4.i.cCMS shall display Signal status for Pedestrians (Walk, Flashing Don’t Walk, and Solid Don’t Walk Indications).
IV.4.iiCMS shall display customizable placement of signal indications.
IV.4.iiiCMS shall display Controller phase information.
IV.5: Alert LoggingCMS shall log the alert types selected by users.
IV.5.iCMS shall store historical information over an adjustable time (e.g. 3 months or 1 year).
IV.5.iiCMS shall export to a spreadsheet (.csv or .xlsx).
IV.5.iiiCMS shall email selected alerts to user accounts.
IV.5.ivCMS shall send selected text message alerts to assigned phone numbers.
IV.6: User Profile CustomizationCMS shall provide the options to create various user account profiles (e.g. administrator, traffic engineer, traffic management center operator).
IV.7: Data and CommunicationCMS shall follow the requirements as listed in IFB Attachment 12 (SFMTA Requirements for Technology Projects)
IV.7.iCMS shall be fully hosted in a commercial cloud environment. All production data must be stored and processed within the United States.
IV.7.iiCMS shall maintain current industry-recognized security certifications, at a minimum have the following certifications or are in process of obtaining:
a)SOC 2 Type II (or equivalent, required)
b)ISO 27001 (preferred, not required)
c)FedRAMP authorization (preferred if applicable, not required)
IV.7.iiiCMS shall support:
a)Encryption of data at rest and in transit (TLS 1.2 or higher)
b)Role-based access control (RBAC)
c)Multi-factor authentication (MFA) for administrative access
IV.7.ivContractor shall maintain a documented disaster recovery and business continuity plan, including:
a)Recovery Time Objective (RTO) of ≤ 24 hours
b)Recovery Point Objective (RPO) of ≤ 24 hours
c)Regular testing of backup and recovery procedures
IV.7.vContractor shall have a formal incident response program and agree to notify the City of any security incident impacting its data within 24 hours of detection.
IV.7.viContractor shall provide the ability to export data in a standard, non-proprietary format upon request or contract termination

PM: Addition per Sid’s email on 9/16.

File details come from the government source that posted it. Updated .