Register now or log in to join your professional community.
Patches should be applied at each instalation of ERP as each has a seperate configuration. Thus, patch requirement for one installation will be different from the other.
To facilitate the adoption of the upgrade by end users, project managers should provide new feature training at multiple points during the project lifecycle and follow it up with reinforcement opportunities, such as:
Also, give the user community rewards for their heavy participation in the upgrade project. Try to address pain points and present users with new features and functions that make them more efficient or provide more beneficial functionality.
ERP Software development is one of the most challenging areas of Software Development you may pick, but it’s also one of the most interesting ones in my eyes. The development of ERP Software demands a large bandwidth of various disciplines on functional and technical side. But no fear about that, there are plenty possibilities nowadays to travel that path, it’s only a matter of continuous and lifelong learning.
I started with the development of Open Source ERP in 2004. In this time I’ve seen and learned a lot about ERP, but I would never say that I’m finished with mastering it. The requirements nearly always differ more or less among user companies and the demand for the use of new technologies has been raising raising fast in the last years. This makes ERP Software development to a very interesting and exciting topic.
Let’s just take a look at the Open Source Project metasfresh ERP as an example and get a rough overview of some possibilities to collaborate and learn in existing teams:
A typical life cycle of an ERP System is as shown below
For patches and upgrade it should be done based on Business Requirement followed by thorough impact analysis once a patch is being applied or upgrade is being done.
ERP life cycle
1- Selection of packages that fits your business environment. A proper study and research should be done before the selection.
2- GAP analysis is performed to analyze the current situation of the organization and its future position as needed.
3- Re-engineering is needed to make the implementation process involves many changes and alterations. The job responsibilities of employees and the number of employees can be altered as well.
4- Project Planning: Resources should be allocated and the team members have to be selected.
5- Parameter settings, workflow setup and producing a proto type.
6- Training of employees starts with the implementation process in the life cycle of the ERP implementation. Employees of getting used to the new system in order to run the system smoothly later. Get the time at this stage to learn the software and its features and become self-sufficient in order to be able to operate later, when consultants and suppliers to end and go.
7- Testing is carried out so that the errors can be found and resolved before the actual application process.
8- Data Conversion also migration for the legacy system and Catch up process in case of existing a legacy system.
9- Maintenance is carried out in the post-implementation life cycle of ERP implementation phase. The problems are identified and employees learn how to deal with it. this phase should be over within six months to one year and the system should start stabilizing.
2,3,4 above start after 1 then 5,6,7,8,take place while 9 will be after go-live.
Patches can be with month frequency while Updates can be per quarter and Upgrades many be required after years.
ERP Roll out
Optimization
Maintenance
Extending Values
Decaying Performance
Reimplementation
Patches should be applied at each instalation of ERP as each has a seperate configuration. Thus, patch requirement for one installation will be different from the other
Patches are aplied to existing dynamics ax application whenever microsoft releases pathes which fix the bug in the standard AX functionality. and upgradtion is depends on the customer requirement whether they are update with the latest technology like D365 cloud based ERP system.
Typical Life Cycle of an ERP is same as product life cycle. It start with installation and implementation, improved with updates, patches and upgrades and ends with new version / technology. For example in MS Dynamics, MS introduces AX 2009, AX 2009 shifted to AX 2012 and AX 2012 Shifted to D365.
Patches and updates are the part of contiuous development and learning experience on the product during the whole life cycle of the ERP porduct. Patches can be applied to the product depending upon the particular functionality is in use where it is needed and as instructed by the ERP product owner. Updates has to be applied regularly as an when makes available by the ERP product owner.
Upgrades are the developmental changes which as per the Roadmap and changing need of the customer the ERP Product owner carrying out in the product to stabilize it in the market. This upgrades help to brought in additional features and smooth performance of the product. Applying regular upgrades leads to smooth shifting form one version to another upgraded version of the product with seamless experience.
ERP are installed once , updation depends as per business needs can be customized.
As per ERP system patches , bundles and upgrades are done quarterly or any period again based on business needs.
Every 6 Months and Whenever New Regulations of country are Comes in to Effect
typical life cycle - mainly strategic planing concept and implementation for stabilization.
frequent update is based on your requirement of the business.
