Attachment B _ JMS Cost Proposal Form.xlsx
XLSX spreadsheet 520 KB Posted
- Solicitation number
- PE-63100-NONST-2026-000000096
- Issued by
- Clayton County, Georgia
About this file
This is a Cost Proposal Form for an Integrated Justice Information and Management System (JMS) Modernization for Clayton County, Georgia. The RFP seeks vendors to provide a comprehensive justice management system solution that includes Use of Force functional requirements, incident reporting capabilities, medical review documentation, and data query and integration functionalities. The system must support linking Use of Force reports with related disciplinary and incident reports, documenting chemical agent usage, and automating equipment issuance processes. The proposed solution should integrate with existing systems through modern APIs via a Data Integration Hub.
The cost proposal is structured across multiple components over a ten-year period: Base System Software (C1), Professional Services for implementation (C2), Software Support and Maintenance for Years 4-10 (C3), and Other Costs (C4), with optional modules and services (O1, O2, O3) available for additional pricing. The implementation timeline spans three years of development with support and maintenance commencing in Year 4 following successful production implementation. Professional services deliverables include comprehensive project management, requirements analysis, gap analysis, system design specifications, environment and application configuration, data conversion and migration, interface development, user acceptance testing across multiple phases, training and knowledge transfer, and post-implementation warranty and defect tracking services. Vendors must provide detailed cost assumptions for each proposal section, including assumptions regarding the number of users and interface development approaches.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Exhibit A _ Data and Infrastructure.pdf | ||
| Exhibit G _ JMS Project Gates and Deliverable.pdf | ||
| Exhibit C _ JMS On_Going Support and Training.pdf | ||
| Exhibit F _ JMS Project Management.pdf | ||
| Exhibit E _ Data Integration Hub Requirements.xlsx | XLSX spreadsheet | |
| Attachment B _ DIH Cost Proposal Form.xlsx | XLSX spreadsheet | |
| Exhibit D _ JMS Functional Requirements.xlsx | XLSX spreadsheet | |
| 26_24 Integrated Justice Information and Mana.pdf | ||
| Exhibit B _ JMS Technical Requirements.xlsx | XLSX spreadsheet |
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
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
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 with description of functionality (Material only) | |
| • | C2 – Professional Services to Implement Base System | |
| • | C3 – Support-Maintenance | |
| • | C4 – 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 B – Technical Requirements for additional information. Professional Services for interface work should be included in C2 and any additional costs anticipated in C4 Other Costs. |
Cost Proposal Summary
| Cost Proposal Summary | ||
| Responder Name: | ||
| Note: This is automatically populated. | ||
| # | Component | Price $ |
| C1 | Base System Software with description of functionality (Material only) | $ - 0 |
| C2 | Professional Services to Implement Base System | $ - 0 |
| C3 | Software Support/ aintenance for Years 4 - 10 (TOTAL) | $ - 0 |
| C4 | Other Costs | $ - 0 |
| COST PROPOSAL TOTAL | $ - 0 | |
| # | Optional | Price $ |
| O1 | Optional Recommended Software Add-ons (Material only) | $ - 0 |
| O2 | Professional Services to Implement Optional Recommended Software/Modules/Add-ons | $ - 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 |
C1 - Base System SW
| Cost Proposal - C1 - Base System Software | ||||||||||||||
| # | Component | Description | Yr 1 | Yr 2 | Yr 3 | Yr 4 | Yr 5 | Yr 6 | Yr 7 | Yr 8 | Yr 9 | Yr 10 | Price $ | Response Assumptions |
| 1 | XX | $ - 0 | ||||||||||||
| 2 | XX | $ - 0 | ||||||||||||
| 3 | XX | $ - 0 | ||||||||||||
| 4 | XX | $ - 0 | ||||||||||||
| 5 | XX | $ - 0 | ||||||||||||
| 6 | XX | $ - 0 | ||||||||||||
| C1 Total | $ - 0 |
C2 - Professional Services
| Cost Proposal - C2 - Professional Services to Implement Base System. Please note any cost assumptions and/or optional software and services in the Cost Assumptions tab. | |||||
| # | Phase | Stage Gates | Deliverable Name | ||
| Description in Appendies E and I | Price $ | ||||
| 1 | Inception | Planning | Project Kickoff Presentation | $ - 0 | |
| 2 | Inception | Planning | Project Management Plan, Project Schedule, Change Log, Risk Log, Decision Log, Monthly Project Management & Reporting | $ - 0 | |
| 8 | Elaboration | Requirements / Design | Gap Analysis Report | $ - 0 | |
| 9 | Elaboration | Requirements / Design | Requirements Traceability Matrix | $ - 0 | |
| 10 | Elaboration | Requirements / Design | Software Architecture Document | $ - 0 | |
| 11 | Elaboration | Requirements / Design | System Configuration Specifications | $ - 0 | |
| 12 | Elaboration | Requirements / Design | System Design Specifications | $ - 0 | |
| 13 | Elaboration | Requirements / Design | Inventory of Reports, Dashboards, Forms & Queries | $ - 0 | |
| 14 | Construction | Configure, Build | Environment Configuration | $ - 0 | |
| 15 | Construction | Configure, Build | Application Configuration | $ - 0 | |
| 16 | Construction | Configure, Build | Develop Reports, Dashboards, Custom Design & Enhancements | $ - 0 | |
| 17 | Construction | Configure, Build | Detailed Data Cleansing Plan(s) | $ - 0 | |
| 18 | Construction | Configure, Build | Detailed Data Conversion Plan(s) | $ - 0 | |
| 19 | Construction | Configure, Build | Detailed Data Migration Plan(s) | $ - 0 | |
| 20 | Construction | Configure, Build | Conduct Data Conversion(s) and Migration(s) | $ - 0 | |
| 21 | Construction | Configure, Build | Interface & Data Exchange Specification Document(s) | $ - 0 | |
| 22 | Construction | Configure, Build | Conduct Interface and Data Exchange Development | $ - 0 | |
| 23 | Construction | User Acceptance | Detailed Test Plan(s) | $ - 0 | |
| 24 | Construction | User Acceptance | Develop Test Cases | $ - 0 | |
| 25 | Construction | User Acceptance | Data Conversion Testing | $ - 0 | |
| 26 | Construction | User Acceptance | Interface and Data Exchange Testing | $ - 0 | |
| 27 | Construction | User Acceptance | Performance Testing | $ - 0 | |
| 28 | Construction | User Acceptance | System Integration Testing | $ - 0 | |
| 29 | Construction | User Acceptance | Final Test Report | $ - 0 | |
| 30 | Construction | User Acceptance | User Acceptance Test Plan | $ - 0 | |
| 31 | Construction | User Acceptance | User Acceptance Test Scripts | $ - 0 | |
| 32 | Construction | User Acceptance | User Acceptance Test Report | $ - 0 | |
| 33 | Transition | Cutover | Training and Knowledge Transfer Plan | $ - 0 | |
| 34 | Transition | Cutover | Training Materials | $ - 0 | |
| 35 | Transition | Cutover | Training Environment | $ - 0 | |
| 36 | Transition | Cutover | Train the Trainer | $ - 0 | |
| 37 | Transition | Cutover | Technical Training (Administrator & Technical Training ) | $ - 0 | |
| 38 | Transition | Cutover | Cutover Plan | $ - 0 | |
| 39 | Transition | Cutover | Performance Testing Report | $ - 0 | |
| 40 | Transition | Cutover | System Documentation | $ - 0 | |
| 41 | Transition | Cutover | Go-Live Readiness Assessment | $ - 0 | |
| 42 | Transition | Cutover | Verification of Cutover and Final Acceptance Report | $ - 0 | |
| 43 | Transition | Cutover | Lessons Learned | $ - 0 | |
| 44 | Transition | Warranty | Detailed Expectations and Service Level Agreements. | $ - 0 | |
| 45 | Transition | Warranty | Service Level Requirements Performance Report | $ - 0 | |
| 46 | Transition | Warranty | Post Go-Live Release Notes & Narrative (for initial release, on-going Release Notes shoud be included in Support & Maintenance) | $ - 0 | |
| 47 | Transition | Warranty | Defect Tracking and Mitigation Review (for initial release, on-going Defect Tracking and Mitigation Review shoud be included in Support & Maintenance) | $ - 0 | |
| N* | $ - 0 | ||||
| C2 Total | $ - 0 | ||||
| *Insert as many needed. Leave additional lines at the bottom of the spreadsheet. Include the Phase they would fall within, the corresponding Stage Gate, and Deliverable Name. |
C3 - Support-Maintenance
| Cost Proposal - C3 - Software Support/Maintenance for Years 4 - 10 | |||
| # | Description | Price $ | Assumptions |
| Year 1 | NA | County assumes Year 1 - 3 will be development of the JMS and support and maintanence would not be necessary unitl post-implementation. | |
| Year 2 | NA | County assumes Year 1 - 3 will be development of the JMS and support and maintanence would not be necessary unitl post-implementation. | |
| Year 3 | NA | County assumes Year 1 - 3 will be development of the JMS and support and maintanence would not be necessary unitl post-implementation. | |
| Year 4 | $ - 0 | ||
| Year 5 | $ - 0 | ||
| Year 6 | $ - 0 | ||
| Year 7 | $ - 0 | ||
| Year 8 | $ - 0 | ||
| Year 9 | $ - 0 | ||
| Year 10 | $ - 0 | ||
| C3 Total | $ - 0 |
Note: For maintenance and support services, please include an annual price for post-implementation maintenance and support for a seven-year period beyond successful implementation of the proposed solution into a production environment (customer acceptance). 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.2).
C4 - Other Costs
| Cost Proposal - C4 - Other Associated Costs | ||||
| # | Component | Description | Price $ | Assumptions |
| 1 | $ - 0 | |||
| 2 | $ - 0 | |||
| 3 | $ - 0 | |||
| 4 | $ - 0 | |||
| 5 | $ - 0 | |||
| N* | $ - 0 | |||
| C4 Total | $ - 0 | |||
| *Insert as many needed |
O1 - Optional SW
| Cost Proposal - O1 - Optional Recommended Software / Modules / Add-ons (Material costs only) | ||||
| # | 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/Modules/Add-ons | ||||
| # | 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 |
File details come from the government source that posted it. Updated .