Automation
Overview
| Introduction | The ability to stay competitive requires the automation of manual, labor intensive processes. |
| Long term solutions may not be the best choice |
Technology is moving forward more quickly today than ever before. SESAs are encouraged to take advantage of off-the-shelf software to support their recovery programs. Long term solutions to today's automation needs may not be the best choice since automated systems can become obsolete before they can be implemented. |
| Use what you have | Many SESAs may not be utilizing equipment and technology already at their disposal. Personal computers, servers, and network capability can become effective recovery systems for smaller organizations. |
| In this section | The following topics will be discussed in this section. |
| Topic | Page |
| Introduction | 2 |
| Legacy Mainframe Systems | 4 |
| Automation Today | 6 |
| Case Management Systems | 9 |
| Collectibility Profiling | 10 |
| Summary of Guidelines | 11 |
| Background | Automated collection systems are critical to the effectiveness of a recovery program. Traditionally, cost savings are realized when routine, large volume clerical operations are automated. Overpayment record-keeping and certain initial collection activities are routine clerical tasks which are cost effective to automate. |
| Level of automation | The chart below reflects the level of automation as reported by the SESAs in 1996. |
| Analysis: While some progress may have been made since 1978, many SESAs are still struggling with manual recovery methods. There is clearly a need for automation of collection activities. |
| Benefits of an automated recovery system | The primary benefits of an automated recovery system are:
|
| Some tasks cannot be automated | Although automated record-keeping and recovery techniques are a major part of any
recovery system, it is recognized that automated efforts alone do not comprise a
comprehensive recovery system.
Some tasks cannot be automated. Negotiating win-win solutions while working with debtors to develop alternatives for repayment is a primary objective of collection staff. The level of customer service provided can result in the recovery of overpaid UI benefits while maintaining the goodwill of the debtor. |
| Guidelines | It is recommended that SESAs:
|
| Introduction | SESAs have a variety of legacy automation systems. These systems are generally mainframe systems that have been in existence for more than a few years. SESAs invested valuable resources to develop mainframe systems that were once on the leading edge of technology. However, technology continued to move forward at an incredible rate of speed, and mainframe systems developed only a short time before became the "legacy" mainframe system of today. |
| Problems with legacy systems | Problems associated with legacy systems are:
|
| Automation constraints | Common automation constraints include:
|
| Low priority on automating recovery efforts | A low priority on automating recovery efforts was identified in the 1978 Handbook. "The recovery of overpayments has been given a back seat to fraud detection and establishment of overpayments. In addition, most SESAs have placed a low priority on automating recovery efforts as automation efforts have been directed at improving the benefit payment system. It seems fruitless to detect and establish an overpayment unless equal attention is given to recovery since an unrecovered overpayment defeats one of the purposes for which the recovery program was established." |
| Information Technology Support Center | Over the years, USDOL provided funds for SESAs to develop and implement enhancements to their automated systems. This resulted in even further customization and continued to erode potential for sharing technology among the SESAs. To overcome this, the USDOL supported the ITSC UI Web Site as a vehicle for SESAs to share best practices and lessons learned. This resource can provide detailed as well as practical information among the SESAs. |
| Guidelines | It is recommended that SESAs:
|
| Introduction | Technology today consists of applications developed for legacy mainframe systems, client server applications, and/or personal computers. |
| Examples of technology currently in use | Examples of technology currently in use:
|
| Components of an automated collection system | The automated collection system should include components with the ability to:
|
| Suggestions for maximizing investments in automation | Suggestions for maximizing investments in automation include:
|
| Guidelines |
It is recommended that SESAs:
|
| Introduction | Many SESAs are managing their collection workload through system generated reports and/or paper files. This can prevent the SESA from focusing available resources on those overpayments with the most potential for recovery. An effective case management system is critical to an effective recovery program. |
| Features of an automated case management system | Some of the features of an automated case management system include:
|
| Guidelines | It is recommended that SESAs:
|
| Introduction | Collectibility profiling can be an effective tool for determining workload prioritization and collection strategy. Most collection organizations do not have the time or resources to devote to uncollectible accounts. Collectibility profiling allows staff to quickly evaluate the potential of collection efforts and then focus efforts on debts with the greatest potential for collection. |
| Factors to consider | Profiling is used to categorize debts by potential for collectibility. Based on criteria
determined by management, debts receive points, plus or minus, for factors such as:
|
| Guidelines | It is recommended that all SESAs:
|
| Introduction | Automation guidelines are provided for SESA consideration to enhance the recovery of overpaid UI benefits. |
| Automating manual processes | It is recommended that SESAs:
|
| Legacy mainframe systems | It is recommended that SESAs:
|
| Automation today | It is recommended that SESAs:
|
| Case management systems | It is recommended that SESAs:
|
| Collectibility Profiling | It is recommended that all SESAs:
|