A: The CWS-CARES V1 Scope Assessments are preliminary and based on functionality descriptions provided by organizations. Production Simulation provides the opportunity for organizations to validate functionality in CWS-CARES V1 prior to go-live, in order to identify any gaps or issues that were not previously identified or documented by the gap analysis process. Use of the Production Simulation environment also allows organizations an early opportunity to validate and finalize business process changes ahead of go-live. This will minimize the effort for Fully-In-Scope decommissioning planning as validated systems can be made inactive or read-only prior to December 31, 2027.

A: Yes, counties will be able to run and test reports against practice data entered in Production Simulation including all Key Performance Indicators (KPI) reports and Tableau reports.

A: The Binti Family Finding module was part of the original scope for Binti data conversion, it was not added later on.

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

A: For CWS-CARES data migration, CWS/CMS remains the system of record. Naming and facility records will follow CWS-CARES standards, with issues reviewed during data mapping and validation.

A: To access the Readiness Checklist in Asana, please contact your respective Implementation Lead (IL).

A: Yes, when CWS-CARES receives data from CalSAWS for issued assistance-related payments, we will only be able to read that information but not edit it. Issuances outside of CalSAWS will be read-only as well after they are uploaded into CWS-CARES via the supplemental form.

A: Data will exchange as close to real-time as possible. A nightly batch occurs as a 'failsafe' if any data does not go through in near real-time.

A: Yes, in All County Letter 18-47 CDSS encourages counties to work with their contract and procurement offices to incorporate language into any vendor contracts for external systems that may allow for flexibility to modify and/or terminate contracts as appropriate as the statewide functionality is developed and fully implemented in CWS-CARES.

A: Organizations should use Production Simulation and recorded demonstrations to test real workflows in CWS-CARES V1 using converted data as it becomes available.

For fully in-scope systems, we recommend organizations validate their required workflows can be completed from start to finish in CWS-CARES V1 without relying on the external system.

For partially in scope systems, organizations are encouraged to use a mix of common daily tasks, workflows, and county-specific processes to identify the boundary between CWSCARES V1 and the external system. The organization will then know which steps occur in CWS-CARES, and which steps remain outside CWS-CARES. Thus, validating functionality that is partially in-scope.

The ESCU recommendations for validation tools and activities in Production Simulation are available in the February 2026 External Systems Monthly Meeting Materials within the External Systems Portal.