Frequently Asked Questions

Q: What ticketing tool will be used during Production Simulation to log incidents? If it is ServiceNow, will counties receive training, and if so, when?

A: At least during Phase 1, ServiceNow will be used for logging incidents for Tier 2 to work on. County/organization Tier 1 teams will be able to log tickets using the ServiceNow portal (CSM). Otherwise, county users who are not Tier 1 should reach out to their Tier 1 staff or contact Tier 2, and Tier 2 will log the ticket in ServiceNow. Tier 1 will receive dedicated overviews of how to create a ServiceNow incident.

Q: Is there an Admin training module in Train-the-Trainer (TTT)?

A: The Train-the-Trainer (TTT) curriculum mirrors the Instructor-Led Training (ILT) curriculum, which includes an Administrator (Help Desk) course.

Q: Is there help desk or service desk specific training?

A: Yes. Service desk/help desk personnel have role-specific On-Demand courses. The recommended audience in the Instructional Design Maps indicates the ILT courses the CWS-CARES Team feels would support this group of people the best. However, you may choose to assign ILT courses that do not indicate service/help desk personnel as the target audience if you feel the content covered aligns with the tasks performed by the individual.

Q: Will current feedback items be compared to feedback that was given during previous Extended User Scenario Testing (EUST) periods?

A: Yes, the EUST 3 feedback items have been compared against the feedback submitted during the first two EUST cycles as the Product Team reviewed each item. As part of our analysis, we reviewed the product backlog all three periods to identify recurring themes, confirm whether previously reported issues had been addressed, and assign appropriate determination type for each feedback item. We understand that some items may still appear during Production Simulation. In many cases, these items are already scheduled for updates in upcoming releases, are in progress, or require further validation to ensure the solution meets user expectations. Production Simulation is intended to provide counties with another opportunity to confirm whether previously reported items have been resolved and to surface anything that still needs attention. Our goal is to ensure counties feel heard and that feedback from all EUST cycles is thoroughly considered as we prepare for rollout.

Q: Were users contacted for the Extended User Scenario Testing (EUST) 3 items that were categorized as "can't replicate?"

A: Users were contacted to request the additional information needed to accurately triage and prioritize the issue. If no response was received, the item remained categorized as 'Unable to Replicate' because the project team could not reproduce the issue without further details.

Q: Why were some users invited to provide Extended User Scenario Testing (EUST) 3 feedback and not invited to Production Simulation?

A: Participation in the current phase of Production Simulation was based on whether users participated in EUST 3. Our goal for this phase was to start with users who are already familiar with the system’s navigation and processes, so they can help validate updates and identify any remaining issues efficiently. Additional phases of Production Simulation will expand participation to a wider tester group, allowing more users to provide feedback as we progress.

Q: How are you planning to consolidate Production Simulation feedback with existing Extended User Scenario Testing (EUST) feedback?

A: All feedback from Production Simulation and EUSTs follows the same process and is reviewed by the same team. All feedback is evaluated collectively alongside all other feedback received.

Q: How will County Help Desk staff be expected to take over support without completing the required training, and will the support transition timeline vary by county based on training schedules? The current plan suggests that County Help Desk support begins in July, yet the CWS‑CARES trainings required for Help Desk staff in Riverside do not begin until August–September.

A: The Project is working on confirming timelines and a plan to support those counties. Once those are available, they will be released through a formal communication.

Q: Will the project hold post Go-Live check points with county help desks during the first few weeks post Go-Live?

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.

Q: Can counties build flexibility into Binti contracts in case of any unexpected issues with CWS-CARES V1 go-live?

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.