Web-based Jury Management System (JMS)

Request for Information (RFI)

This RFI is issued by the Administrative Office of the U.S. Courts (AO) to conduct market research for a modernized Jury Management System (JMS). The AO is seeking industry feedback, capability details, and technical insights to refine requirements, acquisition strategy, and the Statement of Objectives (SOO) for a future solicitation. The goal is to replace the existing legacy JMS with a secure, scalable, cloud-based solution for federal jury operations.

The AO is requesting information on:

• Commercial solutions and technical capabilities

• Hosting models and security compliance (including FedRAMP, NIST RMF, Zero Trust)

• Integration approaches with financial systems and identity management services

• Data migration strategies

• Implementation timelines

• User experience and accessibility standards

• Reporting, analytics, and system performance

• Training and support models

• Deployment experience

• Vendors are encouraged to provide detailed responses to the general questions outlined on pages 3-5 of the RFI document.

• Responses can be submitted as a capabilities statement or via email.

• Questions regarding the RFI should be directed to AJ Lee (AJ_Lee@ao.uscourts.gov) or Vanessa Jackson (Vanessa_Jackson@ao.uscourts.gov).

• Responses are due no later than April 6, 2026, at 12:00 p.m. Eastern Time.

• This RFI is for market research purposes only.

• The AO does not intend to award a contract based on this solicitation.

• No costs associated with responding will be reimbursed.

• Information received may be used to develop and refine the final solicitation.

• An Excel file for submitting questions has been prepared by the AO.

Form / Attachment / Pricing Sheet

This document outlines the Judiciary's requirements for Identity, Authentication, and Access Management (IAM) for applications requiring public access and internal Judiciary applications. It details the standards and controls necessary for secure user authentication and identity services.

• Public-Facing Applications: Require integration with a federated Identity Provider (IdP) vendor, supporting capabilities like Single Sign-On (SSO), Multi-Factor Authentication (MFA), and centralized identity management. Login.gov is currently used for this purpose.
• Internal Applications: Must integrate with an enterprise IAM/IdP platform, supporting SSO, MFA, and identity governance. Azure AD (Microsoft Entra ID) is currently leveraged.
• Mandatory Requirements:
  • Identity Proofing (IA-12) is mandatory for Moderate (M) and High (H) classified systems; optional for Low (L).
  • MFA (IA-02) is mandatory for all Judiciary organizational users across all system impact levels (High, Moderate, and Low), including privileged and non-privileged accounts.
  • Authenticator Assurance Level 2 (AAL2) is required whenever Personally Identifiable Information (PII) is made available online, necessitating two distinct authentication factors (MFA).
• NIST Compliance: Adherence to NIST Digital Identity Guidelines is required, with specific references provided for Federation and Assertions (NIST SP 800-63C-4) and Authentication and Authenticator Management (NIST SP 800-63B-4).

Vendors responding to opportunities requiring identity and access management solutions, or developing applications for the Judiciary, must understand and comply with these stringent authentication, identity proofing, and MFA requirements. This document is critical for ensuring proposed solutions meet federal security standards and Judiciary-specific policies.

Form / Attachment / Pricing Sheet

This document is a "Questions Submission Form" for the "USCA26R0059 - JMS RFI". It provides a structured template for potential bidders to submit questions regarding the opportunity.

• Column B: Drop-down feature to identify the specific document section the question pertains to.
• Columns C, D, E: Fields for Question Number, Paragraph, and Page Number.
• Column F: Optional field for a detailed "Question Narrative" if further explanation is needed.
• The form is intended to be filled out by the bidder to facilitate organized communication with the government.

This form is crucial for bidders who have questions about the "USCA26R0059 - JMS RFI" opportunity. It outlines the required format for submitting inquiries, ensuring that questions are clearly categorized and directed to the appropriate sections of the solicitation documents. Proper use of this form will aid in obtaining timely and relevant clarifications from the government.

Solicitation / RFP / RFQ

This document is a solicitation for an Indefinite Delivery/Indefinite Quantity (IDIQ) contract for a Web Based Jury Management System (JMS) solution. The scope includes system design, development, implementation, operations, and maintenance, encompassing travel, deliverables, and labor.

• Development and implementation of a Web Based Jury Management System (JMS) solution.

• Operations and maintenance of the JMS solution.

• Delivery of electronic copies of document deliverables.

• Contractor must provide a continuity plan and associated costs within 12 hours of a COOP event.

• All personal computer products delivered must be EPEAT® bronze-registered or higher.

• Contract Type: Indefinite Delivery/Indefinite Quantity (IDIQ)

• Period of Performance: Seven (7) year ordering period with a six (6) month option period.

• Ordering Years: 09/30/2026 to 09/29/2033.

• Option to Extend Services: Six (6) month extension (Clause 2-90C).

• Minimum Guarantee: $1,000.00.

• Estimated Ceiling: $38,000,000.00 (may be exceeded without modification).

• Proposal Submission Deadline: April 6, 2026, 12:00 PM ET (for questions).

• Proposal Due Date: TBD.

• Evaluation Factors: Best value determination method, considering non-priced factors (Factors 1-3) as significantly more important than price. Non-priced factors will be evaluated using confidence ratings. Price will be evaluated using price analysis techniques.

• Discussions: The government reserves the right to award without discussions, but may issue clarification/revision requests.

• Not specified in the provided pages.

• The solicitation incorporates numerous clauses by reference. Offerors are advised to review these carefully.

• Specific details regarding the Task Order 0001 and its requirements will be provided in the RFP.

• The Judiciary intends to award a single IDIQ contract and Task Order 0001 from this solicitation.

Statement of Work (SOW) / Performance Work Statement (PWS)

The objective is to acquire a secure, cloud-based jury management solution (JMS) to modernize federal jury operations, ensuring compliance, operational efficiency, and improved public service. The solution will replace the current legacy system.

• Procure a Software as a Service (SaaS) solution hosted in a FedRAMP High authorized environment.

• Support the full lifecycle of federal jury operations: selection, qualification, summoning, management, and tracking.

• Provide a configurable solution to improve juror experience and operational efficiency.

• Integrate with the Government's current financial management system (Momentum) and future systems.

• Support scanning, multi-channel communication (IVR, email, SMS), and proximity-based check-in.

• Ensure compliance with federal and Judiciary standards for security, cloud hosting, identity management, accessibility, data protection, and continuity of operations.

• High availability (at least 99.9%).

• Average response times of 3 seconds or less under normal load.

• Scalability to peak demand.

• Defined Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO).

• Secure integration with Government systems using approved protocols.

• Compliance with NIST Risk Management Framework (RMF) and FedRAMP requirements.

• The solution will be deployed nationwide across all 94 federal district courts and two Administrative Office (AO) sites, including OCONUS locations.

• Support will be provided during judiciary working hours (8:00 a.m. to 7:00 p.m. ET), excluding weekends and federal holidays.

• Must operate in a Government-approved cloud environment compliant with NIST RMF and FedRAMP.

• Integration with Government identity and access management services (PIV, SSO, MFA).

• Support for open standards and avoidance of vendor lock-in.

• Comprehensive transition and data migration plan from the legacy system.

• Nationwide user support and training.

• Disaster recovery and continuity capabilities.

• Compliance with Section 508 accessibility standards.

Form / Attachment / Pricing Sheet

This document outlines the business requirements for a Multi-Factor Authentication (MFA) solution for public access to the Technology Solution Office (TSO) systems. It details the functional, security, and support requirements for vendors providing such a solution.

• Basic Authentication, MFA, Identity Proofing (Enrollment): Requirements for user identity management, compliance with NIST guidelines (SP 800-63-3), support for various assurance levels (IAL, AAL, FAL), and multiple authentication methods (biometric, push notifications, TOTP).
• User Management: Features for managing access, user roles, permissions, provisioning/de-provisioning, and periodic reauthentication.
• Performance: Requirements for scalability, high availability (99.999%), logging, and monitoring.
• Support: Expectations for comprehensive support for end-users and development teams, including development support, application configuration flexibility, and post-production support.
• Security and Standards: Mandates for security measures against phishing and MitM attacks, adherence to NIST standards (SP 800-63-4, SP 800-53), FIDO compatibility, FIPS 140-3 compliance, and Zero-Trust policy adherence.

This document serves as a detailed specification for potential vendors to understand the technical, security, and operational requirements for providing an MFA solution. Bidders must demonstrate how their proposed solution meets or exceeds these requirements, including NIST compliance, scalability, and support capabilities, to be considered for this opportunity.

Form / Attachment / Pricing Sheet

This document, "Attachment C - Recommendation for PACER MFA.pdf", is a solution recommendation for integrating Multi-Factor Authentication (MFA) into the Public Access to Court Electronic Records (PACER) system. Its purpose is to improve filer security and support opt-in MFA for non-filers without altering existing user identities and credentials.

• Business Requirements: Outlines the need for MFA for public users, including mandatory MFA for users with Case Management (CM)/Electronic Case Files (ECF) level access and optional MFA for read-only users.
• Proposed Solutions: Evaluates two primary solutions: Open Time-Based One-Time Password (TOTP) and an Inhouse Platform Level API Gateway.
• Solution Evaluation: Compares the proposed solutions against the business requirements, indicating which requirements each solution supports.
• Recommendation: Recommends Open TOTP as the preferred authentication method due to its ease of implementation, familiarity with the technology by the development team, strong security features, user-friendliness, and cost-effectiveness.
• Appendices: Includes reference implementation libraries for PACER (dotNET, Java, Rails) and details on Authentication Assurance Level 2 Requirements (NIST800-63B) and Risk Impacts.

This document provides insight into the government's strategy for enhancing security within the PACER system through MFA. While it is a recommendation document and not a direct solicitation, it details the requirements and preferred solution that may inform future procurements or system integrations related to PACER security. Bidders interested in providing authentication solutions or related services for government systems may find the outlined requirements and evaluation criteria informative.

Form / Attachment / Pricing Sheet

This document, "Attachment D - Judiciary Info Security Framework - JISF.pdf", outlines the Judiciary Information Technology Security Program's framework for managing information security risks across the judiciary. It provides a structured approach to ensuring the confidentiality, integrity, and availability of information.

• Judiciary Information Security Framework (JISF): A comprehensive security approach for court units, national systems, and others within the judiciary.
• Seven-Step Risk Management Framework (RMF): A cyclical process including Prepare, Categorize, Select Controls, Implement Controls, Assess Controls, Authorize System, and Monitor System.
• Judiciary Recommended Security Controls: A customized set of controls organized into eighteen families, modeled on NIST standards, to assist in managing information security risks.
• Version History: Details updates to the framework, with the latest version (2.2) updated in October 2021.

This document serves as a foundational security framework for the U.S. Courts. Bidders responding to opportunities within the judiciary, particularly those involving IT systems or data handling, should be aware of and prepared to comply with the security requirements and controls outlined in this framework. Understanding the JISF and its associated RMF process is crucial for developing compliant proposals and ensuring the security of judiciary information and systems.

Form / Attachment / Pricing Sheet

This document, "Attachment E - Jury Selection and Service Act.pdf", appears to be a legal document related to jury selection and service within the United States federal court system. It is likely intended to provide information or requirements regarding jury service.

• 28 U.S.C. Chapter 121: This chapter of the U.S. Code pertains to "Juries; Trial by Jury."
• Sections 1861-1878: The document details various sections within this chapter, including:
  • Declaration of policy regarding jury service.
  • Prohibition of discrimination in jury selection.
  • Plans for random jury selection.
  • Qualifications for jury service.
  • Procedures for drawing names, summoning panels, and challenging selection processes.
  • Maintenance and inspection of records.
  • Definitions related to jury service.
  • Protection of jurors' employment.
  • Trial by jury in specific courts (e.g., Court of International Trade).
• Historical and Revision Notes: These sections provide context and explain changes made to the law over time.
• Amendments: Details specific legislative changes to the sections.

While this document is not a solicitation, RFP, or SOW, it provides the legal framework and requirements for jury selection and service in federal courts. If the opportunity involves any aspect of legal proceedings, court operations, or services that might require understanding or interacting with the federal jury system, this document could be relevant for understanding the operational context or potential legal requirements.