City and County of

San Francisco

Request for Proposals for

Security Services

RFP No. SFMTA-2026-47-LOC

EVENT ID: SFGOV-0000012149

(CCO No. 26-1696)

Date Issued:

Pre-Proposal Conference:

Deadline to Submit NDA:

Deadline for Questions:

Proposal Due:

October 7, 2026

October 23, 2026, 1:00 PM PT

October 26, 2026, 1:00 PM PT

October 30, 2026, 1:00 PM PT

November 9, 2026, 1:00 PM PT

Contract Administrator: Carlos F. Peza Principal Administrative Analyst II San Francisco Municipal Transportation Agency Phone: (415) 579-9801 Email: Carlos.Peza@sfmta.com

SFMTA P-690 (03-25) i October 7, 2026

4922-3039-6368 v.1

San Francisco Municipal Transportation Agency (SFMTA) Request for Proposals for

Security Services

Table of Contents

Page

I. Introduction and Schedule

A. Background and Operating Environment

B. Procurement Objectives

C. Facility and Function Information

D. Access to Confidential Information

1. Confidential Appendices and NDA Access Process

2. Responsibility for Timely NDA Submission

E. Selection Overview

F. Anticipated Contract Term

G. Anticipated Contract Not-to-Exceed Amount

H. Reserved. (Indefinite Quantity, As-Needed Contract)

I. Reserved. (Cooperative Agreement)

J. RFP Schedule

K. Contract Terms, Performance Metrics, and Negotiations

L. City’s Social Policy Requirements

M. City Supplier Registration

II. Scope of Services

A. Overview of Services

B. Service Delivery Framework

C. Organization and Use of RFP Documents

D. Contractor Responsibilities

E. Innovative Service Delivery Approaches (ISDAs) and Optional Enhancements

III. Minimum Qualifications

IV. Submission Requirements

A. Time and Place for Submission of Proposals

B. Proposal Content and Format

SFMTA P-690 (03-25) ii October 7, 2026

C. Part 1 – Written Proposal

1. Introduction and Executive Summary (up to 2 pages)

2. Supplier Information (up to 1 page)

3. Minimum Qualifications Documentation (up to 2 page)

4. Project Approach (up to 10 pages)

5. Preliminary Transition and Mobilization Plan (up to 3 pages)

6. Required Base-Service Technology and Technology Integration Plan (up to 4 pages)

7. Performance Management and Quality Assurance Approach (up to 4 pages, excluding the completed

Appendix E table)

8. Innovative Service Delivery Approaches and Optional Enhancements (up to 4 pages)

9. Firm and Team Experience (up to 6 pages, excluding resumes and organizational chart)

D. Part 2 – Contract Monitoring Division (CMD) Attachment 3

E. Part 3 – Fee Proposal

1. Fee Proposal Structure

2. Labor, Pricing, and Service Delivery Assumptions

3. Price Discrepancies

4. Price Lists

F. Part 4 – Contract Terms and Performance Metric Negotiation Requests

1. SFMTA’s Contract Terms Negotiation Requests

2. Performance Metric Modification Requests

3. Consideration of Requested Changes

V. Evaluation and Selection Criteria

A. Initial Screening

B. Overall Evaluation Process

C. Selection Criteria

1. Completeness and Organization of Proposal Submission (10 points)

2. Project Approach (50 points)

3. Preliminary Transition and Mobilization Plan (10 points)

4. Required Base-Service Technology and Technology Integration Plan (30 points)

5. Performance Management and Quality Assurance Approach (30 points)

6. Innovative Service Delivery Approaches and Optional Enhancements (30 points)

7. Firm and Team Experience (30 points)

SFMTA P-690 (03-25) iii October 7, 2026

8. Fee Proposal (100 points)

9. Phase 2 - Supplemental Evaluation of Short-Listed Proposers (100 points, if conducted)

D. Reserved. (Application of LBE Bid Discount/Rating Bonus)

E. Contract Negotiations

VI. Pre-Proposal Conference

A. Pre-Proposal Conference

B. Proposer Questions and Requests for Clarification

VII. Contract Award

VIII. Insurance and Bonds

A. Insurance

B. Reserved. (Proposal Bond)

C. Performance and Payment Bond

D. Fidelity Bond or Crime Policy

E. Failure to Provide Insurance and/or Bonds

IX. Terms and Conditions for Receipt of Proposals

A. Cybersecurity Risk Assessment

B. Errors and Omissions in RFP

C. Inquiries Regarding RFP

D. Objections to RFP Terms

E. RFP Addenda

F. Proposal Term

G. Revision to Proposal

H. Proposal Errors and Omissions

I. Financial Responsibility

J. Proposer’s Obligations under the Campaign Reform Ordinance

K. Limitation on Communications Prior to Contract Award

L. Public Disclosure

M. Public Access to Meetings and Records

N. Proposal Selection Shall Not Imply Acceptance

O. Reservations of Rights by the SFMTA

P. No Waiver

Q. Other

SFMTA P-690 (03-25) iv October 7, 2026

R. Local Business Enterprise Requirements

1. LBE Subcontracting Participation Requirements and Good Faith Efforts Requirements

2. Reserved. (LBE Prime/JV Participation and Ratings Bonuses)

3. CMD Forms

4. Contract Compliance Officer

5. LBE Payment and Utilization Tracking

S. Employment Nondiscrimination and Economically Disadvantaged Workforce Hiring Provisions

1. General

2. Nondiscrimination Provisions

3. Non-Compliance with Article 131 Prior to Contract Award

4. Complaints of Discrimination after Contract Award

5. Trainees – SFMTA Employment Training Program

X. Contract Requirements

A. Nondiscrimination in Contracts and Benefits

B. Minimum Compensation Ordinance

C. Health Care Accountability Ordinance

D. First Source Hiring Program

E. Conflicts of Interest

F. Prevailing Wage and Employee Retention

G. Non-Profit Entities

H. Other Social Policy Provisions

XI. Protest Procedures

A. Protest of RFP Terms

B. Protest of Non-Responsiveness Determination

C. Protest of Non-Responsibility Determination

D. Protest of Contract Award

E. Delivery of Protests

SFMTA P-690 (03-25) v October 7, 2026

Appendices:

Appendix Content Page

A. Scope of Services A-1

B. Non-Disclosure Agreement B-1

C. SFMTA Current Facilities and Function Information

(Non-Disclosure Agreement Required) C-1

D. SFMTA-Owned or SFMTA-Operated Security Equipment, Hardware, Software, Systems, and Resources

(Non-Disclosure Agreement Required)

D-1

E. Performance Requirements, Key Performance Indicators, Performance

Incentives, and Liquidated Damages

E-1

F. Sample Agreement for Professional Services (Form P-600) F-1

G. Fee Proposal Form G-1

H. Prevailing Wage and Related Information for Employees under Agreement

No. SFMTA-2018-48: Armed and Unarmed Security Guard Services

Appendix H-1: Prevailing Wage, Hours, and Related Information for

Security Employees.

Appendix H-2: Current Employee Classifications, Billing Rates, and

Staffing Information

Appendix H-3: Current Security Guard Shift Schedule (Non-Disclosure

Agreement Required)

Appendix H-4: Current Contract Service-Level and Rate Information.

H-1

I. SFMTA Model Post Orders and Standard Operating Procedures (Non-

Disclosure Agreement Required)

I-1

J. CMD Attachment 3: Requirements for General Services Contracts for

Contracts equal or greater than 50% of the Threshold Amount and that are

Advertised on or after November 1, 2025 (separate document). Proposers must submit the following forms:

Form 2A CMD Contract Participation Form

Form 2B “Good Faith Efforts” Requirements Form

Form 3 CMD Compliance Affidavit

J-1

K. Attestation of Compliance on Communications Prior to Contract Award K-1

L. Certification Regarding Debarment, Suspension, and Other Responsibility

Matters

L-1

M. Certification Regarding Lobbying M-1

N. Sample Performance Bond N-1

San Francisco Municipal Transportation Agency RFP for Security Services

SFMTA P-690 (03-25) 1 of 58 October 7, 2026

I. Introduction and Schedule

A. Background and Operating Environment

The San Francisco Municipal Transportation Agency (SFMTA or Agency) is requesting proposals from qualified firms (Proposers) to provide armed and unarmed security guard services and related security operations support functions (Services) to support SFMTA operations.

The SFMTA manages a large, multimodal transportation system and employs a diverse workforce of approximately 6,000 employees. The SFMTA owns, occupies, or operates more than 400 facilities, including bus yards, rail yards, maintenance yards, subway stations, trade shops, and related facilities. The operating environment includes seven bus yards, three rail yards including the Cable Car Barn, 12 subway stations within the Market Street Subway and Central

Subway, and seven tunnels equipped with intrusion detection software.

The SFMTA maintains a Security Operations Center (SOC) staffed by SFMTA and contractor personnel, directed by the SFMTA, with access to SFMTA video systems, including approximately 13,000 cameras on revenue fleet vehicles and 2,500 stationary video cameras located throughout SFMTA facilities and operations.

The SFMTA currently administers its contracted security services through Site-, post-, function-, and assignment-specific Post Orders and Standard Operating Procedures, which are types of SFMTA Operating Documents. Current services generally include fixed-post and access-control functions, patrols, Revenue Security Support, SOC coordination, incident and activity reporting, emergency response, and related operational requirements. Current operations also use SFMTA-owned/operated video, alarm, access-control, communications, and related systems. Appendices C, D, H, and I provide additional information about the Current Operating

Environment for Proposal preparation and transition planning.

The SFMTA’s objective is to maintain required security services coverage and operational readiness necessary to support its facilities and operations while establishing a more accountable, adaptable, and technology-supported service-delivery model. Through this solicitation, the

SFMTA seeks to select a Contractor that will serve as a trusted partner in delivering reliable, responsive, and continuously improving security Services across the SFMTA system.

The Required Baseline State is described in Appendix A (Scope of Services) and may be supplemented by the selected Proposer’s Baseline Proposal as accepted by the SFMTA, including Required Base-Service Technology. Proposers may also separately propose Innovative

Service Delivery Approaches and Optional Enhancements as described in Section II.E.

Before and during the term of the anticipated Agreement, the SFMTA may implement physical access-control, perimeter, and other site improvements. Accordingly, the SFMTA seeks

Services that allow the Agency to adapt staffing levels, deployment models, and service delivery over the term of the Agreement to improve operational flexibility and cost control while maintaining required service levels, operational readiness, and public safety.

SFMTA P-690 (03-25) 2 of 58 October 7, 2026

The Agency encourages Proposers to submit practical, reliable, and cost-effective approaches to staffing and deployment, mobile response, electronic workforce verification, patrol tracking, technology-supported monitoring, integrated reporting, and other operational practices that maintain or improve security outcomes, contract administration, and cost control.

B. Procurement Objectives

The Procurement Objectives below describe the principal security outcomes the SFMTA seeks through this solicitation.

Procurement Objective Description

Systemwide Security Provide systemwide transit security support and visible deterrence to protect customers, employees, facilities, and operations.

Operational Flexibility Support operational flexibility & emergency response capabilities.

Technology-Supported

Accountability

Use reliable, intuitive, user-friendly technology tools to support

Service delivery, reporting, patrol verification, staffing accountability, and invoice validation.

SOC Coordination Support SOC integration with SFMTA operations and centralized

Service coordination.

Cost Control and Service

Improvement

Identify Service delivery approaches that support SFMTA operations, staffing utilization, cost control, or security outcomes.

Reporting and

Documentation

Facilitate accountability for the use of public funds through reports, records, documentation, and invoice-support materials.

Compliance Facilitate contract administration and compliance with regulatory, Agreement, and SFMTA requirements.

Accountable Partnership Establish a collaborative and transparent relationship with a

Contractor that responds to changing operational needs, communicates candidly, addresses Service deficiencies, and supports continuous improvement and cost control.

C. Facility and Function Information

For purposes of this RFP, “facility types” are SFMTA locations where Services may be deployed, and “function types” are security services categories that may apply to one or more locations. The following table summarizes the facility and function types that may require

Services during the term of the Agreement and identifies the principal security objectives, potential deployment models, and supportive controls associated with those service types. The table is provided for general reference and Proposal preparation purposes only and does not establish required Services, staffing levels, deployment models, patrol frequencies, schedules, or

SFMTA P-690 (03-25) 3 of 58 October 7, 2026 other facility- or function-specific operational requirements. The SFMTA will establish applicable facility- and function-specific requirements through SFMTA Operating Documents

(including Post Orders, Standard Operating Procedures, SFMTA-approved operational plans, procedures, and written instructions).

Facility/

Function

Type

Security Objectives Potential Deployment Models Supportive

Controls

Bus and Rail

Yards

Control access, deter unauthorized entry, identify safety or security violations, deny access to unauthorized people, observe and report, and support gate opening or closing periods.

Fixed coverage when directed, foot patrols during gate opening or operational periods, and technology-supported patrols.

Gates, alarms, controlled access, video surveillance, security policies, and non-public facility rules.

Subway

Stations

Visible presence, staff and customer assistance, safety or security response, incident reporting, emergency response, and observe-and-report duties.

Fixed coverage when directed, foot patrols, Roving Patrols, SOC/Transit Management

Center coordination, and other

SFMTA-directed coverage.

Video surveillance and

SFMTA-approved station procedures.

Uncovered

Facilities

Periodic patrols, emergency response, facility condition reporting, and temporary fixed coverage when required.

Scheduled patrols, as-needed coverage, and technology-supported monitoring.

Video surveillance and controlled access.

Tunnel Gates Open/close support, intrusion or alarm response, gate or portal checks, emergency response, and temporary fixed coverage when required.

Scheduled patrols, as-needed coverage, and fixed coverage when directed.

Intrusion detection, cameras, alarms, and controlled access.

SFMTA P-690 (03-25) 4 of 58 October 7, 2026

Facility/

Function

Type

Security Objectives Potential Deployment Models Supportive

Controls

Revenue

Services

Protection of staff, cash, fare media, restricted areas, gate operations, alarm and video monitoring support, observe-and-report duties, and escort support for revenue collection.

Fixed Guard coverage when directed, scheduled escort coverage, Special Event

Services, and other SFMTA-directed coverage.

Controlled access, video surveillance, alarm systems, and Revenue procedures.

SOC Coordinate deployment, monitor alarms and video when assigned, manage communications, produce situational awareness reports, support investigations, and support mass notification.

Non-Guard Support Functions, technology-supported monitoring, administrative support, and dispatch coordination.

Controlled access, video surveillance, alarm notification, mass notification software, badging systems, and other

SFMTA-approved systems.

Appendix C provides additional information regarding the SFMTA’s current facilities, locations, and functions for reference and Proposal preparation. Inclusion in Appendix C does not guarantee that Services will be deployed at a particular facility, location, or function.

D. Access to Confidential Information

1. Confidential Appendices and NDA Access Process

RFP documents that do not contain Confidential Information may be downloaded from the

City’s Supplier Portal website https://sfcitypartner.sfgov.org/pages/Events-BS3/event-search.aspx. Certain materials included in the RFP documents may qualify as Sensitive Security

Information (SSI) or otherwise be protected from public disclosure. Because their public release could compromise the security of SFMTA facilities and operations, these materials are designated Confidential Information and are not posted publicly, but may be available to

Proposers that execute the required Non-Disclosure Agreement (NDA).

These materials include:

• Appendix C (SFMTA Current Facilities and Function Information)

• Appendix D (SFMTA-Owned or SFMTA-Operated Security Equipment, Hardware, Software, Systems, and Resources)

• Appendix H-3 (Current Security Guard Shift Schedule)

• Appendix I (SFMTA Model Post Orders and Standard Operating Procedures) https://sfcitypartner.sfgov.org/pages/Events-BS3/event-search.aspx https://sfcitypartner.sfgov.org/pages/Events-BS3/event-search.aspx

SFMTA P-690 (03-25) 5 of 58 October 7, 2026

These “Confidential Appendices” must be obtained directly from the SFMTA and will be provided only to prospective Proposers that have executed the NDA, included as Appendix B.

Proposers seeking the Confidential Appendices must complete and submit the NDA by e-mail to: Carlos.Peza@sfmta.com by 1:00 PM PT on October 26, 2026. Any requests for the

Confidential Appendices received after this deadline will not be accepted or considered.

The SFMTA will provide the Proposer with copies of the Confidential Appendices within three business days of receiving a completed and acceptable NDA. The SFMTA has the sole and absolute discretion to determine whether an NDA is complete and acceptable.

2. Responsibility for Timely NDA Submission

It is the Proposer’s responsibility to ensure that its request for access to the Confidential

Appendices, including the completed NDA, is received by the SFMTA by 1:00 PM PT on

October 26, 2026. Failure to submit a timely and complete NDA will not be grounds for an extension of the Proposal Due Date, waiver of requirements, or any other relief. Any Proposer that does not receive the Confidential Appendices as a result of a late or incomplete NDA submission shall prepare its Proposal based solely on its own review of the publicly available

RFP documents.

E. Selection Overview

The SFMTA may award a contract to the highest-ranked Proposer that meets the Minimum

Qualifications (see Section III) and LBE requirements of this RFP and successfully completes contract negotiations as described in Section V.

Proposers must provide documentation that clearly demonstrates that each Minimum

Qualification and each Local Business Enterprise (LBE) requirement has been met. Any

Proposal that does not meet the Minimum Qualifications and LBE requirements will be deemed non-responsive.

SFMTA staff will initially review each Proposal for responsiveness. Elements reviewed will include, without limitation: Proposal completeness, compliance with format requirements, compliance with Minimum Qualification requirements, and compliance with LBE requirements.

Responsive Proposals will be evaluated in two phases as described in Section V: Phase 1 -

Written and Fee Proposal Evaluation; and, if conducted, Phase 2 - Supplemental Evaluation. The

SFMTA will combine the applicable scores and invite the highest-ranked Proposer to contract negotiations as described in Sections I.K and V.E.

F. Anticipated Contract Term

A contract awarded pursuant to this RFP shall be non-exclusive with an original term of three (3) years. The SFMTA, at its sole discretion, shall have the option to extend the term for two (2) additional years, for a total of five (5) years.

mailto:Carlos.Peza@sfmta.com

SFMTA P-690 (03-25) 6 of 58 October 7, 2026

G. Anticipated Contract Not-to-Exceed Amount

The not-to-exceed (NTE) amount for a contract awarded pursuant to this Solicitation cannot be anticipated at the time of this RFP but shall be based on the selected Proposal.

H. Reserved. (Indefinite Quantity, As-Needed Contract)

I. Reserved. (Cooperative Agreement)

J. RFP Schedule

The anticipated schedule for this RFP is set forth below. These dates are tentative and subject to change. It is the responsibility of the Proposer to check for any Addenda to this RFP or other pertinent information posted in the City’s Supplier Portal.

Phase Date

RFP is issued by the SFMTA: October 7, 2026

Pre-Proposal Conference: October 23, 2026, 1:00 PM PT

Deadline for submission of Appendix B, Non-

Disclosure Agreement (NDA):

October 26, 2026, 1:00 PM PT

Deadline for submission of written questions or requests for clarification:

October 30, 2026, 1:00 PM PT

Proposals due: November 9, 2026, 1:00 PM PT

K. Contract Terms, Performance Metrics, and Negotiations

The highest-ranked Proposer will be invited to contract negotiations and will be required to enter into a contract substantially in the form attached as Appendix F (Sample Agreement for

Professional Services).

A Proposer seeking changes to the SFMTA’s contract terms in Appendix F or to an

SFMTA-established Performance Metric in Appendix E shall submit all requested changes as Part 4 of its Proposal in accordance with Section IV.F. Following the scoring and ranking of Proposals, the highest-ranked Proposer will be invited to contract negotiations. Negotiations will constitute the final stage of the evaluation and selection process. During contract negotiations, the SFMTA may consider the nature and extent of the Proposer’s requested changes to Appendix F or any Performance Metric in Appendix E in determining whether a satisfactory Agreement can be reached. Requested changes will not be scored or evaluated by the

Evaluation Panel, and the Baseline Proposal may not depend on SFMTA acceptance of requested changes.

The highest-ranked Proposer will also be required to prepare a Detailed Transition and

Mobilization Plan, as described in Section V.E. If the SFMTA determines, in its sole discretion, that a satisfactory Agreement cannot be negotiated within a reasonable time, the SFMTA may terminate negotiations and begin negotiations with the next highest-ranked Proposer that meets the Minimum Qualifications and LBE requirements of this RFP.

SFMTA P-690 (03-25) 7 of 58 October 7, 2026

L. City’s Social Policy Requirements

The San Francisco Municipal Code establishes requirements for people seeking to do business with the City (Social Policy Requirements). The Social Policy Requirements set forth in

Sections IX and X below are NOT a complete list. A complete list of Social Policy Requirements applicable to this Solicitation can be found in Appendix F, Sample Agreement for Professional

Services.

M. City Supplier Registration

Contractors must become an “Approved Supplier” in order to enter into an Agreement with the City or the SFMTA. Approved Suppliers are entities that have met all the compliance requirements necessary to conduct business with the City, such as business tax registration and

Article 131 (Nondiscrimination in Contracts and Equal Benefits Requirement) compliance. The following requirements pertain only to Proposers not currently registered with the City as a

Supplier.

Step 1: Register as a BIDDER at the City’s Supplier Portal:

https://sfcitypartner.sfgov.org/pages/index.aspx

Step 2: Follow instructions for converting your BIDDER ID to a SUPPLIER ID. This will require you to register with the City Tax Collector’s Office and submit the online 12B

Declaration for Article 131 (Equal Benefits Program) compliance through the Supplier portal.

Once these forms have been completed, submitted, and processed, you will be notified via email with your organization's new Supplier ID. That email will also provide instructions for completing your Supplier registration.

• City Business Tax Registration Inquiries: For questions regarding business tax registration procedures and requirements, contact the Tax Collector’s Office at (415)

554-4400 or, if calling from within the City and County of San Francisco, 311.

• Equal Benefits Program Inquiries: For questions concerning the San Francisco

Labor and Employment Code Articles 131 and 132, go to: www.sfgov.org/cmd.

https://sfcitypartner.sfgov.org/pages/index.aspx http://www.sfgov.org/cmd

SFMTA P-690 (03-25) 8 of 58 October 7, 2026

II. Scope of Services

A. Overview of Services

This section provides an overview of the Services the Contractor shall provide under the

Agreement.

The Contractor shall provide Guard Service Delivery, Non-Guard Support Functions, and

Supervision, Administration, and Management Services, including providing trained and qualified armed and unarmed Guards, supervisors, management personnel, SOC coordination and support, Revenue Security Support, and other Services required by the Agreement, this RFP, Appendix A, and SFMTA direction.

The SFMTA may identify minimum staffing, post coverage, patrol, response, or service requirements where necessary for operational, safety, regulatory, or security reasons. However, the SFMTA seeks Proposals that demonstrate how the Contractor will achieve required security outcomes through efficient staffing, mobile response, technology-enabled monitoring, patrol verification, SOC coordination, and other approved operational strategies.

B. Service Delivery Framework

To support Proposal preparation, this RFP describes the SFMTA’s security program across three service-delivery states: (1) the Current Operating Environment, (2) the Required Baseline

State, and (3) Innovative Service Delivery Approaches and Optional Enhancements.

1. Current Operating Environment: Appendices C, D, H, and I provide information regarding current facilities, functions, staffing, prevailing wage and staffing conditions, SFMTA resources, Post Orders, and Standard Operating Procedures for Proposal preparation and transition planning. This information is intended to assist Proposers in understanding the existing operating environment, preparing transition plans, and identifying implementation requirements.

2. Required Baseline State: Appendix A establishes the required Services and Contractor

Responsibilities, including Deliverables, transition and Baseline Establishment, performance management, and contract closeout. Appendix E establishes the related performance requirements and measurement framework.

3. Innovative Service Delivery Approaches (ISDAs) and Optional Enhancements:

Proposers may separately submit ISDAs that propose innovative methods for meeting

Baseline Requirements and Optional Enhancements that add services, technology, or functionality beyond the Baseline Requirements.

C. Organization and Use of RFP Documents

The RFP documents serve the following functions:

• Appendix A describes the Required Baseline State, including the required Services and

Contractor Responsibilities.

SFMTA P-690 (03-25) 9 of 58 October 7, 2026

• Appendix B provides a Non-Disclosure Agreement that is required for Proposers to access the Confidential Appendices.

• Appendix C provides current facility and function information for Proposal preparation.

• Appendix D identifies SFMTA owned/operated technology and other resources that the

Contractor may access or use in delivering the Services.

• Appendix E establishes performance requirements and measurement framework for the

Required Baseline State, and any accepted ISDAs or Optional Enhancements.

• Appendix F contains the terms and conditions that will govern the Agreement resulting from this RFP, as well as definitions of capitalized terms used in this RFP and its

Appendices.

• Appendix G contains the Fee Proposal form to present costs for the Baseline Proposal and separately identified ISDAs and Optional Enhancements.

• Appendix H contains current prevailing wage, staffing, and contract information for

Proposal preparation and transition planning.

• Appendix I contains model Post Orders and Standard Operating Procedures for

Proposal preparation and transition planning. These samples will not become operative under the resulting Agreement unless the SFMTA designates them as applicable

SFMTA Operating Documents.

• Appendix J contains the CMD Attachment 3 and the required LBE forms for documenting compliance with the RFP’s LBE participation and good-faith outreach requirements.

• Appendix K contains the Attestation of Compliance on Communications Prior to

Contract Award, used to certify compliance with the RFP’s communication restrictions.

• Appendix L contains the Certification Regarding Debarment, Suspension, and Other

Responsibility Matters, used to certify eligibility and responsibility to contract with the

City and County of San Francisco.

• Appendix M contains the Certification Regarding Lobbying, used to certify compliance with lobbying and contingent-fee restrictions and disclose applicable lobbying activity.

• Appendix N contains the Sample Performance Bond that the selected Proposer will be required to furnish in accordance with Section VIII and the Agreement.

SFMTA P-690 (03-25) 10 of 58 October 7, 2026

D. Contractor Responsibilities

The selected Contractor will be responsible for the three principal areas of responsibility summarized in the table below: (1)

Guard Service Delivery, (2) Non-Guard Support Functions, and (3) Supervision, Administration, and Management. The SFMTA will determine which Services are required at particular Sites or for particular functions and will authorize those Services through applicable SFMTA Operating Documents and other SFMTA direction, as provided in Appendix A.

The item numbers below correspond to more detailed requirements presented in Appendix A, Section II. Appendix A contains the complete requirements and governs in the event of any inconsistency with this summary. Unless expressly stated otherwise, the requirements apply to Services performed by Contractor and its Subcontractors, and Contractor remains responsible for Subcontractor compliance and performance.

Appendix A, Section II

Item(s)

Main Area Responsibility Summary of Contractor Responsibilities

1.1–1.2 Guard Service

Delivery

Facility, Transit &

Public-Facing Security

Provide unarmed Guards for fixed-post coverage, facility security, access control, alarm response, lock and unlock support, intrusion-alert support, graffiti and vandalism response, situational awareness, incident reporting, emergency response, subway and station coverage, customer and employee assistance, reporting, and coordination with SFMTA and public-safety personnel.

1.3 Revenue Collection

Security Support

Provide armed or unarmed Revenue Collection Security Support, including fixed coverage, escorts, access-control support, monitoring, incident documentation, field supervision, separation-of-duties controls, and other safeguards for Revenue Collection operations.

1.4 Emergency, Special

Event & Other As-

Needed Coverage

Provide additional armed or unarmed Guards, field supervision and other

SFMTA-approved security resources for emergencies, Special Events, and other SFMTA-requested needs. Maintain continuity procedures and notify the

SFMTA of events that materially affect staffing or operational readiness.

SFMTA P-690 (03-25) 11 of 58 October 7, 2026

Appendix A, Section II

Item(s)

Main Area Responsibility Summary of Contractor Responsibilities

2.1–2.2 Non-Guard

Support

Functions

SOC & Other

Operational Support

Provide Qualified Personnel for SFMTA-directed SOC and operational support functions, including deployment and dispatch coordination, communications, CCTV and alarm support, incident documentation, alerts, reporting, badging, credentialing, data review, administrative support, investigation support, and coordination with public-safety partners.

3.1–3.4 Supervision, Administration &

Management

Management, Staffing, Training & Personnel

Qualifications

Provide on-site and off-site management and supervision; staffing, scheduling, backup and relief coverage; personnel administration; escalation;

and coordination with SFMTA staff. Ensure Contractor and Subcontractor personnel are screened, trained, licensed, certified, equipped, qualified, and assigned only to duties for which they meet applicable requirements.

3.5–3.8 Equipment, Technology, Reporting &

Documentation

Provide and maintain required equipment, vehicles, communications devices, uniforms, materials, and technology. Use SFMTA-approved, intuitive, and user-friendly systems for staffing, scheduling, dispatch, timekeeping, attendance, assignment verification, GPS-based patrol verification, reporting, performance monitoring, and invoice validation. Maintain required data and

Records in a searchable digital format.

3.9–3.12 Performance, Compliance, and

Continuous

Improvement

Analyze operational information and changes in risk; conduct quality assurance, audits, inspections, corrective action, and operational reviews; and recommend improvements to security outcomes, accountability, and cost control. Comply with applicable legal, licensing, labor, LBE, prevailing-wage

(including SF Labor and Employment Code Section 102.11 and Article 109), employee-retention, SFMTA Operating Document, Subcontractor, reporting, and Records requirements.

SFMTA P-690 (03-25) 12 of 58 October 7, 2026

E. Innovative Service Delivery Approaches (ISDAs) and Optional Enhancements

For purposes of this RFP:

1. Current Operating Environment means the current facilities, functions, staffing and labor information, operating practices, SFMTA resources, Post Orders, and Standard

Operating Procedures described in Appendices C, D, H, and I for Proposal preparation and transition planning purposes.

2. Baseline Requirements means all the mandatory requirements of this RFP and the resulting Agreement, including the required Services and Contractor Responsibilities in

Appendix A, the Performance Requirements in Appendix E, Required Base-Service

Technology, and the model Post Orders and Standard Operating Procedures provided in

Appendix I.

3. Baseline Proposal means the Proposer’s Written Proposal and Fee Proposal submitted for meeting the Baseline Requirements without relying on an ISDA or Optional

Enhancement.

4. Required Base-Service Technology means all Contractor-provided technology required to perform the Baseline Requirements.

5. Innovative Service Delivery Approach or ISDA means a Proposer-identified and separately described innovative method for meeting a Baseline Requirement that materially changes how Services are delivered, coordinated, managed, or supported while maintaining or improving required service levels, accountability, and security outcomes.

6. Optional Enhancement means a separately identified addition of services, technology, or functionality beyond the Baseline Requirements. An Optional Enhancement supplements, but does not replace, a Baseline Requirement.

Proposers shall submit a complete and fully compliant Baseline Proposal. An ISDA or

Optional Enhancement may not omit, reduce, condition, reclassify, or separately price a Baseline

Requirement. The SFMTA must be able to accept or reject each ISDA or Optional Enhancement without affecting the compliance or pricing of the Baseline Proposal.

Each ISDA must identify the applicable Baseline Requirement, the approach included in the Baseline Proposal, the proposed innovative approach, and how required outcomes will be maintained or improved.

Each Optional Enhancement must identify the additional service, technology, or functionality and explain how it supplements the Baseline Requirements.

SFMTA P-690 (03-25) 13 of 58 October 7, 2026

Proposers may submit ISDAs or Optional Enhancements under Section IV.C.8, such as:

1. ISDA examples:

a. Technology-enabled or data-informed staffing, deployment, supervision, patrol, monitoring, or response models that materially differ from the Baseline Proposal while maintaining or improving required outcomes.

b. Integrated remote monitoring or dynamic deployment, deterrence, or other innovative methods that reduce fixed-post coverage while maintaining or improving

Service levels, response capability, visibility, accountability, and security outcomes.

c. Other innovative operational approaches that may improve Service delivery, reduce unnecessary duplication, support cost control, or improve security outcomes.

2. Optional Enhancement examples: Optional technology, dashboards, analytics, workflow, or system-integration enhancements beyond Required Base-Service

Technology, including AI-assisted video monitoring or analytics, automated incident tracking and escalation, predictive analytics, or trend reporting.

Each proposed ISDA or Optional Enhancement shall meet the following requirements:

1. Operational Readiness: Preserve operational readiness and avoid increasing the risk of personal injury or property damage related to SFMTA operations or property.

2. SFMTA Objectives: Support SFMTA operational objectives as reflected in Appendix

A and Appendix E.

3. Compliance: Comply with applicable laws and requirements, including privacy, labor, public records, cybersecurity, approved technology, data retention, and data protection requirements.

4. Technology and Data Review: Provide sufficient information for the SFMTA to determine whether proposed technology or data use is subject to San Francisco

Administrative Code Chapter 19B (Acquisition of Surveillance Technology) or Chapter

22J (Artificial Intelligence Tools), including the technology’s purpose and locations of use; the data collected, processed, retained, accessed, or shared; and any automated analytics or artificial intelligence functions.

5. Submission and Pricing: Provide the information required by Section IV.C.8 for each

ISDA or Optional Enhancement. All pricing and financial information must be provided only in Appendix G.

The SFMTA reserves the right to accept, reject, partially accept, modify, defer implementation of, or further negotiate any ISDA or Optional Enhancement at its sole discretion.

Submission of an ISDA or Optional Enhancement does not relieve the Proposer of its obligation to submit a complete and responsive Baseline Proposal.

SFMTA P-690 (03-25) 14 of 58 October 7, 2026

III. Minimum Qualifications

The Minimum Qualifications (MQs) set forth below are required for a Proposer to be eligible for further evaluation and award under this RFP.

Proposers must provide documentation that clearly demonstrates each MQ listed below has been met. MQ documentation should be clearly marked as “MQ1,” “MQ2,” and so on, to indicate which MQ it supports.

Each Proposal will be reviewed for an initial determination on whether the Proposer meets the MQs referenced in this section. This screening is a pass/fail determination and a Proposal that fails to meet the MQs will not be eligible for further consideration in the evaluation process.

The SFMTA reserves the right to request clarifications from Proposers prior to rejecting a

Proposal for failure to meet the MQs. Clarifications are limited exchanges between the SFMTA and the Proposer for the purpose of clarifying certain aspects of the Proposal and will not provide a Proposer the opportunity to revise or modify its Proposal.

MQ # Description

MQ1 Relevant Experience: Proposer has at least five years of direct experience within the last 10 years providing armed and unarmed security guard services for public agencies, transportation systems, large institutional campuses, critical infrastructure facilities, or comparable complex operations.

Include a statement and supporting information that Proposer has the requisite experience to meet this MQ.

MQ2 California Licensing: Proposer must hold a current and active Private Patrol

Operator license issued by the California Department of Consumer Affairs, Bureau of Security and Investigative Services, under the Private Security

Services Act.

At the Proposal Due Date, the license must not be expired, suspended, revoked, or subject to probation or another disciplinary restriction. The

Proposer must promptly notify the SFMTA of any pending or final administrative action that may suspend, revoke, restrict, or otherwise materially affect the license during the solicitation and selection process.

Include a statement and supporting documentation demonstrating that

Proposer meets this MQ, including copies of the Proposer’s current license, any related permits, registrations, or other required licensing documentation.

MQ3 Bonding Capacity: Proposer must provide evidence of the ability to secure the bonds required in Section VIII and the Sample Agreement, including a performance and payment bond in an amount equal to not less than 10 percent

SFMTA P-690 (03-25) 15 of 58 October 7, 2026

MQ # Description of the annual contract value of the Agreement, and any required fidelity bond or crime policy.

Include a statement and supporting documentation demonstrating that

Proposer meets this MQ. At a minimum, provide a Letter of Commitment from a bonding agency, surety, or insurer authorized to do business in the State of

California confirming that the Proposer will be able to secure bond(s) at the time of Contract Award.

MQ4 Local Presence: Proposer must have, or must establish before the Contract start date, an office or base of operations located within the City and County of San Francisco to support staffing, supervision, dispatch coordination, and contract administration.

Include a statement and supporting information that Proposer meets or will meet this MQ. If the Proposer currently has an office, operations base, or other local support structure in San Francisco, provide the address and a description of how it will support the Services. If the Proposer does not currently have such a location, provide a proposed local operations plan describing how

Proposer will establish and maintain the required San Francisco presence before the Contract start date.

Any Proposal that does not demonstrate that the Proposer meets MQ1 through MQ3 by the deadline for submittal of Proposals, or does not include a credible plan to meet MQ4 before the

Contract start date, may be deemed non-responsive.

SFMTA P-690 (03-25) 16 of 58 October 7, 2026

IV. Submission Requirements

A. Time and Place for Submission of Proposals

Proposals must be received by 1:00 PM PT on November 9, 2026. Proposers must submit their Proposals in an electronic format by email to Carlos.Peza@sfmta.com.

Proposers shall limit email messages to 25MB or less.

Proposers are fully responsible for ensuring their entire Proposals are received by the time and date indicated. The SFMTA will not accept late Proposals, even in cases of known email system failure. Accordingly, Proposers are encouraged to submit their Proposals at least 24 hours before the time and date due.

B. Proposal Content and Format

Firms interested in responding to this RFP must submit Proposals that include the information requested in this Section IV.B, in the order and format specified herein. The content of all Proposals must consist of the information specified below, in the order outlined below, in order to be deemed responsive.

Proposers shall ensure that the Proposal is legible and may be easily viewed on a computer monitor, laptop, or (electronic) tablet. The SFMTA prefers that text be unjustified (i.e., with a ragged-right margin), and that Proposers use an 11-point or larger sans-serif font (e.g., Arial).

Pages must have margins of at least 1” on all sides (excluding headers and footers).

Proposals shall be submitted in four separate electronic files, as listed below. Each electronic file shall be clearly marked “SFMTA-2026-47-LOC” and, as applicable, “Proposal

Part 1 - Written Proposal,” “Proposal Part 2 - CMD Attachment 3 Forms,” “Proposal Part 3 - Fee

Proposal,” and “Proposal Part 4 - Contract Terms and Performance Metric Negotiation

Requests.”

• Part 1 - One electronic copy of the Written Proposal, including the completed Appendix

E table, and completed and signed Appendices K, L, and M.

• Part 2 - One electronic copy of the completed and signed Appendix J forms (see

Section IX.R and Appendix J) as a separate electronic file.

• Part 3 - One electronic copy of the completed Appendix G (Fee Proposal Excel

Workbook Form) as a separate electronic file.

• Part 4 - Proposers seeking changes to the SFMTA’s terms and conditions in Appendix

F or to an SFMTA-established Performance Metric in Appendix E must submit all requested changes in accordance with Section IV.F.

Any document requiring a signature must be submitted as a scanned PDF file. Signatures must be by an official authorized to submit a Proposal on behalf of the Proposer. Each electronic file shall be clearly marked “SFMTA-2026-47-LOC.”

mailto:Carlos.Peza@sfmta.com

SFMTA P-690 (03-25) 17 of 58 October 7, 2026

C. Part 1 – Written Proposal

Written Proposals must include the information requested in this Section IV.C, in the order specified. Written Proposals must include a table of contents showing the applicable section headings and sub-headings, section numbering, and page numbers. Page limitations, if any, are indicated below in parentheses next to the corresponding section headings.

It is imperative that the Proposal follow the format as listed below. All sections must be separated by a labeled cover page. Cover pages do not count against the page limits indicated below.

1. Introduction and Executive Summary (up to 2 pages)

Submit a letter of introduction with an executive summary of the Proposal that includes the information listed below. The letter must be signed by an authorized representative of the Proposer. The authorized representative must have the authority to obligate the Proposer’s team to perform the commitments made in the Proposal.

a. Proposer Contact. Name, address, telephone number, and email address of

Proposer’s contact person for this Proposal.

b. Account Manager. Identify an overall account manager who will serve as the primary contact with the SFMTA.

c. Statement of Commitment. A statement confirming that Proposer is willing and able to perform the work described in the RFP and will meet the LBE Ordinance requirements.

d. Executive Summary of Approach. Summary of the Proposer’s overall approach to providing the Services.

2. Supplier Information (up to 1 page)

Proposals shall contain one of the following statements.

a. “My company is currently a City and County of San Francisco Supplier, and the

City and County of San Francisco Supplier Number is: __________.”

Or

b. “My company is currently not a City and County of San Francisco Supplier but will register to become one.”

3. Minimum Qualifications Documentation (up to 2 page)

Provide a one-page summary that clearly demonstrates that each Minimum

Qualification (MQ) listed in Section III (Minimum Qualifications) has been met. Minimum

Qualification documentation should be clearly marked as “MQ1,” “MQ2,” and so forth, to

SFMTA P-690 (03-25) 18 of 58 October 7, 2026 indicate which MQ it supports. Licenses, bonding letters, and other supporting documents do not count against the one-page limit.

4. Project Approach (up to 10 pages)

Describe the Proposer’s approach to delivering the required Services and achieving the Required Baseline State. The response should focus on the overall operating model and should not repeat detailed information requested in the other components of the Written Proposal described below - Preliminary Transition and Mobilization Plan, Required Base-Service

Technology and Technology Integration Plan, Performance Management and Quality Assurance

Approach, or ISDA and Optional Enhancement sections.

At a minimum, address:

a. Service Delivery Model: Describe the proposed baseline service-delivery model and explain how it addresses the SFMTA’s operating environment, security needs, operational constraints, Procurement Objectives in Section I.B, and the

Services and Contractor Responsibilities in Appendix A.

b. Staffing: Describe the approach to: (i) staffing, deployment, supervision, and personnel support; (ii) training and qualifications of personnel; (iii) personnel-level equipment required to perform assigned duties; (iv) customer service, incident response (including de-escalation methods), and other public-facing interactions; and (v) development and maintenance of the required Staffing, Personnel Qualification, Training, and Deployment Plan.

c. Operational Coordination: Describe how the Proposer will establish and maintain a collaborative, responsive, and transparent working relationship with the SFMTA, including the Proposer’s approach to coordinating with: (i) the

SFMTA’s Chief Security Officer; (ii) SOC; (iii) Transit Management Center; (iv)

Revenue Collection and Sales; (v) facility maintenance and operations; (vi) San

Francisco Police Department (SFPD); (vii) emergency responders; and (viii) other

SFMTA or public safety partners.

d. Administration and Continuous Improvement: Describe the approach to (i) workforce accountability, (ii) trend and risk analysis, (iii) operational reviews,

(iv) reporting, (v) records management, (vi) invoice preparation and support, (vii) continuous improvement, and (viii) cost control.

Submit any innovative staffing or deployment models, remote monitoring or deterrence methods, or optional technology enhancements under Section IV.C.8 (Innovative

Service Delivery Approaches and Optional Enhancements). The Project Approach in the

Baseline Proposal shall not rely on SFMTA acceptance of any ISDA or Optional Enhancement to satisfy an RFP requirement.

SFMTA P-690 (03-25) 19 of 58 October 7, 2026

5. Preliminary Transition and Mobilization Plan (up to 3 pages)

Appendix A, Section IV (Transition, Mobilization, and Baseline Establishment) describes the Service transition requirements.

Provide a Preliminary Transition and Mobilization Plan that describes how the

Proposer will meet those requirements while maintaining uninterrupted Service coverage during contract startup. At a minimum, address: (a) the proposed schedule, milestones, responsibilities, dependencies, principal risks, mitigation measures, and achievement of Baseline Establishment no later than 60 calendar days after Service Commencement; (b) staffing and employee retention; (c) administrative and compliance readiness; (d) training, equipment, reporting, system access, and the timing, milestones, and dependencies for implementation of the Required Base-

Service Technology described in Section IV.C.6;…