TMF Initiative 2 - MMI RFI Document 5.29.docx

U.S. DEPARTMENT OF JUSTICE

ANTITRUST DIVISION

Request for Information ATR IT MODERNIZATION: ENTERPRISE LEGAL EVIDENCE AND MATTER MANAGEMENT SYSTEM and DOCUMENT MANAGEMENT SYSTEM (DMS)

TECHNOLOGY DIRECTORATE

WASHINGTON, DC

MAY 2025

VERSION 1.0

RFI DETAILS:

Elliott Jones

Jacob Henson

Chief, Acquisition Management Section

Team Lead, Acquisition Management Section

Elliott.Jones@usdoj.gov

Jacob.Henson2@usdoj.gov Acquisitions

A. Issuing Agency This is a Request for Information (RFI) being issued by the Department of the Justice (DOJ), Antitrust Division (ATR) on behalf its Technology Directorate (TD).

B. Division Background The primary mission of the Antitrust Division (ATR), U.S. Department of Justice (DOJ), is to promote competition in the U.S. economy through enforcement of, improvements to, and education about antitrust laws and principles. Its goal is an environment in which U.S. consumers receive goods and services of the highest quality at the lowest price, and in which businesses compete fairly on the merits. By protecting competition across industries and geographic borders, the Division’s work serves as a catalyst for economic efficiency and growth with benefits accruing to both American consumers and American businesses. The Executive Office provides administrative and management support to the Division and includes three Directorates and the Litigation Support Section: The Technology Directorate, the Management Directorate, and the Human Capital Directorate. The Technology Directorate administers the Division’s technology program, including automated litigation support, management information systems, and office automation systems to support the Division's attorneys, economists, and managers. The Litigation Support Section manages the technology and data workflow for the investigative and litigative matters of the Division.

C. RFI Purpose The Government is seeking to resurvey the marketplace to obtain market research, including industry comments, recommendations, and questions regarding the resources needed to implement a Legal Matter Management and Document Management system. ATR will review vendor solution capabilities and the pricing approach provided by each respondent.

Response to this RFI is strictly voluntary and will not affect any firm’s ability to submit an offer if, or when, a solicitation is released. This RFI is issued solely for information and planning purposes and does not constitute a solicitation or obligation on the part of the Government. Neither unsolicited proposals nor any other kind of offers will be considered in response to this RFI. No entitlement to payment by the Government of direct or indirect costs or charges will arise as a result of the submission of information in response to this RFI.

The Government shall not be liable for or suffer any consequential damages for any improperly identified proprietary information. Proprietary information will be safeguarded in accordance with the applicable Government regulations. If you submit proprietary information, you are responsible for adequately and clearly marking “PROPRIETARY” on every sheet containing such information and segregate the proprietary information to the maximum extent practical from other portions of your response (e.g. use an attachment or exhibit). Responses to the RFI will not be returned. An electronic acknowledgement of the Vendor’s RFI response submission will be provided. If you do not receive an acknowledgement within one workday, please notify the acquisition points of contact listed in this RFI to ensure successful delivery.

D. Problem Statement The Antitrust Division (Division or ATR), within the U.S. Department of Justice (DOJ), works in the public interest to promote a competitive and productive American economy. The highest priorities of the Division are preventing anti-competitive mergers and acquisitions, curbing abuse of monopoly power, and prosecuting criminal bid-rigging and price-fixing cases. Mergers and civil enforcement cases affect the structure and performance of entire industries. The ability of the division to meet these priorities relies heavily on the operational and technological support of the ATR Litigation Support Services (LSS) Section.

Since late 2020, LSS has been crucial in working with members of legal staff to understand and identify functional gaps in technology that exist with current legacy evidence and matter management tracking systems. Through extensive research by the ATR LSS team coupled with the ATR Technology Directorate (TD), four key deficiencies were identified:

· Inefficient use of siloed repositories: ATR users rely on legacy siloed systems that do not share information, reduce productivity, and cause redundant processes which waste between 30-50% of a user’s time to correctly log, track and report on data housed in those systems;

· Lack of innovative collaboration: Information is difficult to find in these siloed systems, preventing the legal staff from gaining valuable insights from prior investigations and managing discoverable material;

· Lack of business process automation: There is a lack of standardization and workflow processes around the intake of work. Current work tracking, tasking, assignment and approval are currently done through email with no way to monitor, administer, report, and aggregate approval processes; and

· Unexposed metrics and measurement: The current siloed systems prevent ATR from having a single resource to find information relevant to a matter, including key information and deadlines, evidence, work product, and reporting insights.

After documenting ATR’s problem statement and objectives and through a series of research and evaluation activities, LSS has identified a series of business, functional, non-functional, and supplemental requirements. Research by ATR has concluded that the implementation of a cloud-based Legal Evidence and Matter Management System (LEMMS) to include legal and evidence management capabilities with business process automation and scalable document management would satisfy the priorities and create efficiencies within the Division. To identify a successful solution, LSS leads this effort within the Executive Office (EXO) of ATR at the DOJ. TD works in close collaboration with LSS to provide comprehensive, enterprise-wide information technology services for all ATR Division employees.

E. Objectives

1) ATR is seeking information for a cloud-based legal matter management and evidence solution. To efficiently and effectively interface with other applications and data within the DOJ and/or specifically ATR, the solution is expected to include an Application Programming Interface (API) Integration. Additionally, the ideal solution will include specifically pre-built service capabilities for legal and evidence management that support FedRAMP-High or Moderate workloads and provides native Document Generation (i.e. templatizing capabilities). The solution must support the implementation and functional requirements of ATR’s matter management application as defined in the attached appendix for Functional/Implementation Requirements.

2) The information provided must also include a solution for the storage of up to 1 Petabyte of matter-related data that can be accessed as part of the matter management system, or outside of the matter management system for unlicensed users (See requirements in Appendix A).

3) Vendors should include information relevant to advanced artificial intelligence capabilities that will enhance its legal and evidence management component, to include the extra costs (if any) associated with the capabilities.

4) Vendors should include information on how its solution pricing is structured, including services/limitations of licenses of the solution to provide support for a minimum of 500 users and a maximum of 750 users. Access to information on public websites is acceptable in lieu of a written statement as to limitations on licensing.

F. Vendor Responses Each vendor shall submit responses that include:

1) Response to Functional/Implementation requirements provided in Appendix A. Appendix A provides definitions for each item and is seeking information as to whether the proposed solution(s) meet the requirements out-of-the-box, whether they require some configuration to meet requirements, or whether they require a greater amount of configuration (see detailed explanation of categories in Row 1 of Appendix A). Respondent must select either Yes (it meets), No (it does not meet), or N/A (the requirement does not apply to the Respondent’s solution(s) within the three defined categories.

2) 1-2 pages of Government High level Pricing of Firm Fixed Price software/licenses for requirements described in Appendix A and for a Rough-Order-of-Magnitude Time and Materials pricing for professional services to implement a minimally viable product (MVP) based on requirements in Appendix A for a minimum of 500 and a maximum of 750 users.

3) 1-2 pages of explanation of how the functional requirements would be provided to include estimate of timeline for implementation of an MVP and explanation of what would be included as part of the MVP.

4) 1-2 pages of explanation of available advanced artificial intelligence features that would enhance legal workflows.

5) Experience/Case Studies. Please include at least three case studies of any direct experience of your organization working with a government agency (of similar size to ATR – approximately 750 users and with similar requirements as in Appendix A) to provide software/licenses for and implement a legal matter, evidence and document management solution. Also identify any experience supporting other DOJ-specific components with similar requirements to ATR. Case Studies should not be longer than 1 page per Case Study.

6) Whether Respondent is an approved bidding resource on GSA or SEWP, and under what classification group.

7) Identification of other competitive bidding proposals respondent has submitted with the government on similar contracting vehicles or specific software development projects.

G. Submission Instructions:

Interested parties who consider themselves qualified to perform the above-listed services are invited to submit their response to this RFI by 11:59 PM EST by Fri, June 20th, 2025. All responses under this notice must be emailed to Elliott Jones at Elliott.Jones@usdoj.gov and Jacob Henson at Jacob.Henson2@usdoj.gov.

If you have any questions concerning this RFI, please contact Elliott Jones at Elliott.Jones@usdoj.gov..

Appendix – A

(Please open this RFI word document in desktop and double click on above icon to open the Appendix A.xlsx file) image1.png image2.emf

Appendix A.xlsx Requirement Analysis

Out-of-the-Box: Describes a solution that is a low-code, out-of-the-box, pre-built offering that can be used as is, and requires minimal configuration changes to meet the requirement. Solution also can meet the performance, reliability and adaptability, security and compliance, maintainability and supportability, interoperability and integration, infrastructure, enhanced usability, business continuity and disaster recovery, compliance and ethics, vendor management and third party integrations, knowledge management and continuous improvement requirements as stated.

Moderate Configuration: Describes a solution that does not meet the out-of-the-box requirement, but with moderate special configuration and/or integration with third party applications, can meet the requirement. Solution has the performance, reliability and adaptability, security and compliance, maintainability and supportability, interoperability and integration, infrastructure, enhanced usability, business continuity and disaster recovery, compliance and ethics, vendor management and third party integrations, knowledge management and continuous improvement requirements that meets at least 80% of the requirement.

Significant Configuration: Describes a solution that does not meet the out-of-the-box requirement and can only meet the requirement with significant custom configuration. Solution does not have the performance, reliability and adaptability, security and compliance, maintainability and supportability, interoperability and integration, infrastructure, enhanced usability, business continuity and disaster recovery, compliance and ethics, vendor management and third party integrations, knowledge management and continuous improvement requirements and cannot meet at least 80% of the requirement.

Vendor Name

Req No. Req Type Requirement Name Out-Of-The-Box Moderate Configuration Significant Configuration

4.1.1(a) Business Unified Platform No No No

4.1.1(b) Business Unified Platform No No No

4.1.2(a) Business Advanced Security No No No

4.1.2(b) Business Advanced Security No No No

4.1.2(c) Business Advanced Security No No No

4.1.2(d) Business Advanced Security No No No

4.1.2(e) Business Advanced Security No No No

4.1.3(a) Business Comprehensive Matter Management No No No

4.1.3(b) Business Comprehensive Matter Management No No No

4.1.3(c) Business Comprehensive Matter Management No No No

4.1.3(d) Business Comprehensive Matter Management No No No

4.1.4(a) Business Knowledge Sharing and AI-Powered Insights No No No

4.1.4(b) Business Knowledge Sharing and AI-Powered Insights No No No

4.1.4(c) Business Knowledge Sharing and AI-Powered Insights No No No

4.1.4(d) Business Knowledge Sharing and AI-Powered Insights No No No

4.1.4(e) Business Knowledge Sharing and AI-Powered Insights No No No

4.1.4(f) Business Knowledge Sharing and AI-Powered Insights No No No

4.1.5(a) Business Scalability and Adaptability No No No

4.1.5(b) Business Scalability and Adaptability No No No

4.1.5(c) Business Scalability and Adaptability No No No

4.1.6(a) Business Evidence Lifecycle Tracking No No No

4.1.6(b) Business Evidence Lifecycle Tracking No No No

4.1.6(c) Business Evidence Lifecycle Tracking No No No

4.1.6(d) Business Evidence Lifecycle Tracking No No No

4.1.6(e) Business Evidence Lifecycle Tracking No No No

4.1.6(f) Business Evidence Lifecycle Tracking No No No

4.1.7(a) Business Intelligent Workload Distribution No No No

4.1.7(b) Business Intelligent Workload Distribution No No No

4.1.7(c) Business Intelligent Workload Distribution No No No

4.1.7(d) Business Intelligent Workload Distribution No No No

4.1.7(e) Business Intelligent Workload Distribution No No No

4.1.8(a) Business Process Automation and Smart Notifications No No No

4.1.8(b) Business Process Automation and Smart Notifications No No No

4.1.8(c) Business Process Automation and Smart Notifications No No No

4.1.8(d) Business Process Automation and Smart Notifications No No No

4.1.9(a) Business Compliance and Export Capabilities No No No

4.1.9(b) Business Compliance and Export Capabilities No No No

4.1.9(c) Business Compliance and Export Capabilities No No No

4.1.9(d) Business Compliance and Export Capabilities No No No

4.1.10(a) Business Standardization and Efficiency No No No

4.1.10(b) Business Standardization and Efficiency No No No

4.1.10(c) Business Standardization and Efficiency No No No

4.1.11(a) Business Extensibility No No No

4.1.11(b) Business Extensibility No No No

4.1.11(c) Business Extensibility No No No

4.1.11(d) Business Extensibility No No No

4.1.12(a) Business Cross-Device Availability No No No

4.1.12(b) Business Cross-Device Availability No No No

4.1.12(c) Business Cross-Device Availability No No No

4.1.12(d) Business Cross-Device Availability No No No

4.1.12(e) Business Cross-Device Availability No No No

4.2.1(a) Functional Unified Platform No No No

4.2.1(b) Functional Unified Platform No No No

4.2.1(c) Functional Unified Platform No No No

4.2.1(d) Functional Unified Platform No No No

4.2.1(e) Functional Unified Platform No No No

4.2.2(a) Functional Advanced Security No No No

4.2.2(b) Functional Advanced Security No No No

4.2.2(c) Functional Advanced Security No No No

4.2.2(d) Functional Advanced Security No No No

4.2.2(e) Functional Advanced Security No No No

4.2.2(f) Functional Advanced Security No No No

4.2.2(g) Functional Advanced Security No No No

4.2.2(h) Functional Advanced Security No No No

4.2.3(a) Functional Comprehensive Matter Management No No No

4.2.3(b) Functional Comprehensive Matter Management No No No

4.2.3(c) Functional Comprehensive Matter Management No No No

4.2.3(d) Functional Comprehensive Matter Management No No No

4.2.3(e) Functional Comprehensive Matter Management No No No

4.2.4(a) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(b) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(c) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(d) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(e) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(f) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(g) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(h) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(i) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.4(j) Functional Knowledge Sharing and AI-Powered Insights No No No

4.2.5(a) Functional Scalability and Adaptability No No No

4.2.5(b) Functional Scalability and Adaptability No No No

4.2.5(c) Functional Scalability and Adaptability No No No

4.2.5(d) Functional Scalability and Adaptability No No No

4.2.6(a) Functional Evidence Lifecycle Management No No No

4.2.6(b) Functional Evidence Lifecycle Management No No No

4.2.6(c) Functional Evidence Lifecycle Management No No No

4.2.6(d) Functional Evidence Lifecycle Management No No No

4.2.6(e) Functional Evidence Lifecycle Management No No No

4.2.7(a) Functional Intelligent Workload Distribution No No No

4.2.7(b) Functional Intelligent Workload Distribution No No No

4.2.7(c) Functional Intelligent Workload Distribution No No No

4.2.7(d) Functional Intelligent Workload Distribution No No No

4.2.7(e) Functional Intelligent Workload Distribution No No No

4.2.8(a) Functional Process Automation and Smart Notifications No No No

4.2.8(b) Functional Process Automation and Smart Notifications No No No

4.2.8(c) Functional Process Automation and Smart Notifications No No No

4.2.8(d) Functional Process Automation and Smart Notifications No No No

4.2.8(e) Functional Process Automation and Smart Notifications No No No

4.2.9(a) Functional Compliance and Export Capabilities No No No

4.2.9(b) Functional Compliance and Export Capabilities No No No

4.2.9(c) Functional Compliance and Export Capabilities No No No

4.2.9(d) Functional Compliance and Export Capabilities No No No

4.2.9(e) Functional Compliance and Export Capabilities No No No

4.2.10(a) Functional Standardization and Efficiency No No No

4.2.10(b) Functional Standardization and Efficiency No No No

4.2.10(c) Functional Standardization and Efficiency No No No

4.2.10(d) Functional Standardization and Efficiency No No No

4.2.11(a) Functional Extensibility No No No

4.2.11(b) Functional Extensibility No No No

4.2.11(c) Functional Extensibility No No No

4.2.11(d) Functional Extensibility No No No

4.2.12(a) Functional Cross-Device Availability No No No

4.2.12(b) Functional Cross-Device Availability No No No

4.2.12(c) Functional Cross-Device Availability No No No

4.2.12(d) Functional Cross-Device Availability No No No

4.2.12(e) Functional Cross-Device Availability No No No

4.2.12(f) Functional Cross-Device Availability No No No

4.3.1(a) Non-Functional Response Times No No No

4.3.1(b) Non-Functional Response Times No No No

4.3.1(c) Non-Functional Response Times No No No

4.3.1(d) Non-Functional Response Times No No No

4.3.2(a) Non-Functional Scalability No No No

4.3.2(b) Non-Functional Scalability No No No

4.3.2(c) Non-Functional Scalability No No No

4.3.3(a) Non-Functional Capacity No No No

4.3.3(b) Non-Functional Capacity No No No

4.3.4(a) Non-Functional Uptime No No No

4.3.4(b) Non-Functional Uptime No No No

4.3.5(a) Non-Functional Fault Tolerance No No No

4.3.5(b) Non-Functional Fault Tolerance No No No

4.3.6(a) Non-Functional Data Integrity No No No

4.3.6(b) Non-Functional Data Integrity No No No

4.3.6(c) Non-Functional Data Integrity No No No

4.3.7(a) Non-Functional Data Protection No No No

4.3.7(b) Non-Functional Data Protection No No No

4.3.7(c) Non-Functional Data Protection No No No

4.3.7(d) Non-Functional Data Protection No No No

4.3.7(e) Non-Functional Data Protection No No No

4.3.7(f) Non-Functional Data Protection No No No

4.3.8(a) Non-Functional Access Control No No No

4.3.8(b) Non-Functional Access Control No No No

4.3.8(c) Non-Functional Access Control No No No

4.3.8(d) Non-Functional Access Control No No No

4.3.8(e) Non-Functional Access Control No No No

4.3.8(f) Non-Functional Access Control No No No

4.3.8(g) Non-Functional Access Control No No No

4.3.8(h) Non-Functional Access Control No No No

4.3.9(a) Non-Functional User Interface No No No

4.3.9(b) Non-Functional User Interface No No No

4.3.10(a) Non-Functional Localization No No No

4.3.10(b) Non-Functional Localization No No No

4.3.11(a) Non-Functional Modularity No No No

4.3.11(b) Non-Functional Modularity No No No

4.3.12(a) Non-Functional Configurability No No No

4.3.12(b) Non-Functional Configurability No No No

4.3.13(a) Non-Functional Versioning No No No

4.3.13(b) Non-Functional Versioning No No No

4.3.13(c) Non-Functional Versioning No No No

4.3.14(a) Non-Functional Logging and Monitoring No No No

4.3.14(b) Non-Functional Logging and Monitoring No No No

4.3.14(c) Non-Functional Logging and Monitoring No No No

4.3.14(d) Non-Functional Logging and Monitoring No No No

4.3.14(e) Non-Functional Logging and Monitoring No No No

4.3.14(f) Non-Functional Logging and Monitoring No No No

4.3.14(g) Non-Functional Logging and Monitoring No No No

4.3.15(a) Non-Functional API and Interfaces No No No

4.3.15(b) Non-Functional API and Interfaces No No No

4.3.16(a) Non-Functional Data Exchange No No No

4.3.16(b) Non-Functional Data Exchange No No No

4.3.16(c) Non-Functional Data Exchange No No No

4.3.17(a) Non-Functional Backup and Recovery No No No

4.3.17(b) Non-Functional Backup and Recovery No No No

4.3.17(c) Non-Functional Backup and Recovery No No No

4.3.18(a) Non-Functional Business Continuity No No No

4.3.18(b) Non-Functional Business Continuity No No No

4.3.18(c) Non-Functional Business Continuity No No No

4.3.19(a) Non-Functional Resource Utilization No No No

4.3.19(b) Non-Functional Resource Utilization No No No

4.3.19(c) Non-Functional Resource Utilization No No No

4.3.20(a) Non-Functional Efficiency No No No

4.3.20(b) Non-Functional Efficiency No No No

4.3.20(c) Non-Functional Efficiency No No No

4.3.21(a) Non-Functional Platform Independence No No No

4.3.21(b) Non-Functional Platform Independence No No No

4.3.22(a) Non-Functional Mobile Support No No No

4.3.22(b) Non-Functional Mobile Support No No No

4.4.1(a) Supplemental Cloud Infrastructure No No No

4.4.1(b) Supplemental Cloud Infrastructure No No No

4.4.1(c) Supplemental Cloud Infrastructure No No No

4.4.2(a) Supplemental Network Requirements No No No

4.4.2(b) Supplemental Network Requirements No No No

4.4.2(c) Supplemental Network Requirements No No No

4.4.2(d) Supplemental Network Requirements No No No

4.4.3(a) Supplemental Storage Infrastructure No No No

4.4.3(b) Supplemental Storage Infrastructure No No No

4.4.3(c) Supplemental Storage Infrastructure No No No

4.4.3(d) Supplemental Storage Infrastructure No No No

4.4.4(a) Supplemental Usage Onboarding and Training No No No

4.4.4(b) Supplemental Usage Onboarding and Training No No No

4.4.4(c) Supplemental Usage Onboarding and Training No No No

4.4.5(a) Supplemental Customization and Personalization No No No

4.4.5(b) Supplemental Customization and Personalization No No No

4.4.5(c) Supplemental Customization and Personalization No No No

4.4.6(a) Supplemental Collaboration and Communication No No No

4.4.6(b) Supplemental Collaboration and Communication No No No

4.4.6(c) Supplemental Collaboration and Communication No No No

4.4.7(a) Supplemental System Compatibility No No No

4.4.7(b) Supplemental System Compatibility No No No

4.4.8(a) Supplemental Operations and Maintenance No No No

4.4.8(b) Supplemental Operations and Maintenance No No No

4.4.8(c) Supplemental Operations and Maintenance No No No

4.4.8(d) Supplemental Operations and Maintenance No No No

4.4.8(e) Supplemental Operations and Maintenance No No No

4.4.8(f) Supplemental Operations and Maintenance No No No

4.4.8(g) Supplemental Operations and Maintenance No No No

4.4.8(h) Supplemental Operations and Maintenance No No No

4.4.8(i) Supplemental Operations and Maintenance No No No

4.4.9(a) Supplemental Data Centers and Redundancy No No No

4.4.9(b) Supplemental Data Centers and Redundancy No No No

4.4.9(c) Supplemental Data Centers and Redundancy No No No

4.4.10(a) Supplemental Business Impact Analysis No No No

4.4.10(b) Supplemental Business Impact Analysis No No No

4.4.10(c) Supplemental Business Impact Analysis No No No

4.4.11(a) Supplemental Ethical AI and Algorithm Transparency No No No

4.4.11(b) Supplemental Ethical AI and Algorithm Transparency No No No

4.4.12(a) Supplemental Data Privacy and Subject Rights No No No

4.4.12(b) Supplemental Data Privacy and Subject Rights No No No

4.4.12(c) Supplemental Data Privacy and Subject Rights No No No

4.4.13(a) Supplemental Vendor Assessment and Monitoring No No No

4.4.13(b) Supplemental Vendor Assessment and Monitoring No No No

4.4.14(a) Supplemental Integration Lifecycle Management No No No

4.4.14(b) Supplemental Integration Lifecycle Management No No No

4.4.15(a) Supplemental Knowledge Base No No No

4.4.15(b) Supplemental Knowledge Base No No No

4.4.16(a) Supplemental Analytics and Insights No No No

4.4.16(b) Supplemental Analytics and Insights No No No

Score: 0 0 0

Requirement Definition

Req No. Req Type Req Name Requirement Definition

4.1.1(a) Business Unified Platform The system shall provide a centralized repository for all investigative matters, documents and related information allowing users to access all relevant matter information from a single interface.

4.1.1(b) Business Unified Platform The system shall support real-time updates and synchronization across all user access points.

4.1.2(a) Business Advanced Security The system shall operate in an environment approved to handle federal government materials using FIPS and NIST standard protocols to protect data security, with customizable role-based access control (RBAC) groups.

4.1.2(b) Business Advanced Security Administrators shall be able to set granular permissions at the document, matter and user levels.

4.1.2(c) Business Advanced Security The system will maintain a comprehensive audit trail of all user actions and data access from the moment a user logs in to the moment the user logs out.

4.1.2(d) Business Advanced Security The system should also include robust security and event monitoring capabilities.

4.1.2(e) Business Advanced Security The system should have field and file level encryption and support multi-factor authentication for user login.

4.1.3(a) Business Comprehensive Matter Management The system shall support full lifecycle of investigative matters, including but not limited to intake, recommendations, case action, discovery, trial, appeals and closure.

4.1.3(b) Business Comprehensive Matter Management The system shall provide document management capabilities, either directly or through API integration, including version control and collaborative editing that supports up to 1PB of data.

4.1.3(c) Business Comprehensive Matter Management The system shall support both criminal and civil investigations, as well as appellate, policy, international outreach, and FOIA work.

4.1.3(d) Business Comprehensive Matter Management The system shall ensure data integrity through checksums, backup mechanisms and conflict resolution processes.

4.1.4(a) Business Knowledge Sharing and AI-Powered Insights The system shall provide a searchable knowledge base of past matters and legal precedents.

4.1.4(b) Business Knowledge Sharing and AI-Powered Insights The system shall implement advanced query and AI-powered search capabilities, where permissible by law or policy, to identify relevant historical data.

4.1.4(c) Business Knowledge Sharing and AI-Powered Insights The system shall be able to share insights and documents across matters, subject to permission settings.

4.1.4(d) Business Knowledge Sharing and AI-Powered Insights The system shall integrate reporting capabilities to allow for creation of canned and ad hoc reports on the data it collects.

4.1.4(e) Business Knowledge Sharing and AI-Powered Insights The system shall provide data analytics tools to identify trends and patterns across multiple matters.

4.1.4(f) Business Knowledge Sharing and AI-Powered Insights The system shall allow for additional functionality to be added either natively or through integration over time (e.g., Economist solutions, LLM or RAG plug-ins, etc.).

4.1.5(a) Business Scalability and Adaptability The system architecture shall support horizontal scaling to accommodate increased load.

4.1.5(b) Business Scalability and Adaptability The system shall allow for the addition of new matter types and workflows without significant downtime.

4.1.5(c) Business Scalability and Adaptability The system shall support low-code customizable fields and metadata to adapt to changing legal requirements.

4.1.6(a) Business Evidence Lifecycle Tracking The system shall provide a comprehensive chain of custody tracking for all evidence.

4.1.6(b) Business Evidence Lifecycle Tracking The system shall support various evidence types, including physical and digital evidence.

4.1.6(c) Business Evidence Lifecycle Tracking The system shall log all actions performed on evidence items, including intake, analysis and disposition.

4.1.6(d) Business Evidence Lifecycle Tracking The system shall track work performed by data stagers, data loaders and others handling evidence to ensure all information relevant to the data ingested in document review systems is captured.

4.1.6(e) Business Evidence Lifecycle Tracking The system shall log key metrics about the data, such as document counts, image counts, metadata information, and volume size for each volume of produced material.

4.1.6(f) Business Evidence Lifecycle Tracking The system shall generate alerts for any breaks in chain of custody or potential errors in evidence handling.

4.1.7(a) Business Intelligent Workload Distribution The system shall maintain profiles of user skills, expertise, and current workload.

4.1.7(b) Business Intelligent Workload Distribution The system shall automatically assign tasks based on user profiles, matter requirements, and availability.

4.1.7(c) Business Intelligent Workload Distribution The system shall provide a dashboard for managers to view and adjust workload distribution.

4.1.7(d) Business Intelligent Workload Distribution The system shall allow for manual override of automatic task assignments when necessary.

4.1.7(e) Business Intelligent Workload Distribution The system shall provide resource allocation reporting for over-utilization.

4.1.8(a) Business Process Automation and Smart Notifications The system shall automate routine tasks such as document generation and filing with pre-built native capabilities.

4.1.8(b) Business Process Automation and Smart Notifications The system shall implement configurable workflows with automatic routing and approvals.

4.1.8(c) Business Process Automation and Smart Notifications The system shall send customizable notifications for deadlines, approvals, and important case updates.

4.1.8(d) Business Process Automation and Smart Notifications The system shall identify potential duplicate efforts and make suggested consolidations.

4.1.9(a) Business Compliance and Export Capabilities The system shall maintain records in compliance with relevant legal and regulatory requirements.

4.1.9(b) Business Compliance and Export Capabilities The system shall support export of data in formats compatible with NARA requirements.

4.1.9(c) Business Compliance and Export Capabilities The system shall provide capabilities for the efficient export of matter contents.

4.1.9(d) Business Compliance and Export Capabilities The system shall generate compliance reports for internal audits and external inspections.

4.1.10(a) Business Standardization and Efficiency The system shall provide a library of standardized templates for common legal documents.

4.1.10(b) Business Standardization and Efficiency The system shall support the creation and enforcement of standardized workflows by authorized users.

4.1.10(c) Business Standardization and Efficiency The system shall provide analytics on process efficiency and suggest improvements.

4.1.11(a) Business Extensibility The system shall support the integration of third-party applications, such as Feith System’s Enterprise Document Management System, ServiceNow, PACER and/or COURTLINK, Relativity, Oracle-based Cloud systems, MS Azure and/or Amazon AWS and Microsoft 365.

4.1.11(b) Business Extensibility The system shall allow for the development and deployment of custom modules to extend matter management, business process automation, etc.

4.1.11(c) Business Extensibility New functionalities shall be made available to all users based on their permission levels.

4.1.11(d) Business Extensibility The system shall provide a sandbox environment for testing new applications before deployment.

4.1.12(a) Business Cross-Device Availability The system shall have client applications that are configurable to work seamlessly on all devices regardless of operating systems or operating environment.

4.1.12(b) Business Cross-Device Availability The system shall be accessible via web browsers on desktop and laptop computers.

4.1.12(c) Business Cross-Device Availability The system shall provide mobile applications for iOS and Android devices.

4.1.12(d) Business Cross-Device Availability The system shall support offline access to critical documents with synchronization upon reconnection.

4.1.12(e) Business Cross-Device Availability The user interface shall be responsive and adapt to different screen sizes and orientations.

4.2.1(a) Functional Unified Platform The system shall provide a dashboard displaying an overview of all active matters, including key dates, assigned personnel and current status.

4.2.1(b) Functional Unified Platform Users shall be able to search for matters using various criteria such as DOJ File number, client name, matter type and assigned attorney(s).

4.2.1(c) Functional Unified Platform The system shall allow for the intake of new matters using a workflow based on whatever intake process that might be relevant such as citizen complaints or inquiries, HSR filing reviews, agency referrals, internal referrals, etc. that contains criteria such as DOJ File number, client name, matter type, and assigned attorney(s).

4.2.1(d) Functional Unified Platform The system shall automatically generate a unique identifier (DOJ File number) for each new matter created.

4.2.1(e) Functional Unified Platform Users shall be able to link related matters, allowing for easy navigation between associated cases.

4.2.2(a) Functional Advanced Security The system shall have a CRM/API Integration platform that is hosted in a FedRAMP Moderate or High level environment.

4.2.2(b) Functional Advanced Security The system shall support the creation of customizable security groups with predefined permission sets.

4.2.2(c) Functional Advanced Security Administrators shall be able to assign users to multiple security groups.

4.2.2(d) Functional Advanced Security The system shall allow for setting permissions at the following levels: matter, document, field, and function (e.g. read, write, delete, share).

4.2.2(e) Functional Advanced Security The system shall provide a user interface for administrators to manage access rights including granting and revoking permissions.

4.2.2(f) Functional Advanced Security The system shall log all login attempts, successful and unsuccessful, with timestamp, IP address and user ID.

4.2.2(g) Functional Advanced Security The system shall support integration with enterprise single sign-on (SSO) solutions.

4.2.2(h) Functional Advanced Security The system shall be compliant with zero trust requirements.

4.2.3(a) Functional Comprehensive Matter Management The system shall provide separate modules for different matter types (e.g., criminal, civil, appellate, FOIA), each with type-specific fields and workflows.

4.2.3(b) Functional Comprehensive Matter Management Users shall be able to upload documents to matters, with automatic versioning and metadata extraction.

4.2.3(c) Functional Comprehensive Matter Management The system shall provide a document viewer supporting common file formats (e.g. PDF, DOCX, XLSX) without requiring external applications.

4.2.3(d) Functional Comprehensive Matter Management The system shall allow for collaborative document editing with real-time updates and conflict resolution either native to the application or through API integrations with other Enterprise Document Management Systems (EDMS).

4.2.3(e) Functional Comprehensive Matter Management The system shall maintain a detailed activity log for each matter, recording all user actions and system events.

4.2.4(a) Functional Knowledge Sharing and AI-Powered Insights The system shall provide advanced searching, including full-text search function across all matters and documents, with multiple criteria filtering options based on metadata.

4.2.4(b) Functional Knowledge Sharing and AI-Powered Insights The search function shall support natural language queries and provide relevant results ranked by AI-determined relevance.

4.2.4(c) Functional Knowledge Sharing and AI-Powered Insights The system shall setup saved search alerts based on a set of relevant criteria

4.2.4(d) Functional Knowledge Sharing and AI-Powered Insights The system shall search records within the CRM platform and across other platforms or applications.

4.2.4(e) Functional Knowledge Sharing and AI-Powered Insights The system shall provide the capability to visualize complex relationships between metadata (e.g., relationship between judges, matters and staff)

4.2.4(f) Functional Knowledge Sharing and AI-Powered Insights The system shall suggest related matters and documents based on content similarity and user behavior patterns.

4.2.4(g) Functional Knowledge Sharing and AI-Powered Insights Users shall be able to tag documents and matters with custom keywords to enhance searchability.

4.2.4(h) Functional Knowledge Sharing and AI-Powered Insights The system shall analyze document metadata (i.e. date, author, file type, subject) to suggest relevant tags and provide automated tagging suggestions based on document content analysis.

4.2.4(i) Functional Knowledge Sharing and AI-Powered Insights The system shall provide a feature for users to create and share knowledge articles linked to specific matters or legal topics.

4.2.4(j) Functional Knowledge Sharing and AI-Powered Insights Should the platform allow for automatic tagging or suggestions? AI?

4.2.5(a) Functional Scalability and Adaptability The system shall support concurrent access by at least 100 concurrent users in various locations and, at times, different time zones without degradation in performance.

4.2.5(b) Functional Scalability and Adaptability The system shall allow for the addition of new matter types through a configuration interface without requiring code changes.

4.2.5(c) Functional Scalability and Adaptability The system shall provide an interface for administrators to create and modify custom fields for different matter types.

4.2.5(d) Functional Scalability and Adaptability The system shall support integration with external databases and services through a documented API-integration tool that includes management, analytics and load balancing.

4.2.6(a) Functional Evidence Lifecycle Management The system shall provide a dedicated module for evidence management, including intake, storage, analysis and disposition tracking.

4.2.6(b) Functional Evidence Lifecycle Management Users shall be able to log physical media with details such as description, location, custodian, document and image counts, volume sizes, and chain of custody, or to import this information from an automated data ingestion pipeline using documented API integrations.

4.2.6(c) Functional Evidence Lifecycle Management The system should allow unique barcodes or QR codes to be generated for physical evidence items to facilitate tracking.

4.2.6(d) Functional Evidence Lifecycle Management For digital evidence, the system should calculate and store hash values to ensure data integrity.

4.2.6(e) Functional Evidence Lifecycle Management The system shall alert users when evidence items are nearing destruction dates based on configurable retention policies.

4.2.7(a) Functional Intelligent Workload Distribution The system shall maintain a skills matrix for all users, allowing for manual updates and automatic learning based on completed tasks.

4.2.7(b) Functional Intelligent Workload Distribution The system shall provide a workload dashboard showing current assignments and capacity for each user.

4.2.7(c) Functional Intelligent Workload Distribution The system shall suggest assignees based on required skills, current workload, availability and past performance when a new task is created and ready for assignment.

4.2.7(d) Functional Intelligent Workload Distribution The system shall allow for manual assignment of tasks overriding automated suggestions when necessary.

4.2.7(e) Functional Intelligent Workload Distribution The system shall provide notifications to users when new tasks are assigned to them.

4.2.8(a) Functional Process Automation and Smart Notifications The system shall provide a visual workflow designer allowing administrators to create and modify automated processes.

4.2.8(b) Functional Process Automation and Smart Notifications The system shall support the creation of document templates with merge fields linked to matter data.

4.2.8(c) Functional Process Automation and Smart Notifications Users shall be able to set up custom alerts and notifications based on matter events, deadlines, or document updates.

4.2.8(d) Functional Process Automation and Smart Notifications The system shall provide an automation rule engine to trigger actions based on predefined conditions (e.g. send approval request when a document is marked as final).

4.2.8(e) Functional Process Automation and Smart Notifications The system shall use machine learning to identify and suggest potential process improvements based on user behavior patterns.

4.2.9(a) Functional Compliance and Export Capabilities The solution shall be compatible with the DOJ requirements for a cloud-based enterprise platform.

4.2.9(b) Functional Compliance and Export Capabilities The system shall maintain an immutable audit log of all user actions and system events, including deletions, compliant with legal and regulatory requirements.

4.2.9(c) Functional Compliance and Export Capabilities Users shall be able to generate compliance reports showing matter status, document history, and user actions within a specified date range.

4.2.9(d) Functional Compliance and Export Capabilities The system shall support bulk export of matter data and documents in industry-standard formats (e.g., EDRM XML or Concordance delimited text files for eDiscovery).

4.2.9(e) Functional Compliance and Export Capabilities The system shall provide a dedicated interface for managing retention policies, allowing automatic flagging or matters and documents for review and destruction.

4.2.10(a) Functional Standardization and Efficiency The system shall provide a template library for common legal documents, organized by matter type and jurisdiction.

4.2.10(b) Functional Standardization and Efficiency Users shall be able to create new templates with merge fields linked to matter and contact data.

4.2.10(c) Functional Standardization and Efficiency The system shall provide a check-in/check-out mechanism for document editing to prevent conflicting changes.

4.2.10(d) Functional Standardization and Efficiency The system shall generate efficiency reports, showing metrics such as average time per task, document turnaround time, and resource utilization.

4.2.11(a) Functional Extensibility The system shall provide a RESTful API allowing secure access to matter data and functions.

4.2.11(b) Functional Extensibility The system shall support the integration of third-party tools through a plug-in architecture.

4.2.11(c) Functional Extensibility The system shall allow administrators to create custom dashboards and reports using a built-in report designer.

4.2.11(d) Functional Extensibility The system shall provide a sandboxed development environment for testing custom modules and integrations.

4.2.12(a) Functional Cross-Device Availability The system shall provide a responsive web interface optimized for desktop, tablet, and mobile devices.

4.2.12(b) Functional Cross-Device Availability Native mobile applications shall be available in iOS and Android, providing core functionality and offline access to key documents.

4.2.12(c) Functional Cross-Device Availability The system shall support secure document viewing on mobile devices without allowing local storage of sensitive data.

4.2.12(d) Functional Cross-Device Availability The system shall provide push notifications to mobile devices for critical alerts and task assignments.

4.2.12(e) Functional Cross-Device Availability Users shall be able to synchronize selected matters for offline access, with automatic update when reconnected.

4.2.12(f) Functional Cross-Device Availability The system shall offer flexibility to adapt to various jurisdictions, support international mission work, and maintain strict compliance with legal and regulatory standards.

4.3.1(a) Non-Functional Response Times The system shall respond to user interactions within 2 seconds under normal load conditions.

4.3.1(b) Non-Functional Response Times The system shall respond to search queries within 5 seconds for databases up to 10 million documents.

4.3.1(c) Non-Functional Response Times The system shall respond to document upload and download operations with a minimum transfer rate of 10 MB/second.

4.3.1(d) Non-Functional Response Times The system shall not use paging of less than 200 items to achieve stated response times

4.3.2(a) Non-Functional Scalability The system shall support minimum of 1000 concurrent users without degradation in performance.

4.3.2(b) Non-Functional Scalability The system shall be capable of managing at least 1 million active matters.

4.3.2(c) Non-Functional Scalability The document repository shall support storage of up to 1 petabyte of data.

4.3.3(a) Non-Functional Capacity The system shall handle a data growth rate of 20% annually without requiring architectural changes.

4.3.3(b) Non-Functional Capacity The system shall support individual document sizes of up to 1 gigabyte.

4.3.4(a) Non-Functional Uptime The system shall meet or exceed 95% availability during business hours (Peak Hours of 6:00am - 9:00PM ET).

4.3.4(b) Non-Functional Uptime Planned maintenance windows shall not exceed 4 hours per month and must be scheduled during off-peak hours.

4.3.5(a) Non-Functional Fault Tolerance The system shall implement automatic failover mechanisms to ensure continuity of service in case of hardware or software failures.

4.3.5(b) Non-Functional Fault Tolerance No single point of failure shall exist in the system architecture.

4.3.6(a) Non-Functional Data Integrity The system shall maintain ACID (Atomicity, Consistency, Isolation, Durability) properties for all database transactions.

4.3.6(b) Non-Functional Data Integrity The system shall perform daily data integrity checks and report any inconsistencies.

4.3.6(c) Non-Functional Data Integrity The system shall audit entries and provide data lineage.

4.3.7(a) Non-Functional Data Protection The system should have native applications capable of meeting the document generation and legal and evidence management tracking requirements outlined in the business requirements section under 4.1. The system should inherit the controls of the platform to the greatest extent, and where not inherited, can meet a minimum of IL4 standards.

4.3.7(b) Non-Functional Data Protection The system shall provide or leverage existing DOJ identity-management services to support system administration capabilities to manage users and groups, where applicable, including creation, provisioning, permissions, etc.

4.3.7(c) Non-Functional Data Protection All data at rest shall be encrypted using AES-256 encryption or equivalent.

4.3.7(d) Non-Functional Data Protection All data in transit shall be encrypted using TLS 1.3 or higher.

4.3.7(e) Non-Functional Data Protection Encryption of data at rest and data in transmission shall be applied when the solution itself is safeguarding data, including but not limited to user data, application data, network traffic, and authentication.

4.3.7(f) Non-Functional Data Protection The system shall comply with Federal information processing standard (FIPS) 140-2 or FIPS 140-3 certified cryptomodules for all encryptions. The Service Provider must provide the National Institute of Standards and Technology (NIST) validation certificate number from https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules wherever the Service Provider uses encryption anywhere in the system.

4.3.8(a) Non-Functional Access Control The system shall display a logon/warning banner with end-user acknowledgment to proceed for every user session.

4.3.8(b) Non-Functional Access Control The system shall support multi-factor authentication for all user accounts.

4.3.8(c) Non-Functional Access Control The system shall support single-user sign-on/personal identity verification (PIV) cards and the ability for integrations of system access control (login/ Windows authentication) through ATR’s active directory.

4.3.8(d) Non-Functional Access Control The system shall…