Helping you to enhance your organisation's performance by helping you create a development path for your business or project. "Turning Acorns into Oaks."
System Selection - Platt & Hill Limited
Platt & Hill Limited, an independent company, specialising in the manufacture of products primarily for the furniture trade, commissioned us to select a replacement for their existing ERP system.More Info
IT Strategy & Systems Selection - Ferranti Technologies Limited
Ferranti Technologies Limited, a world-class supplier of electronic, electrical and electro-mechanical equipment, commissioned us to undertake an IT Strategy Study, followed by a Systems Selection.More Info
IT Strategy - a Stately Home
This 18th Century stately home is now run by a Trust. We were commissioned to produce an IT Strategy to enable evolution from a series of separate systems to an integrated suite of systems.More Info
Selection of Software Developer - Dyson Insulations Limited
Dyson Insulations Limited, which specialises in cavity wall and roof insulation, and home heating systems, commissioned us to select a software developer to develop new applications systems.More Info
There are many problems, which can occur during the implementation of a system. This area will, gradually expand, but, initially, I would draw your attention to a few potential problem areas:
* small requirements which can be met by simple report / enquiry procedures are treated as simple add-ons which can be provided after the system is live,
* larger requirements which are not needed immediately. Unless they drastically affect the a significant part of the system, hold them back until the system is fully operational. Then set up a separate project to plan and implement these changes, with adequate testing to ensure that they have no significant impact on the rest of the system,
* larger requirements which are required immediately, or which, while required later, have significant effect on the system. STOP and think. You need to analyse where the changes will have an impact. The plan will need to be revised to incorporate modifications, changes to programming, and configuration and will, probably, involve some re-testing. Only when you have identified the impact of the changes can you continue with those parts that are not affected, and start work on the areas which are affected. The total impact of the changes should be determined, and the affect on resources, including cost and timescale, should be reported back to the steering committee, who may decide that the change is not worth the effort;
user commitment / acceptance. A system is less likely to work successfully if the users resent it, or do not believe that it will help them. Accordingly, it is advisable to plan, from an early stage, to involve key users in major decisions, and keep the ultimate users well informed about what is happening, and any positive impact on their jobs, especially any current problems that the system will remove. This helps to create an atmosphere of interest and acceptance.
We are happy to expand this page. Please contact us with problems that you have encountered and, if we feel that they have general relevance, we will be happy to incorporate them.