Phase 6: Implementation

1.12 Phase 6: Implementation

Implementation consists of installing the hardware, software and data in the new working environment. A system can be implemented after it has been tested. It is also known as system conversion.

System conversion can be performed in any of the following:

·         Parallel Conversion: A type of conversion in which both new and old systems operate together for a period together for a period of time is called parallel conversion. The results of both systems are compared. It is the safest type of conversion. The old system can carry the load until all problems with the new system are solved. This conversion is also the most expensive because the work is duplicated.

·         Pilot Conversion: In this conversion, one part of the organization uses the new system while the rest of the organization continues to run the old system. When the pilot group is satisfied with new system, the rest of the organization can start using it.

·         Phased Conversion: A type of conversion in which individual components of the new system are implemented one by one is called phased conversion.

·         Direct Conversion: In this type of implementation, the old system is directly replaced by the new system. A direct conversion is the most risky but may be necessary in some situations when time is very short. It is also called crash conversion.

1.12.1 Choosing an Implementation Strategy

Every organization must choose a strategy that is suited to its needs. The strategy for implementation depends on the nature of the application, the user profile of the organization and many other factors as follows:

·         Nature and size of application: If the application is modular and each module affects only particular category of users then phased implementation is a better choice.

Applications that are being introduced for the first time re better suited for direct cut-over implementation.

·         Type of organization: It includes organization size, culture and end user profiles. Some organizations that are young, small and in the businesses like banking, financial services are more adaptable to change and new system of working. The organizations that are larger and old and have experienced years of functioning with manual systems are more difficult to change.

·         Existence of an internal EDP department: EDP staff can convince their colleagues about the new system. If EDP staff has not been consulted on the new system, it may create many problems. Internal EDP staff can help users to user the new system effectively. It can reduce the changeover time.

·         Number of personnel involved in usage of software: If the number is large then a ‘phase in’ strategy can be used.

·         Data volumes: if the data volume is large, a safe strategy should be adopted.

·         Location spread of the application: A widespread organization needs a phase-by-phase implementation strategy.

·         Availability of certain tools: The tools available in software ensure its security, safety and integrity. If such tools are available, the old system can be replaced by the new system sooner.

·         Manpower availability: If a system has to be installed in different locations at the same time, more implementation teams are needed. If many teams are not available, the system should not be implemented simultaneously.

·         Criticality of the application: More critical applications need more safety. A parallel backup system is needed in this situation.