A: Support will be provided for all Product Simulation users via a Service Desk. The specific support model is still being finalized, and more information will be shared as those details are confirmed.

A: Role configuration will be specific to a function. This work will be performed by organizations as part of an activity called role mapping in which security profiles for CWS-CARES will be provided to your organization (through your IC) and your implementation team will have the opportunity to assign profiles based on job responsibilities.

A: The Project will provide the option of both over-the-shoulder and virtual support to organizations post Go-Live. Implementation Leads will be coordinating with the organizations directly to understand what works best for them.

A: OCMAW memberships are approved through the Regional Chairs (RCs). Please ask your RC to send an email to the CWDS Implementation Mailbox.

A: Production Simulation is intended to supersede the Sandbox environment, which will be retired once Production Simulation is activated. It is important to note that Business Process Validation (previously called Process Simulation) is not a standalone environment. Instead, it is an activity conducted within the Production Simulation environment to validate workflows. 
 
Unlike temporary testing sites, the Training environment is a permanent resource that will remain available after CWS-CARES V1 go-live to support onboarding and continued learning using generic (non-production) data and artificial cases. 
 
Environment Summary: 

1. Sandbox: Temporary testing environment; will be replaced by Production Simulation. 

2. Production Simulation (Pending Federal Approval): Real-data practice environment that will be retired once CWS-CARES is live. 

3. Training: Ongoing staff development environment using non-production data. 

4. EUST: Extended User Scenario Testing environment, scheduled to retire after EUST 3. 

A: Following go-live, counties and organizations will maintain access to multiple environments in addition to Production. This multi-environment structure enables them to develop and test county-specific forms and reports, conduct ongoing practice sessions and staff training, and support continuous learning without disrupting live operations.

Available non-production environments include:

• Training Environment – For staff training and onboarding
• County/Organization Dev Environment – Specifically for forms and report authors to continue development work. This environment will have non-production (test/simulated) data
• Readiness Environment – For ongoing practice and readiness activities. This environment will have production data (refreshed from the Production environment at a yet TBD interval). Can also be used for testing county-developed forms and reports against production data

A: If counties are in need of CWDS Website log-in support, please contact Customer Relations.

A: CWS-CARES will have one consistent location for documenting re-entry into EFC activities, so that documentation can be better captured and monitored by the county. The user will be able to manage all of the tasks required when an eligible young adult wishes to re-enter EFC, and the system will prompt the user to complete the required tasks. Training materials are being developed to guide this process. There are various points of re-entry, including at screening and within case units of work. A recent demo is available on the CWDS website under Case Management, titled "Extended Foster Care - Initial Entry & Re-Entry into EFC".

A: Data mapping sessions determine what does or does not have a place in CWS-CARES.

Most Binti data aligns with CWS-CARES and converts successfully. County-specific or Binti-specific fields are reviewed during mapping, including:

• Administrative fields
• County-specific process fields
• Binti administrative/technical fields
• Data with no CWS-CARES equivalent

A: You can find Process Information Session recordings and meetings here: CWS-CARES Process Information Session Materials.

Note: You must log in to the Implementation Portal using your county/organization email address to access these files.