December 19, 2019 Project Steering Committee Meeting - PowerPoint Presentation

December 19, 2019 Project Steering Committee Meeting

Agenda Call Meeting to Order Agenda Review 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.

Action Items

Action Items Approval of the Minutes of the November 21, 2019 PSC Meeting and review of Action Items.

Informational Items

CalSAWS Schedule Impact Resulting from Functional Design Sessions Outcomes

Revised CalSAWS DD&I Project Schedule Background Overview Revised ScheduleFunctional Area OverviewNext Steps Agenda

Revised CalSAWS DD&I Project Schedule Background As discussed at the September and November JPA and PSC meetings, the project team has been analyzing the outputs of the Functional Design Sessions and assessing options for integrating this new scope into the CalSAWS DD&I Project Schedule In addition, the project team identified a risk related to the impact of adding this additional scope to the existing project schedule. Specifically, the risk is associated with implementing a large volume of changes in a short timeframe to meet the current deadlines, and the resulting impact on LA County users, the down steam migration activities (conversion, training, change management) and the quality of future releases.

Revised CalSAWS DD&I Project Schedule Overview Develop a project schedule that: Allows the 39 C-IV Counties to cutover to CalSAWS in September 2021 Provides CalSAWS functionality, including new requirements defined by the Functional Design Sessions, that meets the current business needs of the C-IV Counties Allows for the development and implementation of additional capabilities needed for the CalWIN Counties after C-IV counties go-live Incrementally builds out the CalSAWS requirements for the 57 counties, minimizing any throw away code Completes CalWIN Counties rollout no later than December 2023 Assumptions: Imaging will begin work in January, 2020 (pending JPA approval) All other work begins in March, 2020 for the new scope required by the Functional Design Sessions and Foster Care No changes to the LRS Agreement end date

Revised CalSAWS DD&I Project Schedule The following slide highlights a revised project schedule that assumes: The 39 C-IV Counties cutover to CalSAWS in September 2021 (no change to this date) There would be no functional release during this cutover month There would be no technical release during the month after cutover A phased approach, where appropriate, for the outstanding Functional Design Session scope: Focus on implementing requirements needed by the C-IV Counties to align CalSAWS functionality with current C-IV functionality prior to cutover (referred to as “Phase 1”) Phase in other features/functions needed by the CalWIN counties that may also be used by C-IV counties and LA County in the future. These would be developed and implemented prior to CalWIN UAT (referred to as “Phase 2”) Revised Schedule

Revised CalSAWS DD&I Project Schedule Revised Schedule continued Impacts to CalWIN Implementation Dates: Shifts the first CalWIN wave from January 2022 to October 2022. All subsequent waves are adjusted accordingly No changes to the number of CalWIN waves was contemplated or requested at this time Adjustment to the timing of the second wave to avoid a cutover in a holiday month e.g. (November, December)

Revised CalSAWS DD&I Project Schedule Refer to Handout

Revised CalSAWS DD&I Project Schedule Functional Area Overview The following slides will provide additional details for: 58 County Imaging Task Management Non State Forms GA/GR APIs Ancillary Systems Conversions Analytics: BIP/State Report Replatforming Foster Care

Revised CalSAWS DD&I Project Schedule Functional Area Overview: Requirements Summary Functional Design Session Total Pre FDS Total Post FDS Estimated Total Effort+ Imaging 24 42 87,000 Task Management 39 32 39,500 Non State Forms 2 114 38,000 GA/GR++ 11 28 77,700 APIs 3 37 15,800 Ancillary Systems Conversion 4 50 37,000 Total New Requirements* 83 303 295,000 The 303 FDS requirements are in addition to the existing ~600 requirements + Estimate is under review. Estimate includes the design, build, test, training, tech, and conversion activities as appropriate ++ Final solution is still under review

Revised CalSAWS DD&I Project Schedule Functional Area Overview: 58 County Imaging Category Description Phase 1 Deploy integrated imaging solution to the 39 C-IV Counties at go-live LA County continues to use EDMS interface (already integrated with CalSAWS) Phase 2 Deploy the integrated imaging solution to LA County prior to the CalWIN Wave 1 cutover Deploy the integrated imaging solution to each CalWIN County at their respective CalSAWS Cutover Dependencies Integration with task management and APIs

Revised CalSAWS DD&I Project Schedule Functional Area Overview: Task Management Category Description Phase 1 Core CalSAWS requirements to create a unified task management approach, inclusive of C-IV tasks and automated actions, along with integration with the 58 counties imaging solution (Releases 20.09-21.03) Phase 2 Additional capabilities (needed for the CalWIN counties and that will be available for all counties) will be implemented post C-IV cutover (Releases 21.05-22.01) Dependencies Integration with imaging. Downstream impacts to both conversion and training

Revised CalSAWS DD&I Project Schedule Functional Area Overview: Non State Forms Category Description Phase 1 Non State Forms in English and Spanish (Releases 20.11-21.05) Phase 2 Non State Forms in 13 threshold languages (Releases 21.07-22.07) Dependencies An approved English version of a form is required prior to obtaining translations

Revised CalSAWS DD&I Project Schedule Functional Area Overview: GA/GR Category Description Phase 1 Implement C-IV managed and non managed solution Generate the GA 237 for the 39 counties Send GA transactions to MEDS (Releases 20.11-21.03) Phase 2 Implement CalWIN Counties rules and integrate with GA Correspondence service (Releases 21.05-22.01) Dependencies Downstream impacts to both conversion and training No changes to the LA County GA/GR program already integrated with the CalSAWS system

Revised CalSAWS DD&I Project Schedule Functional Area Overview: APIs Category Description Phase 1 Implement APIs related to task management and imaging (Releases 20.11-21.01) Phase 2 All other APIs (Releases 21.03-22.01) Dependencies Integration with task management and imaging Functional Design Sessions were targeted at the 18 CalWIN Counties

Revised CalSAWS DD&I Project Schedule Functional Area Overview: Ancillary Systems Conversion Category Description Phase 1 N/A Phase 2 N/A Dependencies Extracts from source legacy systems by the counties in accordance with the target schema and conversion team schedule Functional Design Sessions were targeted at the 18 CalWIN Counties for the following systems: Collections, Fraud, and QA/QC

Revised CalSAWS DD&I Project Schedule Functional Area Overview : Analytics – BIP/State reports replatforming Pending results of POC in late December 2019 Replatforming of reports may be prioritized based on: Performance of the existing report with 40 county volumes Legacy system reports that currently do not exist in LRS and must be ported from C-IV counties Underlying application changes driving a reporting change

Revised CalSAWS DD&I Project Schedule Functional Area Overview: Foster Care Category Description Phase 1 Update CalSAWS with additional data collection elements, eligibility rules, NOAs, State forms, reports, and fiscal processing One way, inbound interface with CWS. Replaces LA/LRS datamart with a direct interface from CWS to CalSAWS (Still being discussed) Phase 2 Integration with CWS-CARES System Dependencies Timing of the CWS-CARES System go-live. Downstream impact on training

Revised CalSAWS DD&I Project Schedule Other Consortium Decision Points Decision Description 58 County Portal Solution Procurement pending. If the new 58 County portal is not available by September 2021, C4Yourself would need to be integrated with CalSAWS for the 39 C-IV Counties. YBN is already integrated with the CalSAWS system. 58 County Contact Center Solution Pending Consortium decision on the solution. If the new 58 County Contact Center solution is not available by September 2021, integrate the C-IV Counties AWS Connect Contact Center solution with CalSAWS. The LA County Contact Center is already integrated with the CalSAWS system.

Revised CalSAWS DD&I Project Schedule Other Consortium Decision Points Decision Description Central Print solution Procurement pending for central print services for 56 of 58 counties. If the central print solution is not operational by September 2021, integrate existing C-IV Central Print services with the CalSAWS system LA County Central Print Services are already integrated with the CalSAWS system

Revised CalSAWS DD&I Project Schedule Next Steps Review revised schedule with approval and funding entities (December 2019) Finalize amendment documentation and budget documentation (December 2019) Seek State and Federal approval of the Amendment for Functional Design Sessions and revised schedule (January/February 2020) Seek JPA Board approval for the Amendment (February/March 2020)

Functional Design Sessions Update GA/GR Scope, Estimate, & Funding Strategy Non-State Forms: LA Specific Forms Requirements Impacts to C-IV Counties in the areas covered in the CalWIN Ancillary System Conversion Sessions

Functional Design Sessions Update Region 1 - There was no impact identified Region 2 - There was no impact identified Region 3 - There was no impact identifiedRegion 4 - There was no impact identifiedRegion 5There is potential impact to Riverside (QA)Imperial & San Bernardino have identified no impactsRegion 6 - There was no impact identified Impacts to Non- CalWIN counties in the areas covered in the CalWIN Ancillary System Conversion Sessions

Automated Assistants/Bots Pilot Overview

Business Use Case Improve the level of customer service and provide employee work load relief by handling high volume, low intervention required transactions through virtual assistants Achieve better handle rates for IVR and address more requests from citizens. Supporting IVR with virtual assistants will allow case workers to spend more time on complex scenarios Following scenarios are identified as potential use cases:Address UpdateElectronic Benefit Transfer (EBT) Card ReplacementBenefit Identification Card (BIC) Replacement

Channels Under Consideration Call Deflection Voice Bot Web Channel (YBN) Participant calls DPSS and accesses IVR system Based on the selection of the participant, if it is one of the identified use cases, IVR informs that instead of waiting on the call, a link can be provided to the participant either via text or email to handle the rest of the conversation Participant hangs up and receives a one time link from DPSS, clicking the link takes the participant to the chat Natural Language Processing (NLP) is used to handle questions from the participant When the conversation is over, the participant can close the chat window Participant calls DPSS and accesses IVR system Based on the selection of the participant, if it is one of the identified use cases, IVR informs that instead of waiting on the call, a link can be provided to the participant either via text or email to handle the rest of the conversation Participant hangs up and receives a one time link from DPSS, clicking the link takes the participant to the chat Natural Language Processing (NLP) is used to handle questions from the participant When the conversation is over, the participant can close the chat window Participant accesses his/her ‘Your Benefits Now’ account Chat window is available on their account page to access at any time Natural Language Processing (NLP) is used to answer questions

Recommendation to decommission LDS which stores legacy terminated cases from ISAWS

Legacy Data Solution (LDS) The LDS database is currently being maintained centrally by the project and stores data from cases closed in the original ISAWS counties at the time they were converted to C-IV Data stored on these cases is OVER 12 years old Usage of the LDS averages about 5 users a month across all 35 countiesUsing the new CalSAWS Retention Policy as a guideline, the project recommends decommissioning (and secure disposal) of the LDS data ISAWS 35 Counties – Closed Case Data

Status of Cambria Solutions Corrective Action Plan

Status of Corrective Action Plan Completed remediation of all impacted deliverables General Design Document Submitted on 11/27 Technical Design Document Submitted on 12/4 Project Control Document Submitted on 12/2 Work Plan Submitted on 12/2 Master Test Plan Submitted on 12/2 Proposal Supplement Submitted on 12/3 Requirements Traceability Matrix No Findings Status Reports No Findings Other Work Products No Findings Walkthroughs have been conducted with the Consortium and QA Vendor

Status of Corrective Action Plan Trained all Cambria staff on developing of original content and citing where needed Improved internal deliverable review and QA processes Added use of tools to scan/check all documentsRequire peer reviewsAdded a QA Director Cambria executives approval/submittal of deliverables Quality Improvement steps

Status of Corrective Action Plan Tasks were added for CAP remediation work Tasks for deliverable completion and resources allocations were impacted by remediation effort Critical schedule milestones (e.g., UAT and Go-Live) remain unchangedTechnical Design DocumentUpdates continue in collaboration with the Consortium and QA Vendor; DDEL will be submitted on 12/20 Schedule

CalSAWS Analytics Solution Update

Analytics – Re-platform Communications Working to schedule the Orientation for Fiscal/Reports Committees in January, a webinar to walk through the new platform and introduce committee communication schedule Fact sheet drafted as supporting material to the planned orientation. Plan to expand based on feedback during sessions and leverage to keep parties informed. Planning Efforts:An outcome of the proof of concept for State and Management reports is to estimate and plan the re-platforming of these reports.  As part of the exercise SCR’s in the pipeline and DDI requirements are being reviewed and incorporated.  Exercise planned to complete by end of January. Determine guidelines for changes to reports in the context of the re-platforming. Next Steps

Preview OBIEE & Qlik OBIEE Qlik Navigation/Interactivity : Each report will automatically update when a filter is selected Performance : Better performance due to Qlik’s in-memory loads Drill downs: Drill downs will open on the same page Design : The design will adhere to standardized color palette The OBIEE Subject Area will exist as a Purpose Built Data Set in the new platform

Conversion Team Activities Update Number of Duplicate CINs cases to be worked Reports and Data Cleansing Process Duplicate Persons/CINs Workgroup framework and decision-making process

Timeline August September October November November December December January/February Complete In Progress Not Started

Number of Duplicate CINs Matching on CIN (Only). Identified Duplicate CINs across the C-IV, LRS, and CalWIN County Data Duplicate CIN Scenario (CIN Match) Duplicates* Conversion Process Active / Active (Active Programs in 2 or more Counties) 41,500 1% of Total Identified Duplicates Clean-Up Options: Address prior to the Conversion/Cutover Address post Conversion/Cutover Note: All CINs will Convert, as they exist in the C-IV and/or CalWIN systems, regardless of Cleanup Option.

Duplicate CINs Work Group Decisions Made. Confirmed or gained consensus from the workgroup to: CONVERSION AUTOMATION Apply Conversion Automation to Active / Not Active (or 46% of Duplicate CIN) Scenarios; Conversion Automation replicates the Duplicate Person logic in the CalSAWS ; Automation will not be applied to FC, AAP, KG, Minor Consent programs. DATA CLEANSING REPORT Create a Duplicate CIN Data Cleansing Report for the Active / Active (or approx. 1% of Duplicate CIN) Scenarios; Create a separate report for the Exception programs (FC, AAP, KG, Minor Consent); Identify the Lead County as the County where the CINs Application Date is the most recent. COMMUNICATION Deliver the Active / Active Duplicate CIN Data Cleansing Report; Meet with the Work Group on a Monthly basis.

Duplicate CIN Framework What the Counties can do with these Data Cleansing Reports

Next Steps Tasks on the horizon…

M&O Application and Policy Update SSA COLA

Policy Update Able-Bodied Adults Without Dependents (ABAWD) Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2017 Fixed Clock 8/31/2019 Waiver Expires ACIN I-11-16 ACIN I-88-16 ACL 18-08 ABAWD Handbook ACL 19-93 ABAWD Handbook 2.0 SCRs CIV-7215; CA-57971 Phase II Implemented Release  19.09 PPM #46539- Implemented 8/2018 PPM #47411- Implemented 8/2018 PPM #51360 Implemented 8/19 PPM #52397 Design R60 (2/20) FNS is working with the Western Region to discuss planning and preparation for the publication of the final rule on ABAWDs.    FNS did not provide any information specific to what changes will be implemented in the final rule, but they did share that the Administration still has a December release date on the rulemaking calendar.  When released, a relatively aggressive implementation timeline may be required by States. FNS mentioned that this timeline could be as little as 60-90 days from release of the final rule.  This means that States could be expected to be in compliance as early as March 2020. California may be required to submit an updated waiver request under new waiver criteria.  FNS has confirmed that our current waiver will be valid until final approval of the new waiver is received.  If this is the case, CDSS will take the lead on submitting an updated waiver and will keep impacted counties in the loop.    CDSS encourages counties to begin planning for implementation, but would limit these activities to planning that can occur ahead of a final rule as additional details will only come to light once the rule is finalized. -Continued on Next Slide-

Policy Update Medi-Cal Expansion for Young Adults Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2020 ACWDL 19-23 SCRs CIV-103662; CA-206941 Implemented Release 19.09 SCRs CIV-104022; CA-208241 Implemented Release 19.09 Priority SCRs CIV-103874; CA-207950 Build Release 19.11 Priority SCRs CIV-104826;CA-209956 Design Release 20.03 PPM #51191- Phase 1 Implemented R58B (9/19) PPM #51703- Phase 2 Implemented R59 (11/19) CalSAWS Updates: The effort to turn on young adult expansion eHIT functionality and process a one-time batch EDBC run is tentatively scheduled to run on 11/27/2019. System down time is not required for this process. Batch EDBC memorandum call with the counites was held on 11/6/19. The batch EDBC memorandum provides details on the batch EDBC process, timeline, and list with county action for cases not processed by batch EDBC. The on-going monthly batch process will re-evaluate individuals for Medi-Cal due to aging out of young adult expansion aid codes.  The first time this batch will run is in January 2020 for February 2020 benefit month. CIT 0098-19- CA-208241 | CIV-104022: Posted List for Young Adult Expansion (YAE) Batch was posted to the CalSAWS web portal on 12/2/19. The purpose of this CIT was to inform the counties of posted lists associated to CA-208241|CIV-104022 (One-time Batches to Transition Young Adults from Restricted Scope to Full Scope Medi-Cal). Three one-time lists have been posted to the CalSAWS Web Portal for County follow-up of the Young Adult Expansion population who remain in restricted scope Medi-Cal after the automated transition batch processing is complete or where a program or person were discontinued. -Continued on Next Slide-

Policy Update Medi-Cal Expansion for Young Adults Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2020 ACWDL 19-23 SCRs CIV-103662; CA-206941 System Test Release 19.09 SCRs CIV-104022; CA-208241 Build Release 19.09 SCRs CIV-103874; CA-207950 Committee Review Release 19.11 Priority SCRs CIV-104826;CA-209956 Design Release 20.03 PPM #51191- Phase 1 Implemented R58B (9/19) PPM #51703- Phase 2 Implemented R59 (11/19) CalSAWS County Business Impact: Train staff on changes to system functionality Manually process the cases not processed in the batch EDBC CalWIN Update: Phase 1: Notice of action changes Aid code rule changes to account for the increased age limit Batch triggers inserted for applicable cases for 1/2020 effective date  Phase 2: Batch EDBC run will be scheduled for late November to identify individuals meeting the new criteria and grant full scope eligibility.  Notice of Action snippets for Non-MAGI, such as MC 239P,  MC 239Q and MC 239S. Client Correspondence maintenance Service Requests (SRs) opened for translations to be implemented. MAGI – SR #626668 and Non-MAGI – SR #627578. CalWIN County Business Impact Exception lists will be provided for county action for cases not processed by the batch run.

Policy Update Social Security Admin (SSA) Cost of Living Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2020 ACWDL 19-24 ACIN I-67-19 CIV-100451/CA-200824 Test Release 19.11 CIV-105046/CA-210439 Build Release 19.11 PPM #53339 Design/testing December 2019 Social Security Administration has approved a 1.6 percent Cost of Living Adjustment (COLA) for 2020. Based on the increase in the Consumer Price Index (CPI-W) from the third quarter of 2018 through the third quarter of 2019, Social Security and Supplemental Security Income (SSI) beneficiaries will receive a 1.6 percent increase. On 11/14/19, SAWS met with DHCS to discuss streamlining the release of policy guidance for the Social Security Administration cost of living adjustment and the annual changes to the federal poverty limits. DHCS is going to publish ACWDL as updates become available. On 12/6/19, CDSS provided the following guidance: For the county to take a “county initiated action” there must be enough information available for the county to accurately take action on the CalFresh (CF) budget. Because SAWS does not maintain each household’s standard SSI income amount (i.e. the SSI income amount before any deductions or other adjustments are made) or the household’s most recent SSI income amount paid per SSA, there is not enough available information for the county to accurately apply the SSI COLA increase to the CF budget.    Therefore, CDSS has instructed SAWS to not take any action on CalFresh cases as a result of the 1/1/20 SSI COLA. -Continued on next slide-

Policy Update Social Security Admin (SSA) Cost of Living Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2020 ACWDL 19-24 ACIN I-67-19 CIV-100451/CA-200824 Test Release 19.11 CIV-105046/CA-210439 Build Release 19.11 PPM #53339 Design/testing December 2019 CDSS, SAWS and DHCS are meeting on December 10, 2019 to explore whether it would be possible to act on the updated SSI payment information that is received from SSA. This SSI payment information is only in available MEDs.  CDSS is working thought the details of the QC error risk and will get information out the counties as is becomes available. On 12/5/19, SCR CIV-100451 added/updated the SSI/SSP and SSI Only Other Program Assistance (OPA) records for CF participants to bring the SSI amount to the payment standard for the C-IV counties. Due to the CDSS guidance, SCR CIV-105832 (Reverse the Data Changes applied to OPA Detail SSI Amount) was created to reverse the OPA updates. This change is targeted for implementation on 12/12/19. A CIT with a list of CalFresh cases where EDBC has been processed between 12/5/2019 and implementation date of this SCR will be made available to the counties. The CIT will include county action for processing cases on the list. -Continued on next slide-

Policy Update Social Security Admin (SSA) Cost of Living Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2020 ACWDL 19-24 ACIN I-67-19 CIV-100451/CA-200824 Test Release 19.11 CIV-105046/CA-210439 Build Release 19.11 PPM #53339 Design/testing December 2019 CalSAWS Update: The following changes were implemented 12/12/19: Added the new SSA income amount effective 1/1/2020. Updated the value of the 'Backout Multiplier' to match the rate increase. Updated the Pickle values to match the 'Pickle Disregard Computation Chart' effective 1/1/2020. Updated the SSI/SSP payment standards Updated the Medicare Part B Premium amounts in the system to the new values. Created a Journal entry to document the data changes for SSA Income and Medicare Part B Premium amounts. This journal entry was applied to all applicable cases. The batch EDBC process to apply the SSA COLA change to the applicable cases will run for LA and the C-IV counties on 12/14/19. CalFresh cases with SSI/SSP or SSI only income will NOT be included in the batch process on 12/14/19. The C-IV System will be available until 5pm on 12/14/19. CalSAWS County Business Impact: All Counties, refer to CIT XX-19 to manually process the cases not processed in the batch EDBC. This CIT is scheduled to the published on 12/16/19. -Continued on next slide-

Policy Update Social Security Admin (SSA) Cost of Living Policy Effective Date & State Policy Reference C-IV/LRS Status CalWIN Status Implementation Details 1/1/2020 ACWDL 19-24 ACIN I-67-19 CIV-100451/CA-200824 Test Release 19.11 CIV-105046/CA-210439 Build Release 19.11 PPM #53339 Design/testing December 2019 CalWIN Update: CalWIN COLA process targeting to be run December 14 th and 15th, 2019 for SSA COLA. Related a CAPI COLA will be run December 14, 2019 (PPM# 53122). To minimize the impact to county workers, CalWIN will apply the Social Security increase by updating all cases with SSA income by the percent of the increase, to all programs and all cases where at least one individual is receiving Social Security benefits. The SSI increase will not be applied. CalWIN will not run the SSA COLA on MAGI-Only Medi-Cal and Mixed (APTC/MAGI) Medi-Cal cases. CalWIN County Business Impact Manually process the cases not processed in the batch EDBC.

CalSAWS Imaging Solution Timeline for Conversion Benchmarks, Performance Standards, and Testing Standards/Phases

2021 2023 Today Feb May Aug Nov Feb May Aug Nov Feb C-IV Go-Live Sep 1 LRS Go-Live Nov 1 CalWIN Wave 1 Go-Live Feb 1 CalWIN Wave 2 Go-Live May 1 CalWIN Wave 3 Go-Live Aug 1 CalWIN Wave 4 Go-Live Oct 1 CalWIN Wave 5 Go-Live Dec 1 CalWIN Wave 6 Go-Live Feb 1 Performance Test 1 Feb 14 Performance Test 2 Jul 15 Performance Test 3 Dec 15 Performance Test 4 Mar 15 Performance Test 5 Jun 15 Performance Test 6 Nov 15 Test # County Volume Included in Test 1 C-IV & LRS 2 C-IV, LRS & CalWIN Wave 1, 2, 3, 4, 5 & 6 3 C-IV, LRS & CalWIN Wave 1, 2, 3, 4, 5 & 6 4 C-IV, LRS & CalWIN Wave 1, 2, 3, 4, 5 & 6 5 C-IV, LRS & CalWIN Wave 1, 2, 3, 4, 5 & 6 6 C-IV, LRS & CalWIN Wave 1, 2, 3, 4, 5 & 6 NOTE: Document migration activities will kick off once the amendment is approved. Testing the performance of importing documents will be completed during this time.

Service Level Agreements – Performance SLAs Hyland Monthly Uptime : (Percentage) 99.90% Document View: (Percentage) 90% < = 2 seconds per page Database Transactions: (Percentage) 90% <= 1 seconds per transaction Intelligent Capture Document Processing : (Pages per Hour ) 90,000 Pages Processed Assumptions: SLAs do not account for failures due to faults (such as availability, performance or security) with the Amazon Web Services (“AWS”) or Telecommunication providers (including Cloud Exchange providers). The SLAs in the table below are the responsibility of Hyland.

Service Level Credits Hyland Monthly Uptime Percentage Service Level Credits Monthly Uptime Percentage Service Credit Ranges and Applicable Credit Determinations 99.89-99.00% 10% of the Monthly SaaS Fees Less than 99.00%  20% of the Monthly SaaS Fees Monthly Page View Percentage Target Page View Service Level Credit   3.5% of the Monthly SaaS Fees Monthly Database Transaction Percentage Target Database Transaction Service Level Credit 3.5% of the Monthly SaaS Fees Monthly Intelligent Capture Document Processing Percentage Target Intelligent Capture Document Processing Service Level Credit 3.5% of the Monthly SaaS Fees The credits in the table below are the responsibility of Hyland. (SaaS is “Software as a Service”.)

Imaging Solution Bottomline: Accenture as prime contractor is responsible for delivery of the Imaging solution. To receive payment, Accenture must first receive acceptance and approval of the work. Acceptance requires that the solution meet the Requirements, including performance requirements, that are included in the contract. In addition, timely delivery is enforced by liquidated damages that may be imposed on Accenture if the overall Implementation dates are delayed. Exhibit Z expressly provides that “all Work performed pursuant to Exhibit Z shall be subject to the terms and conditions of the Agreement, unless otherwise expressly stated in this Exhibit Z.” Thus, the Imaging Project has become part of the Work required of Contractor to deliver the CalSAWS System. Consortium Approval of Work (Section 4.2) “All Deliverables, M&O Services, M&E Services and work on the CalSAWS Project provided by CONTRACTOR must have the approval of CONSORTIUM Executive Director…” Right to Reject (Section 4.7) “CONSORTIUM reserves the right to reject any Tasks, Subtasks, Deliverables, goods, or services not approved by CONSORTIUM pursuant to Subparagraph 4.2 or other provisions of this Agreement.” LEADER Replacement System and CalSAWS System (Section 4.4) “CONTRACTOR shall provide the LEADER Replacement System and CalSAWS System to CONSORTIUM in accordance with the terms and conditions set forth in this Agreement.” The definition of CalSAWS System (1.4.19) notes that “Reference to the CalSAWS System may include one or more components thereof or the entire CalSAWS System.” Contract Protections

Amazon Connect Update Marin County Go-Live Kern County Implementation

Marin County Go-Live Marin county go-live was a success. There was no disruption to business process They handled the usual number of callsIssues/Lessons Learned:There were a total of 11 minor issues/lessons learned that we ran into during the two weeks of onsite support. All but two have been resolved:As part of the Kern go-live, we will update the frequency for the Message of the Day.We found an architectural change we need to make that will not affecting Marin/Kern but needs to be added before we add a sixth contact center (in February). Kern will use the same green light process used for Marin.

Not started On or ahead of schedule Behind Schedule At risk 2019 2020 Today March May July September November 2020 March 29 days Mar 5 - Apr 14 Planning 100% 54 days Apr 15 - Jun 30 Marin - Design 100% 63 days Jul 1 - Sep 26 Build 100% 41 days Sep 27 - Nov 22 Test 50% 64 days Jun 3 - Aug 31 Riverside - Design 100% 34 days Sep 1 - Oct 17 Build 100% 44 days Oct 18 - Dec 18 Test 55 days Jun 17 - Aug 31 Kern - Design 100% 50 days Sep 1 - Nov 8 Build 100% 43 days Nov 11 - Jan 8 Test 57 days Jun 24 - Sep 10 Sutter & Yuba - Design 95% 53 days Sep 11 - Nov 22 Build 95% 43 days Nov 25 - Jan 22 Test 55 days Jul 8 - Sep 22 Butte & Shasta - Design 100% 49 days Sep 23 - Nov 28 Build 55% 44 days Nov 29 - Jan 29 Test 56 days Jul 15 - Sep 30 San Bernardino - Design 90% 58 days Oct 1 - Dec 19 Build 38% 44 days Dec 20 - Feb 19 Test 64 days Jul 22 - Oct 20 Humboldt & Stanislaus - Design 80% 54 days Oct 21 - Jan 3 Build 0% 43 days Jan 6 - Mar 4 Test 59 days Aug 5 - Oct 25 Monterey - Design 60% 61 days Oct 26 - Jan 20 Build 0% 42 days Jan 21 - Mar 18 Test 58 days Aug 12 - Oct 31 Kings - Design 50% 61 days Nov 1 - Jan 27 Build 41 days Jan 28 - Mar 25 Test 59 days Aug 19 - Nov 10 Merced & San Joaquin - Design 65 days Nov 11 - Feb 10 Build 41 days Feb 11 - Apr 8 Test Project Kickoff Mar 4 Riverside Apr 10 Kern Jan 10 Sutter & Yuba Jan 24 Butte & Shasta Jan 31 San Bernardino Feb 21 Humboldt & Stanislaus Mar 6 Monterey Mar 20 Kings Mar 27 Merced & San Joaquin Apr 10 Marin Nov 25 Web Chat Design Jun 17 CCP Approved Jun 24 Reporting Decision Jun 17 Overall Timeline

Lunch

Procurement Update Portal/Mobile CalWIN OCM & Training RFP

CalSAWS Statewide Portal/Mobile Application Strategy, Scope and Timeline Timeline Procurement Event Date Released RFP November 4, 2019 Conducted Bidder’s Conference Sacramento County Department of Human Assistance November 20, 2019 10:30am-12:00pm Published RFP Addendum 1 Based on 14 Vendor Questions and Answers November 26, 2019 Received 136 Additional Vendor Questions December 3, 2019 Publish RFP Addendum 2 and Responses to All Vendor Questions By December 16, 2019 Contractor Proposal Due Date January 22, 2020 Evaluate Proposals and Prepare Vendor Selection Report January 23 – April 22, 2020 Contract Negotiations April 27 – May 5, 2020 State, Federal and JPA BOD Approval of Agreement May 7 – August 7, 2020 Start Date of Statewide Portal/Mobile App Vendor August 10, 2020 Portal/Mobile App Go-Live September 2021

CalWIN Training, OCM & Implementation Support Strategy Conduct an open procurement to acquire vendor services to provide Training, OCM and Implementation Support for the 18 CalWIN counties.CalWIN to CalSAWS migration is expected in 6 waves beginning January 2022 and continuing through January 2023CalWIN to CalSAWS migration must address multiple combinations of ancillary systems and business processes. Scope and Key Objectives The Consortium is seeking a Contractor to apply innovative strategies, approaches, and methods for leading the cultural and organizational changes the CalWIN Counties will experience in transforming from their existing state and assimilating into the CalSAWS environment. This effort includes completing the transition from the CalWIN decentralized County-based support model to the CalSAWS regional structure for governance and ongoing system support. Prepare the CalWIN Counties to transition from using the CalWIN application and supporting business processes to using the CalSAWS application. Ensure each County’s As-Is business processes are documented and analyzed in order to prepare for changes, To-Be business processes, resulting from adoption of the CalSAWS application. Conduct a county-specific As-Is and To-Be gap analysis to create a foundation for OCM and communication with internal stakeholders including labor organizations and other County departments. Support county-specific business process change resulting from ancillary system choices. Ensure county-specific Training is developed to address changes in business processes. Where possible, leverage and adopt standard CalSAWS application Training as the target for transition. Strategy, Scope and Timeline

CalWIN Training, OCM & Implementation Support Strategy, Scope and Timeline PROCUREMENT EVENT DATE Federal RFP Review and Approval October 20 – December 13 , 2019 RFP Release December 17, 2019 Bidder’s Conference Sacramento County Department of Human Assistance 4450 East Commerce Way Sacramento, CA January 7, 2020, 10:30am – 12:00pm Contractor Proposal Due Date February 19, 2020 Evaluate Proposals and Prepare Vendor Selection Report February 20 – May 18, 2020 Consortium Issues Notice of Intent to Award May 19, 2020 Contract Negotiation Period May 21 – June 2, 2020 Federal, State and Consortium JPA Board of Directors Approval of Agreement June 5 – August 28, 2020 Planned Start Date of CalWIN Contractor August 31 , 2020

Tech & Cloud Update

Tech & Cloud Update List of production incidents Status of R6 Cloud Migration Issue Resolution Issue Incidents Incident Control Problem Resolution Path Stability with Oracle Software 10/15 – System slowness all day 10/16 – System slowness all morning 10/18 – System slowness early morning Tuning based on information from operational tools  Upgrading Software in 20.01 release (end of January) Stability with Oracle Software 10/22 from 10:39 AM to 10:53 AM Configuration changes  Have already made configuration changes and continue to work on with Oracle on additional changes LA County ISD Active Directory Problems 11/8 from 3:27pm to 3:42 pm 11/19 from 8:40am to 8:44 am 11/19 from 12:40pm to 1:04pm 11/20 from12:15 pm to 12:39 pm LA County ISD made configuration changes  Resolved

Tech & Cloud Update Performance Metrics of Batch in Cloud Monthly batch/interface performance metrics show improved performance across key processes Highlights for specific batch cycles Cloud Batch Performance   Average Runtime (minutes) Modules September October November ABAWD 60 43 32 CCSAS 97 89 53 EDBC 43 15 13 FISCAL 267 240 183 FORMS 180 146 131 MEDS 202 177 150 NOA 91 55 53 SUPER TRIGGER 58 41 49 WDTIP 8 7 7 WPRD 19 12 8   September October November 10-Day Batch EDBC 164,000/hour 386,000/hour 352,000/hour DPSS Payroll 148,000/hour 2.275mil/hour 5.617mil/hour Average runtime for the month Includes wait time for interface files (FISCAL, CCSAS, etc )

Tech & Cloud Update Continuous Improvement

Cal SAWS Cloud Migration Roadmap to the Cloud

Cal SAWS Cloud Migration Cloud Enablement Phase 2 CLOUD US East 1 Region (DR) Workers Database Replicas for Disaster Recovery Infrastructure/Security DATA CODE LRS US West 2 Region ENVIRONMENTS 3 rd Party Software LRS/CalSAWS ADF PMO NorCal Cloud Exchange SoCal Cloud Exchange Updating for Phase 2 PHASE LEGEND Completed in Phase 1 LA/Net CalSAWS Network SDWAN/MPLS Interface Partners Scaling New Capability for Phase 2 Batch Streaming Cloud Native Services EDBC SQL Tuning SCALING Cloud Native Analytics

CalSAWS Staffing Status Review of Requirements for Minimum Qualifications

CalSAWS Staffing Update Project Management Office (PMO) Fiscal/Contract Manager (1 long-term) Fiscal/Contract Analyst (2 long-term)PMO Analysts (2 long-term)Common Services/PMOProcurement Manager (1 long-term)Procurement Analysts (2 long-term)Procurement Analysts (2 limited-term through January 2023) Technical & Operations Cloud Analyst (1 long-term) Conversion Analyst (4 limited-term through January 2023) Application Development & Test Release Coordinator (1 long-term) Release Coordinator (1 limited-term through January 2023) Policy, Design & Application Development Business Analysts (4 limited-term through September 2021 or January 2023 depending on specific assignment) Customer Engagement Implementation Manager (1 limited-term through January 2023) Implementation Coordinators (3 limited-term through January 2023) Trainers (3 limited-term through January 2023) CIT 0084-19 Recruitment of CalSAWS Project Staff Closed Friday Nov. 29, 2019

CalSAWS Staffing Update Applicants Team Position Applicants Policy, Design, Governance and Application Development Business Analyst 16       Application Development Release Coordinator 18                   Customer Engagement Trainer 18   Implementation Manager 8   Implementation Coordinator 12       Technical Operations Cloud Analyst 8   Conversion Analyst 14             PMO/Common Services Fiscal/Contract Analyst 8   Procurement Analyst 8   PMO Analyst 17   Fiscal/Contract Manager 2   Procurement Manager 3         Total 132 Note: 47 individual candidates applied for multiple positions

CalSAWS Staffing Update Select Candidates to Interview and Schedule Interviews 12/2 – 12/6 Interviews – 12/9 through 12/19 Identify selections 12/20 Notify Directors and Receive Director Confirmation 12/23 – 1/3Notify Candidates 1/6 – 1/10Candidates Accept/Reject 1/13-1/17Contingency 1/20 - 1/31 Next Steps

CalSAWS Risks and Issues Reporting

CalSAWS Risk & Issues Executive Summary Legend Risk 102: Lack of Annual Project Funding may cause schedule delay or reduction in scope for CalSAWS M&O, and all existing projects Risk 10 4: Functionality gaps between the 3 systems may result in a loss of functionality for some counties during migration to CalSAWS Risk 201: Pace of Policy Changes may exceed capacity of App-Dev team, resulting in less automation Risk 202: Not all functionalities related to imaging, GA/GR, non-state forms, task management, and API are identified yet, which may impact schedule and cost once more information is known Risk 203: Project communications must be enhanced, otherwise stakeholder / audience needs will not be met Risk 204: Volume of changes to baseline code may cause degradation in quality & increase in defects Risk 206: Delays in staffing the Consortium and/or Accenture teams may delay the project schedule Risk 208: CalHEERS release readiness delays may negatively impact CalSAWS delivery timelines, slowing critical updates to counties Risk 209: CalWIN Counties may not be adequately supported for change readiness prior to 2020 until the CalWIN Change Management Procurement vendor starts Risk 211: Delay in consolidated portal procurement and implementation may impact C-IV and CalWIN go-live dates Risk 213: Number of staff assigned from DHCS might not have the bandwidth to support the CalSAWS project needs Risk 214: If counties are not able to adapt to the regional governance structure, the project schedule is at risk regarding decision making Risk 217: Talend Curation and Database Connection Issues Risk 219 (New): Facilitation across Committees is inconsistent, which may impact the project schedule and quality of decisions Risk 221 (Downgraded Issue 117): The instability of the Oracle security software causes LRS production performance degradation --------------------------------------------------------------------------------------------------------------------------------------------------------------- Issue 118: Some non-production environments using Delphix software do not have the desired responsiveness P Overall Project Risk 218 (Retired): Identified bugs in Talend Platform ETL Tooling are putting the project timeline at risk

CalSAWS Project High Risks 104 : Functionality Gaps between 3 systems resulting in loss of functionality for counties DESCRIPTION MITIGATION PLAN/ STATUS OWNER(S) RISK NAME 201: Pace of Policy Changes may exceed capacity of the project teams, resulting in less automation. There is a risk that the pace of policy changes could exceed the capacity of the project teams during the CalSAWS DD&I Phase. This may result in a reduction of required automation and increased work arounds. This risk may be real, but the project has continued to coordinate, collaborate, and communicate with State partners, CWDA, State legislature, and advocates on the implementation timeline of policy changes. Karen Rapponotti, Lisa Salas, Rocky Givon, DHCS Risk Trend Legend Remains same Trending to Issue Trending to Low Retired Risk Realized into an Issue Trending to Medium RISK LEVEL Probability (70%) * Impact (5) = 3.5 203: Project communications must be enhanced, otherwise stakeholder / audience needs will not be met . Unless the CalSAWS Project scales up and enhances Project communications, stakeholder needs for timely, tailored, and accurate information, as well as the needs of many diverse audience groups, may not be met. Began engaging in design thinking, and gathering requirements for Calsaws.org website subscription with Consortium stakeholders. Holly Murphy, Lulu Fou Probability (70%) * Impact (4) = 2.8 Project Leadership Probability (70%) * Impact (4) = 2.8 202: Not all of the estimates related to Functional Design Sessions have been completed yet. Until the FDS estimates have been completed, cost and schedule impacts to CalSAWS are not known. Not all of the estimates related to imaging, GA/GR, non-state forms, task management, and API have been completed yet. Until the complete set of FDS estimates have been completed, cost and schedule impacts to CalSAWS are not known. Approximately 300 new requirements were identified by the Functional Design Sessions.  Scope, budget, & proposed alternative schedule for FDS have been submitted to Consortium for review. GA/GR is still pending solutioning. Project will continue communication with JPA and PSC December through January.

CalSAWS Project High Risks DESCRIPTION MITIGATION PLAN/ STATUS OWNER(S) RISK NAME Risk Trend Legend Remains same Trending to Issue Trending to Low Retired Risk Realized into an Issue Trending to Medium RISK LEVEL 204: Volume of changes to baseline code may cause degradation in quality & increase in defects. The volume of changes introduced to the baseline code from LRS M&E, DDCRs, and CalSAWS Migration may cause degradation in quality and increase in defects. The first CalSAWS DD&I Release 19.11 initially indicates the code quality remains high. On target of meeting schedule to complete the creation of Automated Regression Testing scripts by end of December 2019, covering 90% of top production transaction volumes. Jo Anne Osborn, Lisa Salas, Dan Dean Probability (50%) * Impact (5) = 2.5 211: Delay in consolidated portal procurement and implementation may impact C-IV and CalWIN go-live dates. If the consolidated portal procurement is not completed timely, the statewide portal may not be implemented in time for the C-IV and CalWIN go-live dates. The Consortium released the Statewide Portal RFP on November 4, 2019. A vendor conference occurred on November 20, 2019. Proposal is due January 22, 2020. Two contingency plans have been developed for C-IV and CalWIN that are within budget. Tom Hartman Probability (70%) * Impact (4) = 2.8 217: Talend Curation and Database Connection Issues. The state/BIP Estimating and Planning will complete in January instead of December, pending completion of POC and successful deployment of Release B. Continue to monitor this risk until January to assess impact. Talend Curation and Database Connection issues are impacting Development and System Testing Phases putting the State and BIP POC (Release A) and the OBIEE Dashboards assigned to Release B At-Risk of meeting the Baselined Schedules, November 29, 2019 and December 30, 2019, respectively. Probability (90%) * Impact (3) = 2.7 Keith Salas, Luz Esparza

CalSAWS Project High Risks DESCRIPTION MITIGATION PLAN/ STATUS OWNER(S) RISK NAME Risk Trend Legend Remains same Trending to Issue Trending to Low Retired Risk Realized into an Issue Trending to Medium RISK LEVEL 221: The instability of the Oracle security software causes LRS production performance degradation. After the migration of LRS to the AWS Cloud, there were performance and stability issues with two products in the Oracle security stack. These problems have mostly been controlled by tuning, additional servers, and scheduled restarts of specific servers, but the underlying root cause has still not been identified. The last performance degradation incident caused by the instability of the Oracle security stack occurred on October 18, 2019 (for 92 minutes). In November, LA County ISD has made changes to Active Directory infrastructure and storage array to improve stability. The tech team is continuing to follow Oracle recommendations for a permanent solution. This risk will be reassessed when the suggested OS patching is complete in December 2019 and the OAM upgrade is complete as part of release 20.01 (January 2020). Laura Chavez, Scot Bailey Probability (50%) * Impact (5) = 2.5

CalSAWS Project Medium Risks 104 : Functionality Gaps between 3 systems resulting in loss of functionality for counties DESCRIPTION MITIGATION PLAN/ STATUS OWNER(S) RISK NAME 104: Functionality gaps between the 3 systems may result in a loss of functionality for some counties during migration to CalSAWS The risk of functionality gaps between the 3 systems and the ancillary systems of the counties may result in a loss of functionality for some counties during migration to CalSAWS . The committee reviewing designs is made up of resources from CalWIN , C-IV and LRS, who try to ensure that designs do not create unnecessary gaps. Karen Rapponotti, Laura Chavez Risk Trend Legend Remains same Trending to Issue Trending to Low Retired Risk Realized into an Issue Trending to Medium RISK LEVEL Probability (50%) * Impact (4) = 2.0 206: Delays in staffing the Consortium and/or Accenture teams may delay the project schedule The project team, both Consortium and Accenture, have been working to staff in accordance with the work plan. If either team experiences delays in achieving the target staff levels, there is a risk that the schedule may be impacted. Consortium PMO is working with RGS to expand recruitment efforts. A follow-up recruitment CIT has been drafted for Section Director review. Holly Murphy, Chris Paige Probability (50%) * Impact (3) = 1.5 208: CalHEERS release readiness delays may negatively impact CalSAWS delivery timelines, slowing critical updates to counties There have been persistent delays in CalHEERS achieving release readiness during the system test cycle, introducing risk to the dependent CalSAWS production release date. Any CalSAWS delay will impact the timely delivery of business functionality, receipt of which is critical to the counties. Additionally, date slips cause negative downstream planning and scheduling churn. 19.09 successfully implemented without impact to the DD&I schedule. Analysis of the Next CH major release 20.02 and collaboration continues. CalSAWS will continue to collaborate with the CalHEERS team as they transition to a New M&O Vendor focusing on potential release impacts. CalHEERs has combined 20.06 and 20.07 to a single release of 20.06 on June 29, 2020, cancelling a release in July, 2020 Jo Anne Osborn, Anna Chia, Fei Collier Probability (50%) * Impact (3) = 1.5

CalSAWS Project Medium Risks 104 : Functionality Gaps between 3 systems resulting in loss of functionality for counties DESCRIPTION MITIGATION PLAN/ STATUS OWNER(S) RISK NAME 209: CalWIN Counties may not be adequately supported for change readiness prior to August 2020 until the CalWIN Change Management Procurement vendor starts. Given the scope of the change for CalWIN counties migrating to CalSAWS and that the procurement for Change Management, Training and Implementation services for the CalWIN counties is targeting June 2020 for a vendor to begin supporting CalWIN , there is a risk that the CalWIN Counties may not feel adequately supported or informed regarding change readiness prior to late 2020. CalWIN OCM RFP is currently in Federal Review, and is scheduled to be released on December 17, 2019. RMs will continue to visit the counties and provide information and support. Targeted topic sessions are being held and others scheduled as needed. Further updates will be provided once funding has been approved. Holly Murphy, Jo Anne Osborn, June Hutchison, Diane Alexander, Tom Hartman Risk Trend Legend Remains same Trending to Issue Trending to Low Retired Risk Realized into an Issue Trending to Medium RISK LEVEL Probability (30%) * Impact (4) = 1.2 214: If counties are not able to adapt to the regional governance structure, the project schedule is at risk regarding decision making. With the creation of the CalSAWS regional structure, committees will now be represented by a regional governance model. This is new to some counties, and a change for some counties, and no change for some counties. If the counties are not able to adapt to or work well in the regional structure, the project is at risk regarding decision making. Joint effort between the Project and RMs to support the counties in the adoption of the regional governance structure. Karen Rapponotti, June Hutchison Probability (30%) * Impact (4) = 1.2 219: Facilitation across Committees is inconsistent, which may impact the project schedule and quality of decisions. Consistency of facilitation across all committees is critical for all committees and the success of the Project. With staffing changes and the addition of new committee members, consistency across the committees has been a concern that has been escalated to the Regional Managers from RCMs and SMEs. A joint effort between the Project, RCM/SMEs, Facilitators and RMs is being planned. RMs have made a recommendation to solicit feedback from RCMs and SMEs on successful committee meeting practices. Establish clear expectations and training for Facilitators. Upon receipt of feedback, next steps will be determined. Karen Rapponotti, Regional Managers Probability (50%) * Impact (3) = 1.5

CalSAWS Project Low Risks 104 : Functionality Gaps between 3 systems resulting in loss of functionality for counties DESCRIPTION MITIGATION PLAN/ STATUS OWNER(S) RISK NAME 102: Lack of Annual Project Funding may cause schedule delay or reduction in scope for CalSAWS M&O, and all existing projects The Project is subject to state funding approval each year. State General Fund payments may be deferred or budget cuts may cause schedule delays, scope reductions, or staff reductions. Consortium PMO continues to monitor status of all funding requests. CalSAWS June 2019 is pending federal approval with no comments received at this time. All premise updates that are currently known were submitted to OSI for the January Governor's Budget, and comments and questions addressed. Holly Murphy, Lulu Fou 213: Number of staff assigned from DHCS might not have the bandwidth to support the CalSAWS project needs The number of staff assigned from DHCS might not have the bandwidth to support the CalSAWS project needs. DHCS staff supports the CalSAWS project, however, they are currently stretched very thin. They have requested additional budget to resolve this risk. Karen Rapponotti Risk Trend Legend Remains same Trending to Issue Trending to Low Retired Risk Realized into an Issue Trending to Medium RISK LEVEL Probability (10%) * Impact (5) = 0.5 Probability (10%) * Impact (3) = 0.3

CalSAWS Project Issues DESCRIPTION RESOLUTION PLAN/ STATUS OWNER(S) ISSUE NAME 118: Some non-production environments using Delphix software do not have the desired responsiveness. Delphix is a third party tool used to mask data, decrease the time needed to refresh data, and reduce storage costs for non-production environments in the cloud. This tool has not performed as expected for the system test environments and is causing the project to use more AWS compute resources than planned. The project has continued to tune the existing version of Delphix based on recommendations from Delphix and AWS. Delphix has provided access to the beta version of the next release. Although the beta version did address the performance problem, it had other issues. The project is waiting for Delphix to provide an updated patch to resolve those outstanding issues, before using it for System Test. Scot Bailey, Shankar Padmanabhuni

State Partner Update on CalSAWS Activities OSI CDSS DHCS

CalSAWS Regional Updates

JPA Board December Meeting Debrief

Adjourn Meeting