Collaborative Public Safety Solution RFI.pdf

FEDERAL BUREAU OF INVESTIGATION

FINANCE AND FACILITIES DIVISION | PROCUREMENT SECTION

REQUEST FOR INFORMATION (RFI) - COLLABORATIVE PUBLIC

SAFETY SOLUTION

According to FAR 15.201, requests for information (RFIs) may be used when the Government does not presently intend to award a contract but wants to obtain price, delivery, other market information, or capabilities for planning purposes. Responses to these notices are not offers and cannot be accepted by the

Government to form a binding contract.

REQUEST FOR INFORMATION (RFI) CJIS31126

Collaborative Public Safety Solution

March 11, 2026

Request for Information (RFI) Version 1.0 Page 2

Disclaimer

This notice is issued solely for informational and planning purposes. It is not a request for proposal or quotation and does not constitute a solicitation or a commitment by the Government.

Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. The Government is under no obligation to award a contract as a result of this announcement. No funds are available to reimburse respondents for any costs incurred in preparing or submitting a response. Any information provided is strictly voluntary.

Introduction

Responses to this RFI may be used to inform the Government’s final requirements and to identify vendors capable of meeting those needs. The information below reflects preliminary requirements for the Collaborative Public Safety Solution. Input received may assist the

Government in shaping the acquisition strategy and developing any future competitive solicitation.

Background

The Federal Bureau of Investigation (FBI) Criminal Justice Information Services (CJIS) Division supports law enforcement and public safety agencies nationwide by delivering advanced information‑sharing tools and services. The Collaborative Public Safety Solution aims to modernize and consolidate existing collaboration capabilities into a unified, secure, and user‑friendly platform that enhances communication, information exchange, and operational efficiency among federal, state, local, tribal, territorial (FSLTT), and international partners.

The envisioned solution will provide a seamless user experience through a single interface that integrates multiple capabilities, including flexible digital workspaces for self‑managed communities of interest, customizable data collection, secure file sharing, real‑time communication, incident and crisis management, personnel accountability, and Artificial

Intelligence (AI)‑enabled user assistance. Emphasis is placed on interoperability, scalability, security compliance (including CJIS and federal cybersecurity standards), and accessibility across a wide range of users and devices.

By strengthening collaboration and situational awareness, the solution is intended to help public safety and law enforcement personnel respond proactively to emerging threats, improve operational coordination, and enhance public safety outcomes nationwide. Access to the solution will be brokered through the Law Enforcement Enterprise Portal, with identity management and authentication provided through the Enterprise Identity Credential and Access Management

System.

This RFI is issued as part of the Government’s market research to gather industry input on capabilities, innovations, and potential challenges that may inform future acquisition strategies. It is not a solicitation and does not commit the Government to award a contract.

Request for Information (RFI) Version 1.0 Page 3

Key Objectives

The Collaborative Public Safety Solution aims to provide a seamless one-stop shopping experience. It features a User Interface/User Experience (UI/UX) that consolidates various services into a single platform, eliminating the need for multiple independent collaboration applications. While easy access is an integral aspect of the overall UX, it is not the primary focus of this RFI. The following are the key objectives:

Enhance Access to Services: Streamline secure user access to CJIS collaboration services, collaborative tools, and resources to enable and enhance efficient communication and information sharing.

Simplify Operations and Maintenance: Establish a user-friendly collaborative suite that minimizes operational complexities and reduces operational and maintenance efforts, thus enabling concentration on core mission activities.

Improve Integration: Ensure seamless integration of various technologies and systems to create a cohesive operational environment.

Promote Interoperability: Wherever necessary, prioritize the adoption of established standards and protocols, including industry-standard frameworks like National Information Exchange

Model (NIEM), to facilitate effective interoperability among agencies and services, thereby enhancing overall collaboration.

Unified UI/UX

The suite must deliver a cohesive, intuitive, and consistent UX across all modules and features. A unified UX guarantees that interactions, navigation, and visual elements—such as typography, colors, and icons—are uniform throughout the entire environment, rather than presenting a fragmented collection of applications. This consistency will enhance usability, making it easier for users to navigate the platform and access the tools and information they need efficiently. By prioritizing a seamless UX, the CJIS Division aims to improve overall satisfaction and effectiveness for all stakeholders involved.

Key Requirements:

• Unified Visual Identity: The suite must provide a cohesive visual identity, navigation structure, and interaction patterns across all services to ensure a seamless transition between capabilities.

• Dynamic Interface Adaption: The interface and information must adapt based on access controls that use either Attribute-Based Access Control (ABAC) or Role-Based Access

Control (RBAC). Some components should be controlled by RBAC roles, while others should adapt based on ABAC.

• Accessibility Compliance: The suite must fully comply with Section 508 accessibility standards to ensure inclusiveness for all users, allowing everyone to effectively engage with the platform.

• Cross-Platform Optimization: The UX must be fully functional and optimized across all platforms— desktop, tablet, and mobile—without compromising critical operational

Request for Information (RFI) Version 1.0 Page 4 capabilities. This ensures that users can access the necessary tools and information regardless of their device.

Collaboration Tools - Secure Workspaces and Dashboards

The collaboration space must encompass a comprehensive set of capabilities for authoring (and co-authoring), organizing, and communicating sensitive information. It is essential to include feature-rich visualization tools that can aggregate complex data and present it in intuitive, visual formats. These tools will enable users to easily interpret and analyze information, facilitating better decision-making and enhancing situational awareness. By providing a robust environment for managing sensitive data, the collaboration space will empower users to effectively share insights and collaborate on critical public safety initiatives.

Key Requirements:

• Custom Displays: The suite must enable users and administrators to create customizable displays and layouts that are saved for their specific profiles or workspaces, allowing for a personalized UX.

• Geospatial Integration: The suite must integrate with geospatial services, such as

ArcGIS, to display layered data on a consolidated map view, enhancing the visualization of spatial information.

• Real-Time Visualizations: Visualizations must update in near real-time as underlying data changes in the proposed system, eliminating the need for manual refresh and ensuring users have access to the most current information.

• Interactive Visual Elements: Users must be able to interact with click on visual elements such as charts, map pins, and heat maps to access the raw data or detailed records associated with those visuals, facilitating deeper analysis.

• Sharing Capabilities: Users must have the ability to share visualizations with other users and groups, promoting collaboration and information dissemination.

• Collaboration Tools: The suite must support wikis or similar functionality to enable real-time collaboration and knowledge-sharing among users.

• Version Control: Version control must be implemented for artifacts, such as files, enabling users to track changes and maintain the integrity of shared information.

• Feedback and Commenting Structure: Feedback and commenting functions must include an organized structure to facilitate thoughts and conversations, ensuring that discussions are coherent and easily navigable.

Data Collection and Business Process Tools

Data collection and business process tools must include automated, customizable data collection functionality that enables administrators, business owners, collaborative space owners, and even end users to create tailored forms for capturing data specific to users’ needs. This flexibility will allow users to design forms that align with their unique requirements, facilitating efficient data

Request for Information (RFI) Version 1.0 Page 5 entry, and ensuring that relevant information is collected accurately. By empowering users to build their own data collection tools, the suite will enhance operational efficiency and support a wide range of business processes across the organization.

File Sharing, Collaboration, and Transport Capabilities

The suite must provide appropriate tools that enable users to efficiently organize and share files within the platform, as well as with external users. This functionality must support various file types and ensure that users can easily locate and manage their documents. The system must support authorized access to collaboration tools that enable real-time editing, commenting, and feedback on shared files. Access controls should be flexible, allowing permissions to be granted based on attributes (ABAC), user roles (RBAC), or other relevant criteria to ensure only authorized users can use these features. Additionally, the system should allow authorized users the option to create a more open collaboration environment when appropriate, facilitating broader access to enhance teamwork and communication both internally and externally. The suite must ensure secure file transport mechanisms to protect sensitive information during sharing. This includes encryption and access controls to safeguard data integrity and confidentiality. The system must allow administrators to set user permissions and access controls for shared files, ensuring that only authorized individuals can view or edit sensitive information.

The suite must include version control features for shared files, allowing users to track changes, revert to previous versions, and maintain a clear history of document modifications.

Key requirements:

• Hierarchical Folder Structure: The suite must allow users to create a hierarchical folder structure to effectively organize files within their collaborative space, facilitating easy navigation and management of documents.

• Internal and External File Sharing: The suite must enable users to share files with both vetted and non-vetted users, ensuring flexibility in collaboration while maintaining security protocols. The system should also have the capability to interface with current

CJIS file sharing systems, either with Application Programming Interfaces (API), or other secure protocols.

• Drop and Share Functionality: The suite must include a drop-and-share feature that allows all authenticated users to easily upload and share files within the platform.

• Access Configuration Options: The suite must provide the ability to configure time limits for file access, batch user notifications, and access controls (read, write, and sharing). The suite must also support sending links or quick response codes for easy access to shared files.

• Cross-Domain System Interface: The solution must be capable of interfacing with existing agency "cross-domain" systems, which may involve the use of APIs, to facilitate file sharing across highly secured boundary enclaves, while adhering to established security protocols. This ensures that data can be exchanged securely between different systems while maintaining compliance with security standards.

• File Size Restrictions: The suite must support administrative staff in setting file size restrictions to meet performance and business needs, ensuring efficient use of resources.

Request for Information (RFI) Version 1.0 Page 6

• File Scanning for Security: The suite must scan all files for viruses, malware, and classification markings (referred to as “dirty words”) before they are submitted into the controlled space.

• Quarantine and Notification Process: Files identified as containing a virus or classified markings must be quarantined and subjected to a manual inspection process. This activity must include a notification process to the operational teams managing the system, potentially through a help desk, as well as a notification to the user that the flagged file(s) cannot be distributed further.

Feature-Rich Report Generation Tools

The suite must provide the capability to aggregate data and files from the full range of collaboration tools to automate the report authoring and delivery process. It should offer optional support for AI tools that can provide analysis and summarization of the collected data, allowing users to choose whether to use AI to generate insights and concise reports quickly. Delivery options must adhere to compatible industry document authoring and data presentation formats, including Microsoft Word, Microsoft Excel, Portable Document Format, Comma-Separated

Values, and ZIP files. The suite must support automated file sharing as attachments or through link-sharing to designated email addresses. These features will facilitate and enhance the efficiency of report generation and delivery, ensuring that users can easily access and share critical information in a variety of formats.

Robust and Modern Communication Tools

Audio/Video Communications

The suite must include a robust set of audio and video conferencing capabilities that support both user-to-user and group conferencing, accommodating up to 1,000 simultaneous sessions for operational and training purposes. All communications within the tools must be encrypted end-to-end to ensure the security and confidentiality of discussions and shared information. The conferencing tools must support voice, video, text chat, file-sharing, and file collaboration, providing a comprehensive communication platform for users. The overall UX should be enhanced through an intuitive and user-friendly interface that will facilitate easy access and navigation for all participants.

The suite must provide a robust chat feature that supports both user-to-user and group chat functionalities, allowing for flexible communication among users. Modern chat capabilities must be incorporated to include text-based communication and file sharing options to enhance user interaction and engagement. This chat feature must always be accessible to users across all components of the collaboration suite, ensuring that communication can occur seamlessly regardless of the specific tool or module being used.

Secure Email and Messaging

The suite should provide either a secure email system capable of hosting a .gov domain and-or the ability to interoperate with other email domains and secure messaging services.

Request for Information (RFI) Version 1.0 Page 7

If an email system is offered, users must be able to access an inbox via a web application. Email account management must be handled through a request system where FBI administrators approve user requests that include justification for needing the email address.

Additionally, the suite must support group email capabilities where an email alias is used to send messages to multiple email addresses. Users must have various options to manage these group emails.

The suite must have the capability to enable users to identify their preferred notification service and when required send messages, such as a short message service, outside the collaborative space. Subscription notifications, for example, are sent via the users preferred notification service.

Shared Calendars and Scheduling

The suite must provide group calendars that support both small and large teams, allowing users to create, manage, and view events collectively. Group calendars should include the ability for users to assign tasks to team members directly within the calendar interface. Notification capabilities must alert users to upcoming events, task deadlines, and changes to the calendar.

Notifications should be customized, allowing users to choose their preferred method of receiving alerts. Group calendars should also integrate seamlessly with other collaboration tools within the suite, enhancing communication and coordination among team members.

Incident and Crisis Management Tools

The suite must include a collection of capabilities to input, organize, track, and respond to both small and large-scale public safety events.

Key requirements:

• Data Entry: The suite must support customizable data entry forms that capture rich-text narratives along with associated attributes, including date/time, location, images, files, and additional customizable text and selection fields.

• Customizable Attributes: The suite must allow for customizable attributes for all data entries, enabling users to tailor the data fields to meet their specific needs.

• Geospatial Visualization: The suite must support geospatial visualization of data, incorporating geocoding and geospatial data analysis tools.

• Integration with Communication Tools: The suite must facilitate integration with communication tools within a collaboration suite, such as email and chat, ensuring seamless information sharing and collaboration among users.

• Integration with Records Management Systems (RMS) and Computer Aided

Dispatch (CAD) Systems: The suite must support integration with known RMS and

CAD systems, allowing for efficient data exchange and interoperability between systems.

Personnel Accountability Tools

The suite must provide a comprehensive collection of tools to manage personnel and shift management. These features must include tracking of employee information, such as roles and responsibilities, as well as a robust shift management capability allowing managers or employees to create, modify, and view shift assignments efficiently. The suite must also be capable of

Request for Information (RFI) Version 1.0 Page 8 capturing location data at sub-second intervals, ensuring accurate and real-time tracking of personnel movement. The establishment of a defined geofence must provide the ability to identify personnel, as well as the ability to contact personnel, facilitating quick communication and coordination during an operation.

Key requirements:

• Dashboard Functionality: The suite must support a dashboard that is accessible within all parts of the collaboration suite, offering real-time visualization of personnel locations and status indicators, such as on/off shift, enroute, arrived. This will enhance situational awareness for management and operational teams.

• Speed of Visualization: Location sharing and depiction features must support real-time networking to ensure that personnel locations are updated and displayed in real-time, allowing for immediate response, coordination, and decision making.

• Personnel Management: The suite must include comprehensive roster management capabilities that encompass shift management, enabling effective scheduling and tracking of personnel assignments.

• Compatibility: The suite must be compatible with the Android Tactical Awareness Kit, ensuring seamless integration and functionality for users operating within that environment.

Support Tools

Consolidated Search

The suite must offer a consolidated search capability that acts as a secure "broker" across the entire collaboration suite, ensuring that users can access information while maintaining data security and privacy. Users must be able to simultaneously search for various entities, including people, objects, locations, and events, across all authorized incidents, workspaces, and connected files. This will facilitate a holistic view of relevant information, effectively breaking down information silos, allowing users to retrieve interconnected data and insights that may span multiple systems or data repositories.

Key Requirements:

• Single Search Bar: The suite must provide a single search bar that allows users to query multiple data indices, including both internal suite data and connected external systems, streamlining the search process and enhancing user efficiency.

• Controlled Search Responses: The search engine must respect data stewardship and ensure that search results are dynamically filtered based on a user’s identity attributes, such as agency affiliation, sworn law enforcement officer status, and originating agency identifier.

Feature-Rich User Support Chatbot

The suite must include an AI-supported chatbot designed to assist users with their queries, providing immediate responses and support for a variety of topics related to the collaboration suite.

Key Requirements:

Request for Information (RFI) Version 1.0 Page 9

• Interactive Space Development: The chatbot must enable users to interactively build personalized collaboration spaces with ease, guiding them through the process and allowing for customization based on their specific needs.

• Self-Managed: The service must incorporate a custom, self-managed model featuring configurable internal knowledge bases to support its operations.

• Self-Help and Troubleshooting: The chatbot must provide comprehensive guidance to users for navigating their new collaboration spaces. It should also offer self-help resources and troubleshooting assistance to facilitate self-remediation, empowering users to resolve issues independently.

• Service Desk: If the user should continue to experience difficulties, the chatbot must facilitate an open chat with help desk support and/or give an option to open a service desk ticket. This ensures users can easily escalate issues when necessary.

• Knowledge Source Integration: The chatbot must be able to utilize CJIS Division knowledge bases and customer-provided information to ground its responses, ensuring answers are accurate, relevant, and consistent with authoritative sources.

Integration and Interoperability, Service Integration

The suite must facilitate seamless, bi-directional data exchange between the collaboration environment and external systems. The suite must specifically consider interoperability with external public safety systems, while utilizing standardized protocols and formats to ensure compatibility with a wide range of external systems.

Key Requirements:

• Managed Gateway: The suite must support a secure, managed gateway to govern all system-to-system interactions. This gateway will ensure that data exchanges are controlled, monitored, and secure, providing a reliable point of access for external systems.

• Data Standards Adherence: The suite must adhere to national data exchange standards, such as NIEM. This adherence will ensure data compatibility with FSLTT agencies and public safety partners, allowing for standardized information sharing regardless of the source system.

• Flexible Adapters: The suite must support a flexible adapter framework or integration architecture designed to rapidly configure connections with common systems, including

CAD, RMS, license plate readers, and internal CJIS Division data repositories, such as the National Crime Information Center and the National Data Exchange System.

• Data Ingest and Updates: The suite must support the ability to ingest data from external systems for display, while also enabling the capability to push updates (e.g., incident status changes and notes) back to the source system of record.

Dedicated Geospatial Services

The suite must be compatible with published Environmental Systems Research Institute ArcGIS standards and specifications, ensuring seamless integration with existing geospatial tools and services. The suite must provide robust geocoding services that are accessible to other components of the collaboration suite. Geospatial services must be available via APIs to support custom application implementations.

Request for Information (RFI) Version 1.0 Page 10

Business Analysis Tools

The suite must include robust business intelligence tools that track system performance metrics, offering insights into how the collaboration suite is functioning and identifying areas for improvement.

Key Requirements:

• User Adoption Tracking: The suite must support tracking of user adoption rates, feature utilization, and session activity across all connected services and workspaces. This feature will offer insights into how effectively users are engaging with the system.

• Real-Time Dashboards: The suite must support real-time dashboards that monitor system latency and uptime, ensuring operational readiness.

• Visualization Tools: The data must be accessible to external enterprise visualization tools, specifically Microsoft Power BI, through standard connectors, Open Database

Connectivity, Java Database Connectivity, and Representational State Transfer API.

• Automated Usage Reporting: The suite must support the automated generation of usage reports to satisfy internal audit requirements and CJIS Division compliance mandates.

• Help Desk Tools and Services: Using industry standards, the suite must support help desk tools and services, allowing users to report issues, request assistance, and track the status of their inquiry.

System Considerations

Performance

All services must have the capability of meeting 99.99% availability, ensuring users can access the system reliably without interruptions. Maintenance activities must incur minimal downtime for all components. Ideally, the system should allow for maintenance without taking the system out of service. The system must be hosted in a single government cloud-based platform and comprised of FedRAMP-approved components, ensuring compliance with federal security standards and regulations.

It is highly desired that system interactions and responses be as close to real-time as possible.

Scalability

The suite must consider scalability, capable of accommodating a large and diverse amount of information shared with users nationwide. The suite must be able to grow in response to users’ ever-changing demands for data, number of users, functionality, performance, and funding availability. This includes the ability to expand resources and capabilities as needed to meet evolving requirements.

User Profiles

User profiles must serve as a digital collection of user-related information and attributes obtained from identity federation and services. This information will be essential for authentication and enabling a streamlined, personalized experience. User profiles must facilitate RBAC and ABAC experience, ensuring users receive tailored content and access based on their specific roles and/or attributes. Profile data must be accessible to all other services within the system and minimally include full name, agency affiliation, job title, roles, contact information, and indicators. The

Request for Information (RFI) Version 1.0 Page 11 profile must also support self-reportable fields that allow users to input information related to their interests, activities, skills, and other relevant attributes.

Granular Access Control

The collaboration space must support dynamic access controls that adapt based on user profiles and session context. The system must leverage user attributes and session information to implement more granular access policies. In areas of the suite that requires more open access, the owners of a specific space must have the ability to configure access settings to allow for more general access.

Search and Connect Functionality

The collaboration space must allow users to search for other users based on specific criteria, such as name, agency, job title, roles, or skills. Users should also be able to send connection requests to other users, enhancing engagement and fostering collaboration opportunities, further developing a professional network.

Language Support

The suite must provide support for non-English-speaking users and include translation services.

Standards and Policies

All services must adhere to established standards such as:

• National Institute of Standards and Technology (NIST) Special Publication (SP)

800-53-IA-8(4) "Authenticator Management."

• Controls outlined in NIST SP 800-63-3B "Authentication and Lifecycle Management."

• CJIS Security Policy.

Logging Requirements

All components must meet the logging requirements detailed within Executive Order 14028, Improving the Nation’s Cybersecurity, and OMB M21-31. The FBI will require documentation detailing how these components meet (will meet) these standards upon implementation.

Additionally, all component logs must be capable of log aggregation to FBI managed logging services.

Additional Considerations

The CJIS Division will use internal resources to address the governance of identity and federation management.

Use of AI

Any AI usage will be approved by the FBI AI Ethics Council prior to implementation. Vendors must be available to work closely with the CJIS Division to capture implementation details in the format provided by the CJIS Division Enterprise Architecture. The process of AI implementation involves working with the CJIS Division legal counsel to ensure compliance with FBI

Information System User Privacy standards and policies.

Request for Information (RFI) Version 1.0 Page 12

Cost Information The CJIS Division is seeking information on solutions that meet or exceed the requirements listed above. In any responses provided, please provide cost information, in the form of a Rough

Order of Magnitude (ROM), for the proposed solutions. For the cost information, please provide cost for a five year life cycle, if applicable. Please also provide capability statements indicating how the solution meets or exceeds all requirements listed in this document.

To support meaningful market research and facilitate comparison across responses, please also include the following:

• Cost Assumptions: Identify all assumptions used in developing the ROM.

• Pricing Model: Describe the pricing structure (e.g., subscription, licensing, usage-based, tiered, or other).

• Optional Components: Identify any optional modules, features, or services and provide separate ROM estimates where applicable.

• Key Cost Drivers: Describe the primary factors that influence cost for your solution.

• Scalability Considerations: Provide information on how pricing scales with user volume, data usage, or other relevant variables.

• Deployment Model: Indicate whether the ROM reflects cloud-hosted, on-premises, or hybrid deployment models.

Response Limits The CJIS Division requests all responses to be no more than 10 pages in length, including the

Cover Page and ROM. All pages must be one-sided. Font must be no smaller than 11-point.

Margins must be 1 inch on all sides. A page must fit on an 8 ½" by 11” sheet.

CONTRACTOR QUALIFICATIONS

This RFI is open to small and large business concerns for market research only to request input from potential providers of systems, products, and services that could support or enable the

Collaborative Public Safety Solution and meet the requirements outlined in this notice.

The Government would like to know which firms can provide the solution for this contemplated requirement by identifying themselves and responding to this RFI. The Government requests the following information:

1. Company name and business size.

2. Provide evidence to show that your company can provide the requested services and/or products required (i.e. technical ability, personnel, and experience). Information provided

Request for Information (RFI) Version 1.0 Page 13 should be succinct and related to the information requested in this RFI. All submissions shall be unclassified.

3. Address whether your company has a GSA Schedule and if they are capable of providing these services on schedule. If able to provide the services on schedule, provide the schedule and SIN.

4. Suggestion of any Best-in-Class vehicles and/or recommended GWACs.

5. Any other assumptions, comments, concerns, and/or questions relating to the contemplated services.

Required Information:

Contractor Legal/DBA Name:

Address:

Point of Contact:

Telephone:

Email Address:

DUNS Number:

Cage Code:

Facility Clearance (if applicable):

Applicable NAICS Codes:

Standard Business Size:

GSA Schedule:

NASA SEWP Contract:

Additional Contract Vehicles:

WHAT SHOULD BE INCLUDED IN YOUR RESPONSE

1. All interested parties shall submit capability packages in response to this notice.

2. Do submit succinct, thoughtful responses to the requirements/questions listed in this RFI.

3. Do submit comments that address the FBI's requirements, assumptions, conditions, or contemplated approaches to this future acquisition.

4. Do submit information and suggestions that may encourage new, different, or innovative approaches that would result in products, solutions, and direct savings to the FBI.

Request for Information (RFI) Version 1.0 Page 14

5. Rough Order of Magnitude (ROM): Include a Rough Order of Magnitude (ROM) cost estimate for the proposed solution, including a five-year life-cycle estimate if applicable.

ROM submissions should also include:

• Cost assumptions

• Pricing model (e.g., subscription, licensing, usage-based)

• Optional components or modules with separate ROMs

• Key cost drivers

• Scalability considerations (e.g., user volume, data usage)

• Deployment model (cloud, on-premises, hybrid)

WHAT SHOULD NOT BE INCLUDED IN YOUR RESPONSE

1. Do not submit proposals or offers.

2. Do not submit past performance information or general descriptions of corporate experience.

3. Do not submit requests to be considered for award or to be notified of a future solicitation.

4. Do not submit requests to be added to a mailing list or distribution list.

5. Do not submit questions or comments not related to this RFI.

6. Do not respond via telephone.

RFI SUBMITTAL INSTRUCTIONS:

Respondents should carefully review all sections of this RFI before preparing their submissions.

All responses must follow the formatting and page-limit requirements outlined in the Response

Limits section. Responses should be complete, well-organized, and clearly address all information requested. All required content, including the ROM, must be consolidated within the

10‑page limit. No additional attachments will be accepted.

Responses must include all items listed in the What Should Be Included in Your Response section, including capability information, comments, recommendations, and a Rough Order of

Magnitude (ROM) cost estimate.

All responses must be submitted electronically in PDF format as a single consolidated file. Pages should be numbered consecutively. Graphics, tables, and diagrams are permitted as long as they comply with the formatting requirements. Marketing brochures or generic corporate materials should not be included unless directly relevant to the capabilities being described.

Request for Information (RFI) Version 1.0 Page 15

Respondents are encouraged to clearly identify any proprietary or business-sensitive information.

The Government will handle such information in accordance with applicable regulations.

All responses and any communications regarding this RFI must be submitted only to the

Contracting Officer listed below. Submissions are due no later than COB March 31, 2026.

Contracting Point of Contact: Nicholas Lawrence

Email: nlawrence@fbi.gov

Address: 1000 Custer Hollow Dr., Clarksburg, WV 26306

DISCLAIMER and RESPONSES

THERE IS NO COMMITMENT BY THE GOVERNMENT TO ISSUE A

SOLICITATION AS A RESULT OF THIS RFI. THIS IS BEING ISSUED SOLEY FOR

INFORMATIONAL AND PLANNING PURPOSES AND DOES NOT CONSTITUTE A

SOLICTIATION. IN ACCORDANCE WITH FAR 15.201(e), RESPONSES TO THIS

NOTICE ARE NOT OFFERS AND CANNOT BE ACCEPTED BY THE GOVERNMENT

TO FORM A BINDING CONTRACT. THIS IS NOT A REQUEST FOR PROPOSAL OR

QUOTE. IT DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE

CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY

FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION

TO AWARD A CONTRACT AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS

ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS

ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS

TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY.