Introduction To Business Software Implementation For Modern Organizations
Tuesday, June 21st, 2011Because business software is frequently changed or entirely replaced, it is important to develop processes to control business software implementation. The life cycle of business software includes many phases. This article will be focused on the installation phase of the implementation process. The software may run in a number of different places. The focus here will be on installation of business software that runs on workstations.
It is best to begin the installation phase by making plans for the installation. Everyone who may be affected by the install should be involved in this. Otherwise, something important may be forgotten, or someone may not know of an activity they are responsible for. The plan should include a schedule indicating what is done by whom when.
The planning process should determine the overall installation strategy. Is it going to be a big bang type install where all workstations are converted at once? Is it going to be a phased install, where the software roll out takes places in a series of phases or stages over time? Or is it only going into a few workstations as a pilot install? What is the backout or recovery process if there are problems?
The new software may require hardware upgrades or even network modifications. Anything from more memory to totally new workstations might be called for. This has to be finished before beginning the software installation.
The install, consisting of the following steps, begins after all the steps it depends on are completed. What we call a phased install can also be thought of as a series of installs, each on a different subset of the workstations. Thus, these steps will occur for each of the phases for business strategy consulting.
How do we know where to install the software? There needs to be a list of workstations. Small organizations can build this list during the planning phase, but larger organizations should do it as late as possible since the population of candidate workstations tends to change often. For phased installs we need a list for each phase. Hopefully this will be an automated task if there are a lot of workstations.
Pushing the changes to the workstations comes next. Unless this creates a network overload it can be done anytime, even with the workstation in use. Larger organizations should automate this.
The actual workstation install usually needs to be done when the workstation is not in use. Hopefully it can be done sometime when the department is not operating. If not, then some sort of careful control will be needed. It may be necessary to give the users an extra break while their workstations are updated.
Once the changes have been made, there will usually be some sort of post test or certification. This is usually just done on a few workstations. However, if this is a high risk install, management may determine that all of the changed workstations should be tested.
Those are the major components of business software implementation. It is not always exactly like this. Organizations always have some unique characteristics that must be accommodated. Unless an install is routine and dead simple, there should always be a plan. Not planning is a great way to have problems.