Frequently Asked Questions
Stakeholder Briefing
Q: Will counties be expected to participate in Production Simulation?
A: Yes, there is an expectation for engagement in Production Simulation. The state is working on getting an All County Letter (ACL) that will outline that guidance (aiming to get it out ASAP). We will continue to communicate about this through all county channels.
Q: Will the State set up all county users/teams/caseloads/offices in Production Simulation?
A: Yes, we will work with your county admin person to set up those users with the exact permission settings they should have and validate that they are correct.
Q: After Go-Live, will there be a procedure manual on how to use CWS-CARES?
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.
Q: When CWS/CMS transitions to read-only before Go-Live, will there be a freeze over that weekend?
A: CWS/CMS will be in read-only mode during the weekend before Go-Live.
Q: How will counties handle manual business processes or workarounds that are not yet supported in CWS-CARES at Go-Live?
A: These will continue to be identified throughout the Production Simulation period as business processes are reviewed. Contingency planning will then be included in the Organizational Change Management (OCM) work.
Q: Why is Sexual Orientation, Gender Identity, and Gender Expression (SOGIE) data being changed to read-only in CWS-CARES?
A: In accordance with federal reporting requirements that changed under federal executive orders, the child welfare information system cannot collect certain SOGIE-related data. Because this functionality was already developed for CWS-CARES, it has been moved to read-only, and the system will not allow this data collection until reporting requirements change.
Q: What is the difference between End User Scenario Testing (EUST), CARES 102, and the Production Simulation environment?
A: EUST 3 is part of structured, large-scope testing windows used to test end-to-end functionality with mock data. Production Simulation is an end-to-end, production-like copy of the system with interfaces, converted data, role-based access, and the ability to practice and validate business processes. CARES 102 (County Development) is a separate environment specifically for forms and reports developers.
Q: During Production Simulation, will there be an opportunity to make system adjustments or modifications if functionality issues are identified?
A: Yes. Production Simulation is designed to help identify critical issues early so they can be evaluated and addressed before Go-Live. Reviewing and resolving high-impact items will be prioritized, but not all adjustments or feedback can be incorporated due to time and resource constraints. The Project will prioritize items that pose the greatest operational risk.
Q: Who will have access to Production Simulation in early May, and how will counties communicate which users they want to have access?
A: More information on this topic was released in All County Letter No. 26-21.
Q: Can the Project provide a complete list of the CWS-CARES Version 1 interfaces that will be accessible in Production Simulation, and will existing data from those systems be available?
A: The expected interface list planned for Production Simulation includes: Case Management Assessment (CMA), Structured Decision Making (SDM), Foster Care Eligibility Determination (FCED), Facility Management System (LIS/FAS data), Juvenile Network (JNET), County Expense Claim Reporting Information System (CECRIS), the data extract from the California Department of Education (CDE), and Regional Center Services for the Department of Developmental Services (DDS). Data availability and timing for some of these interfaces are still being finalized.