臺灣博碩士論文加值系統

『企業資源規劃 (Enterprise Resource Planning, ERP) 』主要是將企業內跨部門作業：財務成本、銷售運送、生產製造、物料管理等資訊資源整合起來，並能隨著產業環境、競爭者情勢、客戶需要等變化隨時調整系統的營運流程進行最佳配置，藉以達到降低成本、提昇作業效率並能及時提供有用的資訊以供管理者作決策等之目的。
本研究採個案研究，分別訪談中冠資訊股份有限公司及國巨股份有限公司。前者成立於2000年四月由中國鋼鐵股份有限公司轉投資，中鋼企業資源規劃作業，主要是傳統資訊系統於1994年第三階段擴廠作業後經由電腦與資訊應用整合而成。後者國巨公司由於購併飛利浦被動元件廠後，全球化運籌作業無法推動，故引進SAP之ERP套裝系統，藉此整合全球資源。中鋼公司ERP系統的建置由早期的管理資訊系統，漸次的整合、擴充而來，其手段是溫和的其著重於作業的延續性。而國巨採取的則將舊有的包袱拋棄，採取一次導入所有系統，再分階段建置於全球研發、生產、行銷各據點，雖然手段較為激進，但是企業綜效立即顯現。
經由訪談及文件資料整理分析，本研究發現：
1.導入ERP系統時，企業應該考慮在不同環境或限制的情況下採取的不同的策略模式因應，本研究發現全球化的企業在資訊整合上的困難度較高，且營運綜效要求程度較高，故較易採取套裝軟體一次導入策略。而傳統系統本土化的企業則依訴求的目標，其策略採取較有彈性。
2.高階主管的承諾上，兩企業皆強調專案必須要有明確的導入目標與範圍，且對專案主管絕對的授權。
3.透過傳統系統整合的企業資源規劃系統，系統功能模組化的程度不夠，其較難在短時間因應外在環境變化所導致的需求；同時由於階段性開發作業透過介面與舊系統整合，其維護成本上也將是一項負擔。
4.影響ERP導入的專案控管上，兩企業皆強調專案控管機制建立的重要性，且高階主管擔任專案負責人，藉以強調專案的重要性與必定成功的決心。
5.與協力廠商合約訂立，強調溝通能力的重要性。議約的內容強調專案採固定成本與保證成功。
6.在流程改造上，強調企業資源規劃必須要作到業務實際流程與資訊流程的同步化作業。
7.強調以組織結構扁平化，彈性的配合組織流程改造。
根據以上七點的發現，本文認為ERP導入策略思維模式，必須依據企業本身的環境與限制條件，首先需透過不斷溝通達成雙方議約，選擇合宜的導入策略，並透過專案控管的機制，配合扁平的組織結構，提供誘因塑造能夠接受變革的企業文化，與業務流程與資訊流程同步化作業，則ERP的導入較易成功。

『Enterprise Resource Planning』(ERP) is an integrated information system consists of different business functions including Financial/Cost, Sales/Distribution, Material Management, Production Planning, etc. It facilitates the business flexibility to adjust for environmental changes such as industries, customer needs, and the status of competitor. The purposes are to reduce the cost, enhance work efficiency, and generate sufficient information for the business decisions.
Two enterprises are studied for their ERP implementation in this thesis; they are the InfoChamp Systems Corporation (ICSC) and the Yageo Company (YC). ICSC which started in 2000 A.D. is a spinout company of the China Steel Company after it successfully constructed the ERP system. The strategy of the China Steel Company was to gradually extend the application function from the original management information system. On the other hand, the Yageo Company adopts the SAP package and discards the whole traditional information system. In order to discover how these two enterprises implement the ERP systems, the author interviewed their representatives several times. Besides, the company documents, publish papers and data from their web sites were collected and analyzed. The main conclusions are summarized as the following.
1.The enterprise needs to carefully consider the organization structure associated with possible constraints before the implementation of ERP system. Whether to extend the traditional management information system or to adopt a certain industrial package, the information integration among new systems and old systems is a very complicated issue.
2.The goal of the implementation project should be clarified and specified to all members in the enterprise. In addition, the project manager should be fully authorized to take charge of the whole implementation process.
3.As the enterprise expend their business functions, the information system also needs extra modules. It is not an enduring decision to simply adopt an available package. However, using interface development to integrate the informational system will result in high maintenance cost.
4.The two enterprises emphasis the importance by establishing the project control mechanism. The executive managers serve as the project leader in order to proclaim the ambition of the project success.
5.The contract negotiation with the consulting company requires careful communication. The cost, durations, customization, and the commitment of a successful project should be included.
6.The consistency of the business and information process may enhance business performance.
7.The bureaucratic organization and workflow need a reformation.

目 錄
第一章緒論
第一節研究目的 ------------------------------------------- 3
第二節研究範圍與步驟與論文結構 ------------------- 3
第二章文獻探討
第一節ERP的定義與發展歷程 ------------------------- 6
第二節ERP導入策略探討 ------------------------------- 8
第三節影響ERP導入的關鍵因素 --------------------- 16
第四節ERP導入方法論探討 ---------------------------- 21
第三章個案研究之設計與方法介紹
第一節研究方法的選擇 ----------------------------------- 30
第二節個案的選擇與分析單位 -------------------------- 31
第三節資料收集的方法 ----------------------------------- 31
第四節問卷設計與訪談 ----------------------------------- 32
第五節資料整理 -------------------------------------------- 33
第四章個案一中鋼公司
第一節公司背景介紹 --------------------------------------- 34
第二節管理資訊系統發展的範圍、目標、原則 ------ 37
第三節ERP規劃階段 --------------------------------------- 38
第四節系統分析、設計與發展 --------------------------- 40
第五節ERP績效 ---------------------------------------------- 44
第六節ERP導入關鍵因素探討 ---------------------------- 45
第五章個案二國巨電子
第一節公司背景介紹 --------------------------------------- 55
第二節導入ERP的動機與價值 -------------------------- 60
第三節ERP導入的參考架構與執行過程 --------------- 62
第四節ERP導入的關鍵因素探討 ------------------------ 70
第六章個案比較分析、命題建立
第一節ERP建置策略的比較 ------------------------------- 78
第二節導入ERP動機的比較 ------------------------------ 80
第三節ERP導入方法論的比較 ---------------------------- 82
第四節ERP導入關鍵成功因素的比較 ------------------- 82
第五節研究命題 ---------------------------------------------- 85
第七章結論與建議
第一節研究貢獻 ----------------------------------------------- 88
第二節後續研究建議 ----------------------------------------- 89
參考文獻
中文部份 ---------------------------------------------------------------- 90
英文部份 ---------------------------------------------------------------- 90
圖目錄
圖1-1：研究步驟流程圖 ------------------------------------- 4
圖2-1：Ｇartner Research ERP II定義架構 ------------------- 7
圖2-2：資訊系統發展的因應策略 ----------------------------- 9
圖2-3：ERP專案生命週期 -----------------------------------23
圖2-4：SAP之ASAP導入流程 --------------------------------23
圖2-5：日本工業會ERP研究所--ERP導入的基本步驟 -----------25
圖2-6：WISDM導入流程 -------------------------------------26
圖2-7：三階段系統開發過程 ---------------------------------26
圖2-8：七階段系統開發過程 ---------------------------------27
圖4-1：中鋼公司組織架構圖 ---------------------------------36
圖4-2：中鋼公司整體資訊系統發展過程 -----------------------39
圖4-3：中鋼整體資訊發展方法 -------------------------------40
圖4-4：中鋼公司整體資訊系統發展架構 -----------------------42
圖4-5：專案月份提報程序 -----------------------------------47
圖5-1：國巨集團分布圖 -------------------------------------60
圖5-2：國巨公司系統發展方法 -------------------------------64
圖5-3：國巨專案組織圖 -------------------------------------65
圖5-4：國巨整體資訊系統架構圖 -----------------------------66
圖6-1：中鋼在生產計劃資訊分享層級架構 ---------------------81
圖7-1：ERP導入分析模式 -----------------------------------89
表目錄
表2-1：ERP發展歷程 ---------------------------------------- 8
表2-2：ERP導入之關鍵影響因素 ------------------------------ 18
表4-1：應用軟體開發程序 --------------------------------------------- 43
表4-2：中鋼公司整體資訊規劃後所產生的效益 ------------------ 45
表4-3：中鋼公司推動ERP的優劣勢 ---------------------------- 53
表5-1：流程績效衡量指標 ------------------------------------ 61
表5-2：國巨電子第二階段企業藍圖工作計劃 -------------------- 71
表5-3：國巨專案管理兩週工作排程 ---------------------------- 72
表5-4：國巨專案管理兩週工作項目內容 ------------------------ 72
表5-5：國巨電子推動ERP的優劣勢 ---------------------------- 76
表6-1：ERP導入策略與關鍵構面影響程度 ----------------------- 79
表6-2：ERP 導入動機的資訊分享模式比較表 -------------------- 80
表6-3：企業ERP導入參考架構比較 ---------------------------- 82
表6-4：ERP 導入專案成功比較 -------------------------------- 83

參考文獻一、中文部份1.中鋼資訊系統處，1989，『中鋼整體資訊系統』。2.中鋼資訊系統處，1990，『資訊作業標準』，7月。3.中鋼資訊系統處，1991，『整體資訊作業發展計劃書』，4月。4.中鋼資訊系統處，1993，『整體資訊系統發展計劃書』，3月。5.王立志，1999，『系統化運籌與供應鏈管理』，滄海書局，6月，pp.474.6.申元洪、李泰琳、許秉瑜，2000，『如何導入ERP提昇競爭力』，資訊與電腦，11月號：51-54。7.石滋宜，1998，『ERP的迷失』，能力雜誌，12月號，pp.108.8.吳仁和、林信惠，2000，『系統分析與設計理論與實務應用』，智勝文化，1月，pp.3-6.9.明雲清，2000，『c-Commerce 蔚為主流揭開ERP II序幕』，CIO Infopro Weekly Taiwan, Dec. 11, pp.46-47.10.陳同賢，2001，『如何成功的導入ERP』，資訊與電腦，6月號：108-110。11.熊培霖，2001，『e時代專案管理的發展與應用』，資訊與電腦，6月號：88-91。12.劉敦仁、房家緯，1999，『企業導入Oracle Applications 建構ERP系統的個案研究』第五屆資訊管理研討會，11月。13.劉西湖、陳孝倫、高福成，2000，『ERP入門』，健峰，9月，pp.4-55.二、英文部份14.Anonymous, “ERP implementation longer than expected”, Manufacturing Computer Solutions Orpington, Jun 199915.Anonymous, “QAD: QAD announces 1998 Asia Pacific ‘Rapid Achiever Award’ for quick ERP implementation” M2 Presswire Coventry, Apr 7 1998.16.Anonymous, “Implementation ERP system successfully”, Computimes Malaysia, Jul 30 1998.17.Appleton, E. L. “How to survive ERP”, Datamation Barrigton, Mar 199718.Bingi, P. and Sharma, M. K. and Godla J. “Critical issues affecting an ERP implementation”, Information Systems Management Boston, Summer 1999.19.Bowen, Ted, S. “ERP installations fit to be tied?”, InfoWorld Framingham, Sep 21,1998 20.Caruso, David, “Implementing ERP”, Intelligent Enterprise San Mateo, Apr 20,199921.Cole-Gomoiski, B. “Enterprise resource Planning; Systems development; Problems; Systems Management”, Computerworld [COW] Vol:32 Iss:38 Date: Sep 21,1998, pp.1,10022.Corcoran, Cate, T. “ERP implementations raise tricky personnel issues”, InfoWorld Framingham, Aug 17 199823.Davenport, T., Putting the Enterprise into the Enterprise System,” Harvard Business Review, July-August 1998, Vol. 76, No. 4,pp.121-131.24.Ferranti, Marc, “Debunking ERP misconceptions”, InfoWorld Framingham, Aug 17 1998.25.Glover, Steven, M. and Prawitt, Douglas, F. and Rommey, Marshall, B., “Implementing ERP”, The Internal Auditor Altamonte Springs, Feb. 1999.26.Goldman, S.L., Nagel, R.N., and Preiss, K. “Agile Competitors and Virtual Organizations, New York: Van Rostrand Reinhold”, 1995.27.Gregg, Jacob, and Tatia, W., “Rapid ERP implementation; The Tuolumne County, California experience”, Government Finance Review Chicago, Aug. 199928.Hammer, Michael, “Up to the ERP revolution”, Informationweek Manhasset, Feb 8 199929.Hammer M. “Reengineering Work: Don’t Automate, Obliterate”, Harvard Business Review, July-August 1990, pp.104-112.30.Holland, C.P. , and Light, B. “A critical success factors model for ERP implementation”, IEEE Software [H.W. Wilson-AST], May/Jun 1999.31.Johnson, J.,”Chaos: The Dollar Drain of IT Project Failure,” Application Development Trends, January 1995, pp.41-48.32.Jesus Bisbal and Deirdre Lawless and Bing Wu and Jane Grimson, 1999. Legacy Information Systems: Issues and Directions. IEEE Software, pp.106. 33.K. Bennett, Legacy System. IEEE Software, Jan. 1995, pp.19-73.34.Kochan, A., The key to success, Works Management, 1999, pp8-9.35.Konsynski, B. R., and McFarlan, E. W. “Information Partnerships — Shared Data, Shared Scale,” Harvard Business Review, Sept.-Oct., 1990, pp. 114-120.36.Levitt T. “The Globalization Of Markets”, May-June,1983, pp.92-102.37.Norbert Welti, Successful SAP R/3 Implementation, Practical Management of ERP Projects, 1999, pp. 7-10.38.Malone, T. W., Yates, J., and Benjamin, R. I. “Electronic Markets and Electronic Hierarchies,” Communications of the ACM, Vol. 30, No. 6, 1987, pp.484-497.39.Mark Kremers and Han Van Dissel “ERP A provider’s versus a customer’s perspective System Migrations”, Communication Of The ACM, April 2000/Vol. 43, No. 4.40.M. Brodie and M. Stonebraker, Migrating Legacy System: Gateways, Interfaces and the Incremental Approach, Mogan Kaufmann, San Francisco, 1995.41.Mousseau, Patrick, “ERP projects call for multi-talented managers”, Computing Canada Willowdale, Nov 9 1998.42.Norbert Welti, “Successful SAP R/3 Implementation, Practical Management of ERP Projects”, Addison-Wesley, 1999.43.Ohame K. “Managing In A Borderless World”, Harvard Business Review, May-June, 1989,pp.152-161.44.Riper, K. and Durham, M. J. “Phased ERP implementation：The city of Des Moines experience”, Government Finance Review Chicago, Aug 1999.45.Reich B.H. and Benbasat I. “Measuring the Linkage between Business and Information Technology Objectives”, MIS Quarterly, May, 1996, pp.55-81.46.Seidmann, A.; Sundararajan, A., “Sharing Logistics Information Across Organization：Technology, Competition and Contracting”, Chris F. Kemerer (Ed.), Information Technology and Industrial Competitiveness：How IT Shapes Competition, 1998, pp. 107-136.47.Sasaki, T. “What the Japanese Have Learned from Strategic Alliances,” Long Range Planning, Vol. 26, No. 6, 1993, pp.41-53.48.Sterling, Brian, “Installation doesn’t have to be painful”, Computing Canada Willowdale, Mar 26 199949.Sweat, Jeff “Learning curve” Informationweek, Aug 2, 1999, pp.44-52.50.Tadjer, Rivka, “Enterprise Resource Planning”, Internetweek Manhasset, Apr 13, 199851.Walecka, J., System Integration; Legacy system, InternetWeek [CWE] Iss:717, Jun 1,1998 pp.49