Planning & Implementation

As the saying goes, 'If you don't plan to succeed, your planning to fail' Planning an implementation is important, it's not just setting a date for an engineer to install the software, but involves decisions about who has access to which parts of the system, role responsibilities, user rights, reporting structures, resource allocations, setting timetables and allowing for the unforeseen by incorporating an element of contingency planning.

Companies and organisations do not change their systems every week or even every 18 months, in fact it's normally only after 3 to 5 years of ineffective usage of an incumbent system, that the defects become unbearable and the search for a replacement system begins.

We on the other hand, do change systems on a weekly basis and can add enormous value to the planning process by incorporating our experience and expertise into the mix.

The final product of the planning process is normally a written document in which timetables are laid out, personnel roles defined, resources allocated and areas of responsibility are made clear.

Implementation
System implementation is the point at which everything comes together. Working from our agreed planning document, the software is installed, configuration is started and other elements such as data transfer or integration are addressed.

Once the system has been installed and configured for use, many clients like to run them in a test mode for a period of time, to ensure that all is operating as expected. This can be a useful exercise, as it can also give system users some familiarity time prior to the commencement of training.