Web-based Jury Management System (JMS)

The document "USCA26R0059 - JMS RFI" outlines instructions for completing a Request for Information (RFI) form. It specifies that Column B contains a drop-down feature for identifying the document section in question. Users are required to fill out columns C, D, and E. Column F, which is for providing a narrative explanation of the question, is optional. The instructions emphasize utilizing the drop-down feature and completing the mandatory columns to ensure accurate and organized responses within the RFI process.

The USCA26R0059 solicitation is a Request for Proposal (RFP) issued by the Administrative Office of the United States Courts for a Jury Management System (JMS) solution. This Indefinite Delivery/Indefinite Quantity (IDIQ) contract covers web-based system design, development, implementation, operations, and maintenance, including travel, deliverables, and labor. The contract has a seven-year ordering period from August 15, 2026, to August 14, 2033, with a six-month option to extend. The estimated ceiling is $38,000,000. It outlines detailed terms for contract administration, invoicing, and deliverables, emphasizing security for sensitive information and compliance with federal regulations. The document also includes specific clauses regarding government-furnished information, key personnel, travel, and data rights, with the government retaining unlimited rights to code created for modifying the base COTS product.

The Administrative Office of the U.S. Courts (AO) has issued a Request for Information (RFI) to gather market research for a new Jury Management System (JMS). This RFI seeks industry feedback on a secure, scalable, cloud-based solution to replace the current legacy system. The new JMS must support the full jury lifecycle, protect sensitive juror data, and integrate with court proceedings, adhering to federal best practices for cloud security and identity management. The AO is interested in vendor capabilities regarding commercial solutions, technical features, hosting models, security compliance, data migration, and implementation timelines. Responses will help refine requirements and the acquisition strategy for a future solicitation. The RFI outlines specific questions across various categories, including jury lifecycle support, operational tools, financial and data integration, cloud hosting, interoperability, user experience, reporting, system performance, transition, training, and deployment. Responses are due by April 6, 2026, at 12:00 p.m. Eastern Time.

The Administrative Office of the U.S. Courts seeks a modern, cloud-based Jury Management System (JMS) to replace its outdated legacy system. This Software as a Service (SaaS) solution, hosted in a FedRAMP High authorized environment, must support the entire jury lifecycle from selection to service completion, ensuring compliance with federal regulations. Key objectives include enhancing operational efficiency through automation, improving the juror experience with intuitive online services and multi-channel communication, and providing real-time data for informed decision-making. The JMS must integrate with existing financial systems, maintain high security standards, ensure operational continuity, and facilitate data exchange with other judiciary systems. The project emphasizes vendor independence, a smooth transition with data migration, comprehensive training, nationwide user support, and a scalable architecture for future needs. The goal is a secure, efficient, and cost-effective jury management capability across all 94 federal district courts.

The Judiciary Identity, Authentication, and Access Management Requirements document outlines the mandates for secure identity and access management for both public-facing and internal Judiciary applications. Public access applications must integrate with a federated Identity and Access Management (IAM) / Identity Provider (IdP) vendor, currently Login.gov, to provide single sign-on (SSO), strong authentication with phishing-resistant Multi-Factor Authentication (MFA), and centralized identity management, aligning with federal security standards. Internal Judiciary applications, used by organizational users, must integrate with an enterprise IAM/IdP platform, currently Azure AD, to enable centralized SSO, MFA, and identity governance, supporting standards like SAML 2.0, OpenID Connect (OIDC), and OAuth 2.0. The document emphasizes mandatory identity proofing (IA-12) for Moderate and High impact systems, and MFA (IA-02) for all organizational users across all system impact levels (High, Moderate, and Low), including privileged and non-privileged accounts. Furthermore, Authenticator Assurance Level 2 (AAL2), requiring MFA, is mandatory when Personally Identifiable Information (PII) is made available online. These requirements are based on the Judiciary Information Security Framework (JISF) and NIST Digital Identity Guidelines, with specific citations to NIST SP 800-63C-4 and NIST SP 800-63B-4 provided for vendor review.

The Technology Solution Office (TSO) requires a Multi-Factor Authentication (MFA) solution for public access to judiciary applications. The solution must be cloud-based (SaaS), FedRAMP certified (Moderate to High impact), and comply with NIST SP 800-63-3 Digital Identity Guidelines (IAL2 & AAL2 recommended). Key requirements include unified identity authentication, user identity storage/management, support for various authentication methods (biometric, password-less, push notifications, TOTP), and robust identity proofing for both national and international users. The system must offer comprehensive user management features, including account provisioning/de-provisioning, self-service options, and periodic reauthentication. It must be scalable, highly available (99.999%), compatible with existing logging, and provide monitoring/reporting. The vendor must offer extensive development support (SDKs, APIs, documentation), configuration flexibility, and efficient handling of production changes. Post-production support requires a tiered ticketing system with SLAs, knowledge base, and escalation procedures. Training modules for authentication, MFA, and user management are essential. Security measures must mitigate phishing and MitM attacks, comply with FIPS 140-3, and adhere to a Zero-Trust Policy.

The PACER Solution Recommendation Version 1.3 proposes integrating Multi-Factor Authentication (MFA) into the Public Access to Court Electronic Records (PACER) system. This is to enhance filer security and offer opt-in MFA for non-filers without altering existing user identities. The document, prepared by the Technology Solution Office (TSO), evaluates two primary solutions: Open Time-Based One-Time Password (TOTP) and an Inhouse Platform Level API Gateway Solution. After a thorough evaluation against Court Services Office (CSO) business requirements, the TSO recommends the Open TOTP solution. This recommendation is based on its ease of implementation, the development team's existing familiarity with TOTP, strong security features, user-friendliness, and cost-effectiveness compared to the more resource-intensive API Gateway solution.

The Judiciary Information Security Framework (JISF) v2.2, updated in October 2021, outlines a comprehensive, seven-step Security Risk Management Framework (RMF) to protect the confidentiality, integrity, and availability of information across the U.S. judiciary. Developed by the Judiciary Information Technology Security Program, this framework aims to standardize security risk management through a repeatable process for federal and local court systems. The seven steps include preparing the judiciary and system, categorizing system and information, selecting, implementing, and assessing controls, authorizing systems, and continuous monitoring. The JISF leverages best security practices, modeled on NIST Special Publications, and includes 18 control families to mitigate threats from various sources.

The document outlines a comprehensive plan for an Electronic Health Record Modernization (EHRM) infrastructure upgrade project, focusing on improving mechanical, plumbing, and fire suppression systems across various buildings. Key aspects include assessing existing conditions, performing demolitions, and installing new equipment while ensuring coordination among different trades. The project emphasizes enhancing sprinkler systems, ductwork, and piping for improved accessibility and maintainability. It also details the integration of mechanical equipment and plumbing fixtures, adhering to strict guidelines and safety measures like infection control and fire watches. The document stresses the importance of detailed planning for all systems to modernize facilities, prioritize safety, and ensure compliance with relevant standards and regulations.