Design Document - CalSAWS

© 2019 CalSAWS. All Rights Reserved.

CalSAWS California Statewide Automated Welfare System

Design Document

CA-208130

Asset Verification Interface

© 2019 CalSAWS. All Rights Reserved. 2

CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Steve Hancock, Connor O’Donnell

Reviewed By

DATE DOCUMENT VERSION REVISION DESCRIPTION AUTHOR

5/28/2020 1.0 Initial design for Review HancockS, ODonnellC


Table of Contents



1 OVERVIEW ACWDL 17-37 provides instructions on new asset verification reports that are now available for use in Medi-Cal eligibility determinations for specified Aged, Blind, and Disabled (ABD) applicants and beneficiaries and MEDIL I-19-12 informs counties of important future changes to the asset verification reports and how they will be delivered. Each month counties receive an Asset Verification Report in the form of an Excel spreadsheet. This report provides asset information for Bank Accounts, Real Property, Aircraft and Watercraft. This SCR will implement changes for The Systems to receive the Asset Verification Data through a flat fixed length file (IEV417) and display this data within the application.

1.1 Current Design An Asset Verification Report spreadsheet is currently delivered through a secure email to the counties by DHCS. This spreadsheet is delivered monthly around the 20th of each month.

1.2 Requests A new flat file, IEV417, will replace the existing asset verification reports, and will no longer be delivered via secure email to the counties by DHCS. The IEV417 flat file will be delivered to The Systems through SFTP (Secure File Transfer protocol ) to be imported into The Systems and displayed in online forms for the workers.

1.3 Overview of Recommendations 1. Create Asset Verification pages which will be used to display data from the

new flat file, IEV417. 2. Create a new Inbound FTP Batch job in each system to import the IEVS417 flat

file into the respective systems. 3. Create a new Asset Verification Inbound Reader job to read the IEV417 data

file and import the file into The Systems. 4. Update The Systems data model to store the inbound Asset Verification data.

1.4 Assumptions 1. The data will be imported as read only data and not be editable by the

workers. 2. The imported Asset Verification data will not generate any types of journal

entries or tasks and no additional functions will be triggered from the importing of this data.

3. The data within the file being imported is not validated and\or translated with any set code values. Although we have expected values for some fields, those values may change and The Systems will show what was sent through the file no matter what the data is in a particular field.

4. The incoming data will be posted at the time of the import and not relayed in any way to post on a later specific date.



2 RECOMMENDATIONS

2.1 Asset Verification Inbound Interface

2.1.1 Overview DHCS will send specific data to The Systems. This data will be transferred in a fixed length flat file format to then be imported into The Systems. The data will be populated into the fields outlined in the online design.

2.1.2 Description of Change 1. Create a new Inbound FTP Batch job in each system to import the

IEVS417 flat file into the respective systems. a. File Naming:

i. The file name specifies the type of file (IEV417) and the creation date of the file (D102019). Note: The naming convention on the DHCS side currently refers to Los Angeles County’s data file as LEADER.

b. The new batch job each night will check the DHCS server to see if the files are available. If the files are available, the job will transfer to a local destination where the batch job will then be able to import the data from the file. CalSAWS will only pull over the proper file based on the file naming described in the above point.

2. Create a new Asset Verification Inbound Reader job to read the IEV417 data file and import the file into The Systems.

a. Create a new journal entry for every case identified in the interface using the criteria below:

Journal Entry Description

New/Update New

Journal Category

Interfaces

Journal Type Interfaces

Short Description

Asset Verification received.

Long Description

Asset Verification information is received on the MM/DD/YYYY run.

Trigger Condition

When Asset Verification is received.


3. Update The Systems data model to store the inbound Asset Verification data.

4. The data elements in the attached ‘IEVS417 Inbound Data Elements Specifications.xlsx’ will be sent from DHCS to The Systems through a fixed length flat file. The spreadsheet has tabs each containing the following columns The tabs are specific to each of the asset types being imported (Bank Records, Real Property Records, Aircraft Records, Watercraft Records):

a. Ref # column: Numbering of the data elements for internal reference which match to the layout specifications provided by DHCS. These values are not in the incoming flat file.

b. Record # column: Data Element grouping numbers. Numbering of the data elements for internal reference which match to the layout specifications provided by DHCS. These values are not in the incoming flat file.

c. Incoming Data Element Name column: Name of the data element from the Data Dictionary for the Data Elements. These values are not in the incoming flat file.

d. Description column: Normal text for what the Data Element Name means. These values are not in the incoming flat file.

e. Incoming Format\Logic\Values\Validation column: Specifies any special formatting, logic on how to handle the data for this element and\or if there are specific values to expect.

f. Sample Data column: This column lists sample data from sample data files to provide examples of data for each data element.

g. Data Type column: This column specifies the data type of the incoming data element.

h. Length column: The length of the incoming data values. i. Start Position column: The starting position in the incoming flat

file for each specific data element. j. End Position column: The ending position in the incoming flat file

for each specific data element. k. Required: This column specifies if the data element is required to

be received by The Systems. l. Additional Information: Additional notes about the data

element. m. Inbound Data Element Specifications:

IEV417 Inbound Data Elements Specification

2.1.3 Execution Frequency Daily – The batch is ran daily to check if a file is ready to be imported, but the file is only delivered monthly. The exact date the file will be provided is unknown so


the batch will check daily for the file. Schedule the FTP job to auto-purge the inbound reader job when a inbound file is not present.

2.1.4 Key Scheduling Dependencies Schedule the new FTP job to run as a predecessor to the new inbound reader job.

2.1.5 Counties Impacted All Counties.

2.1.6 Volume/Performance A system-wide estimate of approximately 15,000-30,000 records per monthly import is based on sample files provided by DHCS.

2.1.7 Interface Partner California Department of Health Care Services (DHCS)

2.1.8 Failure Procedure/Operational Instructions Batch Support Operations staff will evaluate transmission errors and failures and determine the appropriate resolution (i.e., manually retrieving the file from the directory and contacting the external partner if there is an account or password issue, etc…)

2.2 Asset Verification Search Page

2.2.1 Overview Add the Asset Verification Search page to the application. The Asset Verification Search page allows the user to search for Asset Verification records and filter them accordingly.


2.2.2 Asset Verification Search Page Mockup

Figure 2.2.1- CalSAWS: Asset Verification Search Page (After Search – No Records

Found)

Figure 2.2.2- CalSAWS: Asset Verification Search Page (After Search – Records Found)


2.2.3 Description of Changes 1) Search – This button will use the inputs selected on this page and

populate a sortable table that contains matching results. If a search field is empty or if a selection is not made in a dropdown menu then it will not be used to filter the potential results.

2) Case Number – A seven-character case number can be entered as a search filter.

3) SSN – A social security number can be entered as a search filter and must be in numeric format with 9 digits.

4) Status – This is a dropdown with the following options: a) “New” – This indicates that the record has not been manually

reviewed. b) “Reviewed” - This indicates that the record has been manually

reviewed. 5) Program – This is a dropdown that will contain the potential programs

that can be added to a case could be associated within the application.

6) Retrieve 1000 Rows– This checkbox selection determines whether a search will be bounded to the first 1000 results. It is bounded when checked and unbounded when not checked.

7) Month – This is a dropdown where one of the twelve months can be selected

8) Year – This is a dropdown where a year can be selected. 9) Search Result Summary – Results from the search will display in this

section. a) Case Number – This is the Case Number associated to the Asset

Verification record. Clicking on this link will navigate the user to the Asset Verification Detail page. The security right of ‘AssetVerificationDetailView’ is required to view the link. Without this security right, this will display as read only with no link.

b) SSN – This is the Social Security Number associated to the Asset Verification record, formatted as XXX-XX-XXXX.

c) Status – This field displays the status of the record, which be either “New” or “Reviewed”

d) Program – This field displays the program that is associated with the record.

e) Date – Displays the month and year from which the record originated.

2.2.4 Page Location • Global: Special Units • Local: Asset Verification (Directly below IEVS Abstracts) • Task: Asset Verification – The security right of ‘AssetVerificationSearch’

is required to view this task nav item


2.2.5 Security Updates 1. Security Rights

Security Right Right Description

Right to Group Mapping

AssetVerificationSearch The ability to view the Asset Verification Search page

Asset Verification View Asset Verification Edit

AssetVerificationDetailView The ability to view the Asset Verification Detail page

Asset Verification View Asset Verification Edit

2. Security Groups

Security Group Group Description Group to Role Mapping

Asset Verification View

The ability to view an asset verification record

Eligibility Staff Eligibility Supervisor

Asset Verification Edit

The ability to edit an asset verification record


2.2.6 Page Mapping Add Page mapping to the new fields being added to this page.

2.2.7 Page Usage/Data Volume Impacts There are no expected page use impacts


2.3 Asset Verification Detail Page

2.3.1 Overview Add the Asset Verification Detail page to the application. The Asset Verification Detail page lists and links to the different pages for Financial Institution Details, Real Property Details, Aircraft Details, and Watercraft Details associated to a given case.


2.3.2 Asset Verification Detail Page Mockup

Figure 2.3.1-CalSAWS: Asset Verification Detail Page


2.3.3 Description of Changes 1) Reviewed – This button will change the Status of the record from

“New” to “Reviewed”. This button will only be available when the status is “New”. The security right of ‘AssetVerificationReview’ is required to view this button.

2) Close – This button will navigate the user back to the Asset Verification Search page. Clicking this button will cause the page to not save any changes made.

3) Case Number – This is the case number associated to the Asset Verification record.

4) SSN – This is the SSN associated with the Asset Verification record, formatted as XXX-XX-XXXX.

5) Possible Person Matches – This field lists the possible people that this record could relate to based on the SSN and case number, formatted as [Last Name], [First Name] [Age][Gender]. If there is more than one person that matches they will be separated by a semi-colon. Example: Smith, John 38M; Smith Sally 36F.

6) Status – This is a field with the following possible values: f) “New” – This indicates that the record has not been manually

reviewed. g) “Reviewed” - This indicates that the record has been manually

reviewed. 7) Create a Financial Institutions section containing the following table.

This table displays the information about bank accounts attached to this record.

a) Financial Institution – Display the name of the Financial Institution. This field comes from the data element AVP-BANK-FIN-INSTITUTION. This field will be a hyperlink navigating to Asset Verification – Financial Institution Balance Detail.

b) Account Status – This field indicates the status returned by the financial institution regarding accounts. This field has the following options:

i) Account Found – This indicates that the financial institution found an account and provided its data.

ii) No Account Found – This indicates that the financial institution looked for an account and did not find one.

iii) Will Not Respond – This indicates that the financial institution chose not to respond as to whether an account exists or not.

c) Account Value – Display the most recent balance for the given account. This field comes from the most recent occurrence of the data element AVP-BANK-BALANCE.

d) Account Type – Display the type of account (i.e. Checking, Saving, etc.). This field comes from the data element AVP-BANK-ACCOUNT-TYPE.


8) Create a Real Property section containing the following table. This table displays the information about real property attached to this record.

a) Address – Display the full address of the property using the data elements AVP-PROP-ADDR, AVP-PROP-CITY, AVP-PROP-ZIP, and AVP-PROP-STATE. Format this field as [AVP-PROP-ADDR], [AVP-PROP-CITY], [AVP-PROP-STATE] [AVP-PROP-ZIP]. This field will be a hyperlink navigating to Asset Verification – Real Property Detail.

b) Total Value – Display the current market value of the land plus improvements, before exemptions. This field comes from the data element AVP-PROP-TOTAL-VALUE.

9) Create an Aircraft section containing the following table. This table displays the information about aircraft attached to this record.

a) Serial Number – Display the serial number for the aircraft. This field comes from the data element AVP-AC-SERIAL-NUM. This field will be a hyperlink navigating to Asset Verification – Aircraft Detail.

b) Manufacturer – Display the name of the manufacturer of the aircraft. This field comes from the data element AVP-AC-MFR-NAME.

c) Model – Display the name of the aircraft’s model. This field comes from the data element AVP-AC-MODEL-NAME.

10) Create a Watercraft section containing the following table. This table displays the information about watercraft attached to this record.

a) Hull Number – Display a 12 character alphanumeric descriptor that comes from the data element AVP-WC-HULL-NUM. This field will be a hyperlink navigating to Asset Verification – Watercraft Detail.

b) Make – Display the description of the watercraft’s manufacturer. This field comes from the data element AVP-WC-MAKE-DESC.

c) Model – Display the description of the model which comes from the data element AVP-WC-MODEL-DESC.

d) Purchase Price – Display the amount for which the watercraft was purchased. This field comes from the data element AVP-WC-PURCHASE-PRICE.

2.3.4 Page Location • Global: Special Units • Local: Asset Verification • Task: Asset Verification

2.3.5 Security Updates 1. Security Rights


Security Right Right Description

Right to Group Mapping

AssetVerificationReview The ability to review an Asset Verification record.


2. Security Groups

Security Group Group Description Group to Role Mapping


The ability to edit an asset verification record




2.4 Asset Verification - Financial institution Balance Detail Page

2.4.1 Overview Add the Asset Verification – Financial Institution Balance Detail to the application. The Asset Verification – Financial Institution Balance Detail page displays the details of the account along with a list the account’s balances for the eleven most recent months.


2.4.2 Asset Verification - Financial Institution Balance Detail Page Mockup

Figure 2.4.1- CalSAWS: Financial Institution Balance Detail

2.4.3 Description of Changes 1) Close – This button will navigate the user back to the Asset Verification

Detail page. 2) Create an Account Details section containing the following fields:

a) Account Type – Display the type of account (i.e. Checking, Saving, etc.). This field comes from the data element AVP-BANK-ACCOUNT-TYPE.

b) Account Number – Display the number of the account. This field comes from the data element AVP-BANK-ACCOUNT-NUM.


c) Financial Institution – Display the name of the financial institution. This field comes from the data element AVP-BAnK-FIN-INSTITUTION.

d) Account Title – Display the title of the account. This field comes from the data element AVP-BANK-ACCOUNT-TITLE.

e) Financial Institution Balance for [Month/Year from most recent data imported in MM/YY Format] Date of Inquiry

3) Create a History section containing the following table: a) Create a table with the following column headers

i) Date – This column displays all instances of the data element AVP-BANK-MONTH and the data element AVP-BANK-YEAR in MM/YY format ordered from newest occurrence to oldest occurrence.

ii) Balance – This column displays all instances of the data element AVP-BANK-BALANCE ordered from newest occurrence to oldest occurrence.

4) Financial Institution Remarks – Display the financial institution remarks. This field comes from the data element AVP-BANK-FIN-REMARKS.




2.5 Asset Verification - Real Property Detail Page

2.5.1 Overview Add the Asset Verification – Real Property Detail page to the application. The Asset Verification – Real Property Detail page displays the property details, breakdown of the property value, and the property location.


2.5.2 Asset Verification - Real Property Detail Page Mockup

Figure 2.5.1- CalSAWS: Asset Verification - Real Property Detail


Detail page. 2) Create a Property Details section containing the following fields:

a) Property Type – Display the one-character indicator for whether the property is current or prior. A ‘Current’ will be shown if it is current and a ‘Prior’ will be displayed if it is prior. This field comes from the data element AVP-PROP-TYPE.

b) Recording Type - Display the one-character indicator for whether the record type is deed or assessed. A ‘Deed’ will be shown if it is deed and a ‘Assessed’ will be displayed if it is assessed. This field comes from the data element AVP-PROP-REC-TYPE.

c) Property Owned - Display the one-character indicator for whether the property is owned or not. A ‘Yes’ will be shown if it


is owned and a ‘No’ will be displayed if it is not owned. This field comes from the data element AVP-PROP-OWNED.

d) Document Type – Display the translated value of the deed’s record type (i.e. Deed, Interfamily Transfer). This field comes from the data element AVP-PROP-DOC-TYPE.

e) Sale Date – Display the date on which the sales transaction was legally completed in MM/DD/YYYY format. This field comes from the data element AVP-PROP-SALE-DATE.

f) Recording Date – Display the official date the document was recorded by the county recorder in MM/DD/YYYY format. This field comes from the data element AVP-PROP-RECORDING-DATE.

g) Tax Year – Display the current tax year in YYYY format. This field comes from the data element AVP-PROP-TAX-YEAR.

3) Create a Property Value section containing the following fields: a) Total Value – Display the current market value of the land plus

improvements, before exemptions. This field comes from the data element AVP-PROP-TOTAL-VALUE.

b) Assessed Value – Display the current assessed value of the land plus improvements, before exemptions. This field comes from the data element AVP-PROP-ASSESS-VALUE.

c) Market Value – Display the current market value of the land plus improvements, before exemptions. This field comes from the data element AVP-PROP-MARKET-VALUE.

d) Mortgage Amount – Display the current mortgage of property. This field comes from the data element AVP-PROP-MORTGAGE-AMT

4) Create a Property Location section containing the following fields: a) Property Address – Display the street address of the Real

Property. This field comes from the data element AVP-PROP-ADDR.

b) City – Display the preferred city name associated with the Real Property address. This field comes from the data element AVP-PROP-CITY.

c) ZIP Code – Display the ZIP code associated with the Real Property address. This field comes from the data element AVP-PROP-ZIP.

d) Owner Name 1 – Display the Real Property owner name. This field comes from the data element AVP-PROP-OWNER-NAME1 .

e) Seller Name 1 – Display the seller name of the Real Property. This field comes from the data element AVP-PROP-SELLER-NAME1.

f) Owner Name 2 – Display the Real Property owner name. This field comes from the data element AVP-PROP-OWNER-NAME2.

g) Seller Name 2 – Display the seller name of the Real Property. This field comes from the data element AVP-PROP-SELLER-NAME2.




2.5.6 Page Usage/Data Volume Impacts

There are no expected page use impacts

2.6 Asset Verification - Aircraft Detail Page

2.6.1 Overview Add the Asset Verification – Aircraft Detail page to the application. The Asset Verification – Aircraft Detail page displays the various fields pertaining to information on a given aircraft.

2.6.2 Asset Verification - Aircraft Detail Page Mockup

Figure 2.6.1- CalSAWS: Asset Verification - Aircraft Detail


Detail page. 2) Create an Aircraft Information section containing the following fields:


a) Serial Number – Display the serial number for the aircraft. This field comes from the data element AVP-AC-SERIAL-NUM. If there is no data coming from AVP-AC-SERIAL-NUM in a record, display “Unknown” instead.

b) Manufacturer Name – Display the name of the manufacturer of the aircraft. This field comes from the data element AVP-AC-MFR-NAME.

c) Manufacture Year – Display the year in YYYY format in which the aircraft was manufactured. This field comes from the data element AVP-AC-YEAR-MFR.

d) Model Name – Display the name of the aircraft’s model. This field comes from the data element AVP-AC-MODEL-NAME.

e) Model Code – Display the model code for the aircraft. This field comes from the data element AVP-AC-MFR-MODEL-CODE.

f) Action Date – Display the last date on which the aircraft record was updated. This field comes from the data element AVP-AC-ACTION-DT.

g) Cert Issue Date – Display the date on which the aircraft was first registered in the name of the registered owner in MM/DD/YYYY format. This field comes from the data element AVP-AC-CERT-ISSUE-DT.



2.6.6 Page Usage/Data Volume Impacts

There are no expected page use impacts

2.7 Asset Verification - Watercraft Detail Page

2.7.1 Overview Add the Asset Verification – Watercraft Detail page to the application. The Asset Verification – Watercraft Detail page displays information about the watercraft, the title details of the watercraft, and the purchase details of the watercraft.


2.7.2 Asset Verification - Watercraft Detail Page Mockup

Figure 2.7.1- CalSAWS: Asset Verification - Watercraft Detail


Detail page. 2) Create a Watercraft Information section and add the following fields:

a) Hull Number – Display a 12 character alphanumeric descriptor that comes from the data element AVP-WC-HULL-NUM. If there is no data coming from AVP-WC-HULL-NUM in a record, display “Unknown” instead.


b) Watercraft ID – Display a 10 character alphanumeric descriptor that comes from the data element AVP-WC-ID.

c) Length – Display the length of the watercraft in inches. This field comes from the data element AVP-WC-LENGTH.

d) Hull Type Description – Display the description of the hull type (i.e. Fiberglass, Wood, Steel, Other). This field comes from the data element AVP-WC-HULL-TYPE-DESC.

e) State of Origin – Display the two letter code that applies to the state of origin. This field comes from the data element AVP-WC-ORIGIN-ST.

f) Model Year – Display the four-digit year relating to to when the vessel was manufactured, or when the model/series was designated by the manufacturer. This field comes from the data element AVP-WC-MODEL-YEAR.

g) Model Description – Display the description of the model which comes from the data element AVP-WC-MODEL-DESC.

h) Make Code – Display the description of the watercraft’s class (i.e. ’16-26 ft’, ‘less than 16 ft’, etc.) This field comes from the data element AVP-WC-MAKE-CODE.

i) Make Description – Display the description of the watercraft’s manufacturer. This field comes from the data element AVP-WC-MAKE-DESC.

3) Create a Title Details section containing the following fields: a) Title State - Display the two letter code that applies to the state

in which the title was issued. This field comes from the data element AVP-WC-TITLE-STATE.

b) Title Status – Display the description of the status (i.e. Original, Reinstate, Duplicate, Transfer). This field comes from the data element AVP-WC-TITLE-STATUS-DESC.

c) Title Number – Display the title number. This field comes from AVP-WC-TITLE-NUM.

d) Title Type Description – Display the title type description. This field comes from AVP-WC-TITLE-TYPE-DESC.

e) Title Issue Date – Display the date on which the title was issued. This field comes from the data element AVP-WC-TITLE-ISSUE-DT.

4) Create a Purchase Details section containing the following fields: a) Purchase State – Display the two-letter code for the state in

which the watercraft was purchased. This field comes from the data element AVP-WC-STATE-PURCHASE.

b) Purchase Price – Display the amount for which the watercraft was purchased. This field comes from the data element AVP-WC-PURCHASE-PRICE.

c) New/Used – Displays a one-character indicator showing whether the watercraft was purchased new or used. This field comes from the data element AVP-WC-NEW-USED-FLAG.

d) Transaction Type Description – Display the description of the type of transaction that created the record/registration (i.e.


Original, Duplicate, Transfer, Renewal). This field comes from the data element AVP-WC-TRANS-TYPE-DESC.

e) Reg. Status Description – Display the description of the registration status (i.e. Active, Expired, Transferred, Destroyed, Lost/Stolen). This field comes from the data element AVP-WC-REG-STAT-DESC.

f) Reg. Renewal Date – Display the date on which the registration is renewed in MM/DD/YYYY format. This field comes from the data element AVP-WC-REG-RENEWAL-DT.

g) Reg. State – Display the two-letter code for the state in which the watercraft was registered. This field comes from the data element AVP-WC-REG-STATE.

h) Reg. Number – Display the state’s registration number assigned to the vessel. This field comes from the data element AVP-WC-REG-NUM.

i) Reg. Date – Display the date on which the registration was first issued in MM/DD/YYYY format. This field comes from the data element AVP-WC-REG-DATE.

j) Decal Number – Display the decal number for the watercraft. This field comes from the data element AVP-WC-DECAL-NUM.



2.7.6 Page Usage/Data Volume Impacts There are no expected page use impacts.


3 SUPPORTING DOCUMENTS

Number Functional Area

Description Attachment

1 Batch Design

MEDS to SAWS Interface Specifications

IEV417 Inbound Data Elements Specification

2 Batch Design

DHCS provided layout of the IEV417 flat file

Layout IEV417_08152019.pd

3 Batch Design

DHCS provided additional details of the IEV417 flat file

DHCS_PP_IEV417_08152019.pdf

4 Batch Design

DHCS provided data dictionary

Asset Verification Data Dictionary_0815

5 Online MEDS future user interface

DHCS_PP_Future Applicant Process_08

6 Online Security Matrix

AssetVerificationSecurityMatrix.xls


4 REQUIREMENTS

4.1 Project Requirements

REQ # REQUIREMENT TEXT How Requirement Met

5 OUTREACH An SCR will be created in CalSAWS for training and job aid updates.


Design Document

CA-210559 CIV-106141 ACL 20-78 FC, KG CNI Rate Increase

2

CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By S Meenavalli

Reviewed By Ritu Chinya, Paul G, Ignacio

DATE DOCUMENT

VERSION REVISION DESCRIPTION AUTHOR

6/22/2020 1.0 Initial Design S Meenavalli 8/5/2020 1.1 Added recommendation to update

the ACL reference for FC/KG COLA NOA regulations

Nithya Chereddy

3

Table of Contents 1 Overview ........................................................................................................................... 5

1.1 Current Design ........................................................................................................... 5

1.2 Requests ..................................................................................................................... 5

1.3 Overview of Recommendations .............................................................................. 5

1.4 Assumptions ............................................................................................................... 6

2 Recommendations ........................................................................................................... 6

2.1 Schedule A Basic rates for HBFC Homes (LRS/CalSAWS and C-IV) ....................... 6

2.1.1 Description of Changes ................................................................................ 7

2.2 Schedule A specialized Rates for HBFC Homes (LRS/CalSAWS Only) ................... 7

2.3 Schedule B Basic Rates for HBFC Homes (LRS/CalSAWS and C-IV) ...................... 7


2.4 Schedule B specialized Rates for HBFC Homes (LRS/CalSAWS Only) .................... 8

2.5 Level of Care Basic Rates for HBFC Homes (LRS/CalSAWS and C-IV) ................... 8


2.6 Level of Care specialized Rates for HBFC Homes (LRS/CalSAWS Only) ................ 9

2.7 Dual Agency / Regional Center Rates (C-IV Only) ................................................ 9


2.8 Dual Agency / Regional Center Rates (LRS/CalSAWS Only) ................................10

2.8.1 Description of Changes ...............................................................................10

2.9 Foster Family Agencies (FFAs) age based Rates (LRS/CalSAWS and C-IV) .........10


2.10 Foster Family Agencies (FFAs) Level of Care Rates (LRS/CalSAWS and C-IV) .....10


2.11 Intensive Services Foster Care (ISFC) Rates (LRS/CalSAWS and C-IV) .................11


2.12 Group Homes (LRS/CalSAWS and C-IV) .................................................................11


2.13 Short-Term Residential Therapeutic Program (STRTP) Rate Type (LRS/CalSAWS and C-IV) ..........................................................................................................................12


2.14 Transitional Housing Placement – Plus – Foster Care (THP+FC) (LRS/CalSAWS and C-IV) ..................................................................................................................................13


4

2.15 Journal Entry Updates (LRS/CalSAWS only) ............................................................13

2.15.1 Foster Care Journal Entry .............................................................................13

2.15.2 Kin-GAP Journal Entry ...................................................................................14

2.16 NOA Changes ..........................................................................................................14

2.16.1 Updates to generate a COLA NOA ............................................................14

3 Supporting Documents ...................................................................................................14

4 Requirements ...................................................................................................................15

4.1 Project Requirements ...............................................................................................15

5 Migration Impacts ...........................................................................................................15

6 Outreach ..........................................................................................................................16

7 Appendix..........................................................................................................................16

5

1 OVERVIEW This document details the changes necessary in LRS/CalSAWS and C-IV to implement the adjusted schedules of rates that reflect the California Necessities Index (CNI) increase of 3.72% for Fiscal Year (FY) 2020-21 for Foster Care (FC) and Kin-GAP (KG) programs.

In LRS/CalSAWS, ARC is a subset of the Foster Care program, so the rates for ARC are implicitly updated by updating the Foster Care rates to the new levels for the FY 2020-21.

The CNI increase is applicable to out-of-home placements and the Aid to Families with Dependent Children-Foster Care (AFDC-FC) program.

This document also reflects the CNI increase to be applied to Dual Agency and other additional rates applicable to FC programs effective July 1, 2020.

The one-time batch run details related to the CNI COLA Rate increase for FC/KG programs can be found under the SCR’s CA-217268 for LRS/CalSAWS and CIV-107488 for C-IV Systems.

1.1 Current Design Currently LRS/CalSAWS and C-IV use the CNI rates of FY 2019-20 that are effective from July 1, 2019. C-IV and LRS/CalSAWS generates Rate Change NOAs to notify FC/KG vendors when FC/KG Monthly rate changes due to COLA or any other reason.

1.2 Requests

• As per the ACL 20-78, the new CNI rate increase for the FY 2020-21 will be implemented in LRS/CalSAWS and C-IV effective July 1, 2020.

• C-IV - Add an entry of COLA Month to the COLA Program Months CT table for FC/KG COLA NOAs to be generated.

• LRS/CalSAWS – Update the hard-coded COLA begin and end dates to the new dates for NOAs to be generated with correct COLA month.

• Update the regulation reference of ACL 19-70 to ACL 20-78 for FC/KG COLA NOA.

1.3 Overview of Recommendations

• The Code detail tables that reflect the CNI rates will be updated for all the applicable placement types.

• Update the CT744_DC Short and Long Decode names from “DCFS Annual COLA” to “CWS Annual COLA”.

• C-IV - Add an entry of COLA Month to the COLA Program Months CT table for FC/KG COLA NOAs to be generated.

• LRS/CalSAWS – Update the hard-coded COLA begin and end dates to the new dates for NOAs to be generated with correct COLA month.

• Update the FC/KG COLA regulations to remove the ACL reference of 19-70 and add the ACL NO. 20-78.

6

1.4 Assumptions

• Under this SCR, Eligibility is only updating the amounts and effective dates of CNI rates in the Code Tables.

• COLA Rate in rate/code table updates are only the scope of this SCR. • No change will be made to Rate determination logic in this SCR. • Home Based Family Care (HBFC) Providers list referred in this SCR can be found

at the end of design document. • HBFC LOC2 thru LOC4 rates will not have change based on the CDSS/State

recommendation that they will release another ACL if required. • Foster Family Agency (FFA) facility types list referred in this SCR can be found at

the end of design document. • Existing COLA rate change NOA will generate during the COLA Batch run with

the COLA effective month of July 2020 for FC/KG in C-IV and KG in LRS/CalSAWS. • LRS/CalSAWS: Existing FC COLA rate change NOA will generate during the

COLA Batch run with the effective months from July 2020 through Batch run months based on the EDBC run month.

• During the batch EDBC COLA run, the CCR Rate Change NOA will not be generated for EDBCs that have a rate change and are run for COLA month (LRS/CalSAWS Only).

• FC/KG Monthly rates that are changed manually by worker may result into generation of FC/KG COLA NOA if the Rate change effective month is same as COLA effective month for the program and EDBC is run for that month. Workers may suppress the generated COLA NOA in such cases and generate a manual NOA for FC/KG Rate change.

• Threshold FC/KG COLA NOAs will be added to the systems by a future SCR CA-209638/CIV-104665

• Under this SCR, there will be no impact to Fiscal process such as creating the issuances and then sending those issuances to the Auditor Controller in a separate COLA file.

• No COLA changes will be made to the Infant Supplement. • Batch EDBC will continue to use the run reason "DCFS Annual COLA" for the Fiscal

COLA payment file (LRS/CalSAWS Only). • Batch EDBC will have a run reason for every month of COLA run (i.e. July, Aug,

Sept).(LRS/CalSAWS Only).

2 RECOMMENDATIONS The CNI rates will be updated in LRS/CalSAWS and C-IV code tables for all the applicable placement types for Foster Care (FC) and Kin-GAP (KG) Programs.

2.1 Schedule A Basic rates for HBFC Homes (LRS/CalSAWS and C-IV)

• Schedule A Basic rates are applicable to both LRS/CalSAWS and C-IV systems. • Schedule A rates apply to Kin-GAP cases in which dependency was dismissed

and NRLG cases including probate whose guardianship was established, prior to May 1, 2011.

7

• For Foster Care programs these rates are paid when the child is in a Facility that receives the Home-Based Family Care (HBFC) rates and the selected Basic Rate Code in the rate detail page is Schedule A (LRS/CalSAWS Only; automatically set in C-IV).

• For Kin-GAP programs these rates are paid when the “Date of Legal Guardianship” is prior to May 1, 2011 in LRS/CalSAWS or Case Dismissal Date is prior to May 1, 2011 in C-IV.

2.1.1 Description of Changes • Update HBFC Homes age-based standard state rates in LRS/CalSAWS

and C-IV for Schedule A by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

2.2 Schedule A specialized Rates for HBFC Homes (LRS/CalSAWS Only)

• Schedule A LRS/CalSAWS only specialized rates. • The D, F1 thru F4 rates for Schedule A are only applicable to LRS/CalSAWS and

these rates need to be updated in LRS/CalSAWS only.

2.3 Schedule B Basic Rates for HBFC Homes (LRS/CalSAWS and C-IV)

• Schedule B Basic rates are applicable to both LRS/CalSAWS and C-IV systems. • Schedule B rates applies to Kin-GAP cases where dependency was dismissed

and NRLG cases including probate guardianship and guardianships established by the juvenile court, between May 1, 2011 and December 31, 2016.

• For Foster Care programs these rates are paid when the child is in a Facility that receives the Home Based Family Care (HBFC) rates and the selected Basic Rate Code in the rate detail page is Schedule B (LRS/CalSAWS Only; automatically set in C-IV).

Age 0-4 5-8 9-11 12-14 15 and Over

Basic $603 $656 $702 $774 $849

Age 0-4 5-8 9-11 12-14 15 and Over

D Rate $1,379 $1,370 $1,365 $1,389 $1,411

F1 Rate $972 $959 $956 $980 $999

F2 Rate $1,118 $1,108 $1,103 $1,128 $1,146

F3 Rate $1,379 $1,370 $1,365 $1,389 $1,411

F4 Rate $1,601 $1,588 $1,585 $1,611 $1,626

8

• For Kin-GAP programs these rates are paid when the “Date of Legal Guardianship” is on / after May 1, 2011 and KG Summary begin date is on / before December 31, 2016 in LRS or Case Dismissal Date is on / after May 1, 2011 and on / before December 31, 2016 in C-IV.

2.3.1 Description of Changes • Update HBFC Homes age-based standard state rates in LRS/CalSAWS

and C-IV for Schedule B by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

2.4 Schedule B specialized Rates for HBFC Homes (LRS/CalSAWS Only)

• Schedule B LRS/CalSAWS only specialized rates. • The D, F1 thru F4 rates for Schedule B are only applicable to LRS/CalSAWS and

these rates need to be updated in LRS/CalSAWS only.

2.5 Level of Care Basic Rates for HBFC Homes (LRS/CalSAWS and C-IV)

• Level of Care Basic rates are applicable to both LRS/CalSAWS and C-IV systems. • For Foster Care programs these rates are paid when the child is in a Facility that

receives the Level of Care rate and the Benefit Month is on or after January 2017. • For Kin-GAP programs these rates are paid when the Case Dismissal Date is on

or after January 1, 2017 in C-IV or Kin-GAP Summary Begin Date is on or after January 1, 2017 in LRS/CalSAWS.

2.5.1 Description of Changes • Update the HBFC Homes LOC1 (Basic Level) Rate by end-dating the

rate/code table records that began 07/01/2019 with an end date of

Age 0-4 5-8 9-11 12-14 15 and Over

Basic $825 $891 $939 $983 $1,030

Age 0-4 5-8 9-11 12-14 15 and Over

D Rate $1,601 $1,605 $1,602 $1,598 $1,592

F1 Rate $1,194 $1,194 $1,193 $1,189 $1,180

F2 Rate $1,340 $1,343 $1,340 $1,337 $1,327

F3 Rate $1,601 $1,605 $1,602 $1,598 $1,592

F4 Rate $1,823 $1,823 $1,822 $1,820 $1,807

9

06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following LOC1 rate:

Level of Care Basic Level Rate

Basic $1,037

2.6 Level of Care specialized Rates for HBFC Homes (LRS/CalSAWS Only)

• Level of Care Rates LRS/CalSAWS only specialized rates. • The D, F1 thru F4 rates for HBFC Homes LOC1 (Basic Level) rates are only

applicable to LRS/CalSAWS and these rates need to be updated in LRS/CalSAWS only.


D Rate $1,638

F1 Rate $1,228

F2 Rate $1,378

F3 Rate $1,638

F4 Rate $1,858

2.7 Dual Agency / Regional Center Rates (C-IV Only)

• In C-IV system, Birth up to 3 years is California Early Start Intervention Rate (CT 335 - MY), and 3 years and older is Lanterman Developmental Disability Rate (CT 335 - MZ).

2.7.1 Description of Changes • Update Dual Agency rates in C-IV by end-dating the rate/code table

records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Age FY 2020-21

Birth up to 3 years $1,215

*3 years and older $2,714

10

2.8 Dual Agency / Regional Center Rates (LRS/CalSAWS Only)

• In LRS/CalSAWS system, these rates are paid when the rate selected on a case is “Dual Agency RC-California Early Start Intervention (P1)” or “Dual Agency RC-Lanterman Developmental Disability (P2)”.

2.8.1 Description of Changes • Update “Dual Agency/Regional Center” rates in LRS/CalSAWS by end-

dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Description Rate

Dual Agency RC-California Early Start Intervention (P1) $1,215

Dual Agency RC-Lanterman Developmental Disability (P2) $2,714

2.9 Foster Family Agencies (FFAs) age based Rates (LRS/CalSAWS and C-IV)

• These rates are paid on age based Foster Care programs with a facility type of “Foster Family Agency (FFA)” placements made prior to 12/01/2017.

2.9.1 Description of Changes • Update “Foster Family Agencies (FFAs)” age based rates in

LRS/CalSAWS and C-IV by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Age 0-4 5-8 9-11 12-14 15 & Over

Basic $2,280 $2,346 $2,394 $2,438 $2,485

2.10 Foster Family Agencies (FFAs) Level of Care Rates (LRS/CalSAWS and C-IV)

• These rates are paid on LOC Rate Foster Care programs with a facility type of FFA placements made after 12/01/2017.

2.10.1 Description of Changes • Update “Foster Family Agencies (FFAs)” LOC rates in LRS/CalSAWS and

C-IV by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

11

Level of Care Basic Level Rate LOC2 LOC3 LOC4

Basic $2,303 $2,465 $2,629 $2,827

2.11 Intensive Services Foster Care (ISFC) Rates (LRS/CalSAWS and C-IV)

• These rates are paid on Foster Care programs when an ISFC rate is selected.

2.11.1 Description of Changes • Update “Intensive Services Foster Care (ISFC)” rates in LRS/CalSAWS and

C-IV by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

LRS/CalSAWS Only:

ISFC Options Rate

ISCO - ISFC – County $6,388

ISFA - ISFC – FFA $6,388

ISFO - ISFC - Family-Only $2,706

ISTF - ISFC – TFC $6,388

C-IV Only:

ISFC Options Rate

ISFC-RF $2,706

County or FFA ISCF $6,388

2.12 Group Homes (LRS/CalSAWS and C-IV)

• These rates are paid on Foster Care programs when using the standard rate and the placement is a facility type “Group Home” or “Community Treatment Facility.”

2.12.1 Description of Changes • Update “Group Home” rates in LRS/CalSAWS and C-IV by end-dating

the rate/code table records that began 07/01/2019 with an end date

12

of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

RCL Rate

1 $2,865

2 $3,578

3 $4,292

4 $5,002

5 $5,712

6 $6,430

7 $7,141

8 $7,858

9 $8,567

10 $9,283

11 $9,992

12 $10,708

13 $11,429

14 $12,139

2.13 Short-Term Residential Therapeutic Program (STRTP) Rate Type (LRS/CalSAWS and C-IV)

• These rates are paid on Foster Care programs when the rate level is “Short Term Residential Therapeutic Program (STRTP)”.

2.13.1 Description of Changes • Update “Short-Term Residential Therapeutic Program (STRTP)” rates in

LRS/CalSAWS and C-IV by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rate:

Rate

STRTP $14,035

13

2.14 Transitional Housing Placement – Plus – Foster Care (THP+FC) (LRS/CalSAWS and C-IV)

• These rates are paid on Foster Care programs when the placement is a facility type of “Transitional Housing Placement + FC (THP+FC)” and the corresponding rate from the list below is selected.

2.14.1 Description of Changes • Update all “Transitional Housing Placement – Plus – Foster Care

(THP+FC)” rates in LRS/CalSAWS and C-IV by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Rate

THP+FC SINGLE SITE $3,603

THP+FC REMOTE SITE $3,603

THP+FC HOST SITE $2,867

2.15 Run Reason Update (LRS/CalSAWS only)

2.15.1 EDBC Run Reason Update the EDBC Run Reason CT744_DC to reflect “DCFS” term to an applicable 58-county term “CWS”. Current Short / Long Description: DCFS Annual COLA New Short / Long Description: CWS Annual COLA

2.16 Journal Entry Updates (LRS/CalSAWS only)

2.16.1 Foster Care Journal Entry Batch EDBC will insert the below Journal entry for Foster Care (FC) programs. Short Description: Batch EDBC ran for <Month Year>. Long Description: Batch EDBC Ran for <Month Year>. Batch EDBC processed for the <Program Name> program for following reasons: Foster Care COLA

14

2.16.2 Kin-GAP Journal Entry Batch EDBC will insert the below Journal entry for Kin-GAP (KG) programs. Short Description: Batch EDBC ran for <Month Year>. Long Description: Batch EDBC Ran for <Month Year>. Batch EDBC processed for the <Program Name> program for following reasons: Kin-GAP COLA

2.17 NOA Changes As part of the SCRs CA-206310 CIV-100485 - ACL 19-70 Foster Care and Kin-GAP COLA Rate Increase for Year 2019, functionality was added to C-IV and LRS/CalSAWS to generate a FC or KG COLA NOA when the FC/KG EDBC is run for COLA period and there is an increase in FC/KG monthly rate amount compared to the monthly rate amount of previous Accepted and Saved EDBC.

2.17.1 Updates to generate a COLA NOA 1. C-IV - Add an entry to COLA Program Months CT table with the new

COLA effective month of July 2020. 2. LRS/CalSAWS – Update the hard-coded COLA begin date from July 1st,

2019 to July 1st, 2020 and COLA end date from October 31st, 2019 to COLA Batch run month end date i.e. October 31st 2020.

See supporting Documents #1 and #2 for FC and KG COLA NOA language.

2.17.2 Regulation Updates 1. Update the regulations for FC/KG COLA reason fragments to replace

ACL NO. 19-70 with ACL NO. 20-78. Following are the updated regulations.

2. LRS: W&I Code Sections 11364, 11387, 11453, 11460, 11461 ,11461(d)(2)(A), 11462, 11463, 11464, 18254, 18358.30; ACL NO. 20-78; Senate Bill (SB) 1013, Chapter 35, Statutes Of 2012; Assembly Bill (AB) 403, Chapter 773, Statutes Of 2015; AB 1997, Chapter 612, Statutes Of 2016.

3. C-IV: KG - W&I Code Sections 11364, 11387, 11453, 11460, 11461 ,11461(d)(2)(A), 11462, 11463, 11464, 18254, 18358.30; ACL 20-78; SB 1013, Chapter 35, Statutes Of 2012; AB 403, Chapter 773, Statutes Of 2015; AB 1997, Chapter 612, Statutes Of 2016

15

FC - W&I Code Section 18254; W&I Code Section 18358.30; ACL 20-78; SB 1013, Chapter 35, Statutes Of 2012; AB 403, Chapter 773, Statutes Of 2015; AB 1997, Chapter 612, Statutes Of 2016


Number Functional Area Description Attachment

1. Client Correspondence

FC COLA NOA Language

FC COLA NOA Language Mock-up.pd

2. Client Correspondence

KG COLA NOA Language

KG COLA NOA Language Mockup.pdf

4 REQUIREMENTS



2.16.1.2 The LRS shall include an automated method for implementing mass updates triggered by policy changes or mass participant financial changes, including Social Security or Veterans benefits cost of living adjustments (COLAs).

The new CNI Rates released by the County will be updated in the system. These new COLA rates will be used to determine the eligibility benefits.

2.16.4.1 The LRS shall include the ability to process a mass update that includes eligibility and benefits with an effective date of any prior month, the current month, or future month(s).

The Batch EDBC process will be run and determine eligibility using the new CNI Rates.

5 MIGRATION IMPACTS None

16

6 OUTREACH None

7 APPENDIX HBFC (Home-Based Family Care) Providers:

1) Foster Family Home 2) Foster Family Home – Shelter Care 3) Legal Guardian 4) Non-Relative Extended Family Member Home 5) Relative Home 6) Specialized Foster family Home 7) Supervised Independent Living 8) Tribal Specific Home 9) County Shelter / Receiving Home (Non – EA/AFDC) – LRS/CalSAWS Only 10) Court Specified Home – LRS/CalSAWS Only 11) Guardian Home – LRS/CalSAWS Only 12) Resource family Home – LRS/CalSAWS Only 13) Small Family Home – LRS/CalSAWS Only 14) Temporary Shelter Home – LRS/CalSAWS Only

FFA Providers:

1) Foster Family Agency 2) Foster Family Agency (Intensive Programs) 3) Foster Family Agency (Nontreatment) 4) Foster Family Agency (Treatment) 5) Foster Family Agency Certified Resource Family Home (FFACRFH) (Nontreatment)

– LRS/CalSAWS Only 6) Foster Family Agency Certified Resource Family Home (FFACRFH) (Treatment) --

LRS/CalSAWS Only


Design Document

CA-210584 ACL 20-68 AAP CNI Rate Increase for 2020 Year

2

CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By S Meenavalli

Reviewed By Ritu Chinya, Girish Chakkingal

DATE DOCUMENT


6/22/2020 1.0 Initial Design S Meenavalli

3


1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 Eligibility Rate Changes: AAP Rate Details .............................................................. 5

2.1.1 Rates for initial AAP agreements signed 10/1/1992 to 12/31/2007 and adoption finalized before 05/27/2011 – Table A .................................................... 5

2.1.2 Rates for initial AAP agreements signed 1/1/2008 to 5/27/2011 and adoption finalized before 05/27/2011 – Table B ..................................................... 5

2.1.3 Rates for initial AAP agreements signed and adoption finalized on or after 5/27/2011 to 12/31/2016 – Table C ................................................................. 6

2.1.4 Rates for initial AAP agreements signed on or after 01/01/2017 (Age Based Rate value selection) .................................................................................... 6

2.1.5 Rates for initial AAP agreements signed on or after 01/01/2017 (LOC Rates) 7

2.2 Journal Entry Updates ............................................................................................... 7

2.2.1 AAP Journal Entry ........................................................................................... 7

2.3 Update AAP NOA with New CNI Reason .................. Error! Bookmark not defined. 2.3.1 Update the CNI Verbiage in the AAP NOA ... Error! Bookmark not defined. 2.3.2 Add new Variable Population ........................ Error! Bookmark not defined. 2.3.3 Update Section Generation Conditions for AAP NOA Error! Bookmark not defined.

3 Supporting Documents .................................................................................................... 8

4 Requirements .................................................................................................................... 9

4.1 Project Requirements ................................................................................................ 9

5 Migration Impacts ............................................................................................................ 9

6 Outreach ........................................................................................................................... 9

7 Appendix........................................................................................................................... 9

4

1 OVERVIEW This document details the changes necessary in LRS/CalSAWS to implement the adjusted schedules of rates that reflect the California Necessities Index (CNI) increase of 3.72% for Fiscal Year (FY) 2020-21 for Adoption Assistance Program (AAP) Cases.

In C-IV, AAP is a manual EDBC process and no impact of this change for C-IV Counties.

This document reflects the CNI increase to be applied to Adoption Homes applicable to AAP cases effective July 1, 2020.

The one-time batch run details related to the CNI COLA Rate increase for AAP Cases can be found under the SCR CA-217269 for LRS/CalSAWS System.

1.1 Current Design Currently LRS/CalSAWS uses the CNI rates of FY 2019-20 that are being effective from July 1, 2019.

1.2 Requests As per the ACL 20-68, the new CNI rate increase for the FY 2020-21 will be implemented in LRS/CalSAWS for AAP Program effective July 1, 2020.

1.3 Overview of Recommendations

• The Code detail tables that reflect the AAP CNI rates will be updated for all the applicable placement types.

• Update regulations on the AAP NOA with new ACL number i.e. ACL 20-68.

1.4 Assumptions

1. Under this SCR, Eligibility is only updating the amounts and effective dates of CNI rates in the Code Tables.

2. COLA Rates in code detail table updates are only the scope of this SCR. 3. No change will be made to Rate determination logic in this SCR 4. AAP Placement Providers list referred in this SCR can be found at the end of

design document. 5. LOC2 thru LOC4 rates will not have change based on the CDSS/State

recommendation that they will release another ACL if required. 6. Under this SCR, there will be no impact to Fiscal such as creating the issuances

and then sending those issuances to the Auditor Controller in a separate COLA file.

7. Batch EDBC will continue to use the run reason "DCFS Annual COLA" for the Fiscal COLA payment file.

8. Batch EDBC will have a run reason for every month of COLA run. 9. No additional Threshold Languages will be added for the AAP NOA for this effort. 10. Regression test AAP COLA rate change NOA to check the population of the

fiscal year the Fiscal year 2020 – 2021(language below).

5

a. The California Necessities Index (CNI) has increased for Fiscal Year 2020 – 2021

2 RECOMMENDATIONS The CNI rates will be updated in LRS/CalSAWS code tables for all the applicable placement types for AAP Program Cases.

2.1 Eligibility Rate Changes: AAP Rate Details

2.1.1 Rates for initial AAP agreements signed 10/1/1992 to 12/31/2007 and adoption finalized before 05/27/2011 – Table A Update the AAP rates in LRS/CalSAWS for initial AAP agreements signed on or after October 1, 1992 through December 31, 2007 where the adoption was finalized before May 27, 2011 by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Age 0-4 5-8 9-11 12-14 15 & Over

Basic $575 $625 $677 $737 $809

D Rate $1,314 $1,305 $1,308 $1,323 $1,344

F1 Rate $926 $914 $919 $933 $952

F2 Rate $1,065 $1,055 $1,059 $1,074 $1,092

F3 Rate $1,314 $1,305 $1,308 $1,323 $1,344

F4 Rate $1,525 $1,513 $1,518 $1,534 $1,549

2.1.2 Rates for initial AAP agreements signed 1/1/2008 to 5/27/2011 and adoption finalized before 05/27/2011 – Table B Update the AAP rates in LRS/CalSAWS for initial AAP agreements signed on or after January 1, 2008 through May 27, 2011 where the adoption was finalized on or before May 27, 2011 by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Age 0-4 5-8 9-11 12-14 15 & Over

Basic $603 $656 $709 $774 $849

D Rate $1,379 $1,370 $1,372 $1,389 $1,411

6

F1 Rate $972 $959 $963 $980 $999

F2 Rate $1,118 $1,108 $1,110 $1,128 $1,146

F3 Rate $1,379 $1,370 $1,372 $1,389 $1,411

F4 Rate $1,601 $1,588 $1,592 $1,611 $1,626

2.1.3 Rates for initial AAP agreements signed and adoption finalized on or after 5/27/2011 to 12/31/2016 – Table C Update the AAP rates in LRS/CalSAWS for initial AAP agreements signed and adoption finalized on or after May 27, 2011 through December 31, 2016 by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:

Age 0-4 5-8 9-11 12-14 15 & Over

Basic $825 $891 $939 $983 $1,030

D Rate $1,601 $1,605 $1,602 $1,598 $1,592

F1 Rate $1,194 $1,194 $1,193 $1,189 $1,180

F2 Rate $1,340 $1,343 $1,340 $1,337 $1,327

F3 Rate $1,601 $1,605 $1,602 $1,598 $1,592

F4 Rate $1,823 $1,823 $1,822 $1,820 $1,807

2.1.4 Rates for initial AAP agreements signed on or after 01/01/2017 (Age Based Rate value selection) Update the AAP rates in LRS/CalSAWS for initial AAP agreements signed on or after January 01, 2017 by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates: Note: These are for cases that have an agreement sign date on or after January 01, 2017 but the worker has selected age-based rates in the AAP placement page. Even though the selected rate type is age-based by the user in LRS/CalSAWS, all the rate values are updated to the Basic Level LOC rate value in the database.

Age 0-4, 5-8, 9-11, 12-14, 15 & Over

Basic $1,037

7

D Rate $1,638

F1 Rate $1,228

F2 Rate $1,378

F3 Rate $1,638

F4 Rate $1,858

2.1.5 Rates for initial AAP agreements signed on or after 01/01/2017 (LOC Rates) Update the AAP rates in LRS/CalSAWS for initial AAP agreements signed on or after January 01, 2017 by end-dating the rate/code table records that began 07/01/2019 with an end date of 06/30/2020. Insert new rate/code table records effective 07/01/2020 with the following rates:


Basic $1,037

D Rate $1,638

F1 Rate $1,228

F2 Rate $1,378

F3 Rate $1,638

F4 Rate $1,858

2.2 Journal Entry Updates

2.2.1 AAP Journal Entry Batch EDBC will insert the below Journal entry for AAP programs. Short Description: Batch EDBC ran for <Month Year>. Long Description: Batch EDBC Ran for <Month Year>. Batch EDBC processed for the <Program Name> program for following reasons: AAP COLA

8

2.3 NOA Regulation update

2.3.1 Overview As part of SCR CA-208921 AAP COLA Rate Increase, the following regulations were added as part of the AAP rate change NOA. Rules: These rules apply: SENATE BILL (SB) 1013, CHAPTER 35, STATUTES OF 2012; ASSEMBLY BILL (AB) 403, CHAPTER 773, STATUTES OF 2015; AB 1997, CHAPTER 612, STATUTES OF 2016; WELFARE AND INSTITUTIONS CODE (WIC) SECTIONS 11364, 11387, 11453, 11460, 11461 ,11461(d)(2)(A), 11462, 11463, 11464, 18254, 18358.30; ACL NO. 19-58.

2.3.2 Regulation update Update the (AA_CH_RATE_INCREASE_P009 XDP) ACL in the regulations for AAP COLA rate change NOA from ACL. 19-58 to ACL. 20-68. Updated regulation is listed below. Rules: These rules apply: SENATE BILL (SB) 1013, CHAPTER 35, STATUTES OF 2012; ASSEMBLY BILL (AB) 403, CHAPTER 773, STATUTES OF 2015; AB 1997, CHAPTER 612, STATUTES OF 2016; WELFARE AND INSTITUTIONS CODE (WIC) SECTIONS 11364, 11387, 11453, 11460, 11461 ,11461(d)(2)(A), 11462, 11463, 11464, 18254, 18358.30; ACL NO. 20-68.




9

4 REQUIREMENTS



2.16.1.2 The LRS shall include an automated method for implementing mass updates triggered by policy changes or mass participant financial changes, including Social Security or Veterans benefits cost of living adjustments (COLAs).

The new CNI Rates released by the County will be updated in the system. These new COLA rates will be used to determine the eligibility benefits.

5 MIGRATION IMPACTS None

6 OUTREACH None

7 APPENDIX AAP Placement Providers:

1. Adoptive Homes 2. Foster Family Agency 3. Foster Family Home 4. Group Home 5. Legal Guardian 6. Nonrelative Extended Family Member Home 7. Out of State Residential Treatment Facilities 8. Relative Home 9. Small Family Home 10. Specialized Foster Family Home 11. Supervised Independent Living



Design Document

CA-211747 CALFRESH NOTICE OF MISSED INTERVIEW


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Raj Devidi

Reviewed By Pramukh Karla

DATE DOCUMENT


08/07/2020 1.0 Original Raj Devidi



1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 Add CF 386 (2/14) CalFresh Notice of Missed Interview form ............................... 4

2.1.1 Overview ........................................................................................................ 4

2.1.2 Description of Change .................................................................................. 4


4 Requirements .................................................................................................................... 5

4.1 Migration Requirements............................................................................................ 5


1 OVERVIEW The purpose of this change is to add CF 386 (2/14) CalFresh Notice of Missed Interview form in Arabic, Hmong and Lao threshold languages.

1.1 Current Design CF 386 (2/14) CalFresh Notice of Missed Interview form currently exists in English, Spanish, Armenian, Cambodian, Chinese, Farsi, Korean, Tagalog, Russian, Vietnamese.

1.2 Requests Add CF 386 (2/14) form in Arabic, Hmong and Lao.

1.3 Overview of Recommendations 1. Add C 386 (2/14) CalFresh Notice of Missed Interview form in Arabic, Hmong

and Lao forms to LRS/CalSAWS Template Repository. 2. Update CT942 to generate CF 386 (2/14) from batch.

1.4 Assumptions 1. CF 386 (2/14) Arabic, Hmong and Lao forms will use the LRS/CalSAWS Standard

Header. 2. Print options remain same for CF 386 (2/14) current forms and the same will be

applicable to the forms that are being added in Arabic, Hmong and Lao. 3. Barcode options remain same. 4. All the Requirements for the Arabic, Hmong and Lao forms will be the same as

the existing forms.

2 RECOMMENDATIONS

2.1 Add CF 386 (2/14) CalFresh Notice of Missed Interview form

2.1.1 Overview This section will cover CF 386 (2/14) CalFresh Notice of Missed Interview form requirements for adding in Arabic, Hmong and Lao languages.

2.1.2 Description of Change Add CF 386 (2/14) CalFresh Notice of Missed Interview form in Arabic, Hmong and Lao languages.


Add Forms in the following Languages: Arabic, Hmong and Lao 1. Create CF 386 (2/14) form XDP in Arabic, Hmong and Lao languages

Form Mockup/Example: See Supporting Document #1

2. Add the CF 386 (2/14) CalFresh Notice of Missed Interview form in

Arabic, Hmong and Lao to the Template Repository. 3. Update CT942 to generate CF 386 (2/14) from batch in Arabic, Hmong

and Lao languages.



1 Correspondence CF 386 Arabic, Hmong, Lao

CF386_AR.pdf CF386_HM.pdf CF386_LA.pdf

4 REQUIREMENTS

4.1 Migration Requirements

DDID # REQUIREMENT TEXT Contractor Assumptions How Requirement Met

The contractor shall update the LRS CF 386 CalFresh Notice of Missed Interview Form (02/14) version and make available in the additional threshold languages: 1) Arabic 2) Hmong 3) LAO

1. Estimate is just to implement 3 additional new languages. 2. Estimation doesn't include any changes to form version and trigger condition. 3. Estimate does NOT include any effort for modifying or creating new Functional Design Documents (FDDs) for forms being modified/migrated/created.

With SCR CA-211747, CF 386 (2/14) CalFresh Notice of Missed Interview form will be added to LRS/CalSAWS template repository and generate in batch in Arabic, Hmong and Lao languages.


Consortium staff will be modifying or creating FDDs.



Design Document

CA-211756 Update SAWS 2A SAR (04/15)


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Harish Katragadda

Reviewed By

DATE DOCUMENT


08/03/2020 1.0 Original Harish Katragadda



1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 Update and Add SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form ............................................................................................. 5

2.1.1 Overview ........................................................................................................ 5



4 Requirements .................................................................................................................... 6

4.1 Migration Requirements............................................................................................ 6


1 OVERVIEW The purpose of this change is to Update the SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form in existing languages and add SAWS 2A SAR (04/15) in threshold languages which are currently not in LRS/CalSAWS Template Repository.

1.1 Current Design SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form currently exist in LRS/CalSAWS in English, Spanish, Armenian, Cambodian, Chinese, Korean, Russian, Tagalog, Vietnamese languages

1.2 Requests Update SAWS 2A SAR (04/15) in the Existing languages and Add SAWS 2A SAR (04/15) form in Arabic, Farsi, Hmong and Lao.

1.3 Overview of Recommendations 1. Update Form Name on the footer for SAWS 2A SAR (04/15) Rights &

Responsibilities & other Important Information form for the existing languages. 2. Add SAWS 2A SAR (04/15) Rights & Responsibilities & other Important

Information in Arabic, Farsi, Hmong and Lao forms to LRS/CalSAWS Template Repository.

1.4 Assumptions 1. SAWS 2A SAR (04/15) Arabic, Farsi, Hmong and Lao forms will not have the

LRS/CalSAWS Standard Header. 2. Print options remain same for SAWS 2A SAR (04/15) current forms and the same

will be applicable to the forms that are being added in Arabic, Farsi, Hmong and Lao.

3. All the Requirements for the Arabic, Farsi, Hmong and Lao forms will be the same as the existing forms.


2 RECOMMENDATIONS

2.1 Update and Add SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form

2.1.1 Overview This section will cover the updates needed for SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information in existing languages and the requirements for adding Arabic, Farsi, Hmong and Lao forms.

2.1.2 Description of Change Update SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form in existing languages and add Arabic, Farsi, Hmong and Lao version of the form to template repository.

Update Forms in the following Language: English, Spanish, Armenian

Cambodian, Chinese, Korean, Russian, Tagalog, Vietnamese

1. Update the Form Name in the footer of the form

Updates Required: See Supporting Document #1

Add Forms in the following Languages: Arabic, Farsi, Hmong and Lao 1. Create SAWS 2A SAR (04/15) form XDP in Arabic, Farsi, Hmong and Lao

languages with 12 impressions Form Mockup/Example: See Supporting Document #2

2. Add the SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form in Arabic, Farsi, Hmong and Lao to the Template Repository.

3. Add the following barcode options to the SAWS 2A SAR (04/15) Rights

& Responsibilities & other Important Information for the four new forms

Tracking Barcode BRM Barcode Imaging Barcode

N N N

Additional Requirements: Post to YBN/C4Y: No




1 Correspondence SAWS 2A SAR Footer Form Name Updates

SAWS2ASAR_Update.docx

2 Correspondence SAWS 2A SAR Arabic, Farsi, Hmong, Lao

SAWS2ASAR_AR.pdf SAWS2ASAR_FA.pdf SAWS2ASAR_HM.pdf SAWS2ASAR_LA.pdf

4 REQUIREMENTS



The contractor shall update the LRS Version SAWS 2A SAR (04/15) version in the CalSAWS software with the following: 1) Add the following additional threshold languages Arabic, Farsi, Hmong and Lao.

1. Estimate is for updating the form in English and all available threshold languages in LRS. 2. Estimations include to add new additional Threshold languages. 3. Estimate does NOT include any effort for modifying or creating new Functional Design Documents (FDDs) for forms being modified/migrated/created. Consortium staff will be modifying or creating FDDs.

With SCR CA-211756, SAWS 2A SAR (04/15) Rights & Responsibilities & other Important Information form will be updated in Existing languages, and added to CalSAWS repository in Arabic, Farsi, Hmong and Lao



Design Document

SCR CA-213273 CIV-106258 – ACIN I-XX-20 - FFY 2021 CalFresh COLA; ACL 20-XX Update CalWORKs (CW) IRT Levels for 2020-2021


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Sridhar Mullapudi

Reviewed By


7/30/2020 1.0 Initial Draft Sridhar Mullapudi



1.1 Current Design ........................................................................................................... 5

1.2 Requests ..................................................................................................................... 5


1.4 Assumptions ............................................................................................................... 6


2.1 Eligibility Updates ....................................................................................................... 6

2.1.1 CalFresh Maximum Allotments .......................................................................... 6

2.1.2 CalFresh Minimum Allotments ........................................................................... 7

2.1.3 CalFresh Standard Deduction ........................................................................... 7

2.1.4 CalFresh Maximum Shelter Deduction ............................................................. 7

2.1.5 CalFresh Maximum Asset Limits ......................................................................... 8

2.1.6 CalFresh Utility Allowances ................................................................................ 8

2.1.7 CalFresh Homeless Household Shelter Deduction ........................................... 8

2.1.8 CalFresh Net Monthly Income Eligibility Standards .......................................... 9

2.1.9 CalFresh Gross Monthly Income Eligibility Standards ......................................10

2.1.10 CalWORKs Tier 1 IRT Update .............................................................................10

2.1.11 CalWORKs Tier 2 IRT Update .............................................................................11

2.1.12 Programs Impacted ..........................................................................................11

2.1.13 Performance Impacts .......................................................................................11

2.2 C4Yourself Updates ..................................................................................................11

2.2.1 C4Y CF Gross Monthly Income Eligibility Standards ........................................11

2.2.2 C4Y CF Maximum Shelter Deduction...............................................................12

2.2.3 C4Y CF Maximum Allotments ...........................................................................12

2.3 List of CalFresh Cases With Postponed Verifications ..............................................12

2.3.1 Overview ............................................................................................................12

2.3.2 Description of Change ......................................................................................12

2.4 Update C-IV CF COLA NOA logic ...........................................................................13

2.4.1 Overview ............................................................................................................13

2.4.2 Description of Change ......................................................................................13

3 Requirements ...................................................................................................................13




1 OVERVIEW This document identifies required changes to LRS and C-IV related to the CalFresh (CF) Cost of Living Adjustments (COLA) for Federal Fiscal Year (FFY) 2021 for the period of October 1, 2020 through September 30, 2021 as informed by the All County Information Notice I-XX-20, and United States Department of Agriculture, Food and Nutrition Service SNAP COLA Memo FY 2020.

1.1 Current Design 1. The maximum CF allotments and other program limits were last adjusted for FFY

2020 in C-IV under CIV-100442, and in LRS under CA-58614. C-IV and LRS use the FFY 2019-2020 CF amounts for the following values: a. CalFresh Standard Utility Allowance b. CalFresh Limited Utility Allowance c. CalFresh Telephone Utility Allowance d. CalFresh Maximum Allotment e. CalFresh Minimum Allotment f. CalFresh Standard Deduction g. CalFresh Maximum Shelter Deduction h. CalFresh Net Monthly Income Level i. CalFresh Gross Monthly Income Level j. CalFresh Aged Property Limit k. CalFresh Non-Aged Property Limit l. CalFresh Homeless Shelter Deduction m. 165% FPL n. 200% FPL

2. The CW Income Reporting Threshold (IRT) Tier 1 level is at the 2019/2020 amount introduced by SCR CA-58612/CIV-100446.

3. The CW Income Reporting Threshold (IRT) Tier 2 level is at the 2019/2020 amount introduced by SCR CA-206231/CIV-103092.

1.2 Requests 1. Effective October 1, 2020, benefits for all active CalFresh and TCF programs must

be calculated and issued based on the COLA for FFY 2021 as set forth in the following sections.

2. Update the CW Income Reporting Threshold (IRT) levels to the 2020/2021 amount.

1.3 Overview of Recommendations 1. Update LRS and C-IV code tables with the new CF COLA values for FFY 2021 and

end date records from the previous year as of September 30, 2020. 2. Update LRS and C-IV code tables with the new CW IRT value for 2020-2021 year

effective October 1st 2020 and end date record from the previous year as of September 30, 2020


3. Update C4Yourself tables with the new CF COLA values for FFY 2021 and end date records from the previous year as of September 30, 2020.

4. C-IV only: Update the NOA logic to generate the CF COLA NOA for 10/2020 COLA.

1.4 Assumptions 1. Batch EDBC will be run on CF (including TCF) programs, and any active Nutrition

Benefit (NB) programs on the same case as the active CF program to issue benefits for the new CF COLA values under separate SCR’s CIV- 103090 and CA-206229.

2. Tables in this document give values for Household Sizes up to 10 persons to align with the lookup column layout in CT351. The Household Size of “2” in this document applies to both the CT351 column for “2 Persons” and for “2 Adults.”

3. This SCR will update the existing CF COLA NOA fragment in the C-IV system (see Section 2.4). The LRS CF COLA NOA remains unchanged. Per existing LRS logic, other program changes unrelated to the COLA may generate a related NOA instead of the CF COLA NOA.

4. Counties are responsible for providing access to the information in the CF 11 (ENG/SP) CalFresh Mass Change Notice.

2 RECOMMENDATIONS Insert new values into the code tables as specified below using an effective date from 10/01/2020 to high date. The existing high-dated values will be end-dated effective September 30, 2020.

2.1 Eligibility Updates

2.1.1 CalFresh Maximum Allotments The following table lists the new CF Maximum Allotments for all households for FFY 2021. These values are stored in CT351, Code 45.

Household Size Maximum Aid Payment

1 $ 204

2 $ 374

3 $ 535

4 $ 680

5 $ 807

6 $ 969

7 $ 1,071



8 $ 1,224

9 $ 1,377

10 $1,530

Each additional person $ 153

2.1.2 CalFresh Minimum Allotments The CF Minimum Allotment will remain $16. This value is stored in CT 335, Code MA.

2.1.3 CalFresh Standard Deduction The following table lists the new CF Standard Deductions for FFY 2021. These values are stored in CT351, Code 48.

Household Size Standard Deductions

1 $ 167

2 $ 167

3 $ 167

4 $ 181

5 $ 212

6 $243

7 $ 243

8 $ 243

9 $ 243

10 $ 243

Each additional person $0*

* all households of six or more get a $243 deduction with no additional amount added as the household size increases.

2.1.4 CalFresh Maximum Shelter Deduction The CF Maximum Shelter Deduction for households without elderly or disabled members increased from $569 to $586. This value is stored in CT335, Code 50.


Note: The CF Maximum Shelter Deduction does not apply to elderly or disabled households; the full amount of any excess shelter will be deducted. However, this value will still appear in the EDBC Summary.

2.1.5 CalFresh Maximum Asset Limits CF Maximum Asset Limits are not changing with this COLA: • The limit for households with at least one member who is age 60 or older or is

disabled will remain at $3,500. This value is stored in CT 335, Code 85. • For all other households, the limit will remain at $2,250. This value is stored in CT

335, Code 86.

2.1.6 CalFresh Utility Allowances The following table lists the new Utility Allowances for CF for FFY 2021. These values are stored in CT335. The code for each item is identified in the table.

Utility Allowance Type Code Old Value New Value

Standard Utility Allowance (SUA) 49 $432 $ 438

Limited Utility Allowance (LUA) 34 $135 $ 139

Telephone Utility Allowance (TUA) 33 $18 No change

2.1.7 CalFresh Homeless Household Shelter Deduction The CF Homeless Household Shelter Deduction will increase in FFY 2021 from $152.06 to $156.74. This value is stored in CT335, Code 48.


2.1.8 CalFresh Net Monthly Income Eligibility Standards The following table lists the new CF Net Monthly Income Eligibility Standards (100% FPL) for FFY 2021. These values are stored in CT351, Code 46.


1 $1,064

2 $ 1,437

3 $ 1,810

4 $ 2,184

5 $ 2,557

6 $2,930

7 $ 3,304

8 $ 3,677

9 $ 4,051

10 $4,425

Each additional person $ 374


2.1.9 CalFresh Gross Monthly Income Eligibility Standards The following table lists the new CF gross Monthly Income Eligibility Standards for FFY 2021. These values are stored in CT351. The code for each item is in the table.

Household Size

IRT for SAR (130% FPL)

Code 47

Elderly/Disabled (165% FPL) Code 58

MCE/BBCE (200% FPL) Code 60

1 $ 1,383 $ 1,755 $2,128

2 $ 1,868 $2,371 $2,874

3 $ 2,353 $ 2,987 $3,620

4 $ 2,839 $ 3,603 $4,368

5 $ 3,324 $ 4,219 $5,114

6 $ 3,809 $ 4,835 $5,860

7 $ 4,295 $ 5,451 $6,608

8 $ 4,780 $ 6,067 $7,354

9 $ 5,266 $ 6,683 $8,102

10 $5,752 $7,299 $8,850

Each additional member $ 486 $ 616 $748

2.1.10 CalWORKs Tier 1 IRT Update Apply a CTCR in each system to update the 100% FPL for a household of 3 as used by the system for CalWORKs Tier 1 IRT (Code Table 335, code AK) effective 10/01/2020 to high date. The existing high-dated value will be end-dated 9/30/2020. In LRS: the new amount will be $1,810 (the system calculates 55% of this value as $996 per the ACL). In C-IV: the new amount will be $1,811 (the system calculates 55% of this value as $996 per the ACL due to rounding differences from LRS.


2.1.11 CalWORKs Tier 2 IRT Update The following table lists the new CW Tier2 IRT values. These values are stored in CT351. These values are effective 10/01/2020, the current high dated values will be end dated to 9/30/2020

Household Size

CW Tier2 IRT (130% FPL) Code 49

0 $ 1,383

1 $ 1,383

2 $ 1,868

3 $ 2,353

4 $ 2,839

5 $ 3,324

6 $ 3,809

7 $ 4,295

8 $ 4,780

9 $ 5,266

10 $5,752

Each additional member $ 486

2.1.12 Programs Impacted CW, CF

2.1.13 Performance Impacts None.

2.2 C4Yourself Updates

2.2.1 C4Y CF Gross Monthly Income Eligibility Standards Update the C4Yourself CF Gross Monthly Income Eligibility Standards for 130% FPL in CT351, Code 47 with the same values applied to C-IV in section 2.1.9.


2.2.2 C4Y CF Maximum Shelter Deduction Update the C4Yourself CF Maximum Shelter Deduction in CT335, Code 50 with the same value applied to C-IV in section 2.1.4.

2.2.3 C4Y CF Maximum Allotments Update the C4Yourself CF Maximum Allotments in CT351, Code 45 with the same values applied to C-IV in section 2.1.1.

2.3 List of CalFresh Cases With Postponed Verifications

2.3.1 Overview Generate list of cases that might be skipped in EDBC batch run due to Postponed Verifications data. This list will be provided to the counties in advanced of the CF COLA EDBC Run for review.

2.3.2 Description of Change Generate list of cases that may be skipped based on the following criteria:

a) ‘Postponed Verifications Authorized’ is set to ‘Yes’ b) ‘Postponed Verifications Due Date’ is prior to the CF COLA EDBC Batch

Run date (9/05/2020). c) ‘Postponed Verifications received’ is set to ‘No’. d) There are no pending verifications for active members on the CF

program where the ‘Postponed for Expedited Service’ is set to ‘Yes’. The lists will include the following Standard List Columns:

Case Name Case Number County Unit Unit Name Office Name Worker ID

This list will be posted at: LRS: CalACES System Web Portal > System Changes > SCR and SIR Lists > 2020 > SCR CA-213273. CIV: CalACES System Web Portal > System Changes > SCR and SIR Lists > 2020 > SCR CIV-106258


2.4 Update CF COLA NOA logic

2.4.1 Overview The existing English and Spanish fragments will be updated in C-IV for the CF COLA to be generated by this change.

2.4.2 Description of Change C-IV only: Update the existing COLA fragment logic for RSN_COLA_CHANGE to generate for the EDBC benefit month/year of 10/2020.

Existing Fragment (English): “Your change in CalFresh benefits are due to the annual CalFresh Cost of Living Adjustment that is effective <BenefitMonth>. This is due to Federal and State regulations.” Existing Fragment (Spanish): “Su cambio en los beneficios de CalFresh se debe al ajuste anual del costo de vida de CalFresh que es efectivo el <BenefitMonth>. Esto se debe a las regulaciones federales y estatales.”

In both systems: Update the regulation reference for this fragment to generate the following regulations:

MPP 63-502, MPP 63-504.39, ACL 12-25, ACL 12-25E

3 REQUIREMENTS



2.8.1.21 The LRS shall automate eligibility determination and benefit calculation for certain individual and case changes.

This SCR updates the CF COLA values for eligibility determination and benefit calculation FFY 2021.



Design Document

SCR 214032 – Mark Document Received Imaging Inbound Web Service


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Jennifer Kim

Reviewed By [individual(s) from build and test teams that reviewed document]


6/02/2020 1.0 Initial Draft Jennifer Kim



1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 Mark Document Received Inbound Webservice ................................................... 5

2.1.1 Overview ............................................................................................................. 5

2.1.2 Description of Change ....................................................................................... 5

2.1.3 Execution Frequency ......................................................................................... 8

2.1.4 Key Scheduling Dependencies ......................................................................... 8

2.1.5 Counties Impacted ............................................................................................ 8

2.1.6 Data Volume/Performance ............................................................................... 9

2.1.7 Interface Partner ................................................................................................ 9

2.1.8 Failure Procedure/Operational Instructions ..................................................... 9


4 Requirements ...................................................................................................................11


4.2 Migration Requirements ...........................................................................................11

5 Migration Impacts............................................................................................................13

6 Outreach ..........................................................................................................................14

7 Appendix ..........................................................................................................................15


1 OVERVIEW This SCR addresses the Mark Document Received Inbound Web Service to complete the following actions in CalSAWS: update the scan indicator to ‘YES’ and Scan Date for all system-generated, barcoded documents and subsequently, attempt to mark time-sensitive documents as ‘RE’ - Received and additionally, if a SAR7 form, ‘RR’ - Reviewed- Ready to Run EDBC. The CalSAWS Imaging System leverages this call when a barcoded document has been fully indexed, categorized and in the ‘Pre-Archive Processing Queue’. The Mark Document Received Web Service will be invoked for all system-generated barcoded documents (both time and non-time-sensitive forms), excluding NO CASE Identified and CASE Specified Barcoded Coversheet Separator Forms.

1.1 Current Design There is no established web service between the CalSAWS Imaging System and CalSAWS to update the scan indicator to ‘YES’ and Scan Date for all system-generated, barcoded documents and to subsequently, attempt to mark time-sensitive documents as ‘RE’ - Received and additionally, if a SAR7 form, ‘RR’ - Reviewed- Ready to Run EDBC in CalSAWS.

1.2 Requests 1. Create a new Mark Document Received Inbound Web Service for the CalSAWS

Imaging System to update the scan indicator to ‘YES’ and Scan Date for all system-generated, barcoded documents and subsequently, attempt to mark time-sensitive documents as ‘RE’ - Received and additionally, if a SAR7 form, ‘RR’ - Reviewed- Ready to Run EDBC in CalSAWS. This call is invoked when the document has been fully indexed, categorized and in the ‘Pre-Archive Processing Queue’ in the CalSAWS Imaging System.

1.3 Overview of Recommendations 1. Create a new Mark Document Received Inbound Web Service to update the

scan indicator to ‘YES’ and Scan Date for all system-generated, barcoded documents and subsequently, attempt to mark time-sensitive documents as ‘RE’ - Received and additionally, if a SAR7 form, ‘RR’ - Reviewed- Ready to Run EDBC in CalSAWS.

1.4 Assumptions 1. Imaging has updated documentations, such as their design documents, to

invoke the Mark Document Received Web Service for all system-generated barcoded documents (both time and non-time-sensitive forms).

2. Per SCR CA-48386, CalSAWS had implemented some logic to mark Form PA2418B as ‘Received’ by matching it to its due month and program because it lacked a barcode. Additionally, if multiple matches of the form were found,


CalSAWS marked all of them as ‘Received’. However, since Form PA2418B is now barcoded, we do not need to implement such logic around this form.

3. This design will not be implementing retry mechanisms or addressing system outage scenarios for the inbound web service.

RECOMMENDATIONS

1.5 Mark Document Received Inbound Webservice

1.5.1 Overview All system-generated, barcoded documents that have been fully indexed and categorized will be routed to the ‘Pre-Archive Processing Queue’ in the Imaging System. The Mark Document Received Web Service will be invoked from the Pre-Archive Processing Queue of the Imaging System. The Mark Document Received Inbound Web Service will be invoked for all system-generated, barcoded documents: 1. for a barcode value associated to non-time-sensitive forms OR 2. for a barcode value associated to time-sensitive, non-SAR7 forms OR 3. for a barcode value associated to SAR7 forms.

*The Mark Document Received Web Service will be invoked for all system-generated barcoded documents (both time and non-time-sensitive forms), excluding NO CASE Identified and CASE Specified Barcoded Coversheet Separator Forms.

1.5.2 Description of Change 1. Create a DBCR to update the GENERATE_DOC table with the following

change: a. Add a new “Scan Date” Column – This new column represents the

date when the Scan Indicator is set to ‘YES’. 2. Create a ‘Mark Document Received’ Web Service, in which the Imaging

System sets the scan indicator to ‘YES’ and updates the Scan Date for all system-generated, barcoded documents and subsequently, attempts to mark time-sensitive documents as ‘RE’ - Received and additionally, if a SAR7 form, ‘RR’ - Reviewed- Ready to Run EDBC.

a. Using the provided barcode value in the request parameter, retrieve the corresponding GENERATE_DOC record with the matching 2D barcode. If the scan indicator is not currently set to ‘YES’, update the SCAN_IND to ‘YES’ and SCAN_DATE to the System Date.

b. Look for a CUST_RPT record associated with the GENERATE_DOC record identified above. If a record does not exist, the web service


action is complete. If one exists, find the CUST_RPT _PGM_TYPE record(s) associated with the CUST_RPT record. Retrieve the latest status record for each CUST_RPT_PGM_TYPE record. If the latest status is not in the following list, insert a new status record with a value of ‘RE’- Received for each record in the CUST_RPT_PGM_TYPE table:

• ‘RE’- Received, • ‘NA’- Not Applicable, • ‘RD’- Reviewed, • ‘CC’-Completed, • ‘CE’- Complete- EDBC Accepted and • ‘RR’- Reviewed- Ready to Run EDBC

Do not respond with an error code if status record is already marked as one of the statuses in the bullet points above. Set the Status Date Column to match the Received Date Value received in the request parameter. If the Received Date Value is a future date, default this date to the System Date.

c. For each CUST_RPT_PGM_TYPE record updated in step b. above, if the document is a SAR7, refer to the ‘No Change SAR7’ value from the request parameter. If the value is ‘true’, insert a new status record with a value of ‘RR’- Reviewed, Ready to Run EDBC. Set the Status Date Column to the System Date. If the value is ‘false’, skip this step.

3. Perform Integration Testing with the interface partner.

Table 1 – Mark Document Received Request Parameters

Mark Document Received – REQUEST FIELD NAME TYPE COMMENTS REQUIRED

barcodeNumber String The barcode number on system-generated barcoded documents and represents the 2D barcode UID.

Y

noChangeSAR7 Boolean Indicates whether a SAR7 document should be automatically marked as ‘RR’-Reviewed- Ready to Run EDBC.

N

receivedDate Date (“MM/DD/YYYY”)

User-input date that is set at the point of scanning. It is normally set to

Y


the date the worker receives the document. If the user inputs a future date, please default to the System Date.

Table 4 – Mark Document Received - FAILED WEB SERVICE OPERATIONS

HTTP Response

Code Field Name Value COMMENTS

Error codes are intended for backend processes and will not be displayed for end-users.

400 responseCode 400 Return HTTP response code 400 if there is a tech failure because the required data attribute was not supplied.

errorMessage “${Field Name} Must Be Supplied.”

404 responseCode 404 Return HTTP response code 404 if the required data attribute cannot be found in the CalSAWS System.

errorMessage “${Field Name} Not Found.”


422 responseCode 422 Return HTTP response code 422 if there is a problem with the request for the required data attribute and the Integration Server is unable to process it.

errorMessage “${Field Name} Is an Unprocessable Entity.”

500 responseCode 500 Return HTTP response code 500 if there is an unknown internal server error that occurred while trying to process the request.

errorMessage “Internal Server Error.”

1.5.3 Execution Frequency The Mark Document Received Web Service is invoked real-time in the Imaging System when documents have been fully indexed, categorized and in the ‘Pre-Archive Processing Queue’.

1.5.4 Key Scheduling Dependencies N/A

1.5.5 Counties Impacted Counties utilizing the CalSAWS Imaging System will be impacted. C-IV, LRS and CalWIN Counties will be impacted in phases in that order.


1.5.6 Data Volume/Performance N/A

1.5.7 Interface Partner CalSAWS Imaging System

1.5.8 Failure Procedure/Operational Instructions Operations staff will evaluate transmission errors and failures and determine the appropriate resolution (i.e., manually retrieving the file from the directory and contacting the external partner if there is an account or password issue, etc.)


2 SUPPORTING DOCUMENTS [This section should include any supporting documents for the design as imbedded documents. Some examples of supporting documents include the Security Matrix, Form Design Documents, NOA Design Documents, and ETL Source-to-Target Mappings.]




3 REQUIREMENTS [Document what requirements are being addressed with this design and how they are being met]




DDID # REQUIREMENT TEXT Contractor Assumptions

How Requirement Met

2198 The CONTRACTOR shall configure the core capture and indexing scan modes (Single Case, Virtual Print, and Multi-case) to perform the following functions when a system generated barcode is recognized by the imaging solution: 1) Perform a CalSAWS Software lookup of Form Name, Form Number, Case Name, Case Number, and Document Type 2) Check the barcode against the case information entered during the scan mode 2a) Not applicable to multi-case scan mode 3) If the document is time sensitive (tracked), mark the document as received in the CalSAWS Software 3a) If the barcode is not recognized, time sensitive (tracked) documents are reviewed by designated staff to confirm the barcode

None 1. This design creates a Mark Document Received Web Service, in which the Imaging System will request to set the scan indicator to ‘YES’ for all system-generated barcoded documents and subsequently, attempt to mark time-sensitive documents as ‘RE’ - Received and ‘RR’ - Reviewed- Ready to Run EDBC in CalSAWS. The web service will send the document’s ‘Barcode Number’ and ‘Received Date’ and if applicable, the ‘No Change SAR7’ status to validate the request.



How Requirement Met


4 MIGRATION IMPACTS [Document any migration impacts such as data model or potential business process changes]

SCR Number

Functional Area

Description Impact Priority Address Prior to Migration?


5 OUTREACH [Include any specific outreach that needs to occur with implementation i.e. a CIT, a special webcast or onsite demonstration, any lists, etc…]


6 APPENDIX [Include any supplementary items that my not fit in the Description section. Examples could include flow charts, lengthy code tables, etc.…]


Design Document

CA-214034

Generate Task Imaging Inbound Web Service

2

CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Jennifer Kim, Gabe Trejo

Reviewed By

DATE DOCUMENT


08/12/2020 V1.0 Initial Draft Jennier Kim / Gabe Trejo

3


1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 Generate Task Inbound Webservice ....................................................................... 5

2.1.1 Overview ........................................................................................................ 5


2.1.3 Execution Frequency ..................................................................................... 9

2.1.4 Key Scheduling Dependencies .................................................................... 9

2.1.5 Counties Impacted ....................................................................................... 9

2.1.6 Data Volume/Performance .......................................................................... 9

2.1.7 Interface Partner ...........................................................................................10

2.1.8 Failure Procedure/Operational Instructions ................................................10


4 Requirements ...................................................................................................................12


4.2 Migration Requirements...........................................................................................12

5 Migration Impacts ...........................................................................................................13

6 Outreach ..........................................................................................................................13

7 Appendix..........................................................................................................................13

4

1 OVERVIEW This SCR implements the Generate Task Inbound Web Service to be invoked by the CalSAWS Imaging System. The CalSAWS Imaging System is the central point for indexing documents received through various channels, including kiosks, web portals, desktop scanners, etc. Once documents are saved and indexed in the CalSAWS Imaging System, a web service call to CalSAWS is triggered to create a task with relevant document details.

1.1 Current Design There is no established web service between the CalSAWS Imaging System and CalSAWS to create a task when a document is scanned and indexed.

1.2 Requests Add the ability for the CalSAWS Imaging System to create a task in CalSAWS for documents that are scanned and indexed.

1.3 Overview of Recommendations 1. Create a new inbound web service for the CalSAWS Imaging System to create

a task in CalSAWS, based on information supplied by the CalSAWS Imaging System.

1.4 Assumptions 1. Additional pages in CalSAWS to provide configuration of task creation values

will be delivered under the Task Management FDS Requirements (DDID 2247 and DDID 2254). These SCRs will also complete the remaining portion of this webservice to trigger task creation.

5

2 RECOMMENDATIONS

2.1 Generate Task Inbound Webservice

2.1.1 Overview All system-generated barcoded documents that have been fully indexed and categorized will be routed to the ‘Pre-Archive Processing Queue’ in the Imaging System. The Generate Task Imaging Inbound Web Service will be invoked after documents have been scanned and indexed in the Imaging System. The Imaging System will trigger this web service for every document that is being scanned.

2.1.2 Description of Change 1. Create a ‘Generate Task’ Imaging Inbound Web Service in which the

following data elements are received from the CalSAWS Imaging System:

Table 1 – Generate Document Task Request Parameters

Generate Document Task – REQUEST FIELD NAME TYPE COMMENTS REQUIRED

DocumentType String (40 char. limit)

1. For CalSAWS system-generated documents, Document Type is listed in the CalSAWS Imaging Type Code Category Table, which is associated to the IMG_TYPE column in the DOC_TEMPL table. 2. For Imaging-exclusive documents, Document Type is listed in the CalSAWS Imaging Type Code Category Table, which is associated to the IMG_TYPE column in the Static Table for the CalSAWS Imaging System Document Types and Short Names.

Y

formName String (40

1. For CalSAWS system-generated documents, Form Name will be found in the

Y

6

char. Limit)

‘Imaging Form Name’ column of the DOC_TEMPL table. 2. For Imaging-exclusive documents, Form Name will be found in the ‘Imaging Form Name’ column of the Static Table for the CalSAWS Imaging System Document Types and Short Names.

caseUID Long Case Unique ID Y

countyCode String (2 char.)

2-digit County Code (Counties 01-58).

Y

programOverride Object This field overrides the program a task is routed to. The expected data is an object consisting of:

• Decoded Program Name,

• Program Status (as of the system date),

• Worker Number assigned to the program (as of the system date) and

• Program ID A NULL value in this field is interpreted as no program override will be applied to task creation. This field is disregarded if either the taskOverride or noChangeSar7 fields are set to ‘true’

N

taskOverride Boolean This field determines if the task for this document should be suppressed.

• ‘true’ – The task should be suppressed

N

7

• ‘false’ or NULL – Task creation rules should be evaluated and a task is created if appropriate.

noChangeSar7 Boolean This field determines if the

document represents a No Change SAR7, and should therfore have the task suppressed.

• ‘true’ – No Change SAR7, task should be suppressed

• ‘false’ or NULL – Task creation rules should be evaluated and a task is created if appropriate.

This field is disregarded if the Form Name does not indicate a SAR 7 form.

N

imageUID String Image Unique ID in the Imaging System. Example: 321Z485_0016BXM1S0000BE

Y

scanningSource String User name of Staff who scanned in the document to the Imaging System.

N

captureDate String ($date)

This field represents the document’s scan date, as represented in the Imaging System.

Y

receivedDate String ($date)

This field represents the date the document was received, as represented in the Imaging System.

N

8

Table 2 – Generate Task - FAILED WEB SERVICE OPERATIONS

HTTP Response

Code Field Name Value COMMENTS

Error codes are intended for backend processes and will not be displayed for end-users.

400 responseCode 400 Return HTTP response code 400 if there is a tech failure because the required data attribute(s) was not supplied.

errorMessage “${Field Name(s)} Must Be Supplied.”

404 responseCode 404 Return HTTP response code 404 if the required data attribute(s) cannot be found in the CalSAWS System.

errorMessage “Unable to complete task process for this request.”

422 responseCode 422 Return HTTP response code 422 if there is a problem with the request for the required data attribute(s) and CalSAWS is

9

errorMessage “${Field Name(s)} Is an Unprocessable Entity.”

unable to process it.

500 responseCode 500 Return HTTP response code 500 if there is an unknown internal server error that occurred while trying to process the request.

errorMessage “Internal Server Error.”

NOTE: This webservice will not invoke the task creation method under this SCR, therefore no task will be created under this release. The webservice will be updated under a future release SCR (CA-214917), which will solidify the details of the task creation method for document tasks.

2.1.3 Execution Frequency This webservice is invoked real-time in the Imaging System after documents have been scanned and indexed through the OCR process or manually by the Imaging User.

2.1.4 Key Scheduling Dependencies N/A

2.1.5 Counties Impacted Counties utilizing the CalSAWS Imaging System will be impacted. C-IV, LRS and CalWIN counties will be impacted in phases in that order.

2.1.6 Data Volume/Performance N/A

10

2.1.7 Interface Partner CalSAWS Imaging System

2.1.8 Failure Procedure/Operational Instructions Operations staff will evaluate transmission errors and failures and determine the appropriate resolution (i.e., manually retrieving the file from the directory and contacting the external partner if there is an account or password issue, etc.)




4 REQUIREMENTS

4.1 Project Requirements Not Applicable.



How Requirement Met

2504 The CONTRACTOR shall configure the imaging solution to collect and transfer the following data to the CalSAWS Software for task generation: 1) Document Type 2) Form Name 3) Case Info 4) Person Info 5) Program Override Flag 6) No Task Override Flag 7) No Change SAR 7 Flag 8) Image ID 9) Scanning User/Worker/Source 10) Applicable Date 11) Received Date

None 3. This design creates a Generate Task Web Service, in which the CalSAWS Imaging System will send Form, Case and Task Information to CalSAWS.

5 MIGRATION IMPACTS Not Applicable.

6 OUTREACH Not Applicable.

7 APPENDIX Not Applicable.



Design Document

SCR 214037 – Update Distributed Documents Page


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Sarah Steimle





1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 Distributed Documents page ................................................................................... 6

2.1.1 Overview ............................................................................................................. 6

2.1.2 Distributed Documents Mockup ....................................................................... 6

2.1.3 Description of Changes ..................................................................................... 7

2.1.4 Page Location .................................................................................................... 8

2.1.5 Security Updates ................................................................................................. 8

2.1.6 Page Mapping ................................................................................................... 9

2.1.7 Page Usage/Data Volume Impacts ................................................................. 9

2.2 [Automated Regression Test] ...................................... Error! Bookmark not defined. 2.2.1 Overview ............................................................... Error! Bookmark not defined. 2.2.2 Description of Change ......................................... Error! Bookmark not defined.


4 Requirements ...................................................................................................................11

4.1 Project Requirements .................................................. Error! Bookmark not defined. 4.2 Migration Requirements ...........................................................................................11

5 Migration Impacts............................................................... Error! Bookmark not defined. 6 Outreach ............................................................................. Error! Bookmark not defined. 7 Appendix ............................................................................. Error! Bookmark not defined.


1 OVERVIEW This SCR will be implementing an Images button to give the user the functionality to find documents associated to the documents listed in the Distributed Documents page based on specified search criteria. This SCR will also be updating the expandable plus button on the page to have more contrast and this SCR will be updating the “Details” link to be a “Details” button.

1.1 Current Design In LRS today there is no functionality in the system that is able to view documents associated to listed documents in the Distributed Documents page. Additionally, The Distributed Documents page has an expandable plus button that does not have enough contrast and the Distributed Documents page has a “Details” link that, when clicked, shows the worker the details of the associated form.

1.2 Requests The request is to add functionality for the user to be able to view documents that are associated to another document on the Distributed Documents page in the LRS/CalSAWS system based on specified search criteria. The second request is to update the expandable plus button to have more contrast. The third request is to make the “Details” link a button.

1.3 Overview of Recommendations 1. Add an Images button to the Distributed Documents page to be able to view

the associated documents to the documents that are listed on the page. 2. Update the expandable plus button on the Distributed Documents page to have

more contrast. 3. Update the “Details” link on the Distributed Documents page to be a button.

1.4 Assumptions 1. The Imaging system has the functionality to search for the specified criteria. 2. Fields not mentioned in the Description of Changes sections, will not be

updated. 3. SCR CA-214032 will provide the necessary webservice to mark the Scan_IND as

“Y”. 3.4. Routing of barcoded documents when a barcode is not read is explained

in SCR CA-214058 (Environment Workflow Configuration). 4.5. Functionality will not be available to counties that have not been enabled

on the new imaging solution (Hyland).

Formatted: Highlight



2 RECOMMENDATIONS

2.1 Distributed Documents page

2.1.1 Overview The Distributed Documents page lists the documents that have been generated for the case that the worker is on. The page needs to be updated to provide functionality for the worker to be able to view documents associated to the documents listed on the page. This page also needs to have the expandable plus sign updated to have more contrast between the colors to be ADA compliant and the “Details” link needs to be updated to be a button.

2.1.2 Distributed Documents Mockup

Figure 2.1.1 – Distributed Documents Page

Formatted: Highlight


Figure 2.1.2 - Hyland Pop Up from Images Button Mockup

2.1.3 Description of Changes 1. Images Button – The Images button will display for all generated

documents that have a scan indicator that is set to “Y”. This data will be in the generate doc table. When the Images button is clicked, the Images button will display a list of documents in a pop up from Hyland(Imaging Solution) that are associated to the document that is listed in the Document Name column of the Distributed Documents page. The Document Type search criteria for all non-time sensitive or non-tracked documents is:

a. Address/Residency b. Appointment Letter c. Customer/Worker Contact d. Child Support e. Veterans f. Interoffice Correspondence g. Notification/NOA h. Sworn Statements i. Verification Requests j. Personal Expenses k. Customer Verification Forms k.l. Overpayment/Overissuance (OP/OI) Formatted: Highlight


The date range for non-time sensitive or non-tracked documents is 90 days from the LRS/CalSAWS system date. The search criteria for time sensitive or tracked documents is specified in Supporting Document #1: Specific Search Criteria. The document specifies the Form Number, Form Name, Document Type(s), and Scan Date Range. The Document Type(s) column defines what Document Type(s) will be searched for when the Images button is clicked for the associated Form. The Date Range column defines the date range in which the system will search for the Document Type(s). In order to view Images from the Images buttons on this page the user must have the security right “ImagingViewCase”. 2. Details Button – Currently the Distributed Documents page has a

“Details” link. This link will be updated to a button. 3. Plus Button – Currently the Distributed Documents page has a plus

button. This button will be updated to the displayed colors of red and yellow.

Note: This feature and corresponding security rights will only be available when the county is enabled on the CalSAWS Imaging Solution (Hyland).

2.1.4 Page Location Global: Client Correspondence Local: Distributed Documents Task: NA

2.1.5 Security Updates Security Rights

Security Right Right Description Right to Group Mapping

Imaging View Case

Allows view access to the <County> Case drawer documents.

Imaging View Case

Security Groups


Security Group

Group Description Group to Role Mapping

Imaging View Case

Allows view access to the <County> Case drawer documents.

Child Care Supervisor, Clerical Supervisor, Eligibility Supervisor, Employment Services Supervisor, Fiscal Supervisor, Hearings supervisor, Marketing Supervisor, Quality Assurance Supervisor, Quality Control Supervisor, Regional Call Center Supervisor, RDB Supervisor, Special Investigations Supervisor, Imaging Staff

2.1.6 Page Mapping Update page mappings on the Distributed Documents page.

2.1.7 Page Usage/Data Volume Impacts There is no performance concerns.





1 Online Document of specific search criteria for each tracked or time sensitive document.

Specific Search CriteriaSpecific Search Criteria

Specific Search Criteria.xlsx

2 Security This is the security matrix. Security MatrixSecurity Matrix

Security Matrix.xls

Formatted: Default Paragraph Font


Field Code Changed



Field Code Changed


4 REQUIREMENTS


DDID #

REQUIREMENT TEXT Contractor Assumptions

How Requirement Met

DDID 2507 Updated Requirement Text:

The CONTRACTOR shall configure the Distributed Documents Search page in the CalSAWS Software to include additional links. When the link is clicked, the system generated document (captured) will return from the imaging solution with a list of image(s)/document(s) that meet the specific search criteria for that system generated document (if applicable).The CONTRACTOR shall configure the link to have unique search criteria for each of the time sensitive/tracked system generated documents. All other system generated documents will default to the same generic search criteria.

DDID 2507 Original Requirement Text:

The CONTRACTOR shall configure the Distributed Documents Search page in the CalSAWS Software to create a "+" sign next to system generated document(s). The "+" expands to provide a link to the document when it is scanned into the imaging solution. When the link is clicked, the system generated document (captured) will return from the imaging solution with a list of image(s)/document(s) that meet the specific search criteria for that system generated document (if applicable).The CONTRACTOR shall configure the link to have unique search criteria for each of the time sensitive/tracked system generated documents. All other system generated documents will default to the same generic search criteria. The search criteria will be determined during detailed design.

Please refer to Exhibit Z, schedule 1 for contractor assumptions.

Requirement is met by adding an Images button to the Distributed Documents page where the user can click on the button and see the associated images based on the search criteria for the associated documents.



Design Document

SCR CA-214073 – Update CalSAWS interfaces to accommodate larger database sequences

Phase-2.


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Shankar Padmanabhuni



7/28/2020 1.0 Initial Version Shankar Padmanabhuni

07/31/2020 1.0 Updated Interface section Naveen Kumar Bhumandla



1.1 Current Design ........................................................................................................... 4


1.3 Assumptions ............................................................................................................... 4


2.1 Interface : California Child Support Automation System (CCSAS) ........................ 5

2.1.1 Overview ............................................................................................................. 5

2.1.2 Current Design .................................................................................................... 5


2.1.4 Execution Frequency ......................................................................................... 5

2.1.5 Key Scheduling Dependencies ......................................................................... 5

2.1.6 Counties Impacted ............................................................................................ 5

2.1.7 Interface Partner ................................................................................................ 5


4 Requirements .................................................................................................................... 7

4.1 Project Requirements ................................................................................................ 7

4.2 Migration Requirements ............................................................................................ 7

5 Migration Impacts............................................................................................................. 8

6 Outreach ........................................................................................................................... 9

7 Appendix ..........................................................................................................................10


1 OVERVIEW Sequences for ID columns (primary keys on LRS tables) was changed to higher numbers in SCR -202610. This SCR will change interfaces which could not be changed in previous SCR.

1.1 Current Design There are some additional java code changes needed to accommodate larger sequences.

1.2 Overview of Recommendations The recommendations for the SCR :-

1. Change the java based application and partner interface code to accommodate for increased sequence values. Code changes fall into following categories:-

a. Id needs to be treated as type long instead of Integer( max 2,147,483,647).

b. Partner interface file should accommodate fixed width of at least 12 characters wide for Id.

1.3 Assumptions 1. LRS sequences change is completed in SCR 202610 2. Actual id shift in CIV will be done during CIV to LRS cutover. 3. Partner Testing of C-IV interfaces executed as part of SCR - CA-215584 - DDID

1979: C-IV County Interface Exchange Testing Support SCR.


2 RECOMMENDATIONS This SCR will update the code to use architecture Java Id class or long instead of int or Integer where the table Ids are read from database.

2.1 Interface : California Child Support Automation System (CCSAS)

2.1.1 Overview CCSAS Interface shares IVA number identifier with CCSAS to uniquely identify the cases between CalSAWS and CCSAS. Prior to generate a new IVA number, CalSAWS checks the legacy IVA number. If it’s already existing, system uses the legacy IVA number. Otherwise, it generates a new IVA number.

2.1.2 Current Design Current implementation for identifying legacy IVA number does not have county code check. So, this logic works only for LA county.

2.1.3 Description of Change Modify the CCSAS logic to identify the legacy IVA number to include the county code. With this implementation, system will be able to send/process legacy IVA number to/from CCSAS partner for all counties.

2.1.4 Execution Frequency Daily

2.1.5 Key Scheduling Dependencies No changes.

2.1.6 Counties Impacted LA county.

2.1.7 Interface Partner California Child Support Automation System (CCSAS)











How Requirement Met



SCR Number

Functional Area



6 OUTREACH [Include any specific outreach that needs to occur with implementation i.e. a CIT, a special webcast or onsite demonstration, any lists, etc…]


7 APPENDIX



Design Document

CA-215687

DDID 2686 FDS: GA GR Phase 1 - Case Summary and Application Page Changes


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Taylor Fitzhugh



06/01/2020 0.1 Initial Draft



1.1 Current Design ........................................................................................................... 6

1.2 Requests ..................................................................................................................... 6


1.4 Assumptions ............................................................................................................... 6


2.1 Add a system property to disable GA/GR functionality ........................................ 7

2.1.1 Overview ........................................................................................................ 7


2.2 Add the new General Assistance/General Relief program .................................. 7


2.3 Case Summary .......................................................................................................... 8

2.3.1 Overview ........................................................................................................ 8

2.3.2 Case Summary Mockup ................................................................................ 8


2.3.4 Page Location ..............................................................................................11

2.3.5 Security Updates ...........................................................................................11

2.3.6 Page Mapping ..............................................................................................11

2.3.7 Page Usage/Data Volume Impacts ...........................................................11

2.4 Program Detail..........................................................................................................11

2.4.1 Overview .......................................................................................................11

2.4.2 Program Detail Mockup ...............................................................................11


2.4.4 Page Location ..............................................................................................12


2.4.6 Page Mapping ..............................................................................................12


2.5 New/Reapplication Detail .......................................................................................12

2.5.1 Overview .......................................................................................................12

2.5.2 New/Reapplication Detail Mockup ............................................................13


2.5.4 Page Location ..............................................................................................13



2.5.6 Page Mapping ..............................................................................................13


2.6 General Assistance/General Relief Detail ..............................................................14

2.6.1 Overview .......................................................................................................14

2.6.2 General Assistance/General Relief Mockup ..............................................14


2.6.4 Page Location ..............................................................................................21


2.6.6 Page Mapping ..............................................................................................22


2.7 Administrative Role Detail ........................................................................................22

2.7.1 Overview .......................................................................................................22

2.7.2 Administrative Detail Mockup .....................................................................22


2.7.4 Page Location ..............................................................................................23


2.7.6 Page Mapping ..............................................................................................23


2.8 Rescind Detail ...........................................................................................................23

2.8.1 Overview .......................................................................................................23

2.8.2 Rescind Detail Mockup ................................................................................24


2.8.4 Page Location ..............................................................................................24


2.8.6 Page Mapping ..............................................................................................25


2.9 General Assistance/General Relief Person Detail .................................................25

2.9.1 Overview .......................................................................................................25

2.9.2 General Assistance/General Relief Person Detail Mockup .......................25


2.9.4 Page Location ..............................................................................................27


2.9.6 Page Mapping ..............................................................................................27



2.10 Position Detail ...........................................................................................................27

2.10.1 Overview .......................................................................................................27

2.10.2 Position Detail Mockup .................................................................................28


2.10.4 Page Location ..............................................................................................28


2.10.6 Page Mapping ..............................................................................................28


2.11 Application Registration Summary .........................................................................29

2.11.1 Overview .......................................................................................................29

2.11.2 Application Registration Summary Mockup ...............................................30


2.11.4 Page Location ..............................................................................................31


2.11.6 Page Mapping ..............................................................................................31



4 Requirements ...................................................................................................................32

4.1 Migration Requirements...........................................................................................32

5 Appendix..........................................................................................................................37


1 OVERVIEW This SCR will add functionality for the display of the new automated General Assistance/General Relief program.

1.1 Current Design The CalSAWS system is designed to automate the rules for Los Angeles County’s implementation of the General Assistance/General Relief program (GA/GR) as well as the automation and monitoring of their GROW program. The CalWIN system currently uses a different set of rules for each county and currently does not support the employment services programs within its system.

1.2 Requests Create a separate General Assistance/General Relief program to support the automation of eligibility determinations. This program will be available to the 18 counties using the CalWIN system at the time of release. The counties supported by the C-IV system will be able to opt into using the new program at a later time.

1.3 Overview of Recommendations 1. Add the ability to create and track a General Assistance/General Relief

program application. 2. Update the program dropdowns and displays to filter the correct General

Assistance/General Relief program based on the program supported by the county of the logged in user.

1.4 Assumptions 1. EDBC Rules, Batch processes, and reports for the new program will be added

and modified in future SCRs. 2. Manual EDBC will be unavailable for the new program and will be added in a

future SCR. 3. Data collection and employment services pages related to the General

Assistance/General Relief program will be modified in a set of future SCRs. 4. Los Angeles County will continue to use the existing ‘GA’ program code for the

General Assistance/General Relief program and will not use the new program code ‘GR’ that is being added for the automated General Assistance/General Relief solution applicable to the CalWIN counties.

5. Standard event creation logic will be applied to the new General Assistance/ General Relief program.


2 RECOMMENDATIONS

2.1 Add a system property to disable GA/GR functionality

2.1.1 Overview The GA/GR functionality will be implemented in waves and will not be required until other counties outside of LA have been migrated. The functionality will be disabled to prevent impacts to the LA GR workflow until the migration of the CalWIN counties.

2.1.2 Description of Changes Add a new system property that will allow all General Assistance/ General Relief functionality related to the new ‘GR’ program code to be activated and deactivated. This will be deactivated by default. The functionality shall be activated in a future effort at the time of CalWIN go live.

2.2 Add the new General Assistance/General Relief program

2.2.1 Description of Change Add the new General Assistance/General Relief program. Reference Appendix item A for a list of reference table values. These values are the default values and are subject to change based on implementation needs. This program will only be available for the following counties, by default:

1. Alameda 2. Contra Costa 3. Fresno 4. Orange 5. Placer 6. Sacramento 7. San Diego 8. San Francisco 9. San Luis Obispo 10. San Mateo 11. Santa Barbara 12. Santa Clara 13. Santa Cruz 14. Solano 15. Sonoma 16. Tulare 17. Ventura 18. Yolo


2.3 Case Summary

2.3.1 Overview The Case Summary page is the landing page when accessing a case. Each program and person that is present on the case will be displayed with their status based on the view date. This page will be modified to allow the user to view and access the new General Assistance/General Relief program.

2.3.2 Case Summary Mockup

Figure 2.3.2.1 – General Assistance/ General Relief (Month prior to BDA)

Figure 2.3.2.2 – General Assistance/ General Relief (Active/Denied/Ineligible)


Figure 2.3.2.3 – General Assistance/ General Relief (Pending)

Figure 2.3.2.4 – General Assistance/ General Relief (Discontinued)

2.3.3 Description of Changes 1. When the view date is on or after the application date of the program,

but prior to the BDA, the block will display the field “Program Begins On”. This field will display the BDA.

2. Add a section for the General Assistance/General Relief program. These blocks will display only for a date on or after the program’s application date. When the view date is on or after the program’s Beginning Date of Aid (BDA), the blocks will display with the following fields:

a. Worker: The name of the Staff assigned to the position that is assigned to the program.


b. Worker ID: The Identifier for the position. This field will be a hyperlink to the Worker Detail page for the selected position. When no staff is assigned to the position, this field will be blank.

c. Program Status: The status of the program on the given View Date.

d. Discontinued Date: The date the program was Discontinued. This field will only display when the status of the program is discontinued.

e. Aid Code: The aid code associated with the program. f. FBU: The Family Budget Unit for the program. g. Primary Applicant/Recipient: The primary applicant of the

program on the given view date. h. Language: The spoken Language of the primary Applicant. i. Phone Number: The main phone number for the primary

Applicant. j. Email: The email of the primary applicant. k. Payee: The Payee of the program on the given view date. l. Application Date: The date of the application associated to the

status as of the given view date. m. Name: This field will list the names of all participants on the

program. Each person will have their name displayed in a single row. Each name will be a hyperlink to the Program Person History page for the program person selected, if the user has the ‘PersonHistoryView’ right associated to their profile.

n. RE Due Month: The month that the user’s redetermination is due. This field will only display when there is a RE date that covers the given month.

o. Re-Evaluate: This button will clear the root questions and allow the user to recreate them to receive an adjusted input flow based on their new information.

p. Reporting Type: The type of periodic reporting required by the program. This value will be determined by the county based on county. The specific reporting types for each county will be added in a future SCR associated with the customer reporting logic.

q. PR Due Month: The month of the next periodic reporting due month based on the View Date, RE Due Date and the reporting type. This field will only display when a RE Date exists for the current program application.

r. Role: The Role code of the program person at the given view date.

s. Role Reason: The Reason the role was assigned at the given view date.

t. Status: The status of the participant in the program at the given view date.

u. Status Reason: The status reason of the participant’s program status at the given view date.


v. View Details: This button will navigate to the General Assistance/ General Relief Detail page for the associated program.

3. When the system date is within the RE Due month, the program header will display as a yellow banner with the following text, “[Anticipated program termination for the following month]”.

2.3.4 Page Location • Global: Case Info • Local: Case Summary • Task: Case Summary

2.3.5 Security Updates N/A

2.3.6 Page Mapping Add page mappings for new fields that do not have page mappings.

2.3.7 Page Usage/Data Volume Impacts No additional page usage is expected from this update.

2.4 Program Detail

2.4.1 Overview The Program Detail page is used to select new programs to add to the case. Currently, if a General Assistance/General Relief program is selected in a county that does not support the General Assistance/General Relief program, then a validation message is thrown to prevent the program from being added. This functionality will be modified to only display programs that are available within the county of the logged in user.

2.4.2 Program Detail Mockup

Figure 2.4.2.1 – Program Detail


2.4.3 Description of Changes Update the Select Program dropdown to allow the user to only see the programs available within their county. This limitation will also be applied to all other program dropdowns within the system. Please refer to Appendix item B for a list of additional pages that will require an update to filter the program dropdowns based on county. Note: Existing logic in all program fields will continue to apply. The restriction of programs based on county will be an additional restriction and not a replacement.

2.4.4 Page Location • Global: Case Info • Local: Case Summary • Task: New Program


2.4.6 Page Mapping No new page mappings are required.


2.5 New/Reapplication Detail

2.5.1 Overview The New/Reapplication Detail page is used to add or reopen a program for an existing case. The display for this page will be specified for the General Assistance/General Relief program.


2.5.2 New/Reapplication Detail Mockup

Figure 2.5.2.1 – New/Reapplication Detail

2.5.3 Description of Changes 1. Allow the creation and reapplication of the new General Assistance/General

Relief program. Standard page validations for the existing General Assistance/ General Relief program will continue to apply to the new General Assistance/ General Relief.

2.5.4 Page Location • Global: Case Info • Local: Case Summary • Task: New Program


2.5.6 Page Mapping No new page mappings for the existing page.



2.6 General Assistance/General Relief Detail

2.6.1 Overview The General Assistance/General Relief Detail page will be the main view page for the General Assistance/General Relief program. This page will show a collection of detailed information for the program and its participants at a specific date.

2.6.2 General Assistance/General Relief Mockup

Figure 2.6.2.1 – General Assistance/General Relief Detail (View Mode - Active)


Figure 2.6.2.2 – General Assistance/General Relief (Edit Mode - Active)


Figure 2.6.2.3 – General Assistance/General Relief (View Mode - Pending)


Figure 2.6.2.4 – General Assistance/General Relief (Edit Mode - Pending)


Figure 2.6.2.5 – General Assistance/General Relief (View Mode - Denied)


Figure 2.6.2.6 – General Assistance/General Relief (Edit Mode - Denied)

2.6.3 Description of Changes 1. View History button: This button will navigate the worker to the General

Assistance/General Relief History page. 2. Edit button: This button will refresh the page in ‘Edit’ mode. This button is only

available in ‘View’ mode. 3. Close button: This button will navigate the worker to the Case Summary page.

This button is only available in ‘View’ mode. 4. Save and Return button: Saves the changes that have been made to the

General Assistance/General Relief Detail page and will navigate the worker to the Case Summary page. This button is only available in ‘Edit’ mode.

5. Cancel button: Returns the worker to the Case Summary page. This button is only available in ‘Edit’ mode.


6. Date: Date which will be used to retrieve information for the page. The application that has a status as of the Date will have its information displayed. This is a required field.

a. View Date button: Pressing this button will refresh the page with the program information as of the Date. This button is only available in ‘Create’/’Edit’ mode.

7. Program Information Section a. Status: Status of the program as of the Date. This field is required. b. Status Reason: Reason for the value displayed in the Status column. c. Source: Source of the Application that is tied to the Status as of the Date.

This field is required. d. Application Date: Date of Application for the application that is tied to

the Status as of the Date. This field is required. i. Edit button: Pressing this button will navigate the worker to the

Application Detail page. e. Automatically Reassign When Activated: This field will be a Yes/No

dropdown that will let the current case be reassigned through an overnight batch job after being Activated through EDBC.

f. Reporting Type: This field will display the reporting type associated to the program based on the current view date. This field will only display for an Active, Ineligible, or Discontinued Status.

g. PR Due Month: This field will display the due date of the periodic report. This field will only display when there is a valid RE Due Month

h. RE Begin Month: This field will display the RE Begin Month for the application based on the current view date. This field will only display when a RE period has been established.

i. RE Due Month: This field will display the due month for the Redetermination forms for the program. This field will only display when a RE period has been established.

j. Sub-Program Type: This field will display the sub-program type for the General Assistance/General Relief program for each county. This field will only display if a county has a Sub-Program Type available for their General Assistance/General Relief program. At the time of implementation, only San Francisco County will have options available. The options are as follows:

i. Age Exempt ii. CAAP

iii. Cash Aid Link to Medical iv. General Assistance/General Relief v. Personal Assisted Employment Services vi. SSI Pending

k. Issuance Method – This button will navigate the user to the Issuance Method Detail page in view mode.

8. Administrative Roles section a. Name - Name of the person assigned to the Administrative Roles as of the

Date. b. Administrative Role: Administrative Role that is assigned to the person in

the Name column.


c. Begin Date: Date that the person in the Name column was assigned to the Administrative Role.

d. End Date: Date that the person in the Name column ended the Administrative Role.

e. Edit button: Navigate the worker to the Administrative Role Detail page in ‘Edit’ mode. This button is only available in ‘Create’/’Edit’ mode.

f. Add button - Navigate the worker to the Administrative Role Detail page in ‘Create’ mode. This button is only available in ‘Create’/’Edit’ mode.

9. Program Person section a. Name: Name of the Program Person. This field will be a hyperlink that

navigates the user to the General Assistance/General Relief Person Detail page in view mode.

b. Role: Role of the Person as of the Date. c. Role Reason: Reason for the value displayed in the Role column. d. Status: Status of the Person as of the Date. e. Status Reason: Reason for the value displayed in the Status column. f. Edit button: Navigates the worker to the General Assistance/General

Relief Person Detail page in ‘Edit’ mode. This button is only available in ‘Create’/’Edit’ mode.

g. Rescind button: Navigates the worker to the Rescind Detail page. This button is only available in ‘Create’/’Edit’ mode.

h. Reapply button: Navigates the worker to the New/Reapplication detail page. This button is only available in ‘Create’/’Edit’ mode.

i. Add button: Navigates the worker to the General Assistance/General Relief Person Detail page in ‘Create’ mode. This button is only available in ‘Create’/’Edit’ mode.

10. Secondary Worker Assignment section a. Worker: Name of the Worker that is assigned as a secondary assignment.

Clicking on the Worker will navigate the worker to the Worker Detail page. i. Select button: Pressing button will navigate the worker to the Select

Worker page to find a worker for the secondary assignment. This button is only available in ‘Create’/’Edit’ mode.

ii. Remove button: Pressing the button will Remove the secondary assignment. This button is only available in ‘Create’/’Edit’ mode.




2.6.6 Page Mapping Add page mappings for new page.


2.7 Administrative Role Detail

2.7.1 Overview The Administrative Role Detail page is used to assign administrative roles to the program such as Payee and Primary applicant. This page will be updated to have unique options for the new General Assistance/General Relief program.

2.7.2 Administrative Detail Mockup

Figure 2.7.2.1 – Administrative Role Detail

Figure 2.7.2.2 – Administrative Role Detail (Payee Selected)


2.7.3 Description of Changes Update the Administrative Role field to display the following options when the program type is the new General Assistance/General Relief program:

a. Payee b. Primary Applicant/ Recipient

Note: All existing page logic tied to these fields will continue to apply.

2.7.4 Page Location • Global: Case Summary • Local: Case Summary • Task: Case Summary


2.7.6 Page Mapping No new page mappings for the existing page


2.8 Rescind Detail

2.8.1 Overview The Rescind Detail page is used to reopen denied and discontinued programs. Each program has a unique set of rescind reasons based on the date and status of the program being rescinded.


2.8.2 Rescind Detail Mockup

Figure 2.8.2.1 – Rescind Detail

2.8.3 Description of Changes 1. Display the following options when rescinding a Denied status for the new

General Assistance/General Relief program. a. Admin Decision b. Erroneous Disc/Deny c. Good Cause d. Other e. Rescind Disc/Deny

2. Display the following options when rescinding a Discontinued status for the new

General Assistance/General Relief program. a. Admin Decision b. Erroneous Disc/Deny c. Good Cause d. Other e. Periodic Reporting f. PR - County Error g. PR - Mental/Physical Condition h. PR - Other Extenuating Circumstance i. Rescind Disc/Deny




2.8.6 Page Mapping No page Mappings Required.


2.9 General Assistance/General Relief Person Detail

2.9.1 Overview The General Assistance/General Relief Person Detail page will display detailed information for the General Assistance/General Relief program person.

2.9.2 General Assistance/General Relief Person Detail Mockup

Figure 2.9.2.1 – General Assistance/General Relief Person Detail (View Mode)


Figure 2.9.2.2 – General Assistance/General Relief Person Detail (Edit Mode)

Figure 2.9.2.3 – General Assistance/General Relief Person Detail (Create Mode)

2.9.3 Description of Changes 1. Display the Recipient Information section with the name field. The Name will

display in the format: “Last Name, First Name AgeGender”. This field will be a multi select dropdown in Create Mode.

2. Display the Application Detail Section with the following fields a. Application Date: The Date of the person’s application for the status

related to the view month from the General Assistance/General Relief Detail page. This field will only be editable in Create Mode. This field will have the standard Date constraint and calendar icon, when editable.

b. Beginning Date of Aid: The BDA of the person’s application for the status related to the view month from the General Assistance/General Relief Detail page. This field will only be editable in Create Mode. This field will have the standard Date constraint and calendar icon, when editable.


c. Edit: This button will navigate the user to the Application Detail page in Edit Mode. This button will only display in Edit mode.

3. Display the following buttons at the top and bottom of the page: a. Cancel: This button will only display in Create and Edit Mode. This button

will navigate the user to the General Assistance/General Relief Detail page.

b. Close: This button will only display in View Mode. This button will navigate the user to the General Assistance/General Relief Detail page.

c. Edit: This button will only display in View Mode. This button will reload the General Assistance/General Relief Person Detail page in Edit Mode.

d. Remove: This button will only display in Edit Mode. This button will remove the program person from the General Assistance/General Relief program and navigate the user to the General Assistance/General Relief Detail page.

e. Save and Return: This button will commit any changes that have been made on the page and navigate the user to the General Assistance/General Relief Detail page. This button will only appear in Create and Edit modes.



2.9.6 Page Mapping Add page mappings for the new page


2.10 Position Detail

2.10.1 Overview The Position Detail page is used to record information to help regulate the worker’s access, capabilities and caseload capacity. This page contains a section for programs that a worker can be automatically assigned to that will be updated to include the new General Assistance/General Relief program.


2.10.2 Position Detail Mockup

Figure 2.10.2.1 – Position Detail (Program(s) Section)

2.10.3 Description of Changes Update the Program(s) section to only display programs that are available within the county.

2.10.4 Page Location • Global: Admin Tools • Local: Office Admin • Task: Position


2.10.6 Page Mapping No new page mappings for the existing page



2.11 Application Registration Summary

2.11.1 Overview The Application Registration Summary page is used to allow workers to enter the SAWS I application information in the system to link to the case. When creating the application, the programs can be selected to apply. The General Relief option will be renamed and repurposed for both General Assistance General Relief programs.


2.11.2 Application Registration Summary Mockup

Figure 2.11.2.1 – Application Registration Summary (Main Section)

2.11.3 Description of Changes 1. Update the General Relief option under the “What programs are you applying

for?” question to be General Assistance/ General Relief. 2. Update the logic to populate either the correct General Assistance/General

Relief program code based on county.


2.11.4 Page Location • Global: Case Info • Local: New Application • Task: Application Registration


2.11.6 Page Mapping No new page mappings for the existing page.





4 REQUIREMENTS



How Requirement Met

2686 The CONTRACTOR shall integrate the CalWIN GA/GR rules into the CalSAWS Software. The Contractor shall migrate the existing C-IV GA/GR functionality which includes: - Creation of a GA/GR (Managed/Non-Managed) case - Ability to select the Issuance Method to EBT, Direct Deposit, or Warrant (check) - Ability to run a Manual EDBC to issue benefits to the customer, landlord or utility vendor - Ability to create a Service Arrangement/Payment Request to issue services / valuables

Requirement 1: Online: 1) The Existing GR Program Detail and New/Reapplication Detail pages can be used for program Creation. 2) No Updates are required to the workload assignment logic for the new GR Program. 3) No More than 10 Non-GR Data Collection will need to be updated with additional elements. Eligibility: 1. The existing CalWIN GA/GR rules will be developed in CalSAWS. 2. The Forms/NOA will be rendered by DXC using the Correspondence Service. The triggers conditions for the Forms/NOAs

The General Assistance/General Relief program to be used for automated Eligibility determinations will be added. All EDBC Report, Fiscal and Batch logic will be handled in a future SCR.


will be developed in CalSAWS. 3. The Users will use Run EDBC page to run GA/GR EDBC and authorizes the results like other programs. The Users will navigate to Correspondence page after Authorization to check the existence of a NOA. A NOA hyperlink will be created if EDBC resulted in a NOA. When the User clicks the NOA hyperlink a webservice call will be made to DXC Correspondence Service to render the NOA and return the pdf back to CalSAWS in real time. During this webservice call the entire data related to the case will be transferred. This includes but not limited to Data Collection, Prior Issuances, Address, Assigned worker details 4. Override functionality for the EDBC determined by GA/GR service will be available in CalSAWS.


5. Manual EDBC functionality will be available in CalSAWS. 6. The new GR solution will have a separate program code in backend so that the existing LA county GR and C-IV Managed/Non-Managed GR programs will not be impacted. 7. Preview NOA functionality will not be available for the new GA/GR solution 8. This solution will be subject to a different SLA standard due to external NOA service interaction. 9. The use case for current CalWIN GA/GR rules, NOAs/Forms triggers and MU triggers will be provided by DXC. 10. Based on Use case CalWIN GA/GR rules, NOAs/Forms triggers and Batch Sweeps for MU triggers will be designed and developed in CalSAWS. 11. The existing NOA/form templates and


County Admin's ability to create a customizable pdf version for the county will be maintained and updated by DXC in the new solution. Batch/Interface: 1. Only one web service call will be made to DXC to generate the NOA/Form for GA/GR Participants 2. All information to generate correspondence will be provided in one single request 3. Web service response will have the generated NOAs/Forms pdf. 4. Emulator will be available to get standard NOAs/Forms response for all correspondence request. 5. No webservices is required for rules since it will be handled in CalSAWS. 6. Estimates for web services is covered in DDID 2319 Fiscal:


1) New GR Program will not be available to C-IV and LRS counties, so county specific interfaces will not need to be updated to exclude these programs. 2. Issuance, Adjustment and Claiming logic for GA/GR will be handled in CalSAWS using existing Fiscal framework. Requirement 2: The effort to port the C-IV solution is part of SCR CA 201377


5 APPENDIX A. Program Code Reference Values

Code_Num_Identif GR SHORT_DECODE_NAME General Assistance/General Relief Program Code N Other Assistance Program Code N Considered Public Assistance N FS Count in Allotment Y Multiple Programs Allowed N Organization as Payee Y Intake Program N Report Inter-County Transfer N Eligibility EDBC Indicator N NOABenefitType Caseload Search Indicator Intake Redetermination Flag N WDTIP Program Codes External Programs Y Manual EDBC Indicator N Redetermination Indicator N Recovery Account Indicator Y Allow Service Arrangement Aid Code Base Program Un-Reimbursed Assistance Program Codes N SIU Referred Program Y RA Uncollectible Status N Uncollectible Cash IPV Programs C Is Application Considered Y Time Limits Program C4Yourself Managed Application N EICT EICT Programs Reception Log Program Codes GA RCC Programs Call Log Program Codes General Assistance LALegacyPgmCodes Case Flag Programs Receipt Programs


Program Hierarchy 2 YBN_Outbound Job Development Activity ES Search Code Change Reason Program Distinguish between DCFS and DPSS Programs Spanish Pending Authorization Days To Complete Program Code to Display GR EBT Stagger Program YBN_EW_Communication Program Rescission Time Limit 0 Leader Program Name GA Authorized Representative Program to display online Activity Agreement programs General Assistance/General Relief

B. Pages with affected program dropdowns a. Best Practice Detail b. Best Practice Search c. Call Log Detail d. Care and Maintenance Detail e. Computation Request Detail f. Create QA/QC Batch g. Distributed Documents Search h. Eligibility Non-Compliance List i. Findings Detail j. Fiscal History Search k. Foster care Recovery Account Detail l. Hearing Detail m. Invoice Search n. Money Management List o. Office Detail p. Other Program Assistance Detail q. Pending Authorizations r. Pending Workload Assignment List s. Performance Analysis detail t. Program Detail u. Quality Review Detail v. Receipt Mass Upload Search w. Reception Log Detail x. Recovery Account Detail y. Recovery Account Search z. Recovery Account Workload Inventory

aa. Reminders List bb. Report Search


cc. Select Document dd. Service Arrangements List ee. Special Investigation Detail

ff. Special Investigations Referral gg. Standards Detail hh. Template Repository Search

ii. Unreimbursed Assignment pool jj. Valuable Request Search

kk. Verification Detail ll. Workload Reassignment Detail



Design Document

CA-216414

Migrate CD 7617 (06/14) - Child Care NOA


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Harish Katragadda

Reviewed By Pramukh Karla


6/25/2020 1.0 Original Draft Harish Katragadda



1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


1.4 Assumptions ............................................................................................................... 4


2.1 CD 7617 – Child Care NOA ....................................................................................... 5

2.1.1 Overview ............................................................................................................. 5



4 Requirements ...................................................................................................................15

4.1 Migration Requirements ...........................................................................................15


1 OVERVIEW

1.1 Current Design CD 7617 (06/14)Child Care NOA is currently not available in the LRS/CalSAWS system.

1.2 Requests Migrate CD 7617 (06/14) Child Care NOA which will generate from Child Care Online Pages and make it available in the Template repository. Add pre-population to the CD 7617 form to match the existing C-IV version.

1.3 Overview of Recommendations 1. Add CD 7617 (06/14) form to the LRS/CalSAWS template repository. 2. Add the ability to generate CD 7617 (06/14) from Child Care Online Pages. 3. Prepopulate CD 7617 (06/14) using current C-IV pre-population logic for the form.

1.4 Assumptions 1. CD 7617 will be added in English and Spanish languages. 2. CD 7617 will be available to all 58 counties. 3. CD 7617 will have LRS/CalSAWS standard Header on the Cover Page with no

State Agency Names 4. Existing LRS/CalSAWS header functionality will be used for the population of the

Header.


2 RECOMMENDATIONS

2.1 CD 7617 – Child Care NOA

2.1.1 Overview Add CD 7617 (06/14) – Child Care NOA to template repository. Generate CD 7617 from Child Care Certificate page, Child Care Certificate Detail page has been created or updated to approved status and when child care program gets denied or discontinued.

2.1.2 Description of Change 1. Create CD 7617 form Create CD 7617 (06/14) form with 4 impressions in English and Spanish. The first 2 impressions will be cover page with LRS/CalSAWS standard header with no state agency names. The next 2 impressions will have the CD 7617 form

Form Number: CD 7617 Cover Page: LRS/CalSAWS standard Cover Page (2 Impressions)

Form Title: Child Care NOA Form Descr: Notice to Customers that their Child Care services have been approved or denied.

Program: Child Care Forms Category: NOA Source: State Languages: English, Spanish

Include NA Back 9: No Imaging Barcode: Yes

2. Add CD 7617 to template repository Add the CD 7617 (06/14) – Child Care NOA form to Template Repository. The following parameters will be required:

Required Form Input: Case Number, Customer Name, Program and Language

Form Mockups: Please refer to Section 3.0 – Supporting Document #1, #2.


3. Add the following barcode options to the CD 7617 Form:

Tracking Barcode BRM Barcode Imaging Barcode

N N Y

4. Add the following print options to the CD 7617 Form:

Blank

Template Print Local

without Save

Print Local and Save

Print Central

and Save

Reprint Local

Reprint Central

Y Y Y N Y N

Mailing Requirements:  Mail-To (Recipient): Case Person selected on the Document parameter page/ Primary Applicant of the Child Care Program from online pages Mailed From (Return): Worker’s Office Address Mail-back-to Address: N/A   Outgoing Envelope Type: Standard  Return Envelope Type: N/A  Mailing Priority: Same Day Priority    Additional Requirements:  Special Paper Stock: N/A  Enclosures: N/A   Electronic Signature: N/A  Post to YBN/C4Y: Yes

5. Generate CD 7617 from Child Certificate List Page

a. Clicking ‘Generate CD 7617’ button should generate the CD 7617 form if all the below conditions are true:

i. All the selected certificates are in the Approved status ii. All the selected certificates have the same Start and Stop

Date. iii. All the selected certificates have different child iv. No More than four certificates are selected

b. ‘Generate CD 7617’ button will be hidden on the Child Care Certificates List page, if there are no certificates to display.

c. Add validations to the ‘Generate CD 7617’ button.


i. Selecting a Child Care Certificate with a status of “Pending TrustLine” or “Rejected” and clicking the ‘Generate CD 7617’ button will display the following validation message “Certificate – The certificate needs to be in approved status”.

ii. If multiple certificates are selected and the Start Date is not the same date for all the selected certificates, then display the following validation message “Certificate – All selected certificates must have the same Begin Date”.

iii. If multiple certificates are selected and the Stop Date is not the same date for all the selected certificates, then display the following validation message “Certificate – All selected certificates must have the same End Date”.

iv. If multiple Certificates are selected and where there is same child in more than one certificate, then display the following validation message “Certificate – Cannot include the same child more than once on the form. Please select certificates for different children”.

v. Selecting more than 4 different children with same Start Date and clicking on “Generate CD 7617” button will display the following validation message “Certificate – Cannot select more than four children”.

6. Generate CD 7617 when Child Certificate is Created/Updated

a. Generate CD 7617 when Child Care Certificate has been created or updated from Child Certificate Detail Page if it meets this following conditions

i. The Funding Source for the Child Certificate is not ‘Stage 1’ or ‘Stage 1 Unable to Transfer’

ii. The Child Care Certificate has approved status 1. The first time it has been created or 2. The Previous Child Care Certificate status is not

approved.

7. Generate CD 7617 when Child Care Program is Denied or Discontinued

a. Generate CD 7617 when status has been added to the Child Care program

i. The Funding Source for the Child Care Program is not ‘Stage 1’ or ‘Stage 1 Unable to Transfer’

ii. Status is either Denied or Discontinued


8. Variable Population for CD 7617 Form Populate the variables on the CD 7617 form Note: The Cover Page Population will follow the existing Cover Page Population logic

Section Field Description

1.A. Application of Services

CD 7617 - Page 3 ‘Services Approved to Begin’ Check Box

Check if Child Care Program is Active – High Dated

CD 7617 - Page 3 ‘Services Denied’ Check Box

Check if Child Care Program is Denied - High Dated

2. Distribution of Notice

CD 7617 - Page 3 Date Notice Given or Mailed:

Date the Form Generated Example: 01/01/2020

3. Parent/Caretaker Information

CD 7617 - Page 3 Parent/Caretaker A Template Repository Case person Selected on the drop down menu Child Certificate List - Generate CD 7617’ button Primary Person on the Child Care Certificates, usually a parent Child Care Certificate - Created/Updated Primary Person on the Child Care Certificates, usually a parent

Child Care Program - Denied or Discontinued

Primary Person on the Child Care Program, usually a parent


Section Field Description CD 7617 - Page 3 Address Mailing Address of the

Parent/Caretaker A CD 7617 - Page 3 City City of the Parent/Caretaker A CD 7617 - Page 3 Zip Zip Codes of Parent/Caretaker A CD 7617 - Page 3 Parent/Caretaker B Name of the Second Parent

active/pending on Child Care who is not out of Home and have the same physical Address as the Primary parent populated on Parent/Caretaker A (If Parent/Caretaker is a parent)

4.Approved Child Care Services

CD 7617 - Page 3 Name(s) of Child(ren) Receiving Services

1.Template Repository No Population 2.Child Certificate List - Generate CD 7617’ button: a.Certificates Selected Populate up to 4 Names of the Children from the Child Care Certificates selected b.No Certificates Selected Populate up to 4 Names of the Children on the Child Care Program when the program is ‘Denied’ or ‘Discontinued’ (High Dated) Who has a ‘MEM’ role, ‘Child’ role reason and Status same as the Program and Status started on the same date as the program status. 3.Child Care Certificate - Created/Updated No Population



4.Child Care Program - Denied or Discontinued a. Populate up to 4 Names of Children on the Child Care Program when the program status added is ‘Denied’ or ‘Discontinued’ and person has ‘Child’ role reason b. If no child found with above conditions as in 4.a when program status is added Populate up to 4 Names of the Children on the Child Care Program when the program is ‘Denied’ or ‘Discontinued’ (High Dated) Who has a ‘MEM’ role, ‘Child’ role reason, and Status same as the Program and Status started on the same date as the program status.

CD 7617 - Page 3 Program Code 1.Template Repository No Population 2.Child Certificate List - Generate CD 7617’ button a.Certificates Selected Populate with Funding Source of the Child Care Program if the latest Child Care Program status is Active or Pending and the funding source is ‘CAPP’, ‘C2AP’ or ‘C3AP’. b.No Certificates Selected No Population 3.Child Care Certificate - Created/Updated No Population



4.Child Care Program - Denied or Discontinued No Population

CD 7617 - Page 3 Enter Approved Hours of Enrollment

1.Template Repository No Population 2.Child Certificate List - Generate CD 7617’ button a.Certificates Selected Populate with Total Regular(School) and Vacation hours for the Child Care Certificates selected b.No Certificates Selected No Population 3.Child Care Certificate - Created/Updated No Population 4.Child Care Program - Denied or Discontinued No Population Example : 3h 45m

CD 7617 - Page 3 Monthly Family Fee - Part-time $

1.Template Repository Populate with the current Part time Family Fee similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived. 2.Child Certificate List - Generate CD 7617’ button a.Certificates Selected Populate with the Part time Family Fee on the Begin Date of the Child Care Certificate from the Child Care


Section Field Description program ‘Eligibility Detail’ page if the Family fee is not Waived. b.No Certificates Selected Populate with the current Part time Family Fee similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived. 3.Child Care Certificate - Created/Updated Populate with the current Part time Family Fee from the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived.

4.Child Care Program - Denied or Discontinued Populate with the current Part time Family Fee from the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived. Example :134.00

CD 7617 - Page 3 Monthly Family Fee - Full-time $

Template Repository Populate with the current Full Time Family Fee similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived. Child Certificate List - Generate CD 7617’ button a.Certificates Selected Populate with the Full time Family Fee on the Begin Date of the Child Care Certificate similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived.


Section Field Description b.No Certificates Selected Populate with the current Full Time Family Fee similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived. Child Care Certificate - Created/Updated Populate with the current Full Time Family Fee similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived.

Child Care Program - Denied or Discontinued Populate with the current Full Time Family Fee similar to the Child Care program ‘Eligibility Detail’ page if the Family fee is not Waived. Example :134.00

8. Agency Name CD 7617 - Page 3 Agency Name Program Worker’s Office Name STEP 2 – Agency Address

CD 7617 - Page 4 Agency Name County’s Child Care Hearing Office Name

CD 7617 - Page 4 Agency Address County’s Child Care Hearing Office Address

CD 7617 - Page 4 City/State/Zip County’s Child Care Hearing Office City/State/Zip code

CD 7617 - Page 4 Name of Agency Contact

County’s Child Care Hearing Office Contact Name

CD 7617 - Page 4 Agency Telephone Number

County’s Child Care Hearing Office Contact




1 Client Correspondence

CD 7617 English CD7617_EN.pdf

2 Client Correspondence

CD 7617 Spanish CD7617_SP.pdf


4 REQUIREMENTS


DDID #

REQUIREMENT TEXT Contractor Assumptions

How Requirement Met

Migrate Form CD 7617 (6/14) Notice of Action for Child Care Services. Add the ability to generate this form from the Child Care online page and include all pre-population as it currently exists in C-IV.

N/A With SCR CA-216414,CD 7617 form will be added to LRS/CalSAWS.CD 7617 will be generated from Template Repository and Child Care Certificates List Page, Child Certificate Detail Page and Child Program Detail Page.



Design Document

CA-217007

Enable CMA job and Update CMA Notices to reflect telephonic call due to COVID


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Jamie Ng

Reviewed By Lawrence Samy


06/16/2020 1.0 Original Draft Jamie Ng 06/22/2010 1.1 Added the CMA Job enable S Meenavalli



1.1. Current Design ........................................................................................................... 4

1.2. Requests ..................................................................................................................... 4

1.3. Overview of Recommendations .............................................................................. 4

1.4. Assumptions ............................................................................................................... 4


2.1. Enable the Case Manager Appointment (CMA) Daily Job .................................. 5

2.1.1 Overview ........................................................................................................ 5


2.2. ABP 1460 - General Relief Opportunities For Work Case Manager Appointment Notice ................................................................................................................................ 5

2.2.1 Overview ........................................................................................................ 5


2.1.2.1 Update ABP 1460 - General Relief Opportunities For Work Case Manager Appointment Notice XDP ......................................................................................... 5


4 Requirements .................................................................................................................... 7

4.1. Project Requirements ................................................................................................ 7

4.2. Migration Requirements............................................................................................ 8

5 Migration Impacts ............................................................................................................ 8


1 OVERVIEW This SCR is to enable Case Manager Appointment (CMA) job and to modify the CMA location language in the notice/form to change the location from a physical district office address to a telephonic call , contact person due to the delay in opening of the district offices due to COVID.

1.1. Current Design Currently, CMA Appointment job is disabled and CMA Appointment notice do not include a telephone or video appointment option verbiage.

1.2. Requests Enable CMA Appointment job and Update Appointment Notices with verbiage reflecting change of location from a physical district office address to a telephonic call , contact person due to the delay in opening of the district offices due to COVID.

1.3. Overview of Recommendations 1. Enable the daily CMA Appointment job PB19C905 in the jobs scheduler 2. Revised/create text and templates for the NOAs below:

a. ABP 1460 - General Relief Opportunities For Work Case Manager Appointment Notice

1.4. Assumptions 1. Changes in this SCR will be reverted in future SCR when district offices are

reopened and face-to-face appointments are done in offices.


2 RECOMMENDATIONS

2.1. Enable the Case Manager Appointment (CMA) Daily Job

2.1.1 Overview Daily CMA Appointment is disabled due to COVID-19.

2.1.2 Description of Change Enable the below GROW CMA Appointments Job. Job Id - PB19C905 Description – GROW CMA Appointments schedule job Frequency – Daily This batch sweep will create GROW CMA Appointments for eligible GR persons.

2.2. ABP 1460 - General Relief Opportunities For Work Case Manager Appointment Notice

2.2.1 Overview ABP 1460 (2/2014) - General Relief Opportunities For Work Case Manager Appointment Notice is used to inform participants of Work Case Manager Appointment Notice.

State Form/NOA: ABP 1460 (2/2014) Program(s): General Relief Opportunities For Work (GROW)

Current Attached Forms: N/A Current Forms Category: Form Current Language:

English and Spanish

2.2.2 Description of Change Update ABP 1460 (2/2014) with additional verbiage.

2.2.2.1 Update ABP 1460 - General Relief Opportunities For Work Case Manager Appointment Notice XDP Update XDP with additional verbiage in English and Spanish.

Updated Languages:


English and Spanish

NOA Mockups/Examples: See Supporting Documents #2

Number Existing Text Updated Text

1 You are scheduled for an appointment to meet with your GROW Worker at the date, time and location listed below.

You are scheduled for a telephone appointment to talk with your GROW Worker at the date and time listed below.

2 • If you are required to provide verification or documentation, don't forget to bring it with you to this appointment.

• If you are required to provide verification or documentation, let your worker know during this appointment.

3 (Location variable) By telephone- See number below

4 Attending the appointment with your GROW Worker is mandatory. You might be sanctioned if you do not go.

Keeping the appointment with your GROW Worker is mandatory. You might be sanctioned if you do not call.


5 (3) You had a good reason for not attending your appointment.

(3) You had a good reason for not keeping your appointment.

6 If you cannot keep this appointment or you have any questions about the appointment, contact the GROW Worker immediately at the number listed below.

If you cannot keep this telephone appointment or you have any questions about the appointment, contact the GROW Worker immediately at the number listed below.




1 Form ABP1460 Mockup ABP1460_EN Mockup.pdf ABP1460_SP Mockup.pdf


4.1. Project Requirements

REQ # REQUIREMENT TEXT How Requirement Met 2.18.3.3 CAR-1239

The LRS shall produce various notices, NOAs, forms, letters, stuffers, and flyers, including: a. Appointment notices; b. Redetermination, Recertification, and/or Annual

Update ABP1461With appropriate verbiage


Agreement notices and forms; c. Other scheduling notices (e.g., quality control, GR hearings, and appeals); d. Periodic reporting notices; e. Contact letters; f. Notices informing the applicant, participant, caregiver, sponsor or authorized representative of a change in worker, telephone hours or Local Office Site; g. Information notices and stuffers; h. Case-specific verification/referral forms; i. GR Vendor notices; k. Court-mandated notices, including Balderas notices; l. SSIAP appointment notices; m. Withdrawal forms; n. COLA notices; o. Time limit notices; p. Transitioning of aid notices; q. Interface triggered forms and notices (e.g., IFDS, IEVS); r. Non-compliance and sanction notices; s. Benefit issuance and benefit recovery forms and notices, including reminder notices; t. Corrective NOAs on State Fair Hearing decisions; u. CSC paper ID cards with LRS-generated access information; and v. CSC PIN notices.

4.2. Migration Requirements



SCR Number

Functional Area





Design Document

SCR CA-218528 – Update TIFF to PDF conversion library


CalSAWS

DOCUMENT APPROVAL HISTORY Prepared By Ihsan Abdulsamed

Reviewed By Sumeet Patil


8/10/2020 1.0 Initial Revision



1.1 Current Design ........................................................................................................... 4

1.2 Requests ..................................................................................................................... 4


2.1 Update TIFF to PDF Conversion Libraray .................................................................. 5

2.2 Update IctHelper module to use FileConverter ...................................................... 5

3 Impacted Batch Jobs:...................................................................................................... 5


1 OVERVIEW This SCR will upgrade the TIFF to PDF conversion utility in CalSAWS application.

1.1 Current Design Currently the CalSAWS system uses iText library for TIFF to PDF conversion utility. EICT Image Reader batch job uses this conversion utility.

1.2 Requests The current iText library has limitations and fails to convert some eICT images.


2 RECOMMENDATIONS

2.1 Update TIFF to PDF Conversion Libraray Upgrade the TIFF to PDF conversion architecture utility module (FileConverter) to use the following libraries - Apache PDFBox (v2.0.17) - com.twelvemonkeys.imageio (v3.3.1)

2.2 Update IctHelper module to use FileConverter Update IctHelper module to use the TIFF to PDF conversion architecture utility module (FileConverter) to remove the duplicate code.

3 IMPACTED BATCH JOBS: The following batch jobs utilize the TIFF to PDF conversion and are impacted by this change:

Module Jobs

org.civ.interfaces.common.SupportUtilityFile PB19C630

org.civ.interfaces.eict.EictImageReaderWrapper PICWE101, PILDE101, PIC4E101

4 APPENDIX: License Information –

1. Apache PDFBox : License 2. TwelveMonkeys ImageIO: License

https://www.apache.org/licenses/

http://opensource.org/licenses/BSD-3-Clause