Public Safety Report System

The Vendor is required to provide the system will enable judges to review both a defendant’s criminal history and public safety report, make informed and appropriate bail decisions, make a record of those decisions, and generate necessary reports.
- Develop an understanding of the needs and challenges to implement an expedient, seamless, and minimally disruptive implementation of the System.
- Services include:
•    Perform all activities necessary to provision all environments needed to run the System, including any networking needed to connect securely to external systems.
•    Implement and configure the System per the developed design to prepare for testing activities.
•    Provide stakeholders and their vendors with the necessary documentation for them to connect to the API.
•    Meet with stakeholders and their vendors to provide overview of the API and to gather information as to when they will be able to connect.
•    Assist stakeholders and their vendors as issues arise.
•    Develop the System Implementation Plan.
•    Provision and configure the System based on the Requirements Traceability Matrix and approved System Implementation Plan.
•    Integrate all components of the System.
•    Configure the user interfaces and APIs needed to run the System.
•    Develop the standard API documentation.
•    Configure any emailing services needed.
•    Provide technical support to stakeholders and office.
•    Build and/or modify all reports and dashboards.
•    Develop the Cutover Plan.
- Security Plan
•    Approach for monitoring security, including how it complies with applicable security protocols and regulations.
•    Approach for keeping security capabilities current with evolving known and potential security threats.
•    Security roles and responsibilities, mission statement, key terms governing incident response, identification of an incident response lead, and incident detection channels.
•    Strategy to identify and categorize incidents.
•    Process to communicate, contain, eradicate, and recover from incidents.
•    Post-incident activities to ensure continuous security improvement.
- Disaster Recovery and Business Continuity Plan
•    Approach for initiating disaster recovery and/or business continuity procedures to be undertaken in the event of a disaster affecting the system.
•    Approach for ensuring all information necessary to restore operational service in the event of a disruption are correct and up to date.
•    Functional roles and responsibilities of recovery teams
•    Description of recovery scenarios that can be implemented.
•    Recovery activities to be exercised and frequency of testing.
•    Description/location of data backups, inventories, or other related documentation that must be recorded.
•    Communication protocols and processes for restoring operations in a timely manner.
•    Approach for retention and storage of backup files and software.
- Infrastructure Services Plan
•    Definition of environments and the approach for maintaining application and infrastructure component consistency across all applicable environments.
•    Approach for certifying and/or providing quality assurance of all applicable environments.
•    Approach for managing programming environment changes including management of testing and deployment of new releases while maintaining capacity to apply hotfixes to production.
•    Approach for communicating and supporting testing of all applicable environments with internal and external organizations/systems.
•    Approach for establishing initial capacity and anticipated growth requirements for the system including but not limited to storage, processing, and network bandwidth.
•    Approach to performance tuning to ensure the system operates optimally and within defined service levels.
•    Approach for monitoring ongoing usage and growth patterns of system resources including for cumulative growth and peak usage patterns.
•    Approach for deployment of additional capacity as specified in the original plan and per the results of ongoing capacity monitoring.
•    Approach for preventative and unplanned services to system services.
•    Documentation of third-party infrastructure service providers and associated communication and management processes.

- Contract Period/Term: 5 years
- Pre-Offer Conference Date: August 11, 2025
- Questions/Inquires Deadline: August 18, 2025