This is the part of the sub-web covering the Implementation of Applications Software. To go to the overview of this sub-web, please click Overview. To go to the web-site home page, please click Home.

Any major packaged system, whether Teir 1 ERP, such as SAP or Oracle, Teir 2 ERP, such as Axapta, Syte-Line, or Syspro, or CRM, such as Siebel, offer a wide range of features, from which the customer can select those most appropriate to their business. As part of the process of implementation, the supplier will ‘customise’ each module (or granule, or whatever they call it). Usually, somebody from the supplier will need to get involved with users to discuss the options, agree on which are appropriate, and then review how the system will be used, so that internal procedures can be amended. In addition, training and staffing needs should be identified.

We would, normally, recommend that a ‘user group’ is set up, of key users (often the number 2 person in a department), who will devote much, or all, of their time, to agreeing the configuration of the system. These people may be the same as those on the user committee, mentioned in Project Management. Provided that every functional area of the organisation is represented, then problems, caused by the differing needs of different functions, should be reduced. As the system will affect some areas of the organisation quite significantly, many organisations take the opportunity to examine how they undertake the work in those areas and determine if there are better ways of doing them. This process can extend to full Business Process Re-Engineering, and will be discussed further in the fuller expansion of this part of this site.

When the system has been configured, any modifications will need testing, and users will need training.