ERPs usually require frequesnt application of vendor software patches in order to address minor security/functionality issues and bugs. Not applying these patches can result in the vendor withdrawing support for the ERP. This process occurs in Operation stage. Moreover larger updates, requiring mini ERP implementation projects, can occur as frequently as every 3 years. What are the implications for organisations adopting an ERP? Do you think the text captured the complexity of this? Why/Why not?
ERPs require frequent application of vendor software patches in order to adress minor issues and bugs, this occurs in the Operation/post go live stage because thats when the system is monitored for performance and maintained to ensure that it still works properly. By not having venodrs frequently monitoring and patching the system, the system can become to overwhelmed by issues and bugs that the vendor no longer wants to support the system. By frequently applying these small patches, larger updates which usually occur every three years will not be as significant. These are implications that the organisation incur when adopting an ERP system, it is something hat needs constant maintence and de-bugging. While this is a constant cost to the organisation, the ERP system ultimatley benefits the business if looked after apprpriately.The other cost implication for organisations adopting, is the training of staff, not a large number of staff are going to be tech-savy and be able to immediatly grasp the system, this will cause an intial lack in productivity.
The text provided, when first read, does not appear to be a complex task. For some one with limited knowledge about ERP systems and IT as a whole, that comes across as a simple task of applying patches where deemed neccesary and testing to ensure it now works theyw ay it should. From reading up on how to answer this question, it has become evident that software patches are complex, costly, and can hold back an organisations productivity.