Integrated Justice Information and Management System Modernization

The Vendor is required to provide justice information and management system (JMS) solution must be flexible, scalable platforms that support future operational growth and business transformation.
- JMS and court case management system (CCMS) solution using one or more commercial off-the-shelf (COTS) software products and services that are fully integrated to meet the county's business needs.
- Project management plan 
1. Schedule management plan
• This plan establishes the policies, procedures, and documentation for planning, developing and managing the project schedule. 
• The schedule management plan will: 
o Define the scheduling method
o Process for baselining the schedule and schedule updates 
o Provide a milestone list 
2. Cost management plan
• Define standard thresholds and criteria for escalation. 
• Continually monitor and analyze project financial performance for risk, negative trends, or early indicators of unfavorable performance. 
• Provide performance reports based on the county and proponent’s developed criteria. 
3. Quality management plan
• The quality management plan addresses the management of the project and the deliverables of the project. 
• Quality measures and techniques are specific to the type of deliverables being produced and will be specified in the deliverable expectations document for project deliverables.
• The quality management plan will include the following elements. 
4. Resource management plan
• Identification of resource requirements (proponent and county), activities, roles and responsibilities, skill requirements, expertise, required level of engagement and duration 
• Training requirements for project resources (if needed) 
• Organizational structure for resources (reporting and coordination of project tasks) 
• Process to replace resources who have left the project.
• Office space, equipment, background checks, access requirements, meeting room requirements, etc. 
5. Risk management plan
• Create and update the risk assessment log. 
• Anticipate and identify risks. 
• Identify the severity and quantify the potential impact of each identified risk. 
• Quantify the probability of each identified risk. 
• Support the development of risk mitigation plans for each identified risk. 
• Guidance for assessing the efficacy of risk mitigation actions
• Work products and processes for assessing and managing risks. 
• The escalation and remediation mechanisms for risks. 
• Risks and issues will be tracked and reported and the format of risk and issues reports (depth, detail, and content). 
6. Communications management plan
• Types of meetings and frequency including, status meetings, stakeholder meetings, project scrum meetings 
• Communication methods (email, reports, presentations, etc.) 
• Distribution methods 
• Approach for documenting and distributing meeting minutes 
• Collaboration tools 
- Risk log
1. The proponent project manager will maintain a project risk log that tracks all risks and issues and will include at a minimum the following:  
• Date risk was identified 
• Description of risk 
• Impact description (budget, schedule, staffing, etc.) 
• Severity of the risk 
• Probability of the risk 
• Risk mitigation strategy 
• Action items and assignment 
• Status of the risk (open, closed) 
2. Proponent responsibilities 
• Maintain the risk log on an on-going basis throughout the life of the project and update it, in collaboration with the county’s pm as necessary, but no less than weekly to reflect the accurate status of the project.   
• Ensure the availability of the project risk log in a central location. 
• An update on key risks and issues on weekly status reports 
- Requirements traceability matrix
• Requirements traceability matrix (RTM) is to document and trace the requirements identified by the county to the system being implemented. 
• The RTM is used to track each project requirement from its origin through the various phases of the project. 
• It provides a means to track requirements throughout the project life cycle helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project. 
• It also provides a structure for managing changes to project.
- System configuration specifications
• Hardware configuration 
• Operating system configuration 
• Software configuration 
• Interface configuration 
• Data configuration.