It460 Final Project-Legacy Data

Legacy Data

The new system might have to interface with one or more legacy systems, which are older systems that typically run on mainframe computers. When considering physical design, we must determine how the new application will communicate with existing legacy systems. Interfacing a new system with a legacy system involves analysis of data formats and compatibility.(Shelly & Rosenblatt, 2013) The TIMS system will eventually eliminate the legacy system so the legacy data will need to be converted to the TIMS system architecture. The new vendor doesn’t want the old data and any of its problems cluttering up the new system.

There are several reason why decommissioning a legacy system is needed. The costs of maintaining old hardware and software can really add up in a hurry from a few thousand dollars a monthly to several million over the course of a year. Decommissioning is key, but the data must be retained in an environment less costly than the retiring applications. Audits, such as Federal EEOE, RAC, and others require quick and complete access to records going back as many as 10 years. Inaccessible data in formats that don’t allow robust querying will leave SCR with lost revenues and fines for non-compliance. Depending on the nature of the records, the old data will still need to be part of the dynamics of the workflow. For example student accounts will require billing several years after the last date of training. End Users need real time access to important legacy records through an easy-to-use interface.

The importance of managing legacy data during a system conversion can’t be overemphasized. While the legacy system may be a burden, the legacy data is money in the bank. The best solution will retire the old system while retaining the data. Effectively managing this important transition to new the new TIMS will keep the cash flowing, maintain compliance, minimize the cost of transition and get you closer to the streamlined operations that come...