Firearms Detection for MTAPF RFI.pdf

1 | P a g e

Request for Information (RFI) Artificial Intelligence (AI) Visible Firearm Detection Software

1 INTRODUCTION

The Maryland Transit Administration (MTA), on behalf of the Maryland Transit Administration Police Force (MTAPF), is seeking information from qualified vendors regarding commercially available Artificial Intelligence (AI) software capable of detecting visible firearms through existing video surveillance systems.

MTA is conducting market research to better understand currently available AI software, vendor capabilities, system requirements, integration methods, implementation considerations, licensing models, and lifecycle costs. MTA is particularly interested in software that can integrate with its existing Internet Protocol (IP) camera infrastructure and Video Management Systems (VMS) to support timely notification and response to potential firearm-related threats.

This RFI is issued solely for information-gathering and planning purposes. It does not constitute a solicitation, request for proposals, invitation for bids, or commitment by MTA to procure any goods or services.

2 OBJECTIVES

The objectives of this RFI are to:

• Conduct market research regarding commercially available AI visible firearm detection software.

• Understand vendor capabilities and software implementation methodologies.

• Identify software compatible with MTA’s existing video surveillance infrastructure.

• Understand cybersecurity, privacy, and applicable Criminal Justice Information Services

Security Policy requirements.

• Identify software implementation requirements, support services, and industry best practices.

• Explore lifecycle costs and software licensing models.

2 | P a g e

3 SOFTWARE CAPABILITIES OF INTEREST

MTA is seeking information regarding commercially available AI software capable of detecting visible firearms through existing video surveillance systems. Respondents are encouraged to describe software that, as applicable, provides:

• Detection of visible firearms using AI

• Integration with existing IP camera infrastructure

• Compatibility with existing Video Management Systems

• Real-time alerting capabilities

• Optional human verification

• Mobile and desktop notifications

• Deployment across rail stations, subway stations, bus facilities, maintenance facilities, administrative buildings, parking facilities, and other critical infrastructure

• Software updates

• Technical support

• Operator training

4 CALENDAR OF EVENTS

The anticipated schedule of activities related to the Artificial Intelligence (AI) Firearms Detection Software RFI is as follows:

Activity Date

RFI Release August 13, 2026

Questions Due August 20, 2026 at 2:00pm EST

Responses Due September 3, 2026 at 2:00pm EST

All dates are subject to change at the discretion of MTA. MTA reserves the right to ask clarifying questions about submitted responses.

Responses to this RFI will be utilized strictly for the purposes of information gathering so that MTA can determine the best options available. Any official competitive procurement process will begin with the issuance of an Invitation for Bids (IFB) or a Request for Proposal (RFP). Information provided as a response to this RFI document may or may not be used by MTA for development of a future opportunity.

Submission of information pursuant to this RFI does not give any vendor an advantage or disadvantage in any future solicitation, should one result from this RFI.

3 | P a g e

5 RFI CONTACT & RESPONSE SUBMISSION

Respondents should email questions and responses to this RFI to the Procurement Officer, Akia Wheeler, at awheeler3@MDOT.Maryland.gov.

5.1 ISSUING OFFICER

The sole Point of Contact (POC) for this RFI shall be the “Issuing Officer”, Akia Wheeler with the MTA Office of Procurement located at 6 Saint Paul Street; Baltimore, MD 21202. All inquiries regarding this RFI shall be referred to the Issuing Officer via e-mail at Awheeler3@MDOT.Maryland.gov.

5.2 QUESTIONS REGARDING THE RFI

Respondents may submit written questions regarding this RFI to the Issuing Officer by the Questions Due date specified in Section 4.

The subject line of the email shall state:

[Respondent Name] – Questions – AI Visible Firearm Detection Software RFI

MTA’s responses to questions, along with any revisions to the RFI, will be issued through an addendum posted on eMaryland Marketplace Advantage (eMMA) at emma.maryland.gov.

Only written responses issued by MTA through an addendum shall constitute an official response to a question or modification of this RFI.

5.3 RFI RESPONSE INSTRUCTIONS

Respondents are requested to address the questions contained in Section 6. Respondents may also submit additional information they determine to be relevant to MTA’s market research.

Responses shall be submitted electronically to the Issuing Officer by the Responses Due date specified in Section 4. Each respondent shall submit one consolidated response document in searchable PDF format. The response shall address the questions in Section 6 and be organized using the same section headings and question numbers presented in this RFI.

Supplemental materials and supporting documentation may be submitted as separate attachments. All supplemental attachments should be clearly identified and referenced in the respondent’s main response.

The subject line of the email shall state:

[Respondent Name] – Response – AI Visible Firearm Detection Software RFI

The response should include:

mailto:awheeler3@MDOT.Maryland.gov https://emma.maryland.gov/

4 | P a g e

• Company name

• Business address

• Contact person’s name and title

• Telephone number

• Email address

• Website address, if applicable

Respondents may answer any or all questions applicable to their software and experience. If a question is not applicable, the respondent should identify it as “Not Applicable.” Marketing materials and supplemental literature may be submitted as separate attachments but should not replace direct responses to the questions in Section 6.

The response should be signed by an individual authorized to submit the information on behalf of the respondent.

5.4 PUBLIC INFORMATION ACT NOTICE

All responses to this RFI will be handled in accordance with the Public Information Act.

Respondents should give specific attention to the identification of those portions of their responses that they deem to be confidential, proprietary information or trade secrets and provide any justification for why such materials, upon request, should not be disclosed by the State under the Maryland Public Information Act.

MTA will not pay for the preparation of any response, nor for information submitted to MTA, nor for MTA’s use of such information. MTA may, at its sole discretion, use information provided in response to the RFI to develop the Program and/or the Project. However, MTA is not obligated to use any information received as part of this RFI process.

6 QUESTIONS / SUBMISSION REQUIREMENTS

The questions below address AI visible firearm detection software, including company experience, technical capabilities, integration, implementation, cybersecurity, support, licensing, and nonbinding budgetary pricing.

MTA requests that respondents address the following questions:

6.1 COMPANY EXPERIENCE

1. How many years has your company provided AI visible firearm detection software?

2. How many public safety, transit, government, or critical-infrastructure customers currently use your software?

3. Provide three references for comparable software deployments.

4. Describe your company’s experience working with transit agencies.

5 | P a g e

6.2 AI SOFTWARE CAPABILITIES

5. Describe how the AI software detects visible firearms through video surveillance systems.

6. What types of firearms can the software detect?

7. Can the software distinguish actual firearms from replicas or toys? Please explain.

8. How frequently are the AI models updated?

9. Does the software require retraining to detect new firearm types or models?

6.3 DETECTION PERFORMANCE

10. What are the documented detection, false-positive, and false-negative rates for the software?

11. Provide any available independent validation, testing results, or performance studies supporting these rates.

6.4 HUMAN VERIFICATION

12. Is human verification available? If so, describe the verification process, staffing, monitoring hours, average verification time, and continuity plan.

6.5 SOFTWARE INTEGRATION

13. Which IP cameras and Video Management Systems are supported by the software?

14. Can the software operate using existing cameras?

15. What are the minimum camera specifications required for the software?

16. Does the software support indoor and outdoor environments?

6.6 ALERTS AND NOTIFICATIONS

17. Describe the software’s available notification methods, including mobile, desktop, text message, email, Computer-Aided Dispatch, Application Programming Interface integration, and video-clip delivery.

6.7 CYBERSECURITY

18. Describe how the software supports compliance with applicable Criminal Justice Information Services Security Policy requirements.

19. Does your company maintain SOC 2, ISO, FedRAMP, or other relevant cybersecurity certifications or authorizations? If so, please identify them.

20. Describe the software’s encryption, multifactor authentication, disaster-recovery, and business-continuity capabilities.

21. Describe any cybersecurity incidents involving the software or company systems within the past five years and the corrective actions taken.

6 | P a g e

6.8 PRIVACY AND DATA

22. Who owns the data processed, generated, or stored by the software?

23. What information does the software retain, and for how long?

24. How does the software protect personally identifiable information?

6.9 SOFTWARE IMPLEMENTATION AND SUPPORT

25. Describe the anticipated software implementation schedule, onboarding process, configuration, user training, documentation, service-level agreements, maintenance, updates, and technical support.

6.10 LICENSING, BUDGETARY PRICING, AND PERFORMANCE

26. Describe the software licensing model, including how licenses are structured, managed, renewed, and scaled. Identify any software updates or upgrades included with the license.

27. Provide nonbinding budgetary pricing for the software and related services. Identify all assumptions and describe the licensing units, implementation services, recurring services, optional services, and other components included in the pricing.

28. What is the average time between detection of a visible firearm and delivery of a notification?

29. How does the software perform in crowded or low-light environments?

30. What differentiates your software from other commercially available visible firearm detection software?

31. What software limitations should MTA understand before implementation?

7 RFI CONDITIONS AND DISCLAIMER

7.1 NATURE OF THE RFI

This RFI is issued solely for information-gathering, market-research, and planning purposes. It does not constitute a solicitation, bid request, Request for Proposals, Invitation for Bids, offer, or commitment by MTA to procure any goods or services.

This RFI does not authorize any respondent to perform work at MTA’s expense. Any work performed or expense incurred by a respondent in connection with this RFI shall be at the respondent’s sole discretion and expense.

MTA will not pay or reimburse a respondent for:

• Preparing or submitting a response

• Providing information to MTA

• Participating in discussions

7 | P a g e

• Preparing or conducting a demonstration or presentation

• Any other costs associated with this RFI

Submission of a response constitutes acknowledgment that the respondent has reviewed and accepts these conditions.

7.2 USE OF SUBMITTED INFORMATION

MTA may, at its sole discretion, use information submitted in response to this RFI for market research, planning, or development of a potential future procurement. MTA is not obligated to use any information received.

Responding to this RFI will not provide a respondent with an advantage or disadvantage in connection with any potential future procurement.

MTA may request clarification or additional information from one or more respondents. Any such a request shall not constitute an evaluation, selection, prequalification, negotiation, or commitment by MTA.

7.3 NONBINDING BUDGETARY PRICING

Pricing submitted in response to this RFI will not be evaluated for contract award or establish pricing for any potential future solicitation. MTA makes no representation that a future solicitation, if issued, will contain the same requirements, quantities, terms, licensing structure, or other conditions described in this RFI.

7.4 DEMONSTRATIONS AND PRESENTATIONS

MTA may invite one or more respondents to provide a software demonstration, presentation, or clarification meeting. Participation shall be voluntary and at the respondent’s own expense.

Participation in a demonstration, presentation, or meeting shall not constitute an evaluation, selection, prequalification, negotiation, or commitment by MTA and will not provide a respondent with an advantage or disadvantage in connection with any potential future procurement.

7.5 PROCUREMENT DISCLAIMER

This RFI is issued solely for information-gathering and planning purposes and does not obligate MTA to issue a future solicitation.

Any future public solicitation will be advertised through the appropriate procurement channels, including eMaryland Marketplace Advantage (eMMA) at emma.maryland.gov. Respondents are responsible for monitoring eMMA for future procurement opportunities.