RFI - Enterprise Collaboration Tools .pdf

FEDERAL BUREAU OF INVESTIGATION

FINANCE AND FACILITIES DIVISION | PROCUREMENT SECTION

REQUEST FOR INFORMATION (RFI)

CJIS Enterprise Collaboration Tools

02/04/2026

Version 1.2 Page 2

DISCLAIMER:

THIS NOTICE IS FOR INFORMATIONAL PURPOSES ONLY. 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.

INTRODUCTION

The CJIS Division (CJISD) is conducting market research through this Request for Information

(RFI) to identify capabilities that will enable and empower our internal workforce by standardizing development and operations environments across CJIS projects. The goal is to implement an integrated suite of tools that supports the Scaled Agile Framework (SAFe) and enables our development and operations teams to work more effectively. This platform should encompass Agile planning and work management to support SAFe practices and streamline sprint planning, backlog management, and work tracking; source code repository management with version control; automated continuous integration and deployment pipelines; service desk capabilities for incident and problem management; technical documentation for development artifacts, operational runbooks, and internal documentation supporting ongoing activities such as Operations and Maintenance (O&M); and centralized user management with role-based access controls. By standardizing these tools and environments, CJISD aims to enhance internal team collaboration, reduce context-switching overhead, improve knowledge retention and sharing among development and operations staff, and increase overall workforce productivity and operational efficiency across all CJIS projects.

This RFI is not a solicitation, and the government will not pay for any costs associated with responding. Responses may contain proprietary information, which must be clearly marked.

There is no set-aside designation, and the government has not disclosed any potential incumbents or current contractors. The government has also not provided any estimated award values or budget ranges, nor have they specified quantities of goods or timelines for

Version 1.2 Page 3 services. The information gathered may be used to formulate acquisition strategies for competitive solicitations.

BACKGROUND

The CJISD, located in Clarksburg, WV, provides IT systems and services serving the criminal justice community.

Currently, we are following the Scaled Agile Framework (SAFe) using a suite of integrated tools that streamline our internal operations and workforce enablement. Our project and issue tracking, repository management, continuous integration and deployment, and internal documentation are all managed through these integrated tools. Centralized user management and role-based access controls ensure secure and flexible administration across our internal teams. This suite of tools has greatly improved collaboration and knowledge sharing among our internal workforce, reducing the need for retraining and administrative burdens, and enabling seamless movement of personnel between systems.

The CJIS Division is striving to unify the environment for both technically focused staff and business-focused staff to enhance internal workforce capabilities and efficiency. To support this workforce enablement initiative, the CJIS Division will use a Request for Information (RFI) to explore, visualize, and demonstrate concepts to the diverse community of employees, aiming to enhance tracking, documentation, collaboration, source control, and continuous development practices. The environment should support SAFe principles to enable efficient project and portfolio management, planning interval (PI) planning, backlog management, and road mapping for our internal teams. It should facilitate alignment of strategy and execution across multiple teams and projects, and provide tools for agile planning, sprint tracking, task management, user story mapping, kanban boards, and metrics visualization that support our workforce's daily activities. Tooling for software development, system administration, automated system testing, and security testing should be included in the final documentation, along with comprehensive O&M documentation and development documentation, to memorialize these concepts for later implementation and to ensure our internal workforce has the appropriate resources and capabilities to execute their responsibilities effectively.

CONTRACTOR QUALIFICATIONS

This RFI is dedicated for market research only and is open to all manufacturers. The Government may request demonstrations. The purpose is to request input from potential

Version 1.2 Page 4 manufacturers of integrated tool platforms that support SAFe implementation, code repository management, CI/CD, and collaboration within government hosted environments.

The Government needs to know which manufacturers can provide the necessary information for this contemplated requirement. Please identify yourselves and respond to this RFI.

The following information is requested:

1. Company name and business size.

2. Evidence to show that your company can provide the requested services and/or products required (i.e. technical ability, personnel, and experience). Information provided shall be succinct and related to the requested information in this RFI. All submissions shall be unclassified.

3. Address whether your company has a GSA Schedule and if they can provide these services on schedule. If applicable, provide the services schedule and SIN.

4. Include any authorized resellers, any GWAC they are available on and if they are small or large.

4. Any additional 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:

Version 1.2 Page 5

CONTEMPLATED REQUIREMENT

Below is a list of the requirements to support CJIS Division of around 5000 users in concept exploration and requirements development:

1. Identify product(s):

a. Hosted and Deployed: Shall be self-hosted within a government cloud service provider and capable of operating in internet-disconnected, air-gapped, isolated on-premises environments.

b. Administration: Centralized user management, project and issue tracking, has or integrates with repository management, continuous integration and deployment, and collaboration and documentation.

c. Access Control: Supports both role-based access control (RBAC) and attribute-based access control (ABAC), multi-factor authentication (MFA), identity federation, and other NIST-compliant authentication and authorization mechanisms for access control and identity verification to manage user permissions and roles across different projects and tools.

d. Integration: Seamlessly integrates unified user management with support for industry standards such as Entra-ID, project tracking, code collaboration, continuous integration, and documentation.

e. Service Desk: Provides a service desk for submitting and managing support tickets, facilitating efficient issue resolution and customer support.

f. Web Based: The suite is web-based for users and does not have a need to install anything.

g. Assets Management: The suite shall have integrations to manage assets from other services such as Active Directory.

h. Federal Authorization: Vendor shall provide information on whether the product has

FedRAMP authorization or existing federal Authority to Operate (ATO).

i. Market Presence: Vendor shall provide documentation of current user base and number of installations, particularly within federal government or similar secure environments.

2. Describe an environment that can support Scaled Agile Framework, including but not limited to:

a. Agile Planning and Tracking

b. Hierarchy item types such as stories, features, epics, portfolio epics, etc.

c. Custom workflows, fields, and inheritance rules.

d. Story point tracking, Capacity planning, Weighted Shortest Job First (WSJF) calculation

Version 1.2 Page 6

e. Different roles for various users in SAFe (such as Product Owner, Scrum Master, Release Train Engineer, Team Member, etc.) support, including the availability of preconfigured roles and the ability to create custom roles.

f. Project and Portfolio Management

g. Metrics and Dashboards

i. Able to feed metrics to other programs, such as PowerBI

h. Workflows and Automation

3. Document how the environment can be customized and configured to meet our needs, including the available out-of-the-box integrations that don't require coding or planned development.

4. Document how the product(s) are designed to be user-friendly for non-IT users while offering advanced features for IT professionals.

5. Document how the system supports multiple configurable helpdesks that handle customer interactions through various channels (phone calls, email, self-service portal), logging all customer interactions and related resolution work while tracking and enforcing Service Level

Agreements (SLAs) including response times, resolution times, escalation procedures, and compliance reporting across all helpdesk instances and request types.

6. Document how the environment can be seamlessly integrated with existing tools such as ticket management systems, git repositories, Continuous Integration and Continuous

Delivery/Deployment (CI/CD) pipelines, wikis, communication and email platforms, Customer

Relationship Management (CRM) systems, and privately hosted AI and LLM platforms.

7. The document should include how the product(s) can utilize authentication methods, such as SAML and/or OAUTH SSO.

8. The document shall outline how API access can be utilized to create, edit, view, and manage the respective product(s), as well as obtain metrics and other relevant data.

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.

Version 1.2 Page 7

WHAT SHOULD BE INCLUDED IN YOUR SUBMITTED RESPONSE:

1. All interested parties shall submit capability packages and (informal) market research pricing in response to this notice. The response shall not be more than 15 pages.

2. Succinct, thoughtful responses to the requirements/questions listed in this RFI.

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

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

WHAT SHOULD NOT BE INCLUDED IN YOUR RESPONSE:

1. Submitted proposals or offers.

2. Past performance information or general descriptions of corporate experience.

3. Requests to be considered for award or to be notified of a future solicitation.

4. Requests to be added to a mailing list or distribution list.

5. Any additional questions or comments not related to this RFI.

6. Responses via telephone will not be accepted.

RFI SUBMITTAL INSTRUCTIONS:

Submit RFI Information (via email) to the attention of:

Contracting Point of Contact: Dionna Brown

Version 1.2 Page 8

Email: dnbrown@fbi.gov

All RFI responses must be submitted electronically no later than 12pm ET on March 25, 2026.

Responses received after this deadline will not be accepted or considered.

Questions regarding this RFI must be submitted in writing via email to dnbrown@fbi.gov.

All questions must be received by March 18, 2026 at 12pm ET.

Questions received after the deadline may not be addressed.

A consolidated Q&A document containing responses to all timely submitted questions will be issued to all known recipients of this RFI. No verbal questions will be accepted, and no individual responses will be provided.