From the point of signing contracts we will assign you with a Project Manager to oversee the complete process of implementation, migration through to “Go Live”.
The Project Manager is responsible for briefing and allocating the training resources and for the monitoring of the implementation in conjunction with the dedicated support co-ordinator.
Your Project Manager will provide advice on code structures, operational procedures, processing cycles and general advice to ensure the user is obtaining the required management information from the system and that the system dovetails into the company's operating structure through to successful live running.
A Pre Installation meeting or a series of meetings are held with the Project Manager prior to system delivery. The purpose of this meeting is to study and define the particular requirements of the user. The topics covered include:
- To review the Company structure and requirements
- To meet personnel responsible for running the system and identify Key staff
- To confirm the volume of transactions being processed daily, weekly and monthly
- To review user documentation and ensure compatibility
- To review user's current filing systems to ensure correct use of field references
-
To determine required coding structures for the following modules:
- Nominal Ledger
- Contract Ledger
- Purchase Ledger
- Sales Ledger
- Subcontractors Ledger
- Purchase Ordering Processing
- Fixed Assets
- Any additional databases
- To assess user accounting routines and reporting timetables
- To determine user implementation priorities and targets
- To determine site preparation requirements
A 'test' company is installed on the system so that training can initially take place without affecting the 'live' company being implemented. This will also allow any testing to be carried out on the operational aspects of the system prior to finalising coding structures and procedures.
As MCA is a well proven package parallel running is not necessary, test batches are sufficient to confirm the correct setting of coding, parameters and user understanding. These test batches should be constructed by the user if required.