Home / Jury Management Solution (JMS) System / Document

Attachment 1: Jury Management Solution Performance Work Statement

Updated

A PDF document (469 KB) attached to Jury Management Solution (JMS) System, from the Administrative Office of the US Courts. Due Oct 30, 2026, 12:00 AM (UTC-4).

File name: Attachment 1 - Jury Management Solution PWS.pdf

Download the full documentSee the bid

The full file is for paid members, or buy this bid alone.

Preview

USCA27R0009 - Attachment 1 - Section C

Jury Management Solution (JMS)
Performance Work Statement

1.0 Background

The Administrative Office of the U.S. Courts (AO) (Government) currently operates a legacy Jury Management System (“Legacy JMS”) that supports jury operations across all the federal district courts (courts), of which there are 94 today.
Federal district courts must comply with Title 28, U.S.C. § 1861 et seq. (Jury Selection and Service Act) and related policies (Guide to Judiciary Policy, Volume 4, Chapter 3) governing random selection, qualification, summoning, and compensation of petit and grand jurors. For the purpose of this solicitation, all references of judiciary policies and court-specific procedures governing jury management are Judiciary-sensitive and will be provided at contract award. Unlike state-court jury management systems, which typically serve a single court under a uniform statewide framework, a federal Jury Management Solution (JMS) simultaneously supports the full operational diversity of the federal judiciary. Each federal district court operates under a court-specific jury selection plan approved by the relevant circuit judicial council, resulting in significant and legally mandated variation in source-list composition, divisional wheel architecture, refill scheduling, excusal and exemption categories, grand jury selection methodology, and panel disclosure timing.
The current environment presents increasing operational risk due to aging platform dependencies, limited configurability, fragile integrations, high manual workload, constrained observability, and rising support and maintenance burden.

2.0 Scope

The scope is to acquire a modern, centralized, secure JMS capable of supporting the full lifecycle of federal jury operations, including the storage, processing, and transfer of highly sensitive data.

3.0 Operational Requirements

The Contractor shall provide and maintain an end-to-end JMS that includes hosting, application administration, monitoring, incident response, problem management, release and change management, identity and access integration, interface operations, disaster recovery, service reporting, and user support escalation. The Contractor’s operating model for the JMS shall clearly distinguish Government and Contractor responsibilities and align with Judiciary service management processes.
The JMS shall provide secure and supportable nationwide jury management that preserves continuity of jury operations, maintains accurate financial processing, supports standards-based

The beginning of the document. Download the full file to read on.

Other documents in this bid