ERP Failure Of Hershey Foods Corporation - A Brief Description

Question: Describe about the ERP Failure of Hershey Foods Corporation? Answer: Executive Summary Numerous organizations are actualizing Enterprise Resource Planning (ERP) frameworks with an end goal to mechanize and incorporate data and methods. While some ERP tasks are fruitful, most executions stay hazardous. Activities take longer and cost more than anticipated, neglect to yield foreseen results, or in most pessimistic scenario situations, are surrendered totally. While specialized issues frequently emerge, ERP frameworks face issues because of numerous complex and collaborating hierarchical and social elements (Bishnoi, 2011). This paper shows Soft Systems Methodology as a conceivable support in recognizing the quality, effect, and boundaries to ERP. SSM is a "delicate" operations examination device intended to break down and model complex frameworks that coordinate innovation with human and authoritative frameworks. Enterprise Resource Planning also termed as ERP is one of the major implementation of the major organization that is dealt in this article. Hershey Food Corporation is one of the major organizations that implemented the ERP procedure for the betterment and fluency in their business techniques to bring fruitful results (Hershey Foods Corp., 2004). Undertaking Resource Planning that is the enterprise resource planning (ERP) frameworks are programming applications that incorporate arranging techniques for numerous capacities inside a business venture. But, Hershey faced a huge knock over their implementation of ERP which prolifically led in the failure of their desired ERP. This article gives a wide ranged and detailed explanation about the major reasons related to the failure of the ERP of the Hershey Food Corporation. The article prolifically states the pros and cons that affected the Hershey Food Corporation and what actually went wrong with the implementation of the ERP and how the SSM model and it techniques were applied to demonstrate the critical analysis. Introduction ERP frameworks are exhaustive applications that help and interface all parts of an association's business forms. At the point when talking about business forms, one method such offices as Accounting, Human Resources, Marketing, Purchasing, Manufacturing, and so forth. ERP frameworks showed up in the 1990s as an approach to give openness, adaptability and consistency over all the significant business capacities, dissimilar to its forerunners. Associations that make proper utilization ERP frameworks have a superior shot of managing game changer in a regularly changing business environment. The development of ERP began amid the early 1990s following quite a while of utilizing storehouse based data frameworks inside business associations (Corporation, 2015). ERP is a product based framework that is in charge of making data, reporting and capacities generally accessible and midway placed inside business associations. What's more, the part keeps on explaining that ERP usage is not as simple as selecting and introducing bundled programming. The opening Hershey case demonstrates how a business went about the methodology the wrong way, and after that redressed their missteps the second time around. Hershey ran live with their ERP execution by means of the "Enormous detonation" system. Their starting issue was attempting to execute excessively, excessively quick. The case gives a decent sample of what to stay away from. In the year 1996, Hershey's embarked to update its interwoven of legacy IT frameworks into a coordinated ERP environment. It picked SAP's R/3 ERP programming, Manugistic's store network administration (SCM) programming and Seibel's client relationship administration (CRM) programming. Notwithstanding a prescribed usage time of 48 months, Hershey's requested a 30-month turnaround so it could reveal the frameworks before Y2K. In view of these booking requests, cutover was made arrangements for July of 1999. This run live planning agreed with Hershey's busiest periods the time amid which it would get the main part of its Halloween and Christmas requests. To meet the forceful planning requests, Hershey's usage group needed to take a route that is excessively expedient on basic frameworks testing stages. At the point when the frameworks went live in July of 1999, unforeseen issues kept requests from moving through the frameworks (Chen, Law and Yang, 2009). Thus, Hershey's was unequipped for preparing $100 million value of Kiss and Jolly Rancher requests, despite the fact that it had the vast majority of the stock. With a specific end goal to animate the execution process, Hershey picked Big Bang implementation, where a few modules were actualized all the while. Some of them couldn't be tried appropriately because of absence of time. This prompted a few issues identified with request administration and fulfillment, and requests from numerous retailers and merchants couldn't be fulfilled, even however Hershey had the completed item supplied n its distribution centers. The unfriendly influences of fizzled ERP execution were immediate, with a critical drop in the incomes or second from last quarter of 1999. Yearly incomes or 1999 were US$ 150 million less contrasted with those in 1998, a drop of 12%. Background information By January 1999, a portion of the modules like SAP budgetary, materials administration, obtaining, and warehousing had been executed. Notwithstanding, different modules like the discriminating request preparing and charging frameworks modules from SAP, the evaluating and advancements bundle from Siebel and arranging and planning modules from Manugistics were behind timetable. In spite of the fact that Hershey wanted to switch over to the new frameworks amid April 1999, which was a lean season for confectionery deals, these modules were included just in July 1999 - three months behind timetable (Hershey Foods Corp., 2005). Around then, Hershey was under weight and was not in a position to augment the usage plan, as the Y2K issue was posing a potential threat. That was the time that requests from retailers for Halloween began pouring in Hershey then chose a Big Bang way to ERP execution. In this approach, the Software was to be executed at one go, rather than a staged methodology of ex ecuting one module at once, testing it, and after that taking up the following module. The staged methodology permitted an organization to discover and right bugs before proceeding onward to the following stage. Then again, Hershey was of the perspective that the Big Bang approach would empower it to meet all its Halloween requests. At first, the take off seemed, by all accounts, to be smooth. In any case gradually, issues relating to request satisfaction, Processing and transportation began to emerge. A few transfers were sent behind calendar, and even among those, few conveyances were deficient. Nonetheless, it was past the point of no return for Hershey to react to this issue. In July 1999, when Hershey decided on the Big Bang way to ERP execution, it had Supplies for around eight days - this was higher than ordinary (Hirata, 2009). Hershey kept up more supplies keeping in mind the end goal to address anything of issues that may happen amid the execution. Anyhow three Weeks after the execution of the new framework it was clear that Hershey would not have the capacity to meet its due dates as the shipments were postponed .As against the ordinary five days, that it took to convey the items, Hershey approached wholesalers for around twelve days to convey their requests. In any case, Hershey missed that due date as well. By August 1999, the organization was 15 days behind Schedule in satisfying requests. A few of Hershey's wholesalers who had requested the items couldn't supply them to the retailers in time, and henceforth lost their validity in the business. The retailers whined that the issues within customary supplies from Hershey had been persevering since summer and they were taking a gander at different options. Hershey likewise lost valuable rack space for which there was high rivalry in the business sector (Khisty et al., 2012). Clients started changing to results of contenders like Nestl and Mars. Retailers opined that fleeting deals as well as long haul offers of Hershey excessively would likewise be influenced. This perplexity astonished business onlookers a d Hershey on its part did not uncover the points of interest of what happened. Later on, examiners distinguished that the issue had happened because of a few casual structures inside the organization. SAP R/3 ERP Implementation obliged all the information relating to the area of the stock and its points of interest. Hershey used to guarantee crest season inflow of items from its assembling units by setting the items wherever the space was accessible; this was not generally the appropriation focus or the stockroom. The interim offices where items were put away were not distinguished as capacity focuses the extent that SAP R/3 ERP programming was concerned, thus numerous such stockpiling areas were just not considered. To satisfy clients' requests, the SAP at first checked the stock accessible at each of the areas said in Hershey's official records. Be that as it may, the items supplied in casual areas were not checked, which SAP R/3 prod uct did not consider. The principle purpose behind the crevice was the absence of coordination between the specialized faculty executing the framework and the individuals included in operations, who did not redesign that Implementing t he programming arrangement (Kiran, 2012). With a few requests staying unfulfilled, Hershey's inability to actualize the ERP programming on time costed the organization US$ 150 million in deals. Benefits for the second from last quarter 1999 dropped by 19% and deals declined by 12%.In its 1999 yearly report, Hershey expressed," The decrease in shipments came about principally from challenges in place satisfaction (client administration, warehousing, and transportation) experienced since the start-up of another coordinated data System and new business procedures amid the second from last quarter of 1999." The execution of the ERP for Hershey was plagued with challenges because of a number of disappointments: Venture administration issues, not broken programming: The organization did not utilize the legitimate assets do guarantee a decent dispatch. This particularly incorporates the disappointments of top administration. Enormous detonation versus staged usage: With their second endeavor Hershey was ready to plan all the more completely keeping in mind the end goal to lessen redundancies, legitimately prepare and investigate on a sensible premise. There were a few key issues Hershey confronted amid the usage of their new Framework: Absence of upper level administration the unlucky deficiency of IT official authority before the landing of George Davis. Lack of a viewpoint lower level directors were settling on choices taking into account their singular business needs as opposed to tending to the needs of the organization overall. Big blast approach: Three new frameworks were executed all the while, as opposed to utilizing a staged execution. Bad timing: Frameworks were actualized amid Halloween, Hershey's top deals season. Improper construction modeling and absence of preparing information section into SAP was troublesome and workers were not appropriate Analysis According to the above case study of Hershey Foods Corporation, the ERP failure is analyzing by the help of the Soft System Methodology (SSM) technique. In the Soft System Methodology (SSM) technique the giving problem is solving by the help of its parameters. In other words, the Soft System Methodology (SSM) technique is constructed by the help of some parameters, which solving the ERP failure of the Hershey Foods Corporation (Meissonier, Houz and Lapointe, 2014). The ERP failure implementation is discussed by the help of analyze the Soft System Methodology (SSM) technique. The parameters of Soft System Methodology (SSM) technique is also known as the implementation step of the Soft System Methodology (SSM) technique. There are total seven steps or parameters which help to evaluate the ERP failure of the Hershey Foods Corporation. The seven step of the Soft System Methodology (SSM) technique is following in below. Problem location unstructured Problem location expressed Root definition Theoretical modeling of the system Comparison of theoretical modeling Possibility and preferred changes in system Accomplishment to improving the system By the help of the above parameters or steps, Soft System Methodology (SSM) system is easily measure and analyzes ERP failure of Hershey Foods Corporation. In the Soft System Methodology (SSM) technique some steps or parameters are related to the real world system or in other words problem location unstructured, problem location expressed comparison of theoretical system, possibility and preferred changes in system as well as accomplishment to improving the system are directly correlated to the ERP failure of the Hershey Foods Corporation (Nah, 2002). In the other hand the steps or parameters are also correlated to system thinking like, the root definition and theoretical model is in the part of the system thinking. By the help of the above steps or parameters the of the Soft System Methodology (SSM) technique, the ERP failure of Hersey Foods Corporation is shown in below. Figure: The Soft System Methodology (SSM) In the above diagram of the Soft System Methodology (SSM) technique, all the parameters are correlated with each other (Por, 2008). By the help of the above discussed parameters or steps of the Soft System Methodology (SSM) technique the ERP failure of the Hershey Foods Corporation are easily analysis and evaluate. By the help of the steps, problem location unstructured and problem location expressed is the combination step to finding the problem in the business model or system. In the Soft System Methodology (SSM) technique the problem location unstructured and problem location expressed is also known as rich picture, which is identifying the problems in the system or business model and also draw an abstract outline or diagram for the system or business model. The identification of the problem in the provided system or Hershey Foods Corporation is finding by the help of its employees and members. For an organization considering ERP, the first step or parameter is include first characterizing at an abnormal state the association and the frameworks and procedures as of now set up to backing to it. The current execution of the frameworks would then be assessed. On the off chance that the execution is not palatable, the shortcomings or deficiencies of the frameworks are recognized. This stage can be essential in that a case for ERP must be manufactured. On the off chance that potential clients of the framework don't feel the need to change, safety may develop and contribution of clients is frequently important for purchase in (Ravasan and Mansouri, 2014). It is imperative to figure it out that the examiners, supervisors, and clients are all piece of the circumstance as well as it is also as dynamic members or as somebody ready to apply control over the circumstance and will subsequently bring their perspectives and assessments into the investigation. The techniques and data frame works set up apply a real impact in the accomplishment of new frameworks and must be distinguished in this step. In the other step (step 3) of Soft System Methodology (SSM) technique, root definition of a framework to address the topics grew in Step 2 is produced. Numerous of the configuration necessities distinguished in Step 2 starts to distinguish components of the root definition. This stage refines also finishes the recognizable proof of the components. The root definition is communicated as a change handle that takes some data, changes or changes the substance, and produces another manifestation of the element as a yield. To developing the root definition some various elements are helps or CATWOE is used. The element of CATWOE is shown in below. Customer Actor Transformation Weltanschauung (World view) Owners Environment By the help of the step 3 or root definition, the system is shown whats the situation of the system or business model and the step 4 (theoretical modeling), the system define how to solve it. The theoretical model recognizes what the framework or business model needs to perform. It distinguishes the exercises in the framework and their connections. These exercises, ordinarily communicated utilizing verbs, depict what needs to happen for the framework to meet the objectives and points characterized in the root definition. Frequently these reasonable models are communicated as models in a pictorial or flowchart structure. The majority of the components of the CATWOE mental helper must be fused inside the theoretical model for it to be finished. In the next step of the Soft System Methodology (SSM) or step 5 (Comparison of theoretical modeling), theoretical model is contrasted and this present framework to highlight conceivable ranges where changes are important (Hardman and Paucar-Caceres, 2010). This calculated model will distinguish where issues or insufficiencies exist between what is happening or the rich picture and what is attractive (the 'root definition') as characterized by the models. The methodology and different models grew in Step 4 are useful here. In a perfect circumstance, the circumstance of step 4 could be actualized through the ERP frameworks. In actuality, then again, on the off chance that we are taking a gander at an ERP framework, the circumstance is definitely not perfect in that progressions are some of the time forced. Actualizing ERP frequently obliges the reengineering of existing business techniques to the layouts of the ERP framework being utilized. In Step 6 or Possibility and preferred changes in system, progressions to address the separates or crevices between the applied model and this present reality distinguished in Step 5 are presented and assessed for possibility. It will be important to look at and see which of these circumstances are conceivable (Elragal and Haddara, 2013). Among the choices here may be whether to change the circumstance to suit the ERP framework or to roll out improvements to the product to match the circumstance. In the event that distinctive ERP frameworks are being viewed as, this stage exhibits a structure for arranging the examination. The organization could contrast the ERP frameworks with recognize which best fits the association. At the last step (Accomplishment to improving the system) of the SSM, proposals for change are executed. For the ERP framework, this is the usage of the framework itself with the going hand in hand with hierarchical and procedure changes. The execution of the framework and related changes will bring about an adjustment of the issue circumstance. This new circumstance might lead to another cycle of the Soft System Methodology (SSM). Discussion By the help of the above analysis, the Hershey Foods Corporations ERP failure is due to the venture administration issues, the ERP system didnt fail due to its software problems or issues. The organization or Hershey Foods Corporation is did not utilize the fitting assets do guarantee a decent dispatch. This particularly incorporates the disappointments of top administration (Delbridge, 2008). Enormous detonation versus staged execution, it is their second endeavor Hershey was ready to plan all the more completely so as to lessen redundancies, legitimately prepare and investigate on a reasonable premise. The implementation of new system Hershey Foods Corporation is also facing some problems like lack of management in business system, lack of perception, poor timing and also for Big Bang theory or approach. The ERP business has developed to a point where increased rivalry has brought declining deals. Therefore, ERP merchants are extending their usefulness to include esteem and backing new authoritative needs from agreeability administration, client help, worldwide supply chain, and rising innovation stages, for example, open source programming and Service Oriented Architectures (SOAs). Open source addresses a key concern in this occurrence. Frequently, ERP sellers pitch to littler undertakings bundled applications that they can run as may be, obliging practically no IT venture. It's an intelligent contribute situations with rare innovation assets (Grabot, Mayere and Bazet, 2008). An alternate pattern among enormous sellers has been to extend their product market for little to medium size business. The immersion of the interest in huge business and the lucrative nature of the little and moderate sized business sector has driven merchants like SAP and Prophet to enter the little to averag e size business model. Recommendation A repeating topic has been absence of information or comprehension. Accomplished choices would appear to assuage numerous ERP disappointments. This is particularly valid for top administration; on the off chance that they could instructed them and focus on the undertaking, ERP disappointment rates would not be so overwhelming. Top administration ought to be mindful of the potential outcomes of their activities. In the event that officials at Hershey's had this illumination of sorts, thousands could have delighted in Kisses amid Halloween (and the organization could have spared $151 million). Consolation, help and satisfactory assets are needed for any undertaking having the scale and multifaceted nature of an ERP (Hindle, 2007). The administration require not get into the detail of an ERP, there are numerous capable advisors that can be employed to give itemized data, a comprehension of the significance, challenges, and obliged assets ought to suffice. The administration ought to too verify that they are mindful of the methods fundamental an association. They ought to be capable to gage the similarity of an ERP with the association. Sufficient steps ought to be taken to help fruitful ERP execution (change administration, representative preparing, and so on.). Correspondence is an alternate key variable. The association ought to pass on what is needed in a clear way. Sellers, Implementers' and advisors ought to additionally be mindful of hierarchical objectives. Endeavors ought to be made to adjust an ERP to suit workers to as huge a degree as could be allowed (Indra and Ramadhan, 2012). They should guarantee that necessities are well caught on. Concentrating on executions in comparative circumstances would help both sides. Actualizing an ERP is a lavish dull issue. ERP executions regularly cost countless dollars. Associations generally can't bear the cost of an ERP disappointment. A choice to actualize an ERP ought to be made after cautious data assembling, investigation, and arranging. Conclusion ERP executions are greatly perplexing and testing. They are not insignificant activities in programming improvement however include the upgrade of methods, associations, and data stream. Given the significance of considering human and different calculates the usage, it is recommended that SSM can give a compelling structure and speaks to an alternate device for helping in this attempt that is discriminating for the proceeded with achievement and practicality of numerous associations (Khisty et al., 2012). Hershey could have maintained a strategic distance from this disappointment in the event that they would have been more centered towards the ERP execution process. As opposed to remembering a sample of effective ERP they ought to have kept the case of disappointment ERP, so then they would now know, in what components organization neglects to execute ERP. In any case Hershey did precisely inverse to this and they did the extremely basic mix-ups which numerous organizations do like E RP usage at wrong time, not changing the business process and actualizing without considering what's to come. The absence of understanding recommends that the investigations of the purposes behind disappointment may be over generalizing, by treating all disappointments as being pretty much the same, though there are truly diverse sorts of disappointment that emerge through distinctive blends of components. There are two things that seem most apparent from the writing. The main is that applying conventional techniques to an ERP improvement venture does not work. The second is that the most punctual phases of the venture are generally basic. Adding to a reasonable and precise picture of the current condition of the business and its techniques is basic, and needs to be completed in the recent past choosing whether an ERP framework can give the fitting arrangement (Kotiadis et al., 2012). It is additionally essential element to recognize the potential dangers previously, then after the fact the ERP bundle is chosen, so that they can be properly overseen. Besides, it is essential that a suitable change administration component is placed set up, and that the effects of any progressions (to the association or the ERP framework) on the undertaking dangers are enough considered. Whilst these proposals may not ensure achievement, on the off chance that they are not given fitting thought, the shots of disappointment are liable to be more prominent than they could be. References Albadri, F. (2013).Cases on enterprise information systems and implementation stages. Hershey, Pa.: Business Science Reference. Amid, A., Moalagh, M. and Zare Ravasan, A. (2012). Identification and classification of ERP critical failure factors in Iranian industries.Information Systems, 37(3), pp.227-237. Bergvall-Kreborn, B., Mirijamdotter, A. and Basden, A. (2004). Basic Principles of SSM Modeling: An Examination of CATWOE from a Soft Perspective.Systemic Practice and Action Research, 17(2), pp.55-73. Bishnoi, V. (2011).Economic analysis of implementing enterprise resource planning (ERP). [S.l.]: Lap Lambert Academic Publ. Braithwaite, J., Hindle, D., Iedema, R. and Westbrook, J. (2002). Introducing soft systems methodology plus (SSM+): why we need it and what it can contribute.Australian Health Review, 25(2), p.191. Checkland, P. and Poulter, J. (2006).Learning for action. Chichester, England: Wiley. Chen, C., Law, C. and Yang, S. (2009). Managing ERP Implementation Failure: A Project Management Perspective.IEEE Transactions on Engineering Management, 56(1), pp.157-170. Corporation, E. (2015).ERP Implementation Failure Hershey Foods Corporation. [online] Academia.edu. Available at: https://www.academia.edu/4630187/ERP_Implementation_Failure_Hershey_Foods_Corporation [Accessed 28 Feb. 2015]. Cucchi, A. (2012). Julien MALAURENT, From global template to local enactments: a longitudinal account of erp practice diffusion in chinese subsidiaries of a french multinational corporation.Systmes d'information management, 17(3), p.143. Delbridge, R. (2008). An illustrative application of soft systems methodology (SSM) in a library and information service context.Library Management, 29(6/7), pp.538-555. Delbridge, R. and Fisher, S. (2007). The use of soft systems methodology (SSM) in the management of library and information services: a review.Library Management, 28(6/7), pp.306-322. Dou, R. (2013).Proceedings of 2012 3rd International Asia Conference on Industrial Engineering and Management Innovation (IEMI2012). Berlin: Springer. Elragal, A. and Haddara, M. (2013). The Impact of ERP Partnership Formation Regulations on the Failure of ERP Implementations.Procedia Technology, 9, pp.527-535. Gargeya, V. and Brady, C. (2005). Success and failure factors of adopting SAP in ERP system implementation.Business Process Mgmt Journal, 11(5), pp.501-516. Grabot, B., Mayere, A. and Bazet, I. (2008).ERP systems and organisational change. London: Springer. Hardman, J. and Paucar-Caceres, A. (2010). A Soft Systems Methodology (SSM) Based Framework for Evaluating Managed Learning Environments.Systemic Practice and Action Research, 24(2), pp.165-185. Hellens, L., Nielsen, S. and Beekhuyzen, J. (2005).Qualitative case studies on implementation of enterprise wide systems. Hershey, PA: Idea Group Publishing. Hershey Foods Corp. (2004).Mergent's Dividend Achievers, 1(4), pp.136-136. Hershey Foods Corp. (2005).Mergent's Dividend Achievers, 2(1), pp.133-133. Hindle, D. and Braithwaite, J. (2002).Soft systems methodology plus (SSM+). Sydney: Centre for Clinical Governance Research in Health. Hindle, G. (2007). Developing a systemic textual analysis methodology based on the human activity system modelling language of soft systems methodology (SSM).Syst. Res., 24(6), pp.599-612. Hirata, T. (2009).Customer satisfaction planning. New York: CRC Press. Indra, D. and Ramadhan, A. (2012). The Relationships of Soft Systems Methodology (SSM), Business Process Modeling and e-Government.IJACSA, 3(1). Khisty, C., Mohammadi, J., Amedkudzi, A. and Khisty, C. (2012).Systems engineering with economics, probability, and statistics. Ft. Lauderdale, FL: J. Ross Pub. Kiran, S. (2012). Discovering Key Factors in ERP Implementation through Success and Failure Cases.International Journal of E-Entrepreneurship and Innovation, 3(3), pp.27-36. Kotiadis, K., Tako, A., Rouwette, E., Vasilakis, C., Brennan, J., Gandhi, P., Wegstapel, H., Sagias, F. and Webb, P. (2012). Using a model of the performance measures in Soft Systems Methodology (SSM) to take action: a case study in health care.Journal of the Operational Research Society, 64(1), pp.125-137. Meissonier, R., Houz, E. and Lapointe, L. (2014). Cultural Intelligence During ERP Implementation: Insights from a Thai Corporation.International Business Research, 7(12). Minatti Ferreira, D., Rosa da Silva, A., Cristina Santos Rebello, T. and dos Santos, N. (2009). Soft Systems Methodology (SSM) No Contexto Da Educao Tecnolgica: Contribuies Aos Processos De Gesto Do Conhecimento (GC).Revista Gesto Industrial, 5(3 s.1). Nah, F. (2002).Enterprise resource planning solutions and management. Hershey, PA: IRM Press. Parthasarathy, S. (2007).Enterprise resource planning (ERP). New Delhi: New Age International. Peci, M. and Vaan, P. (2014). The Biggest Critical Failure Factors in ERP Implementation.AMM, 519-520, pp.1476-1480. Por, J. (2008). The use of soft system methodology (SSM) in a serviced-focussed study on the personal tutors role.Nurse Education in Practice, 8(5), pp.335-342. Ravasan, A. and Mansouri, T. (2014). A FCM-Based Dynamic Modeling of ERP Implementation Critical Failure Factors.International Journal of Enterprise Information Systems, 10(1), pp.32-52. Rennie, H. (1992). Soft Systems Methodology in Action: The Text for SSM Teachers and Practitioners?.The Journal of the Operational Research Society, 43(1), p.77. Rodriguez-Ulloa, R. and Paucar-Caceres, A. (2005). Soft System Dynamics Methodology (SSDM): Combining Soft Systems Methodology (SSM) and System Dynamics (SD).Syst Pract Act Res, 18(3), pp.303-334. Sar, A. and Garg, P. (2012). Analysis of critical failure factors in ERP implementation: an Indian experience.IJBIS, 11(3), p.360. Shirouyehzad, H., Dabestani, R. and Badakhshian, M. (2011). The FMEA Approach to Identification of Critical Failure Factors in ERP Implementation.International Business Research, 4(3). Shtub, A. (2002).Enterprise resource planning (ERP). Boston: Kluwer Academic. Sumner, M. (2005).Enterprise resource planning. Upper Saddle River, N, J.: Prentice Hall. The food manufactureing industries: Structure, strategies, performance and policies by John M. Connor, Richard T. Roggers, Bruce W. Marion, and Willard F. Muller. Lexington, MA: Lexington Robert V. Bishop, Econometrician, Hershey Foods Corporations. (Views expressed are those of Mr. Bishop and do not necessarily reflect those of Hershey Foods.). (1988).Agribusiness, 4(4), pp.403-404. Uchiyama, K. (2003).The theory and practice of actuality. Tokyo, Japan: Institute of Business Research, Daito Bunka University. Wilson, B. (2003).Soft Systems Methodology. Chichester: John Wiley Sons. Winter, M. (2006). Problem structuring in project management: an application of soft systems methodology (SSM).Journal of the Operational Research Society, 57(7), pp.802-812. Zaveri, J. (2009).Enterprise resource planning. Mumbai: Himalaya Pub. House.