Data Clean-up Auto Mail (DCAM)
Original Publication Date: 2001-Feb-28
Included in the Prior Art Database: 2001-Feb-28
Data Clean-up Auto Mail (DCAM)
DCAM is tool as well as a methodology developed by Motorola to manage massive data clean-up problems. The objective of this tool is to promote problem ownership and improve the productivity by 10 folds. The tool automatically detects the problems (defects) and identifies owners for every single problem. It sends owners personalized email, summarizes the defects and provides instruction for the fixes.
This "push" technology can be applied to various business tasks, e.g. customer service, project management, e-business and workflow.
Motorola Semiconductors Product Sector has over 150 thousands components and hundreds data elements. Each data element has its own set of business rules, which define its requirements to various down-stream business processes and tools. Some of the basic rules are enforced by the system at the first time it was entered. However, due to the fact that not all systems can be integrated or developed at the same time of the business rules, many of the business rules are not followed. Meanwhile, most new systems, e.g. Enterprise Resource Planning (ERP), require clean data before it can be fully functional. There is an urgency to clean the data quickly and accurately. If the rules/defects are simple and require not much human justification, the fixes can be done quickly with the help of data cleansing tools. In dealing with rules/defects require human justification, official review/approval processes must be followed, which involve massive activities in finding the owners, training and follow-up with the processes. In view of the amount of resource investment required, complexity or the problems and changing requirements, usually, these efforts are not sustainable and manageable.
DCAM contains 3 basic automated modules: Defect Detection, Contact List and Logistic.
Automated Defect Detection
Based on the business rules, defects can be detected automated by a set of programs. Each defect should be assigned to one or many business roles (like product engineers, planners, product managers, etc.). Defects are detected and mapped to the most detail source items (like Component ID, Customer Code, etc.).
For example, Product Engineer owns defect 378 467 and Salesman owns defect 356. Part 1 has defect 378 and 356 and part 2 has defect 378 and 467.
Automated Contact List
Responsibilities are entered and defined in by roles and higher level groupings for individual employee (like PE/Product Family, Sales/Regional Office, etc.). Once the higher level responsibility info are captured, they are populated to most detail source items automatically based on the groupings information found in the legacy systems, which may change every day.
For a simple example, part 1 to 100 belong to product family ABC and it was owned by Product Engineer A, A signs up for the role of Product Engineer and product family ABC. The tool will populate A as Product Engineer for part 1 to 100. When part 101 was ad...