A: Yes, we are setting up a Service Desk County Advisory Committee (CAC) to work through the ticketing process and service level expectations. This CAC will include county/project representatives and the focus is operational county and state coordination, incidents and escalations, defect prioritization, business continuity, and knowledge base.

A: Yes. CWS/CMS is the system of record. If a field already exists in CWS/CMS, Binti data will not override it.

A: Yes. Binti documents, often referred to as unstructured data, are planned to be migrated into CWS-CARES.

A: Training materials will be accessible to all Production Simulation users. We're currently finalizing the approach to ensure everyone has the most up-to-date resources, and additional details will be shared as soon as they're ready.

A: Yes. Client IDs are essential for forming the correct relationships during conversion. The Project will share which counties have missing Client IDs.

A: The planned go-live date for CWS-CARES is October 26, 2026. This is subject to final readiness approval by the CWS-CARES Board of Directors.

A: Yes, we are continuing to work on plans for training; there will be a Procedure Manual with "Cheat Sheets" that you can utilize as you're training.

A: Yes, Production Simulation will impact the training plan. The project will be making updates with the training workgroup to take the training plan impact into consideration.

A: Guidance will be provided as to what various CWS-CARES users will need for permissions in Production Simulation.

A: Yes, technical Tableau training will be provided to those who are migrating the current reports and extracts (e.g., Business Objects, Other Org Reporting Tools) to Tableau, and/or participating in post go-live Organizational level Tableau report and extract development.