Attachment 2 - Demonstration Script.pdf

USCA24R0030

Attachment 2

RFP USCA24R0030: ATTACHMENT 2 – JURY MANAGEMENT SYSTEM (JMS)

OPERATIONAL CAPABILITY DEMONSTRATION SCRIPT

Process:

1. Each offeror will have a total of two (2) hours to demonstrate their solution’s ability to perform and/or execute the features and functions listed in the following sections provided below. The offeror shall demonstrate each of the eighteen (18) features and functions. It is up to the offeror to determine how the two (2) hours are allotted among the eighteen features and functions. The offeror shall clearly identify when each of the elements are being addressed. The offeror's live demonstration shall not exceed a total of two (2) hours and shall not deviate from the provided script. Any portion of the demonstration that exceeds the two (2) hours will not be evaluated. If the demonstration finishes early, demonstrations outside of the script will not be allowed.

2. Offerors shall perform the demonstration virtually. The Government will set up a Microsoft Teams meeting. The offeror is expected to be able to connect to the meeting using their own software, hardware, and internet connection for the demonstration. The offeror shall not require federal employees to download software onto Government-owned computers. The offeror shall have no more than five (5) representatives from their company in attendance and shall provide the names to the Contracting Officer during time of scheduling.

3. There will be no discussions between the offeror and the Government during the course of the demonstration. Only clarification questions on what is being demonstrated are allowable from the Government.

4. The Government will record the two (2) hour demonstration on Microsoft Teams. By participating in the live demonstration, the offeror consents to being recorded during the demonstration.

5. If an offeror’s commercial-off-the-shelf (COTS) solution cannot demonstrate a function at time of demonstration because it requires customization, workflow configuration, modification, etc., the offeror must describe in detail at the demonstration to the evaluation panel how and when that function will be provided, by contract award or within 24 months of contract award. The technical demonstration will assist in the evaluation and validation of the offeror’s software solution capabilities. The demonstration should clearly show that the offeror can execute the requirements in the table or that their solution is easily modifiable to execute these functions.

Scenarios for Demonstration:

The offeror shall demonstrate their solution’s ability to perform the eighteen (18) items listed below:

FEATURES

1. Load Master Wheel Records: The offeror shall demonstrate their solution to facilitate the seamless importation of potential juror data from various sources such as each court’s current database. It includes functionalities for data mapping, transformation, validation, and deduplication to ensure the accuracy and integrity of imported records. Additionally, the feature incorporates error handling, audit trail logging, and security measures to maintain data quality, compliance, and confidentiality throughout the importing process.

Refer to Attachment 16: Wheel Loading Functions for further information.

2. Qualify Jurors: The offeror shall demonstrate their solution to print a qualified list of jurors, count the number of qualified members in a pool, generate a wheel status reports, and show how court personnel can edit a juror’s record. For more information on qualifying jurors, refer to the “Qualify” section of Attachment 6: Pool Functions.

3. Create a Pool: The offeror shall demonstrate how their solution will enable court personnel to create a new pool, add members to an existing pool, reassign pool members, transfer pool members, and other actions based on the requirements outlined in “Pool” section of Attachment 6: Pool Functions.

4. Respond/Summon Jurors: The offeror shall demonstrate how their solution enables court personnel to summon jurors.

5. Create Events: The offeror shall demonstrate how their solution enables court personnel to create events as outlined in the Event subsection of the “Panel Functions” section in Attachment 7: Panel Functions.

6. Create Strike Lists: The offeror shall demonstrate how their solution creates strike lists, the process of disqualifying and/or excusing a juror as outlined in the “Online Public Access Juror Management” section of Attachment 6: Pool Functions.

7. Pay Jurors: The offeror shall demonstrate how their solution creates a payment file/invoice of juror payments to be received by an external financial system as outlined in the “Pay Attendance Records” and “Pay Event/Jury” subsections of the Attendance section of Attachment 8: Attendance Functions.

8. Create Lists and Reports: The offeror shall demonstrate how their solution creates at least five different reports which will be chosen at random by the Government during the demonstration. These will be chosen from the “Reports” sections in Attachment 6: Pool Functions, Attachment 7: Panel Functions, and Attachment 8: Attendance Functions.

OPERATIONAL PROGRAM FEATURES

1. Text to Background Contrast: The offeror shall demonstrate how their solution encompasses the requirement for text elements displayed within the user interface to maintain sufficient contrast against background colors, ensuring readability and accessibility for end users with visual impairments. The offeror's solution shall include adjustable contrast settings or predefined color schemes to accommodate various user preferences and comply with accessibility standards such as Web Content Accessibility Guidelines (WCAG). Additionally, the solution should undergo rigorous testing before the demonstration to verify compliance with contrast ratio requirements and ensure optimal usability across different display devices and environmental conditions. For further information, refer to the “Accessibility” subsection of the “System Usability” section in Attachment 14: General System Functions.

2. Functionality Requirements for Accessing and Performing Tasks: The offeror shall demonstrate the number of clicks required to access specific features and complete essential tasks within their solution’s interface. The demonstration should highlight streamlined navigation and user-friendly workflows, aiming to minimize the number of clicks necessary for users to accomplish their intended actions, thereby enhancing overall usability and productivity. For further information, refer to the “Navigation” subsection of the “System Usability” section in Attachment 14: General System Functions.

3. Minimal Use of Flash and Add-Ons: The offeror shall demonstrate their solution to incorporate functionality that minimizes the use of Flash technology and add-ons, ensuring compatibility with modern web standards and accessibility guidelines. This includes implementing alternative solutions for interactive elements and multimedia content for enhanced performance, security, and cross-platform compatibility. For further information, refer to the “Accessibility” subsection of the “System Usability” section in Attachment 14: General System Functions.

4. Custom Not Found/404 Page Functionality: The offeror shall demonstrate that their solution provides a mechanism that dynamically generates user-friendly error messages and redirects users to a designated error page when a requested resource is not found. The feature should include customizable error messages and branding options to maintain consistency with the application's overall look and feel. Additionally, the solution should ensure proper handling of HTTP 404 errors, including logging and tracking for analytics purposes, to enhance user experience and facilitate troubleshooting. For further information, refer to the “Navigation” subsection of the “System Usability” section in

5. Main Navigation Clarity and Usability: The offeror shall demonstrate that their solution’s main navigation is identifiable, clear, and concise. This includes implementing intuitive navigation elements that guide users to key functionalities and content areas within the solution. The main navigation should be easily recognizable, featuring clear labels and logical grouping of menu items to enhance user understanding and facilitate efficient navigation throughout the application. Additionally, the navigation design should prioritize usability and accessibility considerations to accommodate users with varying levels of technical expertise and ensure a seamless user experience across different devices and screen sizes. For further information, refer to the “Navigation” subsection of the “System Usability” section in Attachment 14: General System Functions.

6. Easy Access Help: The offeror shall demonstrate that their solution provides users with intuitive access to comprehensive help resources directly within the solution’s interface.

This includes implementing context-sensitive help options, tooltips, and in-app tutorials to assist users in understanding product features, navigating the interface, and resolving common issues efficiently. Additionally, the solution should support multiple formats such as text, images, videos, and interactive guides to accommodate diverse user preferences and learning styles, ultimately enhancing user experience and product usability. For further information, refer to the “Content” subsection of the “System Usability” section in Attachment 14: General System Functions.

7. Menu Navigation Structure: The offeror shall demonstrate that their solution comprises of an intuitive navigation experience for users through a logical and straight-forward menu structure. This includes organizing menu items in a hierarchical manner that aligns with user expectations and workflow, providing clear and descriptive labels for menu options, and minimizing unnecessary complexity to facilitate easy access to key functionalities. Additionally, the menu structure should support efficient navigation across different modules or sections of solution, enabling users to quickly locate and access relevant features and information while enhancing overall usability and user satisfaction. For further information, refer to the “Navigation” subsection of the “System Usability” section in Attachment 14: General System Functions.

8. Headings, Titles, and Labels: The offeror shall demonstrate their solution has clear and easily understandable headings, titles, and labels. This includes employing consistent terminology, logical organization of information, and intuitive placement of navigational elements to enhance user experience and facilitate efficient usage of the solution. For further information, refer to the “Content” subsection of the “System Usability” section in Attachment 14: General System Functions.

9. Enhanced Vertical Scrolling Capability: The offeror shall demonstrate that their solution maximizes vertical scrolling functionality by implementing a smooth and fluid scrolling experience that allows users to navigate through large amounts of content effortlessly. This should include features such as inertia scrolling, where the scrolling speed gradually decreases after the user lifts their finger or releases the scroll wheel, and support for touch gestures such as swipe scrolling and pinch-to-zoom for zooming in and out of content. Additionally, the solution should optimize performance to ensure smooth scrolling even when dealing with complex or graphics-heavy content. For further information, refer to the “Navigation” subsection of the “System Usability” section in

10. Configurable Drop-Down List Functionality: The offeror shall demonstrate that their solution implements a configurable drop-down list feature for entering fields where possible. This functionality should allow users to customize and populate the drop-down options based on their specific needs and preferences. Users should be able to easily add, edit, or remove options from the drop-down list, providing flexibility and adaptability to different use cases. Additionally, the solution should support dynamic updating of the drop-down options based on changes in the underlying data or system configurations, ensuring accuracy and relevance in field selection. For further information, refer to the “Content” subsection of the “System Usability” section in Attachment 14: General System Functions.