There are differences between the ERP software’s functionality and the unique requirements of the end users as well as business requirements.
Hence, customisation is needed to allow the software to align with the organization’s existing processes, enabling not only a smooth shift from the old processes, but also a better fit between the ERP system and the end users.
Strong Process knowledge The first and foremost factor in the customisation decision is the knowledge of the existing systems and processes. If the ERP solution seekers are well versed with their existing systems and understand what exactly is needed, half the bridge is crossed.
User Friendliness Trade-off Most companies want the ERP system to make life of an employee as easy as possible so that he can accomplish more in less time. But a line needs to be drawn in the real world as increasing customisation demands may sabotage the implementation success itself. Also a balance between ERP implementation cost and benefits needs to be charted.
What is the Purpose of the ERP Customisation? :
- Identify key business problems that the customisations should solve.
- Departmental, functional or process related Problems
- Isolate issues that have the greatest impact on:
- Operational costs
- Performance and growth goals
- Non-economic factors
- Common issues:
- Lack of custom reporting
- Workflow customisation
- User-interface design
- Specific department processes (manufacturing, inventory, finance, etc.)
What is the Business Value of the Customisation?
- Identify the benefits gained; from operational efficiencies to the overall impact on stakeholders and the value chain.
- Look beyond economic gains in day to day operations. ERP customisations must contribute to overall satisfaction and buy-in of employees, customers, shareholders, vendors, etc.
What are the Adverse Effects of Customisation?
- Identify issues that can occur before and after a customisation
- I.E – Interference with other key functions of the ERP system – Upgradability of customisations – ERP version compatibility – Implementation timelines – Cost vs. Benefit
How will the Customisation be Structured and Implemented?
- Synconics have general understanding of the development and run-time environment used to create the customisation.
- Synconics will develop a schedule that allows time for implementation to minimize the effects it may have on business operations.
What is required once the Customisation has been implemented?
- Support – Implementation partner support contact
- Servicing – Service contract
- Training – Training sessions
- Detailed log of the implementation from start to finish
- Proper team structure that consists basically of a chief architecture, programmers, system analysts, QA/QC personnel’s, etc., to well manage the different aspects of the software development and implementation.
- Proper versioning tool to monitor the change requests and merge the program version files, to ensure the version is monitored well.