Systems Implementation Options

Direct cutover: the old system is simply dropped and the new one started. If at all possible, it is best to avoid this technique, because it is the most dangerous to data. If anything goes wrong with the new system, you run the risk of losing valuable information because the old system is not available.

Parallel conversion entails running both systems simultaneously, which is safe but can become expensive and time consuming. In many ways, the safest choice is to use parallel implementation. In this case, the new system is introduced alongside the old one. Both systems are operated at the same time until you determine that the new system is acceptable. The main drawback to this method is that it can be expensive because data has to be entered twice. In addition, if users are nervous about the new system, they might avoid the

Pilot introductions, introducing in one or a few locations first. With multiple stores or business units, pilot introductions of phased implementations are common. For pilot testing, designers can bring extra workers, managers, and systems designers to one location and work out the problems with the system. Once the system is running well, it can be implemented at other locations.

Phased implementation. Projects can also be phased in by department or system modules. You might install a set of computer cash registers first. When they work correctly, you can connect them to a central computer and produce daily reports. Next, you can move on to annual summaries and payroll. Eventually the

entire system will be installed.