Exhibit_A.3_-_JMS_Technical_Requirements_Form_25-P-147JRDL.doc

DOC document 84 KB Posted

Attached to
Jail Management System (JMS) State and local contract opportunity
Solicitation number
25-P-147JRD
Issued by
Volusia County, Florida

About this file

This is a Technical Requirements Form (Exhibit A.3) for Volusia County, Florida's Jail Management System (JMS) procurement (RFP #25-P-147JRD). The form establishes comprehensive technical specifications that bidders must address in their proposals, requiring detailed descriptions of system capabilities rather than generic compliance statements. Contractors must respond to 25 technical requirement items covering infrastructure compatibility, security procedures, desktop specifications, network requirements, software components, printing solutions, reporting tools, documentation, service level agreements, performance benchmarks, system downtime, redundancy and failover capabilities, data transmission security, disaster recovery, and public records compliance. For contractors proposing hosted solutions, an additional requirement addresses security certifications, disaster recovery planning, security incident reporting, and detailed hosting facility specifications including single or multi-tenant architecture. The proposal submission deadline is October 9, 2025, with a pre-proposal meeting scheduled for September 5, 2025, and written questions due by September 25, 2025. The contract will be awarded for an initial five-year term with two optional three-year renewal periods, with implementation targeted for completion by May 25, 2026.

The form requires bidders to identify all exceptions to Volusia County's technical infrastructure and computing security standards, justify deviations from desktop minimum specifications, and describe any additional network hardware or software that would require county investment. Contractors must demonstrate current customer references from facilities with at least 800 beds, preferably in Florida, with minimum five years of operational experience. The procurement does not specify set-asides for disadvantaged enterprises. Bidders will be evaluated across firm qualifications (20%), price schedules (10%), software capabilities (25%), project understanding (15%), technology (20%), and maintenance and warranty (10%), with the system required to support 300 concurrent users and 600 named users while integrating with 22 existing interfaces across multiple third-party platforms including Appriss, Aramark, CorEMR, and IC Solutions.

View the file

Other files for this state and local contract opportunity

Other files attached to Jail Management System (JMS), newest first.
File Type Posted
Jail_Management_System_(JMS)_(Addendum_#5_Revision).pdf PDF
Jail_Management_System_(JMS)_(Addendum_#5_Revision).pdf PDF
Exhibit_I_-_Sample_Agreement_-_version_2.pdf PDF
Exhibit_A.10_Version2_-_JMS_Exchanges_25-P-147JRD.pdf PDF
Exhibit_A.10_Version2_-_JMS_Exchanges_25-P-147JRD.pdf PDF
Exhibit_A.9_Version2_-_JMS_Interfaces_25-P-147JRD.pdf PDF
Exhibit_A.9_Version2_-_JMS_Interfaces_25-P-147JRD.pdf PDF
Exhibit_A.5_Version2_-_JMS_Interfaces_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.5_Version2_-_JMS_Interfaces_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_I_-_Sample_Agreement.pdf PDF
Exhibit_E_-_Business_Associate_Agreement_DRAFT_25-P-147JRD.pdf PDF
Exhibit_F_-_County_Computing_Security_Procedures_25-P-147JRD.pdf PDF
Exhibit_D_-_Technology_Systems_Design_and_Installation_Guidelines_(Division_27)_25-P-147JRD.pdf PDF
Exhibit_G_-_CJIS_Security_Policy_v6-0_20241227.pdf PDF
Exhibit_H_-_Acceptance_Form_25-P-147JRD.pdf PDF
Exhibit_E_-_Business_Associate_Agreement_DRAFT_25-P-147JRD.pdf PDF
Exhibit_H_-_Acceptance_Form_25-P-147JRD.pdf PDF
Exhibit_H_-_Acceptance_Form_25-P-147JRD.pdf PDF
Exhibit_B_-_JMS_Price_Schedule.xls XLS spreadsheet
Exhibit_G_-_CJIS_Security_Policy_v6-0_20241227.pdf PDF
Exhibit_B_-_JMS_Price_Schedule.xls XLS spreadsheet
Exhibit_C_-_Technical_Infrastructure_Standards_25-P-147JRD.pdf PDF
Exhibit_E_-_Business_Associate_Agreement_DRAFT_25-P-147JRD.pdf PDF
Exhibit_F_-_County_Computing_Security_Procedures_25-P-147JRD.pdf PDF
Exhibit_D_-_Technology_Systems_Design_and_Installation_Guidelines_(Division_27)_25-P-147JRD.pdf PDF
Exhibit_A_-_JMS_Scope_of_Work_25-P-147JRD.pdf PDF
Exhibit_A_-_JMS_Scope_of_Work_25-P-147JRD.pdf PDF
Exhibit_A_-_JMS_Scope_of_Work_25-P-147JRD.pdf PDF
Exhibit_A.2_-_JMS_Technical_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.2_-_JMS_Technical_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.2_-_JMS_Technical_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.12_-_JMS_Reports_and_Extracts_redacted.pdf PDF
Exhibit_A.11_-_JMS_Third_Party_Software_25-P-147JRD.pdf PDF
Exhibit_A.8_-_JMS_Reports_and_Extracts_Requirements_Matrix.xlsx XLSX spreadsheet
Exhibit_A.8_-_JMS_Reports_and_Extracts_Requirements_Matrix.xlsx XLSX spreadsheet
Exhibit_A.11_-_JMS_Third_Party_Software_25-P-147JRD.pdf PDF
Exhibit_A.11_-_JMS_Third_Party_Software_25-P-147JRD.pdf PDF
Exhibit_A.9_-_JMS_Interfaces_25-P-147JRD.pdf PDF
Exhibit_A.1_-_JMS_Functional_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.5_-_JMS_Interfaces_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.6_-_JMS_Exchanges_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.4_-_JMS_Server_Environment_Worksheet_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.7_-_JMS_Third_Party_Software_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.3_-_JMS_Technical_Requirements_Form_25-P-147JRDL.doc DOC document
Exhibit_A.7_-_JMS_Third_Party_Software_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.3_-_JMS_Technical_Requirements_Form_25-P-147JRDL.doc DOC document
Exhibit_A.1_-_JMS_Functional_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.4_-_JMS_Server_Environment_Worksheet_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.7_-_JMS_Third_Party_Software_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Exhibit_A.1_-_JMS_Functional_Requirements_Matrix_25-P-147JRD.xlsx XLSX spreadsheet
Show all 50

Jail Management System (JMS) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Exhibit A.3

Technical Requirements Form

25-P-147JRD

The Contractor shall complete this Exhibit.

Provide complete responses and a full description of capabilities to the technical requirements listed below. Do not provide one word responses such as “provided”, “comply”, or “see attached sales documentation”. If referencing other documentation, provide a description and clearly label the attachment in response to the item number. Attachments shall be included after this form in the order of the items. Valid attachment types are service level agreements, equipment diagrams, audits, and other requested documentation.

Contractor Hosted responses:

The application shall be hosted on equipment provided, housed, and maintained by the Contractor. The Contractor provides operational support including but not limited to: application monitoring, hardware monitoring, hardware repair, management of backups, loading tapes, electrical, and HVAC. The Contractor is responsible for database tuning, patches, diagnosis, recovery, and version upgrades as needed. The Contractor works directly with on application modifications, customization, configuration, and how-to questions.

County housed server responses:

The County shall house the application on County provided servers and hardware that meets or exceeds the Contractor’s hardware & software warranty. The County provides the server operational support limited to hardware monitoring, hardware repair, management of backups, loading tapes, electrical, and HVAC. Contractor is responsible for database tuning, patches, diagnosis, recovery, and version upgrades as needed. Contractor works directly with the County on application modifications, customization, configuration, and how-to questions.

Technical Requirement
Description
1.
Describe any incompatibility with the County’s technical infrastructure as listed in Technical Infrastructure Standards Exhibit. Contractors shall justify any exceptions to County standards.
2.
Describe any issues complying with the County’s Computing Security Procedure described in County’s Computing Security Procedure Exhibit.
3.
Describe and justify any exceptions to County standard desktop/laptop minimum specifications as listed in Technical Infrastructure Standards Exhibit.
4.
Describe any additional network expansion, hardware or software required to implement the proposed solution that would be the responsibility of the County.

Note: Any TCP/IP networking devices (switches, routers, firewalls, etc) located on County premises must use addressing supplied by and be under the direct control and management of Volusia County Network Services.

5.
Provide the client desktop minimum computer requirements (memory, hard drive, graphics, operating system, and peripherals).
6.
Describe any software or executables that shall reside on the desktop and the ability to install and update the software or executables in an automated function.
7.
Describe how printing is handled and addressed on stand alone and networked printers. Contractors shall also describe how this shall be handled if multiple forms are required to be printed on a single printer.
8.
Describe any additional hardware equipment here such as scanners, printers, etc.
9.
Describe solution for query and reporting tool. Include a description of how application security cascades to the reporting tool.
10.
Describe and list all available documentation. Include in the description if it is available on-line, if it is searchable, and if it is customizable.
11.
Describe and include available service level agreements that are offered.
12.
Provide performance benchmarks from current customers. Benchmarks should include response times and system availability.
13.
Describe all application required downtime. For example a batch process that prevents the user from accessing or updating the system. Describe processes, frequency, and duration.
14.
Describe how Contractor handles redundancy to keep the application available in case of hardware failure. For example clustered servers, virtual servers and /or hot failover solutions.

Is service automatically or manually failed over?

What is expected recovery time?

15.
Describe how the data is secured during transmission i.e. SSL/TLS, VPN protocols, proprietary techniques or some other system.
16.
Describe the procedure that shall be used by the application user when Internet or network access is down or if the system is down unexpectedly.
17.
Describe the availability of test environments that shall support the ability to test processes prior to production runs and the availability of training environments that shall support on-demand training. Explain the procedure for requesting or performing database refreshes to support these environments.
18.
Describe solutions that are in place to support the County in obtaining data for migration/conversion to a different application or solution provider in the future if necessary due to default of Contractor or the County electing to move to another provider at end of the Contract.
19.
Describe and provide documentation demonstrating that the Contractor’s security procedures and policies for its employees and subcontractors accessing client data meet industry standard best practices, including PCI standards.
20.
Describe the procedures that the Contractor will follow to comply with Florida Sunshine laws and public records requests.
21.
Describe all licenses not included for utilizing the system, such as but not limited to report writers, databases, operating systems and software tools.

Contractors providing a Contractor Hosted solution to complete the questions below

22.
Provide copies of security certification or security audits demonstrating security compliance/certification.
23.
Describe disaster recovery plan/continuity of operations in a situation that disables the primary hosting site. What is the expected period of time it will take for the hosting service to be operational? If a secondary backup site is used to bring the service online what is Contractor’s commitment to re-establishing a primary site.
24.
Describe the response and reports to County of any successful server intrusions, corruption, hacks, denial of service attacks or other security events affecting the County.
25.
State if the model is a Single-Tenant or Multi-Tenant hosting model. Fully describe the physical and logical layout of the hosting facility include location, facility description, staffing, electrical, building hardening, servers, data storage, backup equipment and other operational information. If the Contractor does not own and operate the primary or secondary hosting site(s), then provide all required documentation and references for this subcontracted service in addition to the description above.

Exhibit A.3 - Technical Requirements Form.doc

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