Attachment B _ DIH Cost Proposal Form.xlsx

XLSX spreadsheet 555 KB Posted Jun 24, 2026

Attached to: RFP #26-24 Integrated Justice Information and Management System Modernization
Solicitation number: PE-63100-NONST-2026-000000096
Issued by: Clayton County, Georgia

About this file

Written by GovTribe AI · Jul 1, 2026

This is a Data Integration Hub (DIH) Cost Proposal Form for Clayton County, Georgia's RFP #26-24 Integrated Justice Information and Management System Modernization. The document establishes the cost proposal framework for vendors responding to the county's request to implement a comprehensive data integration solution supporting multiple justice system modules, including Use of Force, Medical and Behavioral Health, Searches and Shakedowns, Escapes, Executive Management, Interfaces, and PREA (Prison Rape Elimination Act) functionalities. The DIH implementation is structured in four phases aligned with Jail Management System (JMS) and Case Management System (CMS) rollout timelines, with Phase 1 being the current scope of evaluation. The proposal requires vendors to provide firm fixed pricing across multiple cost categories including software licensing, cloud infrastructure, integration development, training, professional services, support and maintenance, and optional modules.

The cost proposal structure requires vendors to itemize pricing for seven core cost categories (C1 through C7) and three optional categories (O1 through O3). Core costs include software licensing or subscription fees, cloud infrastructure expenses, integration development pricing organized by specific systems (such as Palatine, GCIC, CPU8, RMS, Tracker, JCATS, and approximately 30 additional systems), training and knowledge transfer, professional services for DIH implementation across phases, and support and maintenance services. Professional services are detailed across five implementation tasks in Phase 1 (Discovery, Data Mapping Assessment, DIH Production Build, DIH Initial Integration, and DIH Roadmap Development) with additional costs for Phases 2 through 4 also requested for planning purposes. Vendors must include comprehensive cost assumptions identifying variables such as user counts and unit rates, with the county assuming development will occur in Years 1-3 and that support and maintenance costs will not be necessary until post-implementation in Years 4-5. The document explicitly restricts evaluation scope to Phase 1 costs only, though vendors must complete pricing information for all phases.

View the file

Other files

File	Type	Posted
Exhibit A _ Data and Infrastructure.pdf	PDF	Jun 24, 2026
Exhibit G _ JMS Project Gates and Deliverable.pdf	PDF	Jun 24, 2026
Attachment B _ JMS Cost Proposal Form.xlsx	XLSX spreadsheet	Jun 24, 2026
Exhibit C _ JMS On_Going Support and Training.pdf	PDF	Jun 24, 2026
Exhibit F _ JMS Project Management.pdf	PDF	Jun 24, 2026
Exhibit E _ Data Integration Hub Requirements.xlsx	XLSX spreadsheet	Jun 24, 2026
Exhibit D _ JMS Functional Requirements.xlsx	XLSX spreadsheet	Jun 24, 2026
26_24 Integrated Justice Information and Mana.pdf	PDF	Jun 24, 2026
Exhibit B _ JMS Technical Requirements.xlsx	XLSX spreadsheet	Jun 24, 2026

On GovTribe

Work with this file

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

13.0 Use of Force

Functional Requirements: Use of Force

	Req #	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Vendor Response
	UF-01	The proposed solution must provide the ability for the receiving officer to enter information from paperwork received from agency.
	UF-02	The proposed solution must provide the ability to capture and/or view information. This should include but not be limited to:

a. Incident Reports (see Incident)

b. Medical Review (See Medical)

c. Film/ Photographs/ Video UF-03 The proposed solution must provide the ability to document that PDP requirements for Use of Force were met. This information should include but not be limited to:

a. Security Response

b. Medical Response

c. Mandatory documentation

UF-04	The proposed solution must have the ability to link the Use of Force report with any other related report (Disciplinary, Incident, etc.).
UF-05	The proposed solution must have the ability to document the use of chemical agents and other means. This information should include but not be limited to:

a. Approvals

b. Authorizations

c. Medical Follow up

UF-06	The proposed solution must provide the ability to query Use of Force data, including the use of chemical agents and other types.
UF-07	The proposed solution must provide the ability to automate the process of issuing equipment.

&P &"Calibri,Regular"&11&K000000&A

17.0 Medical

Functional Requirements: Medical, Behavioral Health

	Req #	New ID	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Notes
	MED-01		The proposed solution must have the ability to interface with the medical system that the PDP has implemented. This is the eClinicalWorks Electronic Medical Record.
	MED-02		The proposed solution must have the ability to provide a bi-directional interface with the PDP medical system.
	MED-03		The proposed solution will have the capability to support an interface from the PDP medical system. The information that will be sent from the medical system will include but not limited to:

a. Medical restrictions,

b. Special diets,

c. Watches MED-04 The proposed solution will have the capability to send information to the medical system. This information will include but not be limited to:

a. Intake information

b. Housing information

c. Release information

MED-05	The proposed solution must provide the ability to notify users that a prior medical alert exists for an inmate that is a repeat inmate.
MED-06	The proposed solution must provide for a questionnaire. This questionnaire should be customizable so that it can be used for different purposes.
MED-07	The proposed solution must provide the ability for these questionnaires to be modified without the need for programming.
MED-08	The proposed solution must provide the ability for staff with the appropriate security levels to view medical restrictions, watches and medical orders placed on an inmate.
MED-09	The proposed solution must provide the ability for staff to view KOPs for inmates to include medically approved equipment (i.e. crutches, braces, wheelchairs).
MED-10	The proposed solution must provide the ability to identify inmates with medical alerts as high priority in the intake medical screening queue.
MED-11	The proposed solution must provide the ability to display special medical notices on all inmate information screens to alert users to these special conditions.
MED-12	The proposed solution must provide the ability to enable the medical staff to view the inmate information. This should include but not be limited to:

a. Housing history

b. Current location

c. Reports such as inmates with specific medical alerts

MED-13	The proposed solution must provide the ability to ingest the medical appointment information and update the inmate’s schedule .
MED-14	The proposed solution must provide the ability to create a Behavioral Health Referral form with at least three levels: Emergency (4hrs), Urgent (24hrs) and Routine (5 days) as well as interface with the eCW system.
MED-15	The proposed solution must provide the ability to search Behavioral Health Referrals by inmate name, PP#, and date range.
MED-16	The proposed solution must provide the ability to track and report on the status of Behavioral Health Referrals.
MED-17	The proposed solution must provide the ability to verify that Behavioral Health Referrals have been completed prior to the release of the inmate.
MED-18	The proposed solution should restrict the assignment of KOP medications if the inmate has a “Seriously Mentally Ill” designation. It should enable an override but should capture the name of the person who is doing the override along with the reason for the override.
MED-19	The proposed solution must provide the ability to store pictures related to inmate injuries.

&P &"Calibri,Regular"&11&K000000&A

19.0 Searches_Shakedowns

Functional Requirements: Searches and Shakedowns

	Req #	New ID	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Notes
	ISS-01		The proposed solution must provide the ability to define and document processes related to required types of Searches in accordance with the PDP policies and procedures.
	ISS-02		The proposed solution must provide the ability to document type of search:

a. Inmate/ Detainee

b. Cell

c. Common Area ISS-03 The proposed solution must provide the ability to determine and advise the type of Search allowed by policy. This will include but not be limited to the following types:

a. Strip” Search

(i) Booking/Intake

(ii) Exclusions

(iii) Female

b. “Pat” Search

(i) “Safe keep” status

(ii) “Under Suspicion” Searches

c. General – required monthly

ISS-04	The proposed solution must provide the ability for the facility to manage cell searches by creating a random list by shift of cells to be searched based on policy.
ISS-05	The proposed solution must recommend additional searches that need to be conducted based on the results of the current searches.
ISS-06	The solution must provide the ability to enable an authorized user to add additional common areas to the search schedule, if required.
ISS-07	The proposed solution must support the ability to reconcile and ensure that all cells have been searched based on PDP policies and procedures in a given timeframe.
ISS-08	The proposed solution must support the documentation of the results of the cell searches. This should include the list of the officers that conducted the search as well as supervisor. The information must include but not be limited to:

a. Cell Number

b. Officer Name

c. Results

ISS-09	The proposed solution must provide the ability for the facility to manage common area searches by creating a random list by shift of common areas to be searched based on policy.
ISS-10	The solution must provide the ability to enable an authorized user to add additional common areas to the search schedule, if required.
ISS-11	The proposed solution must document any contraband that is found during the cell and common area searches.
ISS-12	The proposed solution must provide the ability to dispose off the contraband that is found.
ISS-13	The proposed solution must provide the ability to initiative an incident report based on the results of the search.
ISS-14	The proposed solution must provide the ability to initiate a misconduct (disciplinary) report based on the results of search.
ISS-15	The proposed solution must have the ability to enter search results by individual cells/locations or by group of cells/locations. This is especially useful when nothing is found in any cell in an entire housing unit.
ISS-16	The proposed solution must have the ability to document a search and create a report based on Housing unit, cell, inmate name, or common area.
ISS-17	The proposed solution must provide the ability to generate reports that are relevant to searches based on user specified time periods (i.e. 30 days, Daily, Yearly).

&P &"Calibri,Regular"&11&K000000&A

24.0 Escapes

Functional Requirements: Escapes and Walkaways

	Req #	New ID	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Notes
	ESC-01	ES 01	The proposed solution must provide the ability to document an inmates security risk as it pertains to escapes. It should track inmates whom are suspected of planning or assisting others in an escape attempt, an inmate’s history of escapes, and the seriousness of the escape(s). The solution must also provide alerts which would indicate if an inmate is currently an escape risk and increased supervision is required.
	ESC-02	ES 02	The proposed solution must provide the ability to generate Alerts as a way off flagging inmates as “escape risks”.
	ESC-03	ES 03	The proposed solution must provide the ability to provide inmate related demographic, housing and visitor information and to generate notification and routing alerts to various departments when there is an active event (escape, riot, fire, etc.) in progress per the agency’s documented Emergency Plan.
	ESC-04	ES 04	The proposed solution must be able to generate an “Escape Package” that can be transmitted electronically. This package should contain a intake sheet w/ photo, and all records/information related to visits, mail, and phone.
	ESC-05	ES 05	The proposed solution must provide the ability to document an inmate’s status as a fugitive from the PDP or from another agency (local, other county, state, or federal).
	ESC-06	ES 06	The proposed solution must provide the ability for the fugitive staff to search inmate records.
	ESC-07	ES 07	The proposed solution must provide the ability to provide to the fugitive staff information from the courts on new warrants and warrant status changes in a queue to initiate action and track warrant notes.
	ESC-08	ES 08	The proposed solution must provide the ability to electronically capture, store, view, and remove warrant and detainer information.
	ESC-09	ES 09	The proposed solution must provide the ability to verify that a warrant or detainer has been physically removed from the file and that the court has changed the status of the warrant or detainer from the OMS when that warrant has been served.
	ESC-10	ES 10	The proposed solution must provide the ability to print and transmit electronically warrant and detainer information.
	ESC-11	ES 11	The proposed solutions must provide the ability to record and view incoming extradition information.
	ESC-12	ES 12	The proposed solutions must provide the ability to record and view outgoing extradition information.

&P &"Calibri,Regular"&11&K000000&A

25.0 Executive Management

Functional Requirements: Executive Management Support

	Req #	New ID	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Notes
	EMS-01	EM 01	The proposed solution must provide the ability to support the various levels of management at PDP by providing them dashboard views of the operations of the PDP.
	EMS-02		The proposed solution must enable the dashboard view to be personalized to a certain degree. For example, a dashboard view for a Warden of a PDP facility may be different from that of the Dy. Commissioner or Commissioner.
	EMS-03		The proposed solution should support the ability for each Warden or other authorized users to view the key activities in their facility over the past 24 hours. This would include information such as but not limited to:

a. Number of new admissions

b. Number of incidents

c. Number of searches

EMS-04	The proposed solution should have the capability of enabling the view of key activities over the past 24 hours at an enterprise level.
EMS-05	The proposed solution must support the capability of allowing the authorized users of the dashboards to be able to drill down to the specific incident or item to view it in detail.
EMS-06	The proposed solution should support a real time view of the Key Performance Indicators that are identified by PDP.
EMS-07	The proposed solution must provide the ability to analyze data and identify key trends and outliers in any of the KPIs identified above.
EMS-08	The propose solution should support the collection, analysis and display of information to support the Corestar process and Corestar reporting.
EMS-09	The proposed solution must have the ability to support the printing of the Corestar report.

&P &"Calibri,Regular"&11&K000000&A

27.0 Interfaces

Functional Requirements: Interfaces

	Req #	New ID	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Notes
	INF-01		The proposed solution must provide the capability to interface with a number of external entity systems as well as internal systems to exchange data (ingest and push).
	INF-02		As described in the Technical Requirements, it is expected that these interfaces will be a combination of those that support the national information sharing standards such as the National Information Exchange Model (NIEM) as well as the Global Reference Architecture (GRA). as well as those that are already there are past of the proposed solution. All vendors are encouraged to list all the existing interfaces that they have with current systems.
	INF-03		The proposed solution must at a minimum support the interfaces that are listed in Appendix A.
	INF-04		The proposed solution must support the ability to send the Prisoner Packet electronically to the Pennsylvania Department of Correction when an inmate is being sent from PDP to the Pennsylvania Department of Correction.
	INF-05		The proposed solution must have the capability to interface with systems such as the Preliminary Arraignment Systems (PARS) using the NIEM and the GRA standards.
	INF-06		The proposed system must have the capability to interface with multiple web services provided by JNET to obtain addition information required by PDP users. A list of potential web services is provided in Appendix B.
	INF-07		The proposed system must have the capability of interfacing with the CPCMS (Philadelphia Court System) to obtain information including but not limited to:

a. Court Documents

b. Court Schedules These information exchanges should use the NIEM and GRA standards

INF-08	The proposed solution must support the ability of the District Attorneys to receive notifications on specific inmates and allow them to view inmate details when required.
INF-09	The proposed solution must support the ability to send re entry information to the external re-entry providers to support the reintegration of inmates back into the community.
INF-10	The proposed solution must support the capability to interface with bio metric devices include fingerprint systems, photo identification systems.
INF-11	The proposed solution must provide the ability to interface with various Commissary, Food vendor system to exchange data with them.
INF-12	The proposed solution must provide the ability to interface with other PDP systems.
INF-13	The proposed solution must provide information to solutions such as GangNet and have the ability to query information from them.
INF-14	The proposed solution must have the capability of querying local, state and federal databases such as NCIC to look up information on inmates and visitors.

&P &"Calibri,Regular"&11&K000000&A

28.0 PREA

Functional Requirements: PREA

	Req #	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Vendor Response
	PR-01	The proposed solution must support all the PREA requirements based on the policies and procedures of the PDP.
	PR-02	The proposed solution must provide for a PREA Screening questionnaire and create a flag for use in housing/ cell assignment based on the inmate being identified as a:

a. Potential predator

b. Known predator

c. Potential victim

d. Known victim PR-03 The proposed solution must support the notification of the alert created to be sent to the appropriate personnel including but not limited to

- PREA Facility Compliance Manager (Deputy Warden of Administrations at each facility)

- PREA Coordinator, Commissioner

- All Deputy Commissioners,

- Medical Director The information that is sent must include Inmate Name, PID#, Age, Race, Facility, Housing, Census, Perpetrator (Male/Female), Victim (Male/Female)

PR-04	The proposed solution must provide an interface to the medical system to being in the information on the PREA Questionnares that are utilized by the medical department.
PR-05	The proposed solution must support the guidelines defined in the PREA Act as defined by the Bureau of Justice Assistance.

Instructions (WIP)

		RESPONDER COST PROPOSAL
		The County requests Responders offer their “best” solution which will satisfy the requirements set forth in this RFP. Provide a Firm Fixed Price quote for the items listed in the tables below including ALL assumptions and adding rows as necessary:
•	Assumptions (no cost information required)
•	C1 – Software Licensing or Subscription Costs
•	C2 – Cloud Infrastructure Costs
•	C3 – Integration Development Pricing (Per Integration)
•	C4 – Professional Services to Implement Data Integration Hub
•	O1 –Optional Recommended Software / Modules / Add-ons (Material costs only)
•	O2 - Professional Services to Implement Optional Recommended Software/Modules/Add-ons-ons
•	O3 - Other Optional Items

Based on approach to building interfaces, responder is expected to provide cost assumptions as part of their cost proposal. Interfaces are expected to be provided with a modern API(s) through the Data Integration Hub. Please refer to Appendix G – Technical Requirements for additional information. Professional Services for interface work should be included in C2 and any additional costs anticipated in C4 Other Costs.

Instructions

CLAYTON COUNTY

		RESPONDER COST PROPOSAL
		The County requests Responders offer their “best” solution which will satisfy the requirements set forth in this RFP. Provide a Firm Fixed Price quote for the items listed in the tables below including ALL assumptions and adding rows as necessary:
•	Assumptions (no cost information required)
•	C1 – Base System Software or Subcription(Material only)
•	C2 – Cloud Infrastructure Costs

• C3 – Integration Development Pricing

• C4 – Training & Knowledge Transfer

•	C5 – Professional Services to Implement Base System
•	C6 – Support-Maintenance
•	C7 – Other Costs
•	O1 –Optional Recommended Software / Modules / Add-ons (Material costs only)
•	O2 - Professional Services to Implement Optional Recommended Software/Modules/Add-ons-ons
•	O3 - Other Optional Items
		Based on approach to building interfaces, responder is expected to provide cost assumptions as part of their cost proposal. Interfaces are expected to be provided with a modern API(s) through the Data Integration Hub. Please refer to Exhibit E – Data Integration Hub Requirements for additional information. Professional Services for interface work should be included in C2 and any additional costs anticipated in C4 Other Costs.

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

Cost Proposal Summary (WIP)

	Cost Proposal Summary
	Responder Name:
	Note: This is automatically populated.
	#	Component	Price $
	C1	Software Licensing or Subscription Costs
*If vendor is NOT hosting on local install or requesting Clayton County to host, there is not need to respond to C2.	$ - 0
	C2	Cloud Infrastructure Costs	$ - 0
	C3	Integration Development Pricing (Per Integration)	$ - 0
	C4	Training & Knowledge Transfer	$ - 0
	C5	Professional Services to Implement Data Integration Hub
*Only Phase 1 Costs will be Evalauted. Please complete pricing for Phase 2-4 as well.	$ - 0
	C6	Software Support/Maintenance	$ - 0
	C7	Other Associated Costs	$ - 0
		COST PROPOSAL TOTAL	$ - 0
	#	Optional	Price $
	O1	Optional Recommended Software	$ - 0
	O2	Professional Services to Implement Optional Recommended Software	$ - 0
	O3	Other Optional Items	$ - 0

Cost Assumptions

Cost Proposal - All Cost Proposal Assumptions
#	Assumption	Associated Cost Proposal Section(s)

(All, or C1, C2, etc)

1	X numbers of users
2
3
4
5
N*
*Insert as many needed

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C1 - Software or Subscription

Cost Proposal - C1 - Software Licensing or Subscription Costs
#	Unit Type / Unit Rate	Description	Yr 1	Yr 2	Yr 3	Yr 4	Yr 5	Price $	Response Assumptions
1	XX							$ - 0
2	XX							$ - 0
3	XX							$ - 0
4	XX							$ - 0
5	XX							$ - 0
6	XX							$ - 0
C1 Total								$ - 0

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C2 - Cloud Infrastructure Costs

Cost Proposal - C2 - Cloud Infrastructure Costs
#	Unit Type / Unit Rate	Description	Unit Rate	Volume Assumption	Price $	Response Assumptions
1	XX				$ - 0
2	XX				$ - 0
3	XX				$ - 0
4	XX				$ - 0
5	XX				$ - 0
6	XX				$ - 0
C2 Total					$ - 0

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C3 - Integration Development Pr

Cost Proposal - C3 - Integration Development Pricing (Per Integration)

Direction

Frequency

Interface Type

Business Purpose

Data Elements

Modify & Integrate

DIH Scope - JMS

DIH Scope - CMS

LOE (Hours/Points)

Rate (Hourly/Fixed)

Extended Cost

Price $

Response Assumptions

Palatine

One Way Outbound

Real-Time / Event-Driven

REST API / Web Service

Warrant issuance and management; transmits issued warrants from court to law enforcement systems

Warrant ID, Defendant Name, DOB, Charge(s), Issuing Judge, Issue Date, Warrant Status, Case Number

Integrate or Retire

Phase 2

Phase 3

$ - 0

GCIC

One Way Outbound

Real-Time / On-Demand

Web Service (SOAP/REST)

Statewide criminal history lookups; reporting arrest outcomes for each segment (LEA, Prosecution, Judicial)

Name, DOB, SSN/SID, Fingerprint Reference, Criminal History Records, Arrest Outcomes, Charge Codes

Integrate

Phase 2

$ - 0

CPU8 Jail

Bi-Directional

Batch / Near Real-Time

Flat File (CSV/Fixed Width) / Direct DB Connection

Core court and jail case management; source of truth for cases, hearings, dispositions, financials, and bookings

Case Number, Party Information, Charges, Hearing Dates, Dispositions, Financial Transactions, Booking Records, Warrants

Retire

Phase 2

$ - 0

CPU8 Courts

Bi-Directional

Batch / Near Real-Time

Flat File (CSV/Fixed Width) / Direct DB Connection

Core court and jail case management; source of truth for cases, hearings, dispositions, financials, and bookings

Case Number, Party Information, Charges, Hearing Dates, Dispositions, Financial Transactions, Booking Records, Warrants

Retire

Phase 2 - Integrate

Phase 3 - Retire

$ - 0

CPU8 Jury

Bi-Directional

Batch

Flat File / Direct DB Connection

Jury pool management and jury selection coordination within CPU8

Juror Name, Summons Status, Selection Status, Case Number, Jury Pool ID, Attendance Records

Integrate

Phase 3

$ - 0

CPU8 Complaints

One Way Inbound

Real-Time / Batch

Flat File / Direct DB Connection

Intake and management of criminal and civil complaints within CPU8

Complaint Number, Complainant, Defendant, Charges, Filing Date, Case Type, Assigned Judge

Integrate

Phase 3

$ - 0

CPU8 Grand Jury

Bi-Directional

Batch

Flat File / Direct DB Connection

Grand jury case management and indictment processing within CPU8

Grand Jury Case Number, Indictment Status, Charges, Defendant, Grand Juror Records, Hearing Date

Integrate

Phase 3

$ - 0

RMS – Central Square

One Way Inbound

Real-Time / Event-Driven

REST API

Receives incident reports, citations, and arrest reports from Clayton PD for court intake processing

Incident Report Number, Citation Number, Arrest Report, Suspect/Defendant Info, Charges, Officer ID, Incident Date/Time

Integrate

Phase 4

Phase 3

$ - 0

Tracker

Bi-Directional

Real-Time / On-Demand

REST API / Web Service

DA case management; subpoena generation; coordinates with CPU8 for tracking numbers and court orders

Case Number, Tracking Number, Subpoena Records, Court Orders, Party Information, Charges, Case Status

Integrate

Phase 3

$ - 0

JCATS

Bi-Directional

Real-Time / Batch

REST API / Web Service

Juvenile case management including incarceration, community corrections, and case tracking

Juvenile Case Number, Defendant (Minor) Info, Charges, Disposition, Incarceration Status, Community Corrections Records

Integrate

Phase 3

$ - 0

Keefe

Bi-Directional

Real-Time / Batch

REST API / Web Service

Jail commissary management; inmate account transactions synchronized with jail management system

Inmate ID, Account Balance, Transactions, Commissary Orders, Booking Number

Integrate

Point to Point

$ - 0

Tyler eFile Georgia

One Way Inbound

Real-Time / Event-Driven

REST API (ECF/EFM Standard)

Electronic filing of court documents from attorneys and public; replaces paper-based filing

Filing ID, Case Number, Document Type, Filed By, Filing Date/Time, Document Contents, Payment Info, Service Contacts

Integrate

Phase 3

$ - 0

ICS

Bi-Directional

Real-Time / Batch

REST API / Web Service

Inmate communication services (phone, visitation scheduling, tablets); syncs inmate status with jail system

Inmate ID, Booking Number, Call Records, Visitation Schedule, Tablet Usage, Account Balance, Approved Contacts

Integrate

Point to Point

$ - 0

EHR

Bi-Directional

Real-Time / Event-Driven

REST API / HL7 FHIR

Electronic health record management for jail inmates; tracks medical history, prescriptions, and lab results

Inmate ID, Patient Demographics, Medical History, Diagnoses, Prescriptions, Lab Results, Treatment Records

Integrate

Point to Point

$ - 0

Picture Link

Bi-Directional

Real-Time / On-Demand

REST API / SFTP File Transfer

Stores and retrieves inmate mugshots for booking intake and case record association

Inmate ID, Booking Number, Photo Image, Capture Date, Booking Date

Integrate or Retire

Point to Point

$ - 0

Brazos

One Way Inbound

Real-Time / Event-Driven

REST API / Web Service

Mobile data capture for officers in the field; forms-based application feeding incident and arrest data to RMS/court

Officer ID, Incident/Arrest Data, Citation Data, Defendant Info, Geolocation, Capture Timestamp

Integrate

Phase 4

$ - 0

Utility

One Way Inbound

Batch / On-Demand

REST API / SFTP File Transfer

Manages and stores body-worn camera footage for Clayton PD; used for safety, compliance, and evidence

Officer ID, Video File Reference, Capture Date/Time, Incident Number, Device ID

TBD

$ - 0

Axon

One Way Inbound

Batch / On-Demand

REST API / SFTP File Transfer

Storage and management of body-worn and dash cam video evidence for the Sheriff's Office and Jail

Officer/Deputy ID, Video File Reference, Capture Date/Time, Incident Number, Device ID, Case Association

TBD

$ - 0

Jagware

One Way Outbound

Real-Time / Batch

REST API / Web Service

Automated probation management; transmits probation case and supervision data to court systems

Probationer Name, Case Number, Supervision Status, Compliance Records, Payment History, Violation Reports

Integrate

Phase 2

$ - 0

In Court – Catalyst

One Way Outbound

On-Demand / Batch

Flat File / SFTP File Transfer

Realtime transcript creation for court proceedings; produces electronic and printed transcripts

Case Number, Hearing Date, Transcript Text, Reporter ID, Court Room ID, Proceeding Type

Integrate

Phase 3

$ - 0

Ameris

One Way Inbound

Real-Time / Event-Driven

REST API

Online payment processing for court fines, fees, and costs paid by the public

Payment ID, Payer Name, Case Number, Amount, Payment Method, Transaction Date, Payment Status

Integrate/Retire

Phase 3

$ - 0

Quickbooks

One Way Inbound

Batch (Monthly)

Flat File (CSV) / Manual Upload

Month-end financial close for Pre-Trial services; manages revenue and expenditure accounting

Account Code, Transaction Amount, Transaction Date, Description, Period, Vendor/Payee

Integrate

Phase 3

$ - 0

Munis

Bi-Directional

Batch

Flat File (CSV) / REST API

Accounts payable processing; pays court-appointed attorneys; receives payment data from courts

Attorney Name/ID, Case Number, Invoice Amount, Payment Date, Account Code, Approval Status

Integrate

Phase 3

$ - 0

Eagle Biometrics

Bi-Directional

Real-Time / Event-Driven

Web Service / REST API

Livescan fingerprint capture during jail intake; transmits biometric data to GCIC and booking systems

Inmate ID, Booking Number, Fingerprint Data, Biometric Reference ID, Capture Date, Operator ID

Integrate

Phase 2

$ - 0

VINES

One Way Outbound

Real-Time / Event-Driven

REST API / Web Service

Automated victim notification system; notifies registered victims of inmate custody status changes

Inmate ID, Booking Number, Custody Status, Release Date/Time, Victim Contact Info, Notification Timestamp

Integrate

Phase 2

$ - 0

CourtView

One Way Outbound

Real-Time / On-Demand

REST API / Web Service

Public-facing court case inquiry portal; provides read-only access to case information

Case Number, Hearing Dates, Case Status, Party Names, Charges, Disposition (public-accessible fields only)

Integrate

Phase 3

$ - 0

CJT JusticeTech

Bi-Directional

Batch / Real-Time

REST API / Web Service

Case management system for Probate Courts; manages probate case records and court activities

Probate Case Number, Party Names, Case Type, Filing Date, Hearing Dates, Disposition, Estate Records

Integrate

Phase 3

$ - 0

Fythe

Bi-Directional

Real-Time / On-Demand

REST API / SFTP File Transfer

Digital document management for Superior Clerks; stores, retrieves, and manages court case documents

Document ID, Case Number, Document Type, File Date, Document Contents/Metadata, Clerk ID

Integrate/Retire

Phase 3

$ - 0

ZAPs

Bi-Directional

Real-Time / Scheduled

REST API / Web Service

Court calendar communications and scheduling coordination for the District Attorney's office

Hearing Date/Time, Case Number, Courtroom, Participants, Hearing Type, Calendar Updates

Integrate

Phase 3

$ - 0

Imfax

One Way Inbound

Real-Time / Scheduled

REST API / Web Service

Courtroom docket display system; receives and displays scheduled hearings and case docket information

Case Number, Hearing Time, Courtroom, Judge, Parties, Case Type, Docket Status

Intgrate

Phase 3

$ - 0

Connexis

Bi-Directional

Real-Time / Batch

REST API / Web Service

Manages dispute resolution and health-related cases; supports Accountability Courts including specialty programs

Case Number, Program Type, Participant Info, Compliance Records, Hearing Dates, Case Outcomes

Integrate

Phase 3

$ - 0

Tech Friends

Bi-Directional

Real-Time / Batch

REST API / Web Service

Manages inmate tablet services including content, accounts, and usage tracking

Inmate ID, Booking Number, Tablet Usage Data, Account Balance, Content Access, Messaging Records

Integrate

Phase 4

$ - 0

Kronos

One Way Inbound

Batch (Daily/Weekly)

Flat File (CSV) / REST API

Time and attendance tracking for jail staff; employee hours exported to Munis for payroll processing

Employee ID, Hours Worked, Pay Period, Department Code, Shift Data, Leave Balances

Integrate

Phase 4

$ - 0

OnPoint

Bi-Directional

Real-Time / On-Demand

REST API / Web Service

Web-based document management and administration for the Jail; manages administrative documents and records

Document ID, Document Type, Author, Creation Date, Associated Inmate/Case, Document Status

Integrate

Phase 4

$ - 0

C3 Total

$ - 0

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C4 - Training & Knowledge Trans

Cost Proposal - C4 - Training & Knowledge Transfer
#	Training Component	Phase (1-4)	Delivery Model	Sessions	Attendees	Cost/Session	Price $	Response Assumptions
1	XX						$ - 0
2	XX						$ - 0
3	XX						$ - 0
4	XX						$ - 0
5	XX						$ - 0
6	XX						$ - 0
C4 Total							$ - 0
The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C5 - Professional Services

	Cost Proposal - C5 - Professional Services to Implement Data Integration Hub. Please note any cost assumptions and/or optional software and services in the Cost Assumptions tab.
	#	Phase	Task / Deliverable Name
Description in 6.0 of Exhibit	Price $
	1	Phase 1: Implementation and Configuration of the DIH tool.	Task 1: Discovery and Detailed Solution Planning	$ - 0
	2	Phase 1: Implementation and Configuration of the DIH tool.	Task 2: Data Mapping Assessment	$ - 0
	3	Phase 1: Implementation and Configuration of the DIH tool.	Task 3: DIH Production Build	$ - 0
	4	Phase 1: Implementation and Configuration of the DIH tool.	Task 4:DIH Initial Integration	$ - 0
	5	Phase 1: Implementation and Configuration of the DIH tool.	Task 5: DIH Roadmap Development	$ - 0
	C5 - Total Costs (Phase 1)			$ - 0
	7	Phase 2: Support JMS integration messages	Task 1: JMS Bronze Layer Integration and CPU8 JMS Retirement	$ - 0
	8	Phase 2: Support JMS integration messages	Task 2: JMS Silver and Gold Layer Development	$ - 0
	9	Phase 2: Support JMS integration messages	Task 3: Monitoring, Error Handling, and Data Governance	$ - 0
	10	Phase 3: Support CMS Integration Messages	Task 1: CMS Bronze Layer Integration and CPU8 CMS Retirement	$ - 0
	11	Phase 3: Support CMS Integration Messages	Task 2: CMS Silver and Gold Layer Development	$ - 0
	12	Phase 3: Support CMS Integration Messages	Task 3: Monitoring, Error Handling, and Data Governance	$ - 0
	13	Phase 4: Support Additional JMS Integration Messages, New Integration Messages, Data Sources and Data Mining	Task 1: Additional Integration Messages and Extended Data Sources	$ - 0
	14	Phase 4: Support Additional JMS Integration Messages, New Integration Messages, Data Sources and Data Mining	Task 2: Business Intelligence and Analytics Delivery	$ - 0
	15	Phase 4: Support Additional JMS Integration Messages, New Integration Messages, Data Sources and Data Mining	Task 3: Transition, Knowledge Transfer, and Operational Handoff	$ - 0
	N*			$ - 0
	C5 Total Costs (Phase 2 - 4)			$ - 0

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C6 - Support-Maintenance

Cost Proposal - C6 - Software Support/Maintenance
#	Description	Price $	Assumptions
Year 1		NA	County assumes Year 1 - 3 will be development of the DIH and support and maintanence would not be necessary unitl post-implementation.
Year 2		NA	County assumes Year 1 - 3 will be development of the DIH and support and maintanence would not be necessary unitl post-implementation.
Year 3		NA	County assumes Year 1 - 3 will be development of the DIH and support and maintanence would not be necessary unitl post-implementation.
Year 4		$ - 0
Year 5		$ - 0
	C3 Total	$ - 0

Note: For maintenance and support services, please include an annual price for post-implementation maintenance and support for a two-year period beyond successful implementation of the proposed solution. Any ongoing maintenance and support (i.e., production services) prior to the completion of all work provided under this agreement should be included in the Professional Services section of the Cost Proposal (C.5).

The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

C7 - Other Costs

Cost Proposal - C7 - Other Associated Costs
#	Component	Description	Price $	Assumptions
1			$ - 0
2			$ - 0
3			$ - 0
4			$ - 0
5			$ - 0
N*			$ - 0
C7 Total			$ - 0
*Insert as many needed
The DIH will be implemented in phases aligned with the JMS and CMS implementation timelines. The scope of this engagement is limited exclusively to Phase 1.

O1 - Optional SW

Cost Proposal - O1 - Optional Recommended Software
#	Component	Description	Price $	Assumptions
1			$ - 0
2			$ - 0
3			$ - 0
4			$ - 0
5			$ - 0
N*			$ - 0
		O1 Total	$ - 0
*Insert as many needed

O2 - Optional Services

Cost Proposal - O2 - Professional Services to Implement Optional Recommended Software
#	Deliverable	Associated Projects / Work Streams	Price $	Assumptions
1			$ - 0
2			$ - 0
3			$ - 0
4			$ - 0
5			$ - 0
N*			$ - 0
		O2 Total	$ - 0
*Insert as many needed

O3 - Other Optional Items

Cost Proposal - O3- Other Optional Items
#	Component	Description	Price $	Assumptions
1			$ - 0
2			$ - 0
3			$ - 0
4			$ - 0
5			$ - 0
N*			$ - 0
		O3 Total	$ - 0
*Insert as many needed

31.0 Messaging

Functional Requirements: Messaging (Alerts & Notifications)

	Source	New ID	Requirement Text	Response Code
(I, C, N)	Estimated Hours to Customize	Notes
	NEW	AN - 01	The proposed solution must provide the ability to automatically display critical Alerts on screen and print on lists (e.g., Court Movement list).
	NEW	AN - 02	The proposed solution must provide the ability to automatically track multiple PDP-defined criteria (e.g., medical/psych conditions, high-risk, high-profile, murder charge, escape risk, assault risk, etc.) for an inmate.

&P &"Calibri,Regular"&11&K000000&A

File details come from the government source that posted it. Updated Jul 1, 2026.