TABLE OF CONTENTS - Department of Public Social Services

Los Angeles COUNTY
Department of Public Social Services
LEADER Replacement System (LRS)
8038
8039
8040
8041
8042
8043
8044
8045
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
8057
8058
8059
8060
8061
8062
8063
8064
8065
8066
8067
8068
8069
8070
8071
8072
8073
8074
8075
8076
8077
shall obtain COUNTY Project Director approval for each identified
situation.
60. The LRS shall include an iterative process for cleaning data prior to
final conversion to the LRS. The process shall include multiple runs
of data fields and areas with reports in a format approved by
COUNTY Project Director and lists that include, sorting by office, and
file number and type of conversion case situation.
61. The LRS shall develop conversion rules and logic to convert values
from the DPSS Systems, DCFS Systems, and other legacy systems
into LRS Data element values. Default values shall be identified for
data elements not available on existing systems, including those data
elements which are necessary to establish eligibility or calculate a
benefit level.
62. The LRS shall be loaded with the edited and purified case and client
data. When appropriate, new data elements required for the LRS Data
shall be updated with default values. The LRS database shall be
populated with data including:
a. Payment history (online and archived) attained from existing
sources;
b. Current and historical data from existing COUNTY, ancillary, and
interfacing systems; and
c. All data from the DPSS Systems and DCFS Systems, including
active and inactive cases.
63. The LRS shall have the ability to determine correct eligibility and
benefit levels and otherwise fully maintain the case using the
converted and default data.
64. The LRS shall establish a testing database in the LRS that is retrieved
from a three percent (3%) representative sample of cases from DPSS
Systems and DCFS Systems covering all programs, aid codes, and
scenarios to be used in all phases of testing. The testing database shall
be loaded using LRS conversion programs, edits, and default values.
65. The LRS testing database shall be built from the LRS conversion
programs and shall be kept current and be reloaded as LRS conversion
programs and DPSS Systems data, DCFS Systems, or other legacy
data are refined and corrected.
66. The LRS conversion software shall be tested prior to the initiation of
any conversion activity. All conversion software shall be unit tested,
system tested, and acceptance tested prior to implementation.
67. CONTRACTOR shall prepare a conversion test plan, develop the
conversion test criteria, and provide the test environment. The iterative
LRS RFP - Attachment B (SOR) Page 226 November 30, 2007