Frequently Asked Questions
Q: Will the RFA Applicant Portal be available in Spanish? It really needs to be.
A: The portal is in English, however, for users who need a different language option, they will have to use their browser configuration to select their language of choice for display purposes.
Q: Will CWS-CARES interface with Binti?
A: Binti is not an approved interface for CWS-CARES V1. CWS-CARES V1 will include complete RFA functionality.
Q: Will supervisors be able to see data from different counties? If so, will it be editable or read-only?
A: Access to data will be determined by counties during an implementation activity called Security Role Mapping. During this activity, county implementation teams will have the ability to assign security roles to users which will define what they will be able to access in CWS-CARES and if they have the ability to edit or read-only.
Q: How did we come up with the time commitment estimates for the county implementation teams?
A: The estimates provided for each of the implementation roles are based on past experience designing and delivering similar implementations for other statewide IT projects. They are intended to be a range and will vary by organization. We anticipate these time commitments to increase as we advance towards Go-Live.
Q: Will Organizations have the flexibility to use their preferred virtual meeting platform, or will all meetings need to be conducted over WebEx?
A: In general, the State uses WebEx, but we have to be flexible to meet our organization's needs. The RUGs meetings belong to the counties and they use the format they prefer.
Q: When will feedback submitted by counties be reflected?
A: Feedback is tracked and prioritized by the Product Team. There may be some system limitations, and enhancements may be added after V1 Go-Live.
Q: How can team members be added to meetings to show progress on the system?
A: All Implementation Leads (ILs) attend the weekly PDT Standup on Fridays where demos are provided. In addition, ILs are assigned to each Service Area where designs are discussed with the core constituents. Functionality is also reviewed and practiced each week during Office Hours: Staging Environment Practice meetings.
Q: When will counties be able to see/tailor the process changes for to the new system?
A: Organization Change Management (OCM) has completed the As-Is process maps and is building the To-Be process maps along with Change Impacts as functionality is being completed. OCM will present these to counties according to the Implementation Roadmap.
Q: How can team members join the Organizational Change Management (OCM) or Training Advisory Workgroups?
A: Participants for the OCM and Training Advisory workgroups were recruited from the regional RUGs meetings. Each region submitted several names to participate. Others interested can contact their Regional Chair through their SPOC in the case that there are future openings.
Q: What is the difference between the Organizational Change Management (OCM) Advisory Workgroup and the Counties' Organizational Change Management (OCM) Coordinators?
A: The OCM Advisory Workgroup is a larger overreaching group comprised of select people from different counties within each region and is used as a forum to gather counties perspectives on the materials and communications. This group will assist the OCM branch of the Implementation Team in creating global To-be processes, validate communication products like email announcements, FAQs, and will participate in various stakeholder engagement activities such as system demos, videos, and change impact analysis. The County OCM Coordinator works directly within their county only and handles county specific communication and OCM activities. Things like leading and supporting staff through migration, coordinating tailoring and delivery of communications, and understanding and tailoring as-is and to-be business processes to align with county processes and procedures.