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
Click Here to Read More
Comments
Post a Comment