Attachment 22 - Web-Based JMS Architecture.pdf

PDF 160 KB Posted

Attached to
Web-based Jury Management System (JMS)
Solicitation number
USCA24R0030
Issued by

About this file

This document is an attachment that provides an overview of the web-based architecture for the current Jury Management System (JMS) environment. It describes the server hardware, operating systems, database, web server, and application requirements. The key details are:

The current JMS environment runs on VMware virtual servers using Red Hat Enterprise Linux (RHEL) 7.x for the application server and Informix 12 on Linux 8.x or greater for the database. The application must be web-based and cloud-native, with a single installation accessed by multiple users over HTTPS. The government recommends commonly available web servers that utilize web standards, and the application must be architected to handle these requirements. Connectivity to the government network will be provided through the Axway API Gateway product.

The related federal contract opportunity is a solicitation for a web-based Jury Management System (JMS) solution to assist the courts with juror selection, management, tracking, financial, and statistical functions. This is an Indefinite Delivery, Indefinite Quantity (IDIQ) contract, with a draft Task Order 0001 attached. Responses are due by 12:00 P.M. ET on May 31, 2024, and questions are due by 12:00 P.M. ET on May 10, 2024.

View the file

Other files

File Type Posted
USCA24R0030 Amendment 0004.pdf PDF
USCA24R0030 Amendment 0003.pdf PDF
USCA24R0030 Amendment 0002.pdf PDF
Attachment 4 Task Order 0001_rev1.pdf PDF
Attachment 8 - Attendance Functions_rev1.pdf PDF
Attachment 24 - Deliverables_rev1.pdf PDF
Questions and Answers Spreadsheet USCA24R0030 05222024.xlsx XLSX spreadsheet
Attachment 19 JIFMS-JMS Web Service Interface Requirements Specifications REVISED.pdf PDF
Amendment 0001 USCA24R0030.pdf PDF
JMS RFP USCA24R0030 dated 4.29.2024.pdf PDF
Attachment 4 - Task Order 0001.pdf PDF
Attachment 8 - Attendance Functions.pdf PDF
Attachment 11 - Interactive Voice Response System Functions.pdf PDF
Attachment 15 - Customization Functions.pdf PDF
Attachment 16 - Wheel Loading Functions.pdf PDF
Attachment 25(b) - Sensitive Information Nondisclosure Agreement.pdf PDF
Attachment 30 - EOC-SOP-SBO-20-101-Communications.pdf PDF
Attachment 9 - Scanning Technology Functions.pdf PDF
Attachment 13 - Glossary of Terms.pdf PDF
Attachment 17 - Wheel Deletion Functions.pdf PDF
Attachment 23(a) - Judiciary Information Security Framework (JISF).pdf PDF
Attachment 25(a) - Nondisclosure Agreement.pdf PDF
Attachment 26 - Section 508 Requirements.pdf PDF
Attachment 29 - EOC-NSD-SOP-SBO-22-103-Request-Fulfillment.pdf PDF
Attachment 7 - Panel Functions.pdf PDF
Attachment 31 - EOC-SOP-SBO-22-102-Problem Management.pdf PDF
Attachment 2 - Demonstration Script.pdf PDF
Attachment 3 - Past Performance Questionnaire.pdf PDF
Attachment 14 - General System Functions.pdf PDF
Attachment 18 - Statistical Reporting Functions.pdf PDF
Attachment 19 - JIFMS-JMS Web Service Interface Requirements Specifications.pdf PDF
Attachment 23(c) - Guide to Implementing the Judiciary Information Security Framework JISF.pdf PDF
Attachment 24 - Deliverables.pdf PDF
Attachment 32 - EOC-SOP-SBO-22-105-Knowledge-Management.pdf PDF
Attachment 1 - Web-Based JMS Price Tables.xlsx XLSX spreadsheet
Attachment 5 - Web-Based JMS Traceability Matrix.xlsx XLSX spreadsheet
Attachment 6 - Pool Functions.pdf PDF
Attachment 10 - Online Public Access Juror Management Functions.pdf PDF
Attachment 12 - Proximity Technology Functions.pdf PDF
Attachment 20 - Appear Speech Overview.pdf PDF
Attachment 21 - Current Forms Used by District Courts.pdf PDF
Attachment 27 - EOC Service Desk and Support.pdf PDF
Attachment 28 - EOC-NSD-SOP-SBO-24-102-Incident-Management.pdf PDF
Attachment 33 - Root Cause Analysis Template.pdf PDF
Attachment 34 - OCS Bulletin and ERC Templates.pdf PDF
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

Attachment 22 1

Web-Based JMS Architecture

The architecture overview below is a high-level representation of the environment the current Jury Management System (JMS) resides on.

Server Hardware:

VMWare is our current virtualized server. All server operating systems will be loaded on VMWare virtual servers.

Application Server:

RHEL 7.x is our current operating system. The Government (AO) supports the following application servers:

• Red Hat Enterprise Linux version 8.x or greater

• Windows Server 2019 or greater

Database Server:

The current JMS environment supports Informix 12 on Linux version 8.x or greater.

The Contractor has the option to propose cloud-native databases. The Contractor shall notify the Government if this necessitates the need to procure different licenses to migrate to the cloud.

Webserver:

Apache/Tomcat is the current web server. The Government (AO) recommends any commonly available web server that utilizes web standards.

Application:

No recommendations will be given on the application. However, the application must be architected in such a way to handle the following:

1. The application must be web-based and cloud-native (i.e., no software installed on computer workstations).

2. The application must offer a single installation with access by multiple users.

Clients:

All client connectivity shall be HTTPS. This will include internal and external users of the application. No application software should be loaded on the client, except to support specialized peripherals like document scanners.

Attachment 22 2

Firewall Connectivity:

Axway’s API Gateway product will be used for connectivity by the application from the DMZ and Internet networks to the Government (AO) Data Communications Network (DCN).

Potential Architecture Diagram:

File details come from the government source that posted it. Updated .