The Maryland Overpayment Case Management System (MDOCS) was developed for the Maryland Department of Labor Licensing and Regulation (DLLR), to support its Division of Unemployment Insurance (DUI) Benefit Payment Control (BPC) unit in expediting the detection and collection of overpayment benefits. The MDOCS automated system is a central repository of all overpayment benefit information and is critical to DUI's operation in replenishing the UI Trust Fund. The MDOCS system pulls overpayment case information from MABS (Maryland Automated Benefit System) and performs OCR on the DUI overpayment cases to include archiving and indexing. In addition, MDOCS claimant information is matched against the U.S. Department of Labor's (DOL's) National New Hire program registry. MDOCS generates documents for employment verification for claimant matches who are working and collecting benefits. The resultant documentation allows the BPC staff the ability to view, schedule, and maintain overpayment cases.
The scope of work included technical services to provide development as well as Operations and Maintenance (O&M) support for the MDOCS database, application, and hardware environment. XPAND's performance on this project includes re-engineering MDOCS, data re-architecture and data consolidation using SQL Server Integration Services (SSIS), document management system integration, UI redesign per Maryland ADA Compliance Standards including Section 508, integration with a Document Management System, and providing staff training.
Many issues pertaining to functionality, performance, poor quality data imports/exports, and non-compliance with Maryland ADA Compliance Standards plagued the existing MDOCS application. XPAND was contracted to help address these pain points. Our approach was to first stabilize the system, and then improve functionality. Stabilizing the system involved rebuilding the ETL functionality to fix data discrepancies, and then rewriting and replacing all of the unstable custom code. All changes reflected the use of Microsoft best practices, aligned with Maryland ADA Compliance Standards and Section 508 compliance.
The simultaneous re-engineering of the system and updating occurred as the public site remained in use. Once the system was stabilized and functionality added, XPAND moved on to fixing the FileBound integration component, which was being used as the Document Management System.
The MDOCS application connects to various data sources in order to help provision its decision-making capabilities. The biggest pain point was "expired/incorrect" data being pulled in by the system because many of the daily/real-time imports did not work as required. XPAND rebuilt ETL functionality to pick source files from various legacy systems and data-mined, transformed, and loaded the disparate data sources in to the MDOCS system. Since the MDOCS application had a workflow component built into it, it was essential that the various documents and images that were stored for each unemployment benefits "case record" be accessible within the application. The various documents were stored in a FileBound Document Management System. XPAND fixed the FileBound integration component that was preventing users from being able to pull up documents associated with a "case record" within the MDOCS application.