Exhibit B Technical specifications.xlsx
XLSX spreadsheet 482 KB Posted
- Attached to
- Public Safety Software State and local contract opportunity
- Solicitation number
- 065.25
- Issued by
- Pueblo County, Colorado
About this file
This document is an extensive technical specifications exhibit (Exhibit B) for a comprehensive Public Safety Software Request for Proposal (RFP) involving a multi-agency communications center in Colorado. The RFP seeks an integrated solution covering Computer Aided Dispatch (CAD), Law Enforcement Records Management System (LERMS), Fire Records Management System (FRMS), Jail Management Software (JMS), and Mobile Data Software (MDS) for multiple jurisdictions. The technical specifications comprehensively outline detailed functional requirements across numerous modules, including system administration, interfaces, reporting, mapping, alerting, mobile applications, field reporting, property and evidence tracking, and specialized functions like demographics tracking, use of force reporting, internal affairs management, and compliance with state regulations like Colorado HB20-217.
The technical requirements emphasize a cloud-native solution with robust security compliance, particularly around CJIS standards, two-factor authentication, and role-based access controls. The proposed system must support multi-jurisdictional data sharing while maintaining agency-specific data protections, integrate with numerous external systems like NCIC, state repositories, body cameras, and digital evidence management platforms, and provide comprehensive reporting capabilities. The solution must accommodate complex, configurable workflows across law enforcement, fire, corrections, and emergency medical services, with particular attention to capturing demographic information, maintaining audit trails, supporting redaction and record sealing, and facilitating interoperability between different public safety agencies and systems.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| RFP 065.25 - Exhibit C - Sample Contract.pdf | ||
| RFP 065.25 - Public Safety Software.pdf | ||
| Exhibit A Agency Info - 4.23.25.pdf |
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
Instructions
| Instructions for Exhibit B - Technical Specifications |
| The expectations and functionality outlined in this document represent the key features and capabilities we seek in a comprehensive CAD and RMS solution. We recognize that not every vendor may offer a full suite of applications covering all aspects of Dispatch CAD, Law & Fire Mobile, Law Field-Based Reporting, Law RMS, Fire RMS, Property & Evidence, and Jail/Corrections. As such, our expectations include the ability to provide robust interfaces and integrations with third-party systems to ensure seamless interoperability. Vendors should clearly outline their solution's capabilities, identify any gaps, and propose interface options to meet the outlined requirements/request. |
General Questions
| Item Number | Module/Description of Requirement/ Functions | Comments |
| We strongly prefer a cloud-native solution over on-premise or cloud-hosted alternatives to ensure scalability, resilience, and continuous innovation in our public safety environment. A cloud-native architecture should leverage modern microservices, containerization, and elastic scalability, allowing for real-time system updates, high availability, and disaster recovery without reliance on physical infrastructure. Vendors must provide a detailed system architecture outlining how their solution is designed, including network topology, data storage, redundancy, failover strategies, security protocols (CJIS compliance, encryption standards, zero-trust architecture), and API accessibility for integrations. |
If the proposed solution is on-premise or cloud-hosted, the vendor must provide a clear roadmap for migration to a cloud-native model, including timelines, technical considerations, and expected costs for transition. The response should outline how the vendor ensures system reliability, security, and compliance in both current and future deployment models, addressing factors such as data sovereignty, multi-region redundancy, and disaster recovery capabilities. Vendors should also specify their approach to automatic scaling, patch management, and secure access control mechanisms to align with evolving cybersecurity best practices in public safety environments.
| Questions for the Vendor | |
| GIS/Addressing Information | |
| What platform/software does CAD mapping use? | |
| What platform/software does Mobile mapping use? | |
| How and where is the GIS data maintained? | |
| Does your solution support shape files? | |
| Does your solution support centralized geo files on a network? | |
| Does your solution support ESRI ARC GIS Dynamic Feeds | |
| Does your solution support street centerline files, point layers and polygons? | |
| GIS/Mapping solutions | |
| We would like to have the ability to use agency maintained ESRI based GIS layers to populate and maintain the geofile. | |
| We would like to have the ability to test the GIS data to ensure proper functionality. | |
| We would like to have the ability to maintain geofile layers in a current release of ESRI’s products (10.5 and above) | |
| We would like to have the ability to import geofile updates into CAD/RMS using standard ESRI tools or vendor supplied models or scripts. | |
| We would like to have the ability to publish geofile layers to ArcGIS Server map services that can be used by Mobile clients. | |
| We would like to have the ability to have live geofile updates available to CAD/RMS. | |
| We would like to have the ability of providing additional GIS services without involving a third party. | |
| GPS solutions | |
| We would like to have the ability to configure GPS through ethernet or comm port. | |
| We would like to have the ability for GPS to display real time unit location of mobile client on CAD and Mobile map display. | |
| We would like to have the ability for a multi-unit display of GPS location on CAD and Mobile map display. | |
| We would like to have the ability for AVL to use real time GPS location. | |
| We would like to allow for GPS coordinates for units to be utilized for closest, most appropriate unit/resource dispatching and unit recommendations. | |
| Multiple Environments | |
| We would like to provide the support for the following environments: |
• Production
• Test
• Training
• Reporting Server (Reporting to not affect Production when being run, data Replication to Reporting server if needed)
| Does your solution have the ability to modify the test environment and transfer modifications to the production environment? | |
| Does your solution support the ability for an user to operate both a production, test and training environment simultaneously? | |
| Does your solution have the ability to provide visual distinction of environment user is operating? | |
| Licensing | |
| What are your client licensing options? Concurrent/Seat/ enterprise? | |
| Printing | |
| We would like to have the ability to support network printer configuration | |
| We would like to have the ability for user to select applicable printer. | |
| We would like to have the ability to establish default printer based on: |
• User Id
• Device
| Integration | |
| We would like to ensure that all modules integrate with each other (CAD, RMS, JMS, etc.), if 3rd part integrations are needed be prepared to show system integrations. | |
| Integrated modules should provide automatic transfer of critical information (e.g. CFS from CAD to RMS, Arrest and Warrant from RMS to JMS). | |
| We would like to integrate alerts between all modules so that they are accessible by all using any module in the system. (e.g. outstanding warrants) | |
| We would like to ensure that all modules share the same master records for names, addresses, property and vehicles and these master indices are located within a single database. | |
| Mobile Laptop Application | |
| We would like to run on indusrty standard laptop platforms (Getac, Toughbook, Dells etc) | |
| We would like to be compatible with Netmotion Mobility VPN | |
| Mobile (Smartphones/Tablets) Applications | |
| We would like to be compatible with Netmotion Mobility VPN | |
| The proposed solution's application should run successfully on Apple IOS | |
| The proposed solution's application should run successfully on Android | |
| Training | |
| We would like to include system wide training for all modules and adminmistrative functions | |
| We would like to provide On-site end-user training | |
| Support | |
| We would like to have CAD Technical Support is available 24 x 7 and be included in the pricing of the RFP. If not included, then list annual cost in Comment field. | |
| The proposed solution's Technical Support should be based in the United States | |
| Security | |
| We would like to have the ability to meet all CJIS security solutions/ requirments per the current Criminal Justice Information Services (CJIS) Security Policy is Version 6.0,. | |
| We would like to have the ability to support 2 Factor authentication | |
| We would like to support ability of system administrator to remotely log-off users from any device | |
| We would like to have the ability to assign security access per module | |
| We would like to offer security within each module, support assigning security access by function (e.g., insert, modify, delete, read-only) | |
| We would like to restrict access to individual database tables by security (including access from report writer) | |
| We would like to provide centralized user management so each user has a single username and password for the entire The proposed system, incorporated across all applications, ensuring that changes made to a user account are made in a single place. | |
| We would like to have the ability for system administrator to disable an account: |
• Temporarily •Permanently We would like to have the ability to capture the following information associated with each unique Login ID:
• Name
• Title
• Badge Number (not unique - can change)
• Agency
• Email Address
• Security Permissions/Roles
| We would like to have the ability to change Badge number associated with user as needed. | |
| Permissions | |
| We would like to have the ability to support group/role-based security permissions. | |
| We would like to have the ability to allow authorized users to create and maintain user groups/roles. | |
| We would like to have the ability to allow authorized users to assign users to groups/roles. | |
| We would like to have the ability to assign permissions to individual user or roles. | |
| We would like to have the ability to assign users to multiple groups/roles. | |
| We would like to have the ability to provide access levels, including view, add, edit, delete and admin for each component of the system for users and user groups. | |
| We would like to have the ability to define permissions for each group/role, including but not limited to: |
• Application Access
• Module Access
• Jurisdiction
We would like to have the ability to allow authorized user to designate user/users as a System Administrator.
Global System Needs
| Item Number | Module/Description of Requirement/ Functions | Comments |
| Questions for the Vendor | ||
| Below are various systems based questions . | ||
| Reports/ Analytics (See Reporst Reports Request) | ||
| What tool is used to develop reports? | ||
| Does your solution support "if", "then", "when" business rules for notifications throughout the system? | ||
| Does your solution include system-wide business rules that allow authorized users to configure notification scenarios for users and groups? | ||
| Does your solution include system-wide business rules that allow authorized users and groups to be notified via multiple communication channels including internal system messaging, email, and SMS? | ||
| Does your solution include system-wide Incident workflows | ||
| Does your solution warn users of unfinished tasks when they attempt to log out? | ||
| Analytical Reports (See Reporst Reports Request) | ||
| Do you provide any pre-written reports? (If so, please Provide examples) | ||
| To ensure production and operations are not negatively impacted, it is important to use a reporting server/database for generating reports. What does your solution offer for reporting structure | ||
| Ability for the report generating tool to handle: |
• Aggregate math functions
• Fractals
• Percentiles
• Logic operations
• Time operations
• Grouping/sorting on any data element
| We would like to have the ability for users to create ad hoc reports without an in-depth knowledge of databases and query structure. |
| We would like to have the ability to maintain a library of user-created reports. |
| We would like to have the ability to preserve all user-created reports during updates and upgrades. |
| We would like to have the ability for all authorized users to access the library of user-created reports. |
| We would like to have the ability to assign permissions to a report (e.g., who may view report, modify report, etc.) |
| We would like to have the ability to create report templates that can be used to apply standardized layout and formatting to reports for each agency using system. (e.g. different headers/logos per agency) |
| Ability to automatically generate reports on a pre- determined schedule to be uploaded to a designated file location, emailed or printed on specified dates/times. |
| Ability to schedule recurring reports based on user-defined dates, times, days of week, days of month (e.g., every 1st Monday of month). |
| We would like to allow access to all data fields and structures for reporting.. |
| We would like to have the ability to export results into standard formats, including: |
• XLS
• CSV
•JSON
•XML
| Does your solution offer Dashboards for Data analytics |
| We would like to have the ability for reports to display header information, including: |
• Name of individual generating the report
• Date/Time report was generated
• Agency Name, Address, Phone or Agency Header We would like to have the ability to define the layout of a report, including but not limited to:
• Field arrangement
• Column Width
• Font
• Font Size
• Spacing
| Does the solution offer Redactions on reports | |
| Audit Trails | |
| We would like to have the ability to Ability to date and time stamp all |
• System Transactions
• User Transactions
| We would like to have the ability to create a security group defining who has audit trail access permissions. |
| We would like to have the ability to prevent the override of time stamps and record the attempt in the audit trail. |
| We would like to have the ability to maintain an audit trail at the following levels: |
• User
• Field
• Record
• Module
• Application We would like to have the ability to log all actions including, but not limited to:
• Adds
• Changes
• Deletions
• Updates
• Errors
• Security Violations
• Inquiries to all internal and external system
• Views
• Printing
• Override
• Successful Sign-On
• Unsuccessful Sign-On
• Password Changes We would like to have the ability to store audit trail data including, but not limited to:
• User ID
• User Name
• Workstation ID
• Printer ID
• Date/Time Stamp
• Action Taken
• Before and after values of modified data
| We would like to include the ability for users to quickly access the full chronological audit trail for call history and unit history, to include all transactions with the date, time stamp and user performing the action. | |
| We would like to have the ability to review all system activity performed by a specified user during a period of time. | |
| We would like to have the ability to log all vendor access to system (e.g., record a description of all vendor activity). | |
| We would like to have the ability to maintain historical audit trail data based on an agency-defined length of time. | |
| We would like to have the ability to maintain file history so that field value changes can be viewed both before and after change occurred. | |
| We would like to have the ability to visually distinguish data fields that were modified in the audit trail. | |
| We would like to have the ability to extract reports from the audit log. | |
| We would like to have the ability to set notifications on specific activity to designated email address. | |
| Code Table Administration/ Modifications | |
| We would like to have the ability for Agency to maintain code tables (add/change/delete) without vendor intervention. | |
| We would like to have the ability to create a new code and merge/link historical records to a new code. | |
| We would like to allow imports of State-mandated codes and statutes. | |
| We would like to have the ability to store the date a code table value becomes effective. | |
| We would like to have the ability to maintain code table history when a code table is modified so that the Agency may run historical queries/searches. | |
| We would like to have the ability to re-use expired/deleted codes. | |
| We would like to have the ability to prevent the display of obsolete code table values (retire) on drop-down lists. | |
| Code Table Transfer | |
| We would like to have the ability to import tables created in other applications (e.g., Excel). | |
| We would like to have the ability to export code tables into other applications (e.g., Excel) for the purpose of updating and editing the tables. | |
| We would like to have the ability to mass modify codes throughout the system (e.g., converting codes). | |
| We would like to have the ability for code table updates to propagate throughout the system (e.g., an update in a code table for one application component updates the same code table in other application components) where applicable. | |
| We would like to have the ability to designate code table values as obsolete and unavailable for current use, preventing further entry of that value, yet retain the value in the table to maintain data integrity for previous records. | |
| We would like to have the ability to copy code tables across member agencies (e.g., eliminate need to re-enter identical data for separate agencies). | |
| Data entered into the system either directly or |
indirectly is propagated to all relevant databases.
| Statutes | |
| We would like to include federal, state and local statutes. | |
| We would like to allow authorized users to create and update local statutes/ordinances. | |
| We would like to allow authorized users to bulk import local statutes/ordinances. | |
| The proposed system shall allow for annual statute updates and the modification of tables. The statues should allow for the retirement of old statues and the ability to hide the retired statues from end users displays and menu's |
| Attachments | |
| We would like to allow the attachment of files (for example, .PDF, .DOC , .XLS, .JPG, .WAV) to specified record types. Attached files should be able to be opened or viewed on any workstation by authorized users who have the necessary third- party applications (such as MS Word or MS Excel). | |
| We would like to support scanning and attaching documents directly to records in the system without the need to first save them elsewhere. | |
| We would like to store attached files on the vendor’s server within the vendor’s software (not on an open network folder) for security and ease of access. | |
| Queries | |
| We would like to have the ability to conduct searches based on all of the following: |
• Soundex
• "Wild cards"
• Exact Match
• Partial information
• Boolean operators ("and","if","or","not")
• Ranges (date, location, time) We would like to have the ability to query the following ranges:
• Date
• Time
• Location (block range)
| We would like to have the ability to select any result from a query and drill down for detailed information (e.g., hyperlink). | |
| We would like to have the ability to perform global search functions for names, addresses, phone numbers and vehicles. | |
| We would like to have the ability to search narrative fields. | |
| We would like to have the ability to restrict searches that result in large volumes of data by providing a warning of the size of records found with option to continue or cancel. | |
| We would like to have the ability to clearly indicate when additional information (e.g., more search results) is available. | |
| We would like to have the ability to name and save a query. | |
| Custom Forms | |
| We would like to allow authorized users to create custom data collection forms to support agency specified functionality, without any intervention from the vendor. | |
| We would like to allow authorized users to create custom forms. | |
| We would like to support printing the data from custom forms via an agency defined output template and process similar to a mail merge. | |
| We would like to allow authorized users to include as many fields for data collection as are necessary within custom forms, including new fields. | |
| We would like to support the following types of agency-defined fields for custom forms: |
• Address
• Automatic record sequence numbers
• Multiple item select boxes
• Vehicles/Dates/Times
• Dollar Value
• Free form text
• Names
• Numbers
• Signatures (electronic form)
• Checkboxes
• Yes/no Dropdowns or toggle fields
| We would like to allow a custom form to create a relationship on master name or master address records when those fields are specified within the custom form. | |
| We would like to allow authorized users to specify the label for each field on a custom form. | |
| We would like to allow authorized users to specify if each field on a custom form is required or not required. | |
| We would like to allow for setting the default value for each field. | |
| We would like to allow the authorized users to arrange the data items and fields in any order on the form. | |
| Online Documentation | |
| We would like to have the ability to access an online help menu. | |
| We would like to have the ability to provide context-sensitive help that may be accessed from anywhere within the application. | |
| We would like to have the ability for agency to edit text in help files. | |
| We would like to have the ability for help file to automatically update at the time of all version/release updates. | |
| We would like to have the ability to prevent software updates from overriding agency-specific online documentation and help files. | |
| We would like to have the ability to track revisions to online documentation and help files by: |
• User
• Date and Time
| We would like to have the ability to bookmark topics. |
| We would like to have the ability to search help file by: |
• Keywords
• Topics
| We would like to have the ability to include a built-in glossary. |
| We would like to have the inherent ability to send SMS and Email notifications to external numbers and emails without the use of a 3rd party paging tool. |
| The system should allow for SMS and Email notifications sent from the CAD system to be configurable to auto sent based on area, call type, priority, department and/or units assigned. The reconfiguration should include a list of recipients. |
| The system should allow for on the fly SMS and Email notifications to be sent by the system user, even if they have not been preconfigured. |
Report Request
| Item Number | Module/Description of Requirement/ Functions | Comments |
| Below is an example of the reports we would expect to generate from a new system. |
This list sumamrizes reports we would expect to run against our system data for operational oversight, compliance with local, state, and federal regulations, and data-driven decision-making across CAD, Law Enforcement RMS, and Fire RMS. The system should provide standardized, automated, and customizable reports that support incident management, response efficiency, personnel performance, compliance audits, and data integrity. Additionally, reports should meet Colorado-specific requirements, including SB217 transparency mandates, CJIS security compliance, NERIS reporting for fire incidents, and NIBRS compliance for law enforcement data submission.
| Computer-Aided Dispatch (CAD) Reports: | |
| Incident Summary Report – Overview of all incidents by type, priority, location, and time range. | |
| Incident Detail Report – Comprehensive breakdown of individual incidents, including timestamps, call notes, and units assigned. | |
| Unit Response Time Report – Analysis of response times from call receipt to unit dispatch, en route, and on-scene arrival. | |
| Dispatcher Activity Report – Summary of dispatcher workload, calls handled, and unit assignments. | |
| Mutual Aid Report – Documentation of mutual aid requests and responses. | |
| Geospatial Incident Heatmaps – Visual representation of incident hotspots over time. | |
| Repeat Call Location Report – Identifies frequent call locations for potential intervention. | |
| Priority Call Analysis – Breakdown of high-priority calls and their outcomes. | |
| Event Type/Call Nature Trends Report – Analysis of common call types and trends. | |
| CAD System Audit Log – Tracks system access, modifications, and security compliance. | |
| CAD Incident Address Verification Report – Tracks address verification failures and mismatches based on geofile validation. | |
| CAD Premise History Report – Displays historical incidents tied to specific addresses, including hazardous locations. | |
| BOLO (Be-On-The-Lookout) Report – Tracks issued BOLOs, priority levels, and assigned personnel. | |
| Messaging Log Report – Logs inter-agency messages, including those between law enforcement, fire, and EMS. | |
| CAD Shift Summary Snapshot – Provides a real-time view of workstation activity at specific time intervals. |
| Law Enforcement RMS Reports: | |
| Crime Incident Report – Detailed report of crime types, locations, and statuses. | |
| Case Status Report – Summary of open, closed, and pending cases. | |
| Arrest Report – Details on arrests, charges, and dispositions. | |
| Use of Force Report – Documentation of incidents where force was applied. | |
| Traffic Stop and Citation Report – Breakdown of traffic stops, warnings, and citations. | |
| Field Interview Report – Documentation of officer interactions with individuals. | |
| Warrant and Protection Order Report – Active and expired warrants and protection orders. | |
| Property and Evidence Report – Chain of custody and status of evidence. | |
| Juvenile Contact Report – Summary of interactions with juvenile offenders. | |
| Sex Offender Registry Report – Updates on registered sex offenders in the jurisdiction. | |
| Domestic Violence Report – Incident reports involving domestic disputes or violence. | |
| Gang Intelligence Report – Tracking of gang-related activity and individuals. | |
| Mental Health Crisis Report – Summary of mental health-related calls for service. | |
| Animal Control Report – Records of animal-related calls, bites, and citations. | |
| Officer Activity Report – Documentation of officer workload, cases assigned, and shifts worked. | |
| Pursuit and Collision Report – Details of vehicle pursuits and crashes involving department vehicles. | |
| Colorado SB217 Demographic Reporting – Tracks law enforcement interactions by race, ethnicity, gender, and age, per Colorado Senate Bill 217 compliance. | |
| Use of Force Justification Report – Includes incident details, involved officers, subject demographics, and injuries sustained. | |
| Body-Worn Camera Activation Report – Ensures compliance with Colorado police accountability mandates, tracking instances of video activation and retention. | |
| Expungement & Record Sealing Report – Logs cases flagged for record sealing, following Colorado legal guidelines. | |
| Arrest Charge Disposition Report – Tracks the outcome of arrests, required for reporting to the Colorado Bureau of Investigation (CBI). | |
| Mental Health Hold & Crisis Report – Required tracking for interactions involving individuals placed on a 72-hour hold due to mental health crises. | |
| Juvenile Arrest & Detention Report – Documents law enforcement interactions with juveniles, including booking details and parental notifications. | |
| Warrant & Protection Order Compliance Report – Ensures compliance with state laws regarding active protection orders. | |
| Public Records Request & Release Log – Tracks Freedom of Information Act (FOIA) and Colorado Open Records Act (CORA) requests and releases. | |
| Statewide Crime Mapping Data Export – Enables agencies to submit standardized crime reports for state-level analysis. | |
| Fire RMS Reports: | |
| ** If providing Fire Records | |
| Fire Incident Report (NERIS Compliant) – Documentation of fire calls, cause, and damage assessment. | |
| EMS Response Report – Tracking of medical calls, patient care, and transport details. | |
| Response Time Analysis – Review of turnout and travel times for fire and EMS units. | |
| Fire Inspections and Violations Report – Summary of fire code inspections and violations issued. | |
| Pre-Incident Planning Report – Documentation of site surveys and hazard assessments. | |
| Hydrant Inspection Report – Maintenance and inspection status of fire hydrants. | |
| Training and Certification Report – Records of firefighter training, drills, and certifications. | |
| Equipment and Apparatus Maintenance Report – Tracking of maintenance schedules for fire department assets. | |
| Mutual Aid Response Report – Documentation of provided and received mutual aid responses. | |
| **CAD to Fire reporting | |
| Fire Call Summary Report – Overview of all fire-related CAD incidents, including type, priority, and location. | |
| Fire Unit Response Time Report – Breakdown of turnout times, en route times, and on-scene times. | |
| Alarm Handling Time Report – Tracks time from alarm receipt to dispatch and response. | |
| Fire Incident Mapping Report – GIS-based incident visualization for fire calls. | |
| Fire Station Coverage & Response Time Report – Analyzes response times by station area. | |
| Mutual Aid & Automatic Aid Report – Tracks fire department aid given and received. | |
| Jail/Corrections Reports: | |
| Inmate Management Reports | |
| Inmate Roster Report – Lists all current inmates, including booking numbers, charges, and housing assignments. | |
| Booking Summary Report – Tracks all new bookings with details such as time of intake, booking officer, and reason for incarceration. | |
| Inmate Movement Report – Logs all transfers within the facility and movements between facilities. | |
| Inmate Classification Report – Details inmate risk levels, security classifications, and any changes in status. | |
| Inmate Disciplinary Report – Records infractions, disciplinary actions taken, and hearings conducted. | |
| Inmate Incident Report – Tracks altercations, injuries, and any unusual events involving inmates. | |
| Inmate Visitation Report – Logs all visitor interactions, including dates, visitor information, and restrictions. | |
| Inmate Property Inventory Report – Tracks personal property logged at intake and changes over time. | |
| Inmate Housing Assignment Report – Lists current cell assignments and bed availability. | |
| Inmate Release Report – Documents scheduled and completed releases, including parole or early release details. | |
| Inmate Grievance Report – Records all complaints filed by inmates and their resolution status. | |
| Medical & Mental Health Report – Summarizes inmate medical visits, prescriptions, and mental health evaluations. | |
| Suicide Watch & Special Observation Report – Tracks inmates placed under heightened supervision due to mental health concerns. | |
| Booking & Release Reports | |
| Daily Intake & Release Report – Summarizes the number of inmates booked and released each day. | |
| Warrant & Hold Report – Lists all inmates with outstanding warrants, detainers, or holds from other agencies. | |
| Bail/Bond Report – Tracks inmates eligible for release and their bond amounts. | |
| Time Served Credit Report – Calculates sentence reductions based on time served and earned credits. | |
| Release Eligibility & Parole Report – Identifies inmates approaching eligibility for parole or conditional release. | |
| Security & Compliance Reports | |
| Use of Force Report – Logs all instances of force used on inmates, including officer actions and medical evaluations. | |
| PREA (Prison Rape Elimination Act) Incident Report – Tracks allegations, investigations, and outcomes of sexual misconduct cases. | |
| Contraband Report – Lists items confiscated from inmates and any disciplinary actions taken. | |
| Facility Lockdown Report – Documents lockdowns, reasons, and durations. | |
| Shift Activity & Security Checks Report – Ensures officers are conducting and logging security rounds on time. | |
| Escape & Attempted Escape Report – Logs incidents of inmates attempting or succeeding in escaping custody. | |
| Jail Inspection & Compliance Report – Tracks facility inspections and regulatory compliance issues. | |
| Staffing & Administrative Reports | |
| Corrections Officer Shift Report – Summarizes staff assignments, overtime, and daily shift activities. | |
| Training & Certification Report – Documents officer training status and upcoming required certifications. | |
| Visitor & Contractor Entry Logs – Logs individuals entering the facility for visits, legal representation, or maintenance. | |
| Grievance & Complaint Report – Logs inmate complaints against staff and their resolution. | |
| Jail Population & Capacity Report – Tracks facility occupancy, including overpopulation trends. | |
| Financial & Commissary Reports (If Commissary provided, otherwise interafced with Commissary system) | |
| Inmate Trust Account Report – Tracks deposits, withdrawals, and available balances in inmate accounts. | |
| Commissary Sales Report – Summarizes purchases made by inmates, including items and spending trends. | |
| Restitution & Fee Collection Report – Documents money collected for fines, court fees, or victim restitution. | |
| Indigent Inmate Support Report – Tracks supplies and services provided to indigent inmates. | |
| Law Enforcement & External Agency Reports | |
| NCIC/State Criminal History Query Report – Logs searches conducted for inmate records. | |
| Warrant & Hold Notification Report – Notifies external agencies of inmates with outstanding warrants. | |
| Transport & Extradition Report – Summarizes planned and completed inmate transfers to other jurisdictions. | |
| ICE & Immigration Holds Report – Tracks inmates flagged for immigration detainers. | |
| Special & Custom Reports | |
| Custom Ad-Hoc Reporting – Ability to generate custom reports using any field in the system. | |
| Jail Dashboard Report – Real-time operational summary including population, incidents, and upcoming releases. | |
| Predictive Analysis & Trend Report – Analyzes trends in inmate population, security incidents, and staffing needs. | |
| Multi-System & Administrative Reports: | |
| Daily Activity Log Report – Summary of shift activities for CAD, Law, and Fire personnel. | |
| Personnel Scheduling & Shift Report – Tracks personnel hours and shift assignments. | |
| Incident Data Quality Report – Flags missing or incorrect incident data. | |
| Budget & Resource Utilization Report – Tracks costs for operations, equipment, and overtime. | |
| Custom Query Report Builder – Allows agencies to generate ad hoc reports as needed. | |
| Data Integrity & Exception Report – Identifies data anomalies or errors in records. | |
| Public Safety Trend Analysis Report – Identifies long-term crime and fire trends for resource planning. | |
| Community Risk Reduction Report – Assesses risk factors and prevention efforts. | |
| Compliance & Accreditation Reports – Covers CJIS, NERIS, CALEA, and other regulatory requirements. | |
| System Audit & Security Compliance Report – Ensures compliance with CJIS security models, logging system access, encryption, and role-based access. | |
| Supervisor Incident Approval Workflow Report – Tracks incidents requiring supervisory approval before finalization. | |
| Automated Report Review Workflow Summary – Ensures compliance with retrospective quality assurance (QA/QI) processes. | |
| Roster & Personnel Availability Report – Tracks real-time personnel assignments and availability across agencies. |
Interfaces
| Item Number | Module/Description of Requirement/ Functions for Interfaces | Comments |
| In our Public safety environment, seamless integration between various systems is critical for operational efficiency, real-time data sharing, and compliance with local, state, and federal requirements. The vendor must provide detailed descriptions of all available interfaces their solution supports, including what data is exchanged, how frequently data is updated (real-time or batch), the format of data transfers (XML, JSON, NIEM-compliant, API, Web Services, etc.), and security measures in place (CJIS compliance, encryption, role-based access). |
The response should outline each interface’s core function, the direction of data flow (one-way or two-way), and specific data elements shared. Interfaces should include, but are not limited to, CAD-to-Fire RMS, CAD-to-Law RMS, CAD-to-Mobile Data Systems, Jail Management Systems, EMS/Medical Reporting, State/NCIC Query Systems, Court and Case Management, E911 and NG911 Systems, Records Management, Body Camera & In-Car Video, Digital Evidence Systems, GIS Mapping, and Dispatch-to-alerting Systems.
The vendor should also describe how their system integrates with existing third-party solutions, the level of configurability available, and any API documentation or SDKs provided to support custom integrations. If middleware or proprietary software is required, this should be clearly stated.
| CAD Interfaces | |
| E911 | |
| Texting is accomplished through ComTech for both agencies, | |
| The proposed solution must include an interface to the 911 service provider, Motorola Vesta 911, to automatically populate CAD calls with 911 information when selected by dispatcher. | |
| The proposed solution must have the ability to receive the raw ALI/ANI spill data from the 911 service and import and properly parse it into the CFS via a serial or IP connection. | |
| The proposed solution must have the ability to intelligently handle ANI/ALI rebids through the interface. (accept updated information) | |
| The proposed solution must have the ability to geoverify the E911 imported address immediately upon transfer. | |
| The proposed solution must have the ability to determine a physical address from X/Y coordinates imported from the E911 phone system. | |
| The proposed solution must have the ability to transfer E911 call receipt time to CAD to track E911 time stamps. | |
| The proposed solution must have the ability to plot incoming E911 calls on the CAD and Mobile application map. | |
| The E911 interface must include as part of the CAD incident wireless phase 1 and phase 2 information. | |
| ProQA/Priority Dispatch | |
| The proposed solution must support API integration with Priority Dispatch’s ProQA system, which handles the protocol logic (Medical, Fire, and Police). The integration must enable real-time communication between ProQA and the CAD system, ensuring that information from the protocol flows into the CAD system instantly. The integration must allow the CAD system to send data to ProQA (such as incident information, caller name, Caller address, and Contact information) and receive protocol-based recommendations and updates back into CAD. The integration must allow protocol data, such as case entry, determinant codes (e.g., Medical Priority Dispatch System (MPDS) codes), and responses, to be automatically recorded within the CAD system. The CAD system must be able to map incident data to the protocol’s specific fields, including location, call type, and units assigned. The integration must ensure that priority levels and determinant codes generated by ProQA are reflected in the CAD system to inform dispatcher decisions. Any changes to call information (e.g., location updates, unit status, or caller details) must automatically sync with ProQA in real time. Any updates made in ProQA, such as when new protocol recommendations are available, must flow back into the CAD system without manual intervention. | |
| RapidSOS | |
| The CAD system must integrate with the RapidSOS API to retrieve enhanced location data and additional caller information during an active emergency call. The integration must enable real-time data flow between the RapidSOS platform and the CAD system, ensuring that location data and other relevant information from RapidSOS is available as soon as a call is initiated. If necessary, the CAD system must be capable of sending data to RapidSOS (such as call or incident updates), although most data typically flows from RapidSOS to the CAD. The CAD system must automatically receive location updates from RapidSOS as they are available (e.g., as the caller moves), and update the location in the CAD interface in real time. The CAD system must be capable of displaying precise, map-based location data from RapidSOS, including GPS coordinates, device-derived locations, and floor-level information in multi-story buildings. The CAD system’s mapping component must be able to ingest and display RapidSOS data seamlessly, overlaying it on maps for real-time tracking of caller locations. Upon receiving enhanced data from RapidSOS (e.g., medical profiles, vehicle telematics, or alarm system data), the CAD system must automatically populate the relevant fields in the incident record or call log. The CAD system must be able to map and store additional caller data from RapidSOS, including device type, health information, or telematics data, linking it to the specific call or incident. RapidSOS information must be displayed directly within the CAD interface, so that dispatchers do not need to toggle between systems. Key data such as enhanced location, additional caller information, and situational context must be easily accessible. The CAD system’s map must support interactive viewing of caller locations, with real-time updates from RapidSOS. Dispatchers must be able to click on a call and view detailed RapidSOS data, such as building floor plans or movement patterns of the caller. | |
| LPR | |
| The CAD system must integrate with the LPR system through an Application Programming Interface (API). This API will facilitate the communication of LPR data (e.g., license plate reads and vehicle locations) to the CAD system in real time. The integration must support the real-time transmission of LPR data to the CAD system, ensuring that dispatchers and officers receive immediate notifications when relevant license plates are identified. The Cad system must have Bi-DIrectional Data Flow to send data to the LPR system, for the creation of "hot lists" (lists of vehicles of interest) that the LPR system can automatically monitor. The CAD system must be able to integrate with and manage hot lists provided by the LPR system or external sources. Hotlists are vehicles associated with alerts (e.g., stolen vehicles, wanted persons). These lists must be updated regularly and trigger automatic alerts in the CAD system when a match is found. When an LPR hit occurs that matches a vehicle of interest (e.g., stolen vehicle or a suspect in a crime), the CAD system must be able to automatically generate an incident based on the LPR data hit | |
| WatchGuard, Getac, and Axon body Cameras and in-car video system | |
| The proposed solution must include an CAD interface compatible with WatchGuard, Getac, and Axon body cameras and in-car video systems. The integration must enable CAD incident information, such as call type, unit numbers, statuses, and call times, to be transmitted to these systems based on the agency and the specific platform in use. This integration must facilitate tagging video footage and associating it with the corresponding CAD or case incident. | |
| CAD API | |
| The API for a Computer-Aided Dispatch (CAD) solution enables seamless interoperability by transmitting data to external systems and receiving data using a vendor-provided structure, ensuring integration with Fire Records Management Systems (FRMS), Records Management Systems (RMS), Emergency Medical Systems (EMS), and other public safety platforms. Supporting standardized formats like XML and JSON, and ideally compliant with the National Information Exchange Model (NIEM), the API ensures compatibility, consistent data mapping, and synchronization of key elements such as incident details, unit status, and location updates. A RESTful architecture with HTTP methods (GET, POST, PUT, DELETE) provides a scalable framework, allowing real-time "push" updates for incident changes, unit status updates, location changes, and resource requests, while also enabling "pull" functions for querying incidents. Additionally, the API supports periodic polling and data feed subscriptions, allowing bi-directional communication for incident details, GIS mapping, unit status, dispatch assignments, and resource availability. Features like geo-fencing, alerts for critical incidents, and secure data handling compliant with CJIS security models, including encryption and role-based access, ensure reliability, security, and operational efficiency across platforms. | |
| RMS Interfaces | |
| Statutes/CITATIONS | |
| The proposed solution must have the ability to transfer ACCESS/NCIC query information from the CAD/Mobile to the Application if needed | |
| The Law Enforcement Records Management System (RMS) must support the manual upload of all Colorado statutes, allowing for periodic updates or deletions as necessary to ensure the system remains current with legal standards. The interface must enable bulk uploads and provide tools for administrators to easily add, modify, or delete statutes. It must also include validation mechanisms to prevent errors during uploads and offer user-friendly access for searching and referencing statutes within the system. Additionally, audit logs must track changes to ensure accountability and compliance. | |
| The proposed solution must have the ability to accommodate exports from multi-jurisdictional agencies | |
| LiveScan | |
| The Law Enforcement Records Management System (RMS) must include an interface for Live Scan fingerprint systems, enabling real-time capture and submission of fingerprint data to state and federal databases. The interface must securely transmit data, ensuring compliance with Criminal Justice Information Services (CJIS) requirements, and provide integration for retrieving and linking fingerprint results directly to case records within the RMS. Additionally, the system must support tracking of submission status, error handling, and audit logging for accountability and compliance with legal standards. | |
| CARFAX | |
| The Law Enforcement Records Management System (RMS) must include an interface for Carfax that allows officers to access vehicle history reports in real-time. This interface must automatically retrieve relevant vehicle data, such as accident history, service records, and title information, using license plate or VIN searches. It must securely transmit data and integrate it into existing workflows, such as traffic stops and investigations. The system must also support logging of queries and provide audit trails for accountability and compliance with legal standards. The intent of the inmterface is a bi-directional interface for pertinent information like drivers licece info or vehicle registration | |
| State of Colorado | |
| The Law Enforcement Records Management System (RMS) must include an interface for National Incident-Based Reporting System (NIBRS) compliance, allowing for the automatic submission of incident data to state and federal NIBRS databases. The interface must ensure that all data is formatted correctly according to NIBRS guidelines, support validation checks to ensure accuracy, and provide real-time error reporting with the ability to correct and resubmit data. It must also track submission statuses and generate audit logs for compliance and accountability. | |
| The Law Enforcement Records Management System (RMS) must include an interface with the Colorado Bureau of Investigation (CBI) for seamless integration with the Colorado Crime Information Center (CCIC) and National Crime Information Center (NCIC) using OpenFox Markup Language (OFML). This interface must support real-time querying and data exchange, allowing for the submission and retrieval of law enforcement data such as warrants, stolen property, and criminal history. Additionally, it must enable the automated upload of state-required reports, ensuring secure data transmission, error validation, and audit logging for compliance with state and federal standards. | |
| For compliance with Colorado HB-217, the Law Enforcement Records Management System (RMS) must include an interface that enables real-time data capture and reporting of use-of-force incidents, including the type of force used, officer details, and the outcome. The system must also collect and store demographic data for individuals involved in law enforcement encounters, as the law requires. It must support secure, automated submission of this data to Colorado’s state reporting systems via API integration(JSON), ensuring encryption and compliance with state guidelines. Additionally, the system must include validation checks for mandatory fields, error handling for missing data, and role-based access control with audit logging to ensure data integrity and accountability. The system must be able to report this information to the State of Colorado in CSV, XML or prefered JSON per state requirments. This report must be broken out by Agency ORI | |
| LInX | |
| We would like a export interface for LInX to exchange Police Reports , Person information vehicle inofration etx. If possible we would like to get a Bi-directional, realizing the interface will need to be completed in partnership with LInX. | |
| Digiticket | |
| The Law Enforcement Records Management System (RMS) must integrate with the Digiticket electronic ticketing system to allow seamless transfer of citation data. This interface must automatically sync issued tickets, including offender details, violation information, and court dates, directly into the RMS. It must support real-time data exchange, reduce manual data entry, and ensure accuracy by validating the information during the transfer. Additionally, the interface must provide secure data transmission and maintain audit logs for tracking and compliance purposes. Currently Use PBI | |
| E-Discovery | |
| We would like to have the ability tosupport an efficient e-discovery process, enabling the collection, review, and sharing of digital evidence for legal proceedings. This workflow must allow users to search, retrieve, and organize relevant case data, including documents, videos, and communications, directly from the system. The solution must ensure secure access for authorized personnel, offer tools for tagging and categorizing evidence, and provide options for exporting data in legally acceptable formats. Additionally, it must include audit logs to track access and changes for accountability and compliance with legal standards. | |
| Insights | |
| We would like to have the ability to interface for Insights, enabling the integration of data analytics and reporting tools with the agency’s systems. This interface must allow for the seamless extraction, analysis, and visualization of key data to support decision-making and performance evaluation. The solution must provide real-time data access, customizable reports, and secure handling of sensitive information, while ensuring compliance with relevant legal and regulatory standards. | |
| LPR | |
| The proposed solution must include an interface with the agency’s License Plate Recognition (LPR) system, allowing seamless integration with the Records Management System (RMS) and vehicle information databases. This interface must automatically capture and transfer LPR data, including license plate reads, vehicle details, and associated incident information, directly into the RMS. It must function similarly to the CAD integration, supporting real-time data exchange, vehicle tracking, and alert generation for matching plates. The interface must ensure secure data handling and provide audit logs for compliance and accountability. | |
| Body Camera's and In-car Video Systems (Watchgaurd, Getac, and Axon) | |
| The proposed solution must include an interface that allows video data from the agency’s camera systems, such as body-worn and in-car cameras, to be integrated directly into the Records Management System (RMS). This interface must enable cases in the Law Records Management System (LRMS) to be automatically flagged when associated video footage is available, ensuring that relevant video evidence is easily accessible. The solution must support secure data transmission and provide audit logging to maintain compliance and accountability. | |
| Motorola Command Central | |
| The proposed solution must include an interface with Motorola Command Central for seamless integration with the agency’s body camera and digital evidence systems. This interface must enable the automatic transfer of video footage and other digital evidence into the Records Management System (RMS), allowing for efficient case management. The solution must support secure data handling, ensure proper evidence linking to case records, and provide audit logs for accountability and compliance with legal standards. | |
| Julota/ Health and Human Services (HHS) |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .