Cal SAWS Project Steering Committee Meeting July 18

Cal. SAWS | Project Steering Committee Meeting July 18, 2019 Cal. SAWS | Project Steering Committee Meeting 1

Agenda 1. Call Meeting to Order 2. Agenda Review 3. Public Opportunity to speak on items NOT on the Agenda. Public comments are limited to no more than three minutes per speaker, except that a speaker using a translator shall be allowed up to six minutes. NOTE: The public may also speak on any item ON the Agenda by waiting until that item is read then requesting recognition from the Co. Chair to speak. Cal. SAWS | Project Steering Committee Meeting 2

Action Item Cal. SAWS | Project Steering Committee Meeting 3

Action Item 4. Approval of the Minutes of the: a. June 20, 2019 Cal. ACES PSC Meeting (move into the record only) b. June 28, 2019 Cal. SAWS PSC Meeting Cal. SAWS | Project Steering Committee Meeting 4

Informational Items Cal. SAWS | Project Steering Committee Meeting 5

Discuss Purpose/Expectations of Cal. SAWS PSC Cal. SAWS | Project Steering Committee Meeting 6

Purpose of Cal. SAWS PSC Cal. SAWS Bylaws – 4 th Amended § § Section VIII. A – “In addition to any duties assigned by the Board, the Project Steering Committee shall meet with the Consortium’s Executive Director and Consortium staff for Consortium status updates, to review and resolve outstanding Consortium issues and to provide feedback and insight regarding the direction of the Consortium. The Project Steering Committee shall also coordinate and communicate with the Members to ensure work products reflect a consolidated business approach, represent Member views in policy discussions that impact business practices, and serve as advisors and oversight for Consortium staff. ” Section VIII. A. 1 – “…members, or their designees, shall appoint personnel from their respective Regions to serve on project committees…” Section VIII. A. 2 – “…members or their designees, shall recruit personnel from their respective Regions to serve on workgroups, which are established from time to address specific Consortium and system(s)-related initiatives…” Section VIII. A. 3 – “Committee Attendance. All project Steering Committee members are expected to attend meetings. Committee member absences will be noted in the minutes. If a committee member who has been duly notified of committee meetings misses three (3) meetings within a one-(1) year period, the committee member shall be contacted formally and in writing requesting a written response of the member’s ability to continue participation in the committee. If a written response acceptable to the committee is not received within thirty (30) calendar days, then the committee member may be asked to resign for the cause. For instances in which a committee member’s absence is planned, the Project Steering Committee member from their respective Region, or their designee, may recruit a temporary committee replacement. Cal. SAWS | Project Steering Committee Meeting 7

Purpose of Cal. SAWS PSC Cal. ACES PSC Charter 03/16/2017 Primary Functions The Cal. ACES Steering Committee serves at the request of the Cal. ACES Joint Powers Authority Board of Directors and provides stabilizing influence so organizational concepts and directions are established and maintained with a visionary view. The Steering Committee provides insight on long-term strategies in support of legislative mandates and the JPA strategic priorities. Members of the Steering Committee ensure business objectives are being adequately addressed and the project remains under close guidance. In practice, these responsibilities are carried out by: § Meeting to obtain project status updates; § Monitoring and review of the project at regular Steering Committee meetings; § Reviewing and resolving outstanding escalated issues; § Provide feedback and insight regarding the direction of the Cal. ACES Consortium, which includes: • LRS Maintenance and Operations (M&O) • C-IV Maintenance and Operations (M&O) • Cal. ACES Migration D&I, and • Cal. ACES M&O procurement efforts. Approval Responsibilities The Steering Committee is responsible for approving major project elements such as: § Prioritization of project objectives and outcomes as identified by the JPA strategic priorities, state stakeholder initiatives or escalated committee priorities; § Release schedule; § Risk management strategies, ensuring that strategies to address potential risks to the project’s success have been identified, estimated and approved, and that the risks are regularly re-assessed. Cal. SAWS | Project Steering Committee Meeting 8

Purpose of Cal. SAWS PSC Cal. ACES PSC Charter 03/16/2017 continued Role of a Steering Committee Member It is intended that the Steering Committee leverage the expertise and insight of key individuals from the Regions. Steering Committee members are not directly responsible for managing project activities, but provide support and guidance for those who do. Thus, individually, Steering Committee members should: § Understand the strategic implications and outcomes of initiatives being pursued through project outputs; § Value the significance of the project for some or all major stakeholders and represent their interests; § Be genuinely interested in the initiative and be an advocate for broad support for the outcomes being pursued in the project; In practice, this means that they: § Review the status of the project; § Help ensure the project's outputs meet the requirements of the business owners and key stakeholders; § Help balance conflicting priorities and resources; § Provide guidance to the project team and users of the project's outputs; § Consider ideas and issues raised; § Foster positive communication within the regions and between the regions and Project; facilitating resolutions as needed. § Report on project progress to those responsible at a high level, such as agency executive management. Cal. SAWS | Project Steering Committee Meeting 9

FY 19/20 PSC Meeting Schedule Cal. SAWS | Project Steering Committee Meeting 10

Meeting Day Date/Time Location In-Person/Conference Call PSC Meeting (July) Thursday 07/18/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Norwalk Preferred In-Person Conference Call Avail. PSC Meeting (August) Thursday 08/15/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Rancho Cordova Preferred In-Person Conference Call Avail. PSC Meeting (September) Thursday 09/19/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Norwalk Preferred In-Person Conference Call Avail. PSC Meeting (October) No Meeting PSC Meeting (November) Thursday 11/21/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Roseville, CA Preferred In-Person Conference Call Avail. PSC Meeting (December) Thursday 12/19/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Norwalk Preferred In-Person Conference Call Avail. PSC Meeting (January) Thursday 01/16/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Roseville Preferred In-Person Conference Call Avail. PSC Meeting (February) Thursday 02/20/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Norwalk Preferred In-Person Conference Call Avail. PSC Meeting (March) Thursday 03/19/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Rancho Cordova Preferred In-Person Conference Call Avail. PSC Meeting (April) Thursday 04/16/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Norwalk Preferred In-Person Conference Call Avail. PSC Meeting (May) Thursday 05/21/2019 9: 00 a. m. – 3: 00 p. m. Cal. SAWS Rancho Cordova Preferred In-Person Conference Call Avail. JPA/PSC Annual Conference Meeting Wednesday - 06/24/2020 – Friday 06/20/2020 TBD In-Person Cal. SAWS | Project Steering Committee Meeting 11

Brown Act Training Cal. SAWS | Project Steering Committee Meeting 12

Cal. SAWS PSC An Overview of the Brown Act July 18, 2019 Presented by Jeffrey A. Mitchell

Purposes Of The Brown Act § Three purposes of the Brown Act: 1. To ensure that the decision-making process of legislative bodies is conducted in public § Exceptions: no quorum or meeting in closed session 2. To provide notice of the items to be discussed or the action to be taken by the legislative body by posting agendas in advance of the scheduled meeting 3. To guarantee the right of the public to address legislative bodies on matters within the jurisdiction of those bodies § Allow comments before deliberations - no requirement to answer questions

What Are “Legislative Bodies”? § The Cal. SAWS Board of Directors § Also covers committees created by “formal action” of a legislative body Cal. SAWS: Project Steering Committee, System Subcommittees (created by By-laws) § Examples of what are not legislative bodies? Advisory committee made up of less than a quorum of the legislative body with no continuing jurisdiction or fixed meeting schedule Committees that are not formed by formal action of a legislative body, e. g. : § Appointed by regional managers or individual directors § Appointed by the chairs of the committee without approval by the full committee

What Is A “Meeting? ” § Any congregation of a majority of the members of a legislative body at the same time and place to hear, discuss or deliberate upon any item within its subject matter jurisdiction. (Gov. Code § 54952. 2. )

“Meeting” Does Not Include: § Individual contacts between legislative bodies and any other person. (Gov. Code § 54952. 2(c)(1). ) § Attendance by a quorum at: Conferences Public meetings of other legislative bodies discussing some topic of local concern Social & Ceremonial events Committee meetings with non-committee members present as observers § Non-committee members may observe so long as they do not participate in committee business in any fashion (i. e. , verbal, written, other input)

Serial Meeting Is A “Meeting” § A majority of the members of a legislative body shall not, outside an authorized meeting, use a series of communications of any kind, directly or through intermediaries, to discuss, deliberate, or take action on any item of business that is within the subject matter jurisdiction of the legislative body. (Gov. Code § 54952. 2. ) (Gov. Code § 6252. 7. )

Types Of Serial Meetings: § Daisy chain § A B C D…. § Hub and spoke § One person communicates the message to others. C l • B -- A -- D l E § Intermediaries § Emails, text messages, Facetime, Whats App, Skype etc. (See, Gov. Code § 54952. 2(b))

Teleconferencing § Teleconferencing is a meeting of individuals in different locations connected by audio and/or video electronic means. § Votes during teleconferencing must be taken by roll call. § Agendas must be posted at all teleconference locations. (Gov. Code § 54953(b)(3). ) • Each teleconference location must be identified in the notice and agenda at the time of posting, and each teleconference location must be accessible to the public. • The public must be allowed to address the legislative body at each teleconference location. • Teleconferencing must be conducted “in a manner

Agenda Requirements (Regular) § An agenda must be posted at least 72 hours prior to a regular meeting. § Items may be added to the agenda for a regular meeting as follows: When a majority determines that an “emergency” exists. (Gov. Code § 54954. 2(b)(1). ) • By a 2/3 vote of the legislative body present at the meeting (unanimous if less than 2/3 of members present), determination that • there is a need to take immediate action • the need for action came to the attention of the agency subsequent to the posting of the agenda. (Gov. Code § 54954. 2(b)(2). )

Agenda Requirements (special) § A notice (agenda), including the time, place and business to be transacted at the meeting, must be posted and distributed to each member of the legislative body and requesting members of the media 24 hours in advance of the meeting (Gov. Code § 54956) § Items may not be added to the agenda § Cannot make decisions on executive staff compensation, including fringe benefits § Not required to allow public comments on items not on the agenda

Posting Agenda on Website § Any public entity that maintains an agency Internet website must post the agenda of a regularly scheduled meeting of the governing Board at least 72 hours in advance on its website § Similarly, the public entity must post the agenda for special meetings 24 hours in advance

Conduct of Meetings § Public comment on items not on the agenda § Legislative body can not discuss, except limited question or direction to staff § Public comment on items on the agenda § Can place reasonable time limits on public speakers § Can ask speakers to identify, but can not require § Roll call vote not required, except when teleconferencing

Closed Sessions § Closed session procedural requirements (Gov. Code § 54957. 7): • The item must be described in the agenda unless “added on” at a regular meeting Prior to going into closed session, the legislative body must disclose in open session the items to be discussed in closed session and ask for public comment There a number of basis for closed session (i. e. personnel, labor and negotiation, pending litigation/significant exposure to litigation, real estate negotiations) Action taken in closed session must be publicly “reported out” after the action is final. The vote of each member of the legislative body who attended the closed session also must be reported out.

Violations § Brown Act contains cure and correct provisions for violations Appropriate cure and correct action should foreclose on possibility of future violations Curing violation may limit litigation risk § See Transparent. Gov Novato v. City of Novato (April 10, 2019, A 152324) ___ Cal. App. 5 th ___ § Brown Act violations also carry civil or potential criminal penalties

Thank You! For more information about our Public Agency Law Practice please visit us at www. kmtg. com

Cal. SAWS DD&I QA Update Cal. SAWS | Project Steering Committee Meeting 28

Introductions What the Consortium Can Expect § TEAM (Together Everyone Achieves More) – This theme embodies the spirit that the Clear. Best team brings to the Cal. SAWS project. The following themes reflect principles we intend to bring to the project: • Seek solutions not blame • No surprises • Provide proactive insights into problems and solutions • Bring clarity, creativity, and calmness to solving problems, interacting with the broader team and leading staff • Active engagement and collaboration § Transparency and Visibility – Forms the basis of trust. Further exemplified by open and authentic communication § Fact-based Approach to Decision Support – Surface relevant facts and details to support findings and recommendations Cal. SAWS | Project Steering Committee Meeting 29

Introductions- Our Team Clear. Best QA Team – DD&I QA Executive Wendy Battermann QA Project Manager Dan Dean QA PMO Lead Beena Amarnath QA Functional Manager QA PMO Specialist Tim King Kristin Pepper QA Conversion Lead Raj Ganesh QA Technical Manager Don Coffey QA Executive – Advisor Frank Ono QA Testing Manager Cheryl Hofmann QA Implementation Mgr. Abby Darrah QA Imp Lead - OCM Ivan Parra QA Technical Lead TBD QA UAT Lead Rachel Hernandez QA Sr. Admin Assist Julie Hereth Legend Key Staff Non-Key Staff Executives Cal. SAWS | Project Steering Committee Meeting QA BA/Tester Pandu Gupta QA Imp Lead - Training Gail Brown QA Technical Lead Dustin Lish QA Independent Testers/ UAT Leaders Donna Smith (Ind Test) Sindura Kompulari (Ind Test/UAT) Kim Sinclair (Ind Test) Lalitha Ramabhotla (Ind Test/UAT) 30

Introductions- Staff Experience Cal. SAWS | Project Steering Committee Meeting 31

Organization Charts Team Commitment and Location § Roles and Responsibilities – Begin with project orientation to ensure all staff are aware of roles, teammates and appropriate hand offs. § Empowerment – We give our team members the support and tools they need to do the job, as well as autonomy to use good judgment and serve the project as needed and directed by the Cal. SAWS management and Executive teams. § TEAM Philosophy – A culture of collaboration creates a positive and productive environment that facilitates progress. § Communication – Clear and transparent communication requires the ability to adjust to your audience and balance the level of detail provided appropriately to support awareness and informed decision-making. § Participation and Representation – Timely identification and escalation of issues, proactive consultation and diligent reporting is our standard. We consistently represent the best interests of the Consortium. § Team Dedication – Each one of the Clear. Best team members has been hand selected for this project. They possess not only a distinct awareness of the Cal. SAWS environment but a commitment to improved service delivery. § On-Site Presence – We understand the value of being physically co-located with our clients. § Skilled and Engaged Staff –We view our staff are our greatest asset. Our continual investment in them directly supports their individual professional development path and our collective ability to provide a high level of service to our clients. § Bringing Together Known Team Members – Although our team is a blend of Clear. Best and IFG staff, many of our proposed team members have worked together previously on notable projects and were an integral part of project success. Cal. SAWS | Project Steering Committee Meeting North primary Frank Ono Beena Armanath Tim King Julie Hereth Kristin Pepper Sindura Kompulari Lalitha Ramabhotla Pandu Gupta Raj Ganesh Ivan Parra Abby Darrah Donna Smith Both Dan Dean Cheryl Hofmann Rachel Hernandez Kim Sinclair South primary Wendy Battermann Don Coffey Dustin Lish Gail Brown TBD 32

Summary of team status As of July 15, 2019 § § § Rolled on 11 of our 19 fulltime resources per plan • Planned additions: +6 by September 2019, +1 by May 2020 (Implementation) Initiated reviews with Accenture and Consortium on initial Cal. SAWS Vendor Assessments: Work Plan, Conversion Plan, Test Plan, Business Architecture, and General Design Provided overview of DD&I QA team and services at Regional Manager’s meeting Provided overview of Deliverables process to Section Directors and Cal. WIN Exec. Director Added to relevant recurring meetings: Development teams, Status, SCRB/CCB, PSC, JPA, Section Directors, Regional Managers, and appropriate working team sessions Working on QA Deliverables • 69 unique deliverables (258 total with recurring ones) • Stored on Cal. SAWS Share. Point with team deliverables • 14 deliverables in process – submitted 5 Draft DEDs and completed overviews with Section Directors Cal. SAWS | Project Steering Committee Meeting DEL # 1 QA Management Plan DELIVERABLE NAME 2 QA Work Plan (Initial) 5 Deliverable Review and Assessment Plan 17 Assessment of DD&I Vendor Cal. SAWS Business Architecture Design 18 Assessment of DD&I Vendor Cal. SAWS General Design 33

System Automation Guidelines Cal. SAWS | Project Steering Committee Meeting 34

Core Automation Principles • Solutions shall maximize automation in SCR designs. • Solutions shall incorporate county design input from regional committees when determining level of automation in SCR designs. (Stakeholder input will be considered when appropriate. ) • Solutions support a singular interpretation of policy. • Solutions work for customers, counties of all sizes, and resources. • Solutions support multiple business processes where not enforced by policy (i. e. open vs. forced navigation). • Solutions account for future maintainability and system performance: • Allowing counties to maintain county specific data points (security, mileage rates, automated actions, etc. ). • Allow configurability, where appropriate, to align with system maintainability and performance SLAs. • Solutions may include a multi-phase approach to limit risk, potential impact, and/or meet stakeholder deadlines, when necessary. Cal. SAWS | Project Steering Committee Meeting 35

Core Automation Principles • • Solutions do not introduce a migration gap before Cal. SAWS implementation, unless otherwise agreed upon by Consortium Leadership. Solutions should avoid the introduction of redundant or duplicative functionality. Committees shall consider alternative approaches when: • Total count impacted is less than 1% of the Consortium volume for the given area (e. g. programs, tasks created, applications taken, issuances, etc. ). • There are viable alternatives available, for example: • Changing an individual county business process. • Manual system functionality (e. g. manual EDBC, template repository, ad hoc reporting, etc. ). • Time required to utilize alternative does not cause undue hardship on the Counties (e. g. worker/customer/staffing issues or delayed processing). • When the Counties (through the Committees) have not prioritized or requested the change. When possible, Alternate Procedures will be provided when system updates are not able to be implemented into the system. Cal. SAWS | Project Steering Committee Meeting 36

Cal. SAWS DD&I Overview Cal. SAWS | Project Steering Committee Meeting 37

Overview of Cal. SAWS Conversion Scope, Schedule and Milestones • Discuss Draft Data Retention Process/Policy Cal. SAWS | Project Steering Committee Meeting 38

Discuss Draft Data Retention Process/Policy Seeking Approval of the Cal. SAWS Conversions Data Retention Requirements (defined below) to be voted on at the August 2019 Project Steering Committee Meeting. Once approved, Legacy Data will be extracted from C-IV and Cal. WIN system databases (in accordance with these requirements) and provided to the Conversion team to begin the respective Cal. SAWS conversion transformation processes. Cal. SAWS | Project Steering Committee Meeting 39

Overview of Cal. SAWS Application Development Scope, Schedule, and Strategy • Review Cal. SAWS DD&I Release Management Plan Cal. SAWS | Project Steering Committee Meeting 40

Cal. SAWS Release Plan Overview Background • Cal. SAWS Software development will occur over a series of eight (8) Application Software Modifications and/or Enhancements Services (M&E) releases to the LRS (the “Cal. SAWS Releases”). • Delivery of Cal. SAWS General Designs will be in alignment with the defined Cal. SAWS Releases. The Cal. SAWS General Design documents will be in accordance with the current Cal. ACES design template. As each Cal. SAWS General Design is completed, it will be collected into a package of designs. This package will be assembled every other month as documented in the Cal. SAWS DD&I Work Plan. • There will be a single DED for Cal. SAWS General Design documents. As Cal. SAWS General Design Deliverables are approved, the Cal. SAWS design documents included within each approved Deliverable will be associated as artifacts to Cal. SAWS DD&I SCRs that will be created within the Cal. SAWS Project’s change management tool (Atlassian Jira). Additionally, development work for Cal. SAWS DD&I SCRs will commence upon approval of the Cal. SAWS DD&I SCRs by the designated Consortium approver, with testing and deployment activities to follow after approval of the Cal. SAWS General Design Deliverables. No additional approvals (e. g. committee/workgroup, SCR Planning Group or “SPG”, and Change Control Board) are required for these Cal. SAWS General Design Deliverables, inclusive of the package of designs for Cal. SAWS DD&I SCRs within each Deliverable, and the associated Cal. SAWS DD&I SCRs. • The Cal. SAWS Software requirements will be prioritized based on facilitating the conversion effort as proposed by the CONTRACTOR. For example, changes that add or modify data collection fields will have an inherent impact to conversion and will be prioritized earlier for development. • Cal. SAWS Software requirements will be uploaded to the Cal. SAWS RTM repository within the Cal. SAWS Change Management Control tool. As Cal. SAWS DD&I SCRs are created by the CONSORTIUM, the Cal. SAWS Software requirements will be linked to these Cal. SAWS DD&I SCRs to facilitate the Cal. SAWS DD&I RTM. Cal. SAWS | Project Steering Committee Meeting 41

Cal. SAWS Release Plan Overview Background • 387 Application Development System Requirements. • 36 requirements with CRFI impacts. Modeled in release 3 and onwards to allow for the CRFI turnaround time. Note, in order to meet the Release 3 schedule, CRFI responses would need to be received by September 2019. • 19 requirements identified as needing additional Committee or County input. Modeled in Release 3 and onwards to allow for design input. Cal. SAWS | Project Steering Committee Meeting 42

Cal. SAWS Release Plan Overview Project Schedule The Conversion team to provide converted data for the respective CIV and Cal. WIN Converted Data, UAT, and Interface Testing phases Cal. SAWS | Project Steering Committee Meeting 43

Cal. SAWS Release Plan Overview Release Approach • Small First Release – Ramp up teams. • Remaining Migration changes deployed through 7 LRS M&E releases. • Target Conversion and Training impacts in earlier releases. • Balance workload across releases and development teams. Cal. SAWS | Project Steering Committee Meeting 44

Cal. SAWS Release Plan Overview Current Status 1) 2) 3) 4) 5) 6) NOTES: Total Hours excludes reporting requirements as they are pending the analytic re-platforming approach and the 29, 000 -unforeseen allowance of hours The “Approved” status indicates that the DDID has been approved by the consortium contact The “Pending Approval” status indicates the draft design is complete is awaiting review by the consortium The “Pending Rejection” status reflects SCRs associated to DDID’s that will be removed with the approval of the next General Design Deliverable SCRs associated to DDID 1967 for the unforeseen allowance and DDID 1931 for the reports allowance are excluded Each release includes an SCR associated to DDID 713 for automated regression testing Cal. SAWS | Project Steering Committee Meeting 45

Cal. SAWS DD&I CRFIs Cal. SAWS | Project Steering Committee Meeting 46

Cal. SAWS DD&I CRFIs Background • 387 Application Development DD&I System Requirements • 36 requirements with CRFI impacts identified to date. • 4 week County turnaround time for CRFIs. • Requirements with CRFI impacts have been modeled in Cal. SAWS release 3 and onwards to facilitate the CRFI process and turnaround time. • For Release 3, in order to meet design deliverable milestones, CRFIs will need to be disseminated no later than August 1, 2019. Cal. SAWS | Project Steering Committee Meeting 47

Cal. SAWS DD&I CRFIs Suggested Approach • Host a CRFI County webcast on July 31 st to introduce the Cal. SAWS DD&I App Dev CRFI process. • Review the backlog of M&O and M&E SCRs to identify related changes that should also be prioritized for implementation. • Coordinate with Cal. WIN first to determine if the requested information already exists in their system. • Evaluate requirements with CRFI impacts to determine which items can be grouped together. • Draft CRFIs will be reviewed and approved by the Section Directors and Region Managers before dissemination. • Changes to CRFI responses post their Cal. SAWS release will be routed through the M&E County Enhancement Request (CER) process. CER’s will be prioritized for implementation based on the county go-live date, scope and effort, and Worker/County impact. Cal. SAWS | Project Steering Committee Meeting 48

Cal. SAWS DD&I CRFIs Suggested Approach • Group the 36 requirements into 10 CRFIs: • Release 3 - 4 CRFIs: CRFI Groupings Examples 1. Admin 2. CW/CF/MC 3. MEDS/IEVS 4. WTW Gathering County staff classification titles and program configuration administration display (CFET, IHHS/CMIPS II, etc. ). Opting in or out of automated negative action and form generation batch jobs. Opting in or out of MEDS alerts and automatic journal creation. Opting in or out of automated worker assignment based on program status or automation for WTW supportive services overpayments. • Release 4 - 2 CRFIs: CRFI Groupings Examples 5. Fiscal 6. Text Messaging Gathering Cal. WIN County's benefit issuance and collection information (County specific batch jobs, pay codes, valuable categories, etc. ) Opting in or out of automated text messages. • Release 5 – 2 CRFIs: CRFI Groupings Examples 7. MC 8. Homepage County Images Opting in or out of RE automated outbound calls and reminder notices. Gathering County images that represent the scenery, culture, and character of the 58 counties for the Cal. SAWS homepage. • Release 7 – 1 CRFI: CRFI Groupings Examples 9. FC Opting in or out of Foster Care, Kin-Gap and AAP automated batch jobs (e. g. aid code 45 automation for Foster Care) • Release 8 - 1 CRFI: CRFI Groupings Examples 10. Forms/Imaging Opting in or out of automated updates to the Periodic Reporting Detail page based on the imaging of forms and status. Cal. SAWS | Project Steering Committee Meeting 49

Cal. SAWS DD&I CRFIs Suggested Approach • CRFI Schedule: CRFI Groupings (10 CRFIs) 1. Admin 2. CW/CF/MC 3. MEDS/IEVS 4. WTW 5. Fiscal 6. Text Messaging 7. MC 8. Homepage County Images 9. FC 10. Forms/Imaging Grand total Cal. SAWS | Project Steering Committee Meeting Unique Req. Count 9 3 4 4 8 1 2 2 36 First Cal. SAWS Release impacted Release 3 (Mar 2020) Release 4 (May 2020) Release 5 (Jul 2020) Release 7 (Nov 2020) Release 8 (Jan 2021) CRFI Submission CRFI Response Due Date 8/29/2019 8/1/2019 10/29/2019 10/1/2019 12/30/2019 12/3/2019 4/29/2020 4/1/2020 6/29/2020 6/1/2020 50

Functional Design Sessions • • • Cal. SAWS | Project Steering Committee Meeting Update on Imaging Functional Design Next Steps Update on GA/GR Functional Design Next Steps Update on Functional Designs in progress 51

Imaging Functional Design Overview § The Imaging Functional Design sessions were held over a 6 week period representing all counties within the Cal. SAWS Consortium • Session Objectives: Centralized Imaging Solution for 58 counties integrated into the core application Provide the best solution based on feedback coming out of sessions • Reviewed requirements and business process flows • At the end of each week attendees agreed on the 6 individuals that would represent their region at the consolidated meeting in June 2019 § The information captured from each regions session was consolidated and updates were made to the imaging requirements § The imaging requirements and business flows were reviewed with the Counties at the consolidated meeting where all 6 Regions were represented. • Positive collaborative environment • Confirmed all updated requirements Cal. SAWS | Project Steering Committee Meeting 52

Imaging Functional Design Overview Imaging FD Kick off Apr 1 2019 Apr Imaging Review Sessions Begin Imaging Review Sessions Complete Apr 29 Jun 14 May Jun Present Regional Feedback Complete Jun 28 Handover Imaging Functional Design Jul 26 Jul Today Planning Phase Apr 1 - Apr 26 Review Sessions Region 6 Review Session Region 3 Review Session Region 2 Review Session Region 4 Review Session Region 5 Review Session Region 1 Review Session Consolidate Regional Input Consolidated Functional Design Session (all regions) Apr 29 - Jun 21 May 6 - May 10 May 13 - May 17 May 20 - May 24 May 28 - May 31 Jun 3 - Jun 7 Jun 10 - Jun 14 Jun 17 - Jun 21 Jun 24 - Jun 28 Create Imaging System Functional Design Jul 1 - Jul 26 Cal. SAWS | Project Steering Committee Meeting 53

Imaging Functional Design Solutioning & Approval Process Overview Cal. SAWS | Project Steering Committee Meeting 54

GA/GR Functional Design Session § GA/GR: • Session commenced on June 24, 2019. 78 participants representing the Counties State partners in attendance 77 Parking lot items captured – 31 continue to be researched for discussion during the second session, the remainder are closed • Second week is scheduled for July 23 and 24 2019 Agenda: q q Forms and Notices – Continued discussion and Demos Fiscal demonstration of LRS – Fiscal items from parking lot SSIAP Research findings – SSI items from Parking Lot Employment Service Program (ESP) » Review parking lot items related to ESP q Parking lot items and Final Requirement Validation Review Cal. SAWS | Project Steering Committee Meeting 55

Functional Design Sessions in Process Continued activities for the Functional Design sessions § Non-State Forms: • Functional Design Sessions commenced on July 8, 2019 and will continue through late August. § Task Management: • Functional Design Sessions commenced on July 8, 2019 and will continue through July 18, 2019. § APIs: • Continue to meet internally to plan for the Functional Design Sessions Cal. SAWS | Project Steering Committee Meeting 56

Cal. SAWS Cloud Migration Cal. SAWS | Project Steering Committee Meeting 57

Cal. SAWS Cloud Migration Roadmap to the Cloud 3 b 3 a JAN APR JUL SEP NOV JAN 2022 2022 2023 Cal. WIN Counties Go-Live: WAVES 1 – 6 • 6 waves of Cal. WIN countie go-live (conversion) into the Cal. SAWS system Jan 2022 through Jan 2023 C-IV Counties Go-Live • C-IV go-live (conversion) into Cal. SAWS system • Scale infrastructure 2 JUL Scaling for Statewide Usage • Tuning Online Transactions • Change to Batch 2021 July 2021 • New Reporting Platform 0 Test Results Oct 13 th 2021 OCT 15 TH (2019) Architecture Cloud Proof of Concept • Performance • Scale infrastructure SEPT 1 LRS Go-Live in the AWS Cloud • Build infrastructure 2018 • Plan and Estimate for Changes Cal. SAWS | Project Steering Committee Meeting • Work with stakeholders • Testing ROADMAP TO 58 -COUNTY CALSAWS SYSTEM IN THE CLOUD 58

Cal. SAWS Cloud Migration Cloud Enablement Phase 1 PHASE LEGEND Already Exists Building CLOUD US East 1 Region (DR) DATA CODE US West 2 Region Built LRS/Cal. SAWS LR S ENVIRONMENTS Migration Related C LRS/Cal. SAWS Database Replicas for Disaster Recovery Cloud Native Services Infrastructure/Security B Nor. Cal Cloud Exchange PMO Interface Partners ADF D So. Cal Cloud Exchange A Cal. SAWS Network SDWAN/MPLS Cal. SAWS | Project Steering Committee Meeting LA/Net Workers 59

Cal. SAWS LRS to AWS Summary Schedule Greenlight Meeting Project Start Oct 9 Oct 15 Mar 4 Mar LRS Go. Live Apr May Jun Jul Aug Sep Oct 2019 Today Phase 1: Moving LRS to AWS Cloud Technical Build Exchange / Security Technical Services / Upgrade Non-production Environment Delivery (Dev, AT, Conversion, YBN) Non-production Environment Delivery (Batch, Conversion, Perf) LA County Connectivity Production Environment Delivery Testing Integration Test Interface Partner Testing System Test Performance Test Issues/Risks County Validation Security and Operations Testing Phase 2: Architectural Scaling Issue: SSA Security Approval Risk: Funding for Part 2 of Cloud Cal. SAWS | Project Steering Committee Meeting 60

Lunch Cal. SAWS | Project Steering Committee Meeting 61

Cal. SAWS Staffing Status Cal. SAWS | Project Steering Committee Meeting 62

Cal. SAWS Staffing Status Tasks Completed or In Process § § § Two high priority technical management positions have been selected and will be included in the July 19 th RGS amendment Section Directors will identify remaining selections by July 24 th Executive Directors will review and approve selections by July 26 th PMO/Admin Team will coordinate with counties on preliminary selections to verify salary/benefit levels by July 31 st PMO/Admin Team will confirm Director approval for county employees by July 31 st Offer letters will be distributed to selected candidates by August 2 nd Candidates will respond to accept or reject by August 7 th Back-up candidates will be notified, if needed, by August 9 th Selected candidates to begin transition following position acceptance, according to individual and county situations PMO will prepare draft Regional Government Services (RGS) amendment for candidates selected from the public (salaries to align to LA County ranges) JPA Board to review and vote on RGS amendments during the July and August Board Meetings, with potential additional amendments to follow PMO will coordinate with counties to set up allocations during the month of August Cal. SAWS | Project Steering Committee Meeting 63

Cal. SAWS Staffing Status Back-Fill Approach § § § Additional resources with specific skill sets to support M&O are needed Leverage the LRS QA Agreement which allows for Separate Services Immediate Solution: Leverage the Professional Services allowance already available within the contract with authorization from the Cal. SAWS Executive Director Next Step: Amend the contract to account for the cost increase, along with an extension from March 2021 through September 2021 and secure State and federal approval, followed by the JPA Board approval M&O Consortium Personnel funding will be utilized for these services (Cal. WIN M&O for Cal. WIN staff, Cal. ACES M&O for Cal. ACES staff) Cal. SAWS | Project Steering Committee Meeting 64

Review the scope and status of the Accenture Amendment going through State/Federal review Cal. SAWS | Project Steering Committee Meeting 65

LRS Amendment Overview Amendment 15 Exhibit W Statement of Work for Cloud Enablement and Interim M&O continues work started as part of the Cloud Bridge and includes M&O for LRS October 2019 through September 2021 for $34. 1 M § Schedule 1 – Contractor Assumptions § Schedule 2 – Cal. SAWS Cloud and Initial M&O Pricing Schedule § Schedule 3 – AWS Compute Resource Specifications (estimates only, not part of LRS agreement) § Schedule 4 – Hardware/Software Specifications (estimates only, not part of Exhibit W price, will be included in C-IV Agreement) § Schedule 5 – Initial M&O Prod Ops Specifications Exhibit X Cal. SAWS Maintenance & Operations Extension effective October 2021 through October 2023 for $250 M. Includes 40 county M&O and expands to 58 county M&O § Attachment 1 to Schedule 1 to Exhibit X – Contractor Assumptions § Attachment 2 to Schedule 1 to Exhibit X – Pricing Schedules (these are the costs as of October 2023) § Attachment 3 to Schedule 1 to Exhibit X – HW SW Specifications (estimates only, not part of Exhibit X price, will be included C-IV Agreement) § Attachment 4 to Schedule 1 to Exhibit X – Prod Ops Specifications § Schedule 1 to Exhibit X - Statement of Work for Cal. SAWS Maintenance and Operations Project) (this is the new scope for extended M&O as of October 2023) § Schedule 2 to Exhibit X - Statement of Work for Cal. SAWS DD&I Project) § Schedule 3 (Schedule of Payments) § Schedule 4 (Services To Be Performed in GDN – Security, Access and Technology Requirements) § Schedule 5 (Accenture Performance Guarantee) § Schedule 6 (Performance Bond) § Schedule 7 (Performance Requirements) § Schedule 8 (Contractor Employee Acknowledgement, Confidentiality, and Copyright Assignment Agreement) § Schedule 9 (Contractor and Subcontractor Staff Criminal Conviction Notice and Certification) § Schedule 10 (Required Subcontract Provisions) § Schedule 11 (Contractor’s Equal Employment Opportunity Certification) § Schedule 12 (IRS Notice 1015) Exhibit Y Work To Be Performed in Global Delivery Network (GDN) – Security, Access and Technology Requirements to address offshore scope and terms Cal. SAWS | Project Steering Committee Meeting 66

Exhibit W - Cloud Enablement & Interim M&O Statement of Work Exhibit W includes the services to re-platform the LRS application from its on-premise datacenter to AWS (continuation of the Cloud Bridge), as well as Interim M&O for the LRS application on the AWS cloud-hosted architecture through the C-IV Counties’ cutover to the Cal. SAWS Software (through September 2021 service month). Task 1 – Project Management Task 2 – Network Task 3 – Environment Deployment and Support Task 4 – Application Architecture (Technical Services) Task 5 – Application Development Task 6 – Analytics Task 7 – Innovation Lab Task 8 – Interim Maintenance and Operations Cal. SAWS | Project Steering Committee Meeting 67

Exhibit W - Cloud Enablement & Interim M&O Statement of Work Task Description Task 1 – Project Management § § § Day-to-day operations Work plan management Financial management Task 2 – Network § § AWS Direct Connect Enabled Upgrade southern location office network AWS multi-account configuration Enhanced county to cloud network connectivity Task 3 – Environment Deployment and Support § § § Development environments Training environments Test Environments Conversion environments Technical reference environment Monitoring and support for environments Cal. SAWS | Project Steering Committee Meeting 68

Exhibit W - Cloud Enablement & Interim M&O Statement of Work Task Description Task 4 – Application Architecture (Technical Services) § § § § Cal. SAWS | Project Steering Committee Meeting WCC ( Web. Center Content) Transition Adobe as a Service enablement Technical Services Application transition from Oracle data store (AMP, Audit, LMS Lite, LRS Dashboard) Phonetic Search Optimization YBN ( development env ) transition to AWS Database Upgrade Data Migration Activities (start document migration, transactional data base in sync with on-prem, start DW data migration) 69

Exhibit W - Cloud Enablement & Interim M&O Statement of Work (Remediation for Scalability) Task Description Task 5 – Application Development § § § MEDS batch interface processing was not able to scale for 58 counties, running outside of the nightly batch window. Programming logic to be modified to event-based processing for outbound MEDS transactions in a real time fashion leveraging *cloud streaming capabilities throughout the day and the outbound file sent to MEDS in the evening. CCSAS batch interface processing was not able to scale for 58 counties, running outside of the nightly batch window. Programming logic to be modified to event-based processing for outbound CCSAS transactions in a real time fashion leveraging *cloud streaming capabilities throughout the day and the outbound file sent to CCSAS in the evening. EDBC (Eligibility Determination Benefit Calculation) online & nightly processing to be further tuned to take advantage of event-based processing to meet Service Level Agreements. * The cloud streaming capabilities are also used in conjunction with the Analytics infrastructure. Cal. SAWS | Project Steering Committee Meeting 70

Exhibit W - Cloud Enablement & Interim M&O Statement of Work (Remediation for Scalability) Task Description Task 6 – Analytics § § Cal. SAWS | Project Steering Committee Meeting Existing reporting infrastructure was not able to scale to support 58 counties. A new cloud native analytics infrastructure to be deployed to support scalability of existing Cal. SAWS operational and state reports. Leverage the real time cloud streaming capabilities to support business operational needs such as real time report dashboards. Create a data lake to take advantage of enhanced cloud capabilities such as the ability to handle unstructured types of data sources to support strategic and policy analysis. Utilize modern data visualization tools for an enhanced, more user friendly experience in accessing data. 71

Exhibit W - Cloud Enablement & Interim M&O Statement of Work Task Description Task 7 – Innovation Lab § § Evaluation of emerging technologies Integration of selected technologies Task 8 – Interim Maintenance and Operations § § WAN Administration Service Desk Operations Cal. SAWS | Project Steering Committee Meeting 72

Exhibit W - Cloud Enablement & Interim M&O Summary of Costs Cal. SAWS | Project Steering Committee Meeting 73

Exhibit X - Maintenance & Operations Statement of Work Exhibit X Schedule 1 includes Modifications and Enhancements (M&E) services, Technical Infrastructure services, Production Operations, Innovation Lab services, and support processes, tools, and procedures required to maintain and operate the Cal. SAWS System. The term of Exhibit X begins with the completion of the CIV Counties’ cutover to the Cal. SAWS Software. Task 1 – Modifications and Enhancements Task 2 – Technical Infrastructure Task 3 – Production Operations Task 4 – Innovation Lab Cal. SAWS | Project Steering Committee Meeting 74

Exhibit X - Maintenance & Operations Statement of Work Task Description Task 1 – Modifications and Enhancements § § Task 2 – Technical Infrastructure Cal. SAWS | Project Steering Committee Meeting § § § Cal. SAWS Software Modifications and Enhancements (“M&E”) Overall ongoing management of work for System Change Requests (SCRs) for the Cal. SAWS Software Northern Location and Southern Location Support Database Management Performance and Stress Test Application Architecture Maintenance System Administration Technical Management Hardware and Software Purchasing Support Imaging System Support Contract Center Reporting Network Administration Remote Hardware Maintenance 75

Exhibit X - Maintenance & Operations Statement of Work Task Description Task 2 – Technical Infrastructure (Continued) § § § § § Cal. SAWS | Project Steering Committee Meeting Central Repair Central Print Operations Support Service Desk Batch Support Level 3 Support Production Support Enhanced Application Level 3 and Production Support Technical Infrastructure Services for Cal. HEERS Interface Technical Infrastructure Services for Cal. SAWS Cloud Reports/Analytics Project Management (PMO) 76

Exhibit X - Maintenance & Operations Statement of Work Task Description Task 3 – Production Operations § § § Task 4 – Innovation Lab Cal. SAWS | Project Steering Committee Meeting § Wide Area Network (WAN) Administration Production Operations Support – Services Desk Operations Support; Central Contact Center System Support; Managed Workstations; Managed Windows 10 Workstation Images; Managed Scanner Maintenance; Managed Lobby Management Device Support Central Print for 40 Counties Services for the evaluation of emerging technologies and integration of selected technologies into the Cal. SAWS platform. 77

Exhibit X - Maintenance & Operations Summary of Costs Cal. SAWS | Project Steering Committee Meeting 78

Exhibit Y – Global Delivery Network Overview § Establishes the security, access and technology requirements for the performance of Work in the Global Delivery Network (GDN) § Key Requirements • Requires work to be performed within a secure bay with respect to PII or PHI • Restricts activities to unit, assembly, and automated regression testing, and cannot be applied to activities related to business rules engine, generation of State reports or UAT Cal. SAWS | Project Steering Committee Meeting 79

Overview of the Cal. SAWS IAPDU Cal. SAWS | Project Steering Committee Meeting 80

Overview of the Cal. SAWS IAPDU Key Changes § The September 2018 IAPD was approved on February 15, 2019 and is now available to the public on our website at: http: //www. calaces. org/board_meetings. html § The approved baseline has been updated with the June 2019 IAPDU and includes the following changes: • Schedule Update • Addition of DD&I County Support Staff for Cal. WIN • Updates to GA/GR • Updates to Quality Assurance • Expansion of Independent Verification & Validation (IV&V) • Updates to Cloud Enablement • Updates to Amazon Web Services (AWS) • Updates to Hardware/Software • Updates to M&O Services § To accommodate the expected additional scope and costs associated with GA/GR, the county share of costs for GA/GR Application Development will be shared across 57 counties (LA County retains existing solution) Cal. SAWS | Project Steering Committee Meeting 81

Cal. SAWS Communications Overview • Cal. SAWS Enhanced Communication Roadmaps Cal. SAWS | Member Representatives and JPA Board Meeting 82

Cal. SAWS Communication Roadmap Overview Release 19. 11 November 25, 2019 LRS Go-Live in the AWS Cloud October 15, 2019 AWS Connect April 10, 2020 Cal. WIN Migration Jan 2022 - Jan 2023 C-IV Conversion September 1, 2021 Cal. SAWS | Member Representatives and JPA Board Meeting Cal. SAWS | Member Representatives and PSC Meeting 83

LRS Go-Live in the AWS Cloud Communication Roadmap Build Jun – Sept County Confirm. Aug – Oct LRS Go-Live Oct 15 October 16 October 7 Post-Implementation Checkpoint Conference Call ‘Planned Outage’ Broadcast to LRS Users September 30 Mid-September ‘LA County Impact’ Broadcast to LRS Users Early August Project Informational Alert on Cloud Environment Services Plan CRFI for LA County Confirmation July 15 – October 18 LRS to AWS Go-Live Prep: Bi-Weekly Help Desk Planning Discussions; Monthly Status Updates with State Stakeholder Cal. SAWS | Member Representatives and JPA Board Meeting May 22 – August 14 Bi-weekly Interface Partner Connectivity Planning Meetings 84

Cal. SAWS Release 19. 11 Communication Roadmap R Build Completion December 4 Cal. SAWS 19. 11 Post-Release Checkpoint Sept 27 fects Build Completion Nov 1 lease Greenlight Nov 20 lease Date Nov 25 November 7 October 16 Cal. SAWS Webcast on Release 19. 11 Release Notes sent for Consortium Review End of August June 27 First Bi-weekly Cal. SAWS Release Comms Planning Meeting Cal. SAWS | Member Representatives and JPA Board Meeting LA County completes SCR Review & Project begins preparation of Release Comms June 13 LA County Review of 19. 11 SCRs Begins 85

Overview of Federal Report Cal. SAWS | Project Steering Committee Meeting 86

Federal Report Overview for June 2019 Cal. SAWS | Project Steering Committee Meeting Cal. SAWS | Click View > Master > Slide Master to change 87

State Partner Update on Cal. SAWS Activities • OSI • CDSS • DHCS Cal. SAWS | Project Steering Committee Meeting 88

M&O Application and Operations Update Cal. SAWS | Project Steering Committee Meeting 89

Policy Update Funding for Emergency Caregivers Policy Effective Date & State Letter Reference C-IV Status LRS Status Implementation Details 7/1/2018 SCR 102237 SCR 204665 ACL 18 -75 Implemented Per ACL 18 -33, all counties were required to provide the Short-Term, Interim payment (AB 110) to caregivers who had taken placement of a child prior to completing the Implemented Resource Family Approval (RFA) process between 3/30/2018 and 06/30/2018. CFL 18 -19/81 Release 18. 11 Draft ACWDL Aid Code 5 L SCR 101497 Design in Progress Effective July 1, 2018, all counties must provide a payment equivalent to the basic level rate for a resource family to the Emergency Caregiver (EC) of a child. However, unlike the Short-Term, Interim funding, the EC funding will be exclusively funded SCR 203634 through the Emergency Assistance (EA) Program, aid code 5 K. For more information refer to ACL 18 -75. Implemented Under the current program, relative caregivers and NREFMs are eligible for payment for up to six months during the approval process in 2018 -19, and in 2019 -20 are Release 19. 01 eligible for up to three months of payments, funded primarily under the Emergency Assistance TANF program. SCR 205913 Aid code 5 L will be used to identify the emergency caregiver placements that are not eligible to federal foster care funding and they are not eligible to emergency assistance Design in funding. Aid code 5 L is available in MEDS. Progress Release 20. 01 Implemented Release 19. 01 SCR 102912 On 3/19/19, SAWS received a draft copy of the ACWDL for aid code 5 L, the release date for the ACWDL is TBD. The CFL for aid code 5 L was published on 5/10/19. Cal. SAWS | Project Steering Committee Meeting 90

Policy Update Cal. WORKs Maximum Aid Payment (MAP) Increase Policy C-IV Status Effective Date & State Letter Reference LRS Status Description – Cal. ACES Implementation Effort 10/1/2019 C-IV-103092 CA-206231 Design Release 19. 07 The MAP increase applies to all Cal. WORKs cases, regardless of whether the Assistance Unit (AU) lives in Region One or Region Two and regardless of the AU’s Exempt or Non-Exempt status. The CWDs are to treat the grant increase as a mandatory county-initiated mid-period action for Semi Annual Reporting (SAR) and Annual Reporting/Child Only (AR/CO) cases. Draft ACL Received on 7/3/19 C-IV-103090 CA-206229 Design Release 19. 07 C-IV-104521 CA-209326 Design Release TBD Cal. SAWS | Project Steering Committee Meeting Cal. WORKs and Cal. Fresh recipients must be notified of changes to their Cal. WORKs grant and the associated impact of the household’s Cal. Fresh benefits no later than September 15, 2019. Cal. SAWS Updates: • Send the mail mass mailer to all active CW recipients by 9/15/19 • Update the CW MAP values • Add the new MAP increase Notice of Action fragment • Run batch EDBC on the impacted CW and CF cases 91

Policy Update Cal. Fresh SSI/SSP Expansion Policy Effective Date & State Policy Reference C-IV Status LRS Status Description – Cal. ACES Implementation Effort 6/1/2019 SCR 102555 (e. ICT) SCR 205294 (e. ICT) e. ICT Updates and the NOAs associated to ICTs are scheduled for implementation in July 2019. System Test Release 19. 07 SCR 103739 (Allow ESAP for SSI Households) SCR 207629 (Allow ESAP for SSI Households) • Child Support income not being counted for an SSI child receiving Direct Child support. System changes are targeted for the 19. 07 release. Tested • Nutritional Benefit issuances are appearing on Cash issuances reports. System changes are targeted for the 19. 07 release. Release 19. 07 SCR 102560 (Threshold Language NOAs/Forms) SCR 205319 (Threshold Language NOAs/Forms) Build Release 19. 09 ACL 18 -90 ACL 18 -91 ACL 18 -92 Cal. SAWS | Project Steering Committee Meeting Cal. ACES Update: • SSI/SSP only Cal. Fresh households are not being determined eligible to ESAP. System changes are targeted for the 19. 07 release. • Cal. Fresh cases that are PA/CE and all members are receiving SSI benefits are receiving Cal. Fresh NOAs where the income reporting threshold (IRT) amount is not populated. LRS system changes are targeted for the 19. 07 release. 92

Policy Update Cal. Fresh Notice of Expiration of Certification (NEC) Policy Effective Date & State Policy Reference C-IV Status LRS Status Description – Cal. ACES Implementation Effort 6/1/2019 SCR 102315 SCR 204834 CDSS has updated the NEC form to comply with federal requirements as they apply to requisite language that must be included on the form. Further revisions to the form include removing language only relevant before Simplified Reporting was implemented in 2013, as well as additional revisions. The NEC form was also revised to update language regarding Cal. Fresh eligibility for Supplemental Security Income and/or California State Supplementary Payment (SSI/SSP) recipients. ACL 18 -118 Tested Release 19. 07 Cal. ACES Update: The CF 377. 2 (Notice of Expiration of Certification) 9/2018 version provided in ACL 18 -118 will be added to the systems. This update will include adding the English and all currently system available Threshold Languages. LRS Existing Threshold languages for CF 377. 2: Armenian, Cambodian, Chinese, Korean, Russian, Spanish, Tagalog, and Vietnamese. C-IV Existing Threshold languages for CF 377. 2: Arabic, Armenian, Cambodian, Chinese, Hmong, Lao, Farsi, Korean, Russian, Spanish, Tagalog, and Vietnamese. The translated versions came back from the translation vendor on 6/3/19. Cal. SAWS | Project Steering Committee Meeting 93

Policy Update Able-Bodied Adults Without Dependents (ABAWD) Policy Effective Date & State Policy Reference C-IV Status LRS Status Description – Cal. ACES Implementation Effort 1/1/2017 Fixed Clock SCR 7215 Phase II SCR 57971 Phase II 8/31/2019 Waiver Expires Build Release 19. 09 ABAWD implementation began in September 2018 for San Francisco, San Mateo, and Santa Clara. The remaining counties are on waiver until 8/31/2019. In September, CDSS submitted another ABAWD waiver request to FNS for the time period 9/1/2018 -8/31/2019. If the waiver is approved, three additional counties (Alameda, Contra Costa, and Marin) will be required to implement the ABAWD policy effective September 2019. The ABAWD Handbook version 2. 0 draft was sent to the counties for review on July 1, 2019. ACIN I-11 -16 ACIN I-88 -16 ACL 18 -08 ABAWD Handbook Cal. ACES Update: The SCR design was sent to the CW/CF committee on 5/3/2019 and the project met with CW/CF committee on 5/6/19 to review the design. Committee touch point meetings are scheduled for 5/20, 5/29, and 5/30. The purpose of the meeting on 5/30 is to review the final design for committee approval. The committee approved the design on 5/30/19. A CIV functional presentation is being created for these changes. Phase II changes include the following: • Updates to ABAWD exemption logic • Updates to Count persons as ABAWD in a partial month • Provide a manual way for case workers to indicate whether the ABAWD work requirement was met • Add a task and batch EDBC closure for ABAWD that does not meet work requirement and has no other exemption, good cause, etc. • Provide a way to track whether an ABAWD regained eligibility by meeting the work requirement • Add new ABAWD MEDS codes, calendar, and transactions • Updates to Time Limit data collection pages • New NOAs and forms • Update the Stat 47 report Cal. SAWS | Project Steering Committee Meeting 94

Policy Update Cal. WORKs Stage One Child Care Continuous Eligibility Policy Effective Date & State Policy Reference C-IV Status LRS Status Description – Cal. ACES Implementation Effort 10/1/2019 TBD The State budget enacted policy that requires Cal. WORKs recipients to receive a minimum of 12 months of Stage One child care in order to be determined stable and able to transition to Stage Two. This policy also includes noticing requirements of the availability of child care and child care reports, which is not part of the October 2019 effective date. The Senate adopted the Administration’s May revision proposal and provided an additional ongoing funding to allow stage one child care to be available for additional program activities and to establish a data sharing system between county welfare departments and child care contractors to ensure that child care is not disrupted during transfer (consistent with Senate Bill 321). Cal. SAWS | Project Steering Committee Meeting 95

Policy Update Medi-Cal Expansion for Young Adults Policy Effective Date & State Policy Reference C-IV Status LRS Status Description – Cal. ACES Implementation Effort 1/1/2020 SCR 103662 SCR 206941 Design Building upon SB 75 the Governors budget proposes to expand full-scope Medi-Cal coverage to eligible young adults aged 19 through 25 regardless of immigration status, starting no sooner than July 1, 2019. However, DHCS proposed a January 1, 2020 effective date. Release 19. 11 Priority Draft ACWDL Received on 6/7/19 Draft NOAs Received on 7/1/19 Cal. HEERS e. HIT changes for this policy are scheduled for implementation on September 23, 2019 (19. 9 release). DHCS is setting up a workgroup to discuss the implementation of this policy. The workgroup will include SAWS and Counties participants and will start sometime in April. JADs are complete. DHCS has not provided draft copies of the ACWDL and threshold NOA snippets. Cal. ACES Updates: • Notice of action changes • Aid code rule changes to account for the increased age limit • Updates to existing batch changes -Continued on Next Slide- Cal. SAWS | Project Steering Committee Meeting 96

Policy Update Medi-Cal Expansion for Young Adults Policy C-IV Effective Status Date & State Policy Reference LRS Status Description – Cal. ACES Implementation Effort 1/1/2020 SCR 104022 SCR 208241 Design Turn on young adult expansion e. HIT functionality and process a one-time batch EDBC run. Per DHCS, this needs to run in December 2019 for Jan 2020 benefit month. This batch process will re-evaluate individuals for full scope Medi-Cal if they are age 19 -25, inclusive, and receiving restricted scope Medi-Cal. Release 19. 11 Priority Draft ACWDL Received on 6/7/19 Draft NOAs Received on 7/1/19 SCR 103874 SCR 207950 Design Release 19. 11 Priority Cal. SAWS | Project Steering Committee Meeting On-going Batch portion of Young Adult Expansion, which will create an age 26 batch process to re-evaluate individuals for Medi-Cal due to aging out of young adult expansion aid codes. The first time this batch needs to run will be in January 2020 for February 2020 benefit month. 97

Cal. SAWS Regional Updates Cal. SAWS | Project Steering Committee Meeting 98

Update on Foster Care Eligibility and Determination (FCED) Strategy and Next Steps Cal. SAWS | Project Steering Committee Meeting 99

JPA Board Agenda Review Cal. SAWS | Project Steering Committee Meeting 100

Adjourn Meeting Cal. SAWS | Project Steering Committee Meeting 101