What is typical implementation cycle for an ERP solution?
The ERP implementation cycle varies based on various factor, client availability, availability of data as required, modules and scope of work.
This article aims to give you fair idea about the overall flow of the implementation, different vendor uses different terminology while addressing same document and might club two phases in one.
Requirement Study
Functional Requirement Study (FRS) or Business Requirement Study (BRS) there are various names for this process. Briefly, the requirements are listed down based on the meeting with ERP implementation stakeholders. Usually there is a Module Head and Key users identified to make the information flow smooth.
Outcome
A detailed document with the entire business requirement/ business flow is recorded.
Requirement Analysis
Functional Requirement Documentation (FRD) for some it is separate document and many do changes in FRS document in this phase. The requirement listed in the first phase in analyzed to find the GAP. It is also referred as GAP analysis phase. The user requirements are mapped against the ERP solutions and any exception are highlighted.
The documentation should clearly specify the listed user requirement will be met in existing solution or customization is requirement, also can provide work around in-case customization is not required. It could be possible some user requirement need not be possible even after customization due to application architecture – such things need to be highlighted.
Outcome
GAP analysis document with signed acceptance of requirement.
Development
In case any customization required, the development efforts are estimated and cost is approved by customer prior development.
Outcome
Functional Design Document (FDD) or proto type of functionality flow is prepared for user understanding and approval
Deployment
It has three steps involved
- Installation of the application
- Data Migration
- Training
The software is hosted as per agreement in customer server/ cloud – installation of the application in mentioned computer. Once the application is installed, it must have user historic data, opening balance migrated (in some case transaction also migrated, based on scope). Training – The customer users must be trained on how to use the application.
Customer Acceptance
UAT (User Acceptance Testing) – The user needs to certify that the application is in working condition and as per his requirement (agreed scope)
Go Live
After UAT, the customer will set a date to go live with using the system and discontinue using other system, if applicable
Post Go-Live
After go-live the user might need support and hand holding for some time this is provided by vendor based on agreed scope and cost.
Most vendors charge a fraction of ERP Cost as AMC (Annual Maintenance Contract) this will include cost to fix bug or assist user. For Pricing Inquiry and estimation parameters contact our marketing department of BrainSphere IT Solutions.