TABLE OF CONTENTS - Department of Public Social Services
TABLE OF CONTENTS - Department of Public Social Services
TABLE OF CONTENTS - Department of Public Social Services
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Los Angeles COUNTY<br />
<strong>Department</strong> <strong>of</strong> <strong>Public</strong> <strong>Social</strong> <strong>Services</strong><br />
LEADER Replacement System (LRS)<br />
7997<br />
7998<br />
7999<br />
8000<br />
8001<br />
8002<br />
8003<br />
8004<br />
8005<br />
8006<br />
8007<br />
8008<br />
8009<br />
8010<br />
8011<br />
8012<br />
8013<br />
8014<br />
8015<br />
8016<br />
8017<br />
8018<br />
8019<br />
8020<br />
8021<br />
8022<br />
8023<br />
8024<br />
8025<br />
8026<br />
8027<br />
8028<br />
8029<br />
8030<br />
8031<br />
8032<br />
8033<br />
8034<br />
8035<br />
8036<br />
8037<br />
49. The LRS shall not prevent or impede full access to the existing DCFS<br />
Systems by existing DCFS Systems users and COUNTY-specified<br />
Users.<br />
50. The LRS shall include an analysis <strong>of</strong> DPSS Systems source files,<br />
DCFS Systems source files, and other legacy data source files in order<br />
to determine what DPSS Systems data, DCFS Systems data, and other<br />
legacy data can and/or cannot be extracted and processed during the<br />
conversion process.<br />
51. The LRS shall include an analysis <strong>of</strong> DPSS Systems and DCFS<br />
Systems duplicated and unduplicated records with a priority ranking<br />
based upon the accuracy <strong>of</strong> each record’s data in order to extract and<br />
load the most accurate data.<br />
52. The LRS shall identify data exceptions. Edits and logic shall be<br />
developed that will identify invalid data values, incomplete records,<br />
duplicate identifiers, individuals with more than one identifier,<br />
inconsistencies between files, and other exception conditions. All<br />
exceptions shall be documented on reports in a format approved by<br />
COUNTY Project Director.<br />
53. The LRS shall correct data exceptions, as a first priority via update<br />
transactions that will be created and processed against the appropriate<br />
existing source file(s) in order to correct the exception(s) if possible.<br />
54. The LRS shall correct data exceptions by additional conversion code<br />
that shall correct the problem during the conversion process, where an<br />
automated data correction is not possible.<br />
55. The LRS shall document all automated corrections via update<br />
transactions in reports in a format approved by COUNTY Project<br />
Director.<br />
56. The LRS shall identify all instances where an automated correction is<br />
not possible via update transactions and shall, as the second priority to<br />
item 10 above, write conversion code that will correct the problem<br />
during the conversion process.<br />
57. The LRS shall document and produce reports, in a format approved by<br />
COUNTY Project Director, <strong>of</strong> all instances where automated<br />
correction will be achieved via conversion logic and default values.<br />
58. The LRS shall identify all instances where update transactions and<br />
conversion logic as automated solutions are not possible and shall<br />
document these instances in reports, in a format approved by<br />
COUNTY Project Director, with a corrective action plan.<br />
59. The LRS shall, as part <strong>of</strong> the conversion transaction corrective action<br />
plan above, include the option to treat the case as a manual case under<br />
the ED/BC requirements for overriding the system. CONTRACTOR<br />
LRS RFP - Attachment B (SOR) Page 225 November 30, 2007
Change language