Attachment 14 - General System Functions.pdf
PDF 227 KB Posted
- Attached to
- Web-based Jury Management System (JMS)
- Solicitation number
- USCA24R0030
- Issued by
-
Administrative Office of the U.S. Courts
About this file
This document is an attachment titled "General System Functions" that outlines the requirements for a web-based Jury Management System (JMS) as part of a federal contract opportunity. The key details include:
The current JMS is being upgraded to a new web-based application with substantially different usability features, including data output options, accessibility controls, navigation capabilities, database access, and content management. The system must support various user roles and stakeholders, and adhere to specific documentation and randomness requirements during the jury selection process.
The related federal contract opportunity is a solicitation by the Administrative Office of the U.S. Courts (AO) to award a single Indefinite Delivery, Indefinite Quantity (IDIQ) contract for a modified commercial-off-the-shelf (COTS), web-based JMS solution. Responses to the solicitation are due by 12:00 P.M. ET on May 31, 2024, and any questions must be submitted by 12:00 P.M. ET on May 10, 2024.
View the file
Other files
Show all 45
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
General System Functions
Web-Based Jury Management System Requirements
Version 1.0
Attachment 14
Contents Overview
Users and Roles Stakeholders
System Usability Data Output Accessibility Navigation DB Access Content Documentation Randomness
Property of the Administrative Office of the U.S. Courts Attachment 14 1
Overview
The current Jury Management System (JMS) uses old technology and is being upgraded to new server technologies as well as being upgraded to a web-based application.
The look and feel of the web-based application is expected to be substantially different from the current user-driven interface and should contain the following standard usability functions.
Users and Roles
Jury Administrators, Jury Clerks, and other jury-related user roles
Stakeholders
JMS users
Attachment 14 2
System Usability
The system shall have the following standard functions and usability features.
Data Output
• Printed output
• On-screen HTML rendering
• Downloadable/printable PDF
• Exportable data in CSV and/or text file
• Email (specific print outputs, such as letters)
Accessibility
• Simple, easy-to-use login screens.
• Log out option to close web session.
• Allows use of complex passwords.
• Allows passwords to be changed at specified intervals.
• Auto-recovery of password.
o Ability to recover Juror ID Number for the Online Public Access Website.
• Provides lock-out after X number of login attempts.
• Unique homepage for each court location.
• Page load/response time no greater than 3 seconds.
• Easy-to-use, intuitive interface.
• Font size – minimum font size = 11.
• Text to background contrast.
• Standard browsers supported.
• Supports idle-time lockout.
• Allows editing of user profiles.
• Web-responsive design.
• Minimal use of flash and add-ons.
Navigation
• A mouse hover, also called just hover, triggers an event when the user places a pointer over a designated area. The action of moving the mouse over the item causes events such as pop-up windows or description boxes that contain a context description.
• Ability to tab across input fields.
• A custom not found/404 page functionality.
• Enhanced vertical scrolling.
• Minimal clicks and steps to perform functions.
o One process for collecting and reviewing mileage.
o Streamlined process for printing questionnaires and summons.
o Streamlined process for downloading questionnaire and summons files.
• Ability to change any aspect of a juror’s record from any functional area in the system (such as review screens):
Attachment 14 3 o Update a status.
o Update juror’s personal data, phone number, address, email, etc.
o Collect and review mileage.
o Transfer juror to another pool.
o Defer juror due to change of address.
DB Access
• Ability to create reports and run queries against the database (DB)
• Ability to view and print query results.
• Ability to modify stored query selection criteria.
• DB back-up at specified intervals.
Content
• CASS-certified – Certification from the United States Postal Service (USPS) for address validation. CASS standardizes mailing lists, updates outdated addresses, and verifies addresses are valid and complete.
• Editing data – Inserting and replacing text shall be supported. A majority of data fields shall be editable. The exceptions are Juror ID Number and Pool Sequence Number/Juror Number.
• Appropriate punctuation (i.e., dollar signs ($) for dollar amounts on reports, etc.).
• Reports and screen displays should be sortable by column headers.
• Configurable drop-down lists.
• Consistent heading labels.
• Easy access help built into the system.
• Ability to cancel print jobs.
• Ability to select any printer on the court’s network.
• Standard “Save, Don’t Save, Cancel” window when changing data throughout system.
• Ability to customize email and letter text instead of using preformatted letter and email text.
• Ability to change the subject line of email letters.
• System generated unique pool number.
• Standard headings on reports, date, time, report name, etc.
• Standard footers on reports, page numbers (Page 1 of 1, etc.)
• Totals and grand totals on reports (where applicable).
• Descriptive warning messages and user prompts.
• All irrevocable functions shall have warning messages.
• Ability to search by wildcard (*) throughout the system.
• Ability to sort columns in any part of the system (high to low, low to high).
• Provides capability of using handheld scanners.
• Display pool sequence number (“juror number”) throughout the system.
• Supports barcoding.
• System must have the ability to track version history as versions change.
• History records include, but are not limited to, the following:
o Recording system access – login/out on the Online Public Access Website.
o Recording details of every change to a participant’s record (such as reporting
Attachment 14 4 pools, panels, seated juries, attendance, status changes, etc.).
o Recording when participants use proximity technology or the kiosk for attendance check in/check out.
o Recording whenever a utility parameter is changed.
o Recording changes to user access rights.
Documentation
• Robust Online Help System (such as RoboHelp)
• User Guide and User Manual
• Flowcharts (or the like) that illustrate the data flow through the system and how error messages are triggered.
• Release Notes (when new versions are released)
Randomness
At specific stages in the jury selection process prospective jurors must be selected by a random method that is demonstrably random for potential jury challenges. The Contractor is responsible to implement true randomness during the selection process and possibly defend it in a court of law.
The following processes require random selection:
1. Selecting participants to mail qualification questionnaires (2-Step) or questionnaire and summons (1-Step).
2. Selecting participants for reporting jury pool (2-Step).
3. Creating panel for voir dire.
4. Any substitution or replacement functions by zip code.
The process of selecting names from the source list(s) to create the master jury wheel also must be random. However, this contract does not include wheel building. Refer to 28 USC 1863(b)(4).
| Overview |
| Users and Roles |
| Stakeholders |
| System Usability |
| Data Output |
| Accessibility |
| Navigation |
| DB Access |
| Content |
| Documentation |
| Randomness |
File details come from the government source that posted it. Updated .