Sign Up Now
Get instant access to over 1 million+ study documents
OR
Already registered? click here to login
By creating your account, you agree to our terms of service, privacy policy and student honor code.
Vicro Failure at BPR and ERP
What is BPR? In a plain language, what does it mean to an organization that is underperforming?
Business Process Re-engineering (BPR) are a series of processes, systems and techniques for increasing the efficiency and profitable performance of businesses by re-architecting their workflows (Hammer, 2001). BPR for an underperforming organization is specifically designed to provide a pathway out of the inefficiencies and lack of internal communication and collaboration that over time degrade the operational and financial performance of an enterprise (Hammer, Haney, Wester, Ciccone, Gaffney, 2007).
Why can IT be one of the biggest obstacles for BPR?
Information Technologies (IT) often unnecessarily complicate the process of redefining and re-engineering processes by forcing organizations to change how they do business to just fit into an IT-supported framework (Tsai, Chen, Hwang, Hsu, 2010). IT can become more of a constraint than an enabler of organizational change quickly given its lack of agility and flexibility in supporting...
This is exactly what happened at Vicro from a systems-based standpoint. The greatest factor of the Vicro failure however was the lack of change management planning that was put into place before the systems were installed (Khosrow-Pour, 2003).
What went wrong with the ERP implementation? Note four (4) major issues.
There were many factors that contributed to the ERP implementation at Vicro failing, with the greatest being the lack of planning for change management programs to overcome resistance to change and fear of what the system would do to people's jobs and stability in the company (Khosrow-Pour, 2003). This is often the most critical success factor for any ERP system, yet the management and system integration teams completely missed this aspect of developing their implementation plan. The system integration teams did not ask for any feedback from the employees most affected by the systems being installed, virtually guaranteeing these shifts in how people did their jobs would fail over time (Khosrow-Pour, 2003). A second major…
References:
Michael Hammer. (2001). The new business agenda. Strategy & Leadership, 29(6), 42-43.
Michael Hammer, Carole J. Haney, Anders Wester, Rick Ciccone, & Paul Gaffney. (2007). The 7 Deadly Sins of Performance Measurement and How to Avoid Them. MIT Sloan Management Review, 48(3), 19.
Annals of Cases on Information Technology, Volume 5 by Mehdi Khosrow-Pour (ed), IGI Publishing © 2003
Tsai, W., Chen, S., Hwang, E., & Hsu, J.. (2010). A Study of the Impact of Business Process on the ERP System Effectiveness. International Journal of Business and Management, 5(9), 26-37.
New Payroll Application Architecture One of the most commonly automated business processes and operations in the recent past is payroll, which is also the most often used human resource solution. The increased use and automation of payroll is attributable to the need to ease and reduce the time spent in payroll processes, which is one of the first applications in the working environment. Despite the increased automation of payroll, there are
However, the company did feel it should develop its own Database infrastructure that would work with the new underlying database management system and would mesh with existing organizational skills and the selected enterprise software solution. Because the company followed a standardized implementation process, they were able to successfully reengineer their existing business structure. The objective of the System Development Life Cycle is to help organizations define what an appropriate system
system development life cycle (SDLC) approach to the development of Information Systems and/or software is provided. An explanation of SDLC is offered, with different models applied in implementing SDLC delineated. Advantages and disadvantages associated with each of the models will be identified. System Development Life Cycle According to Walsham (1993), system development life cycle (SDLC) is an approach to developing an information system or software product that is characterized by a
Evolution of System Performance: RISC, pipelining, cache memory, virtual memory Historically, improvements in computer system performance have encompassed two distinct factors: improvements in speed and also improvements in the number of applications which can be run by the system. Of course, the two are interlinked given that high levels of speed are linked to expansions of short-term memory and the ability of computers to use that memory to perform critical functions. One
From approximately 1930 until the 1980s, rectangular and functional spaces were the chief form of architecture around the world in general. The latter part of the 20th century -- the 1980s onward -- saw change once again, however (2008). For the most part, 20th century architecture, however, "focused on machine aesthetics or functionality and failed to incorporate any ornamental accents in the structure" (2008). The designs were, for the
Third myth is "the industry is going "plug and play" or "do-it-yourself" and does not require specific integration efforts, given greater systems diversity but "although experiments are underway to use cable modems and set-top controllers for more than just entertainment delivery, the current generation of devices does not pretend to be a true systems integration controller." Project managers and architecture designers are still necessary for electrical contractors to fully integrate