臺灣博碩士論文加值系統

專案管理是企業執行產品開發和產品生命週期期間流程控制一個重要的功能。在全球化競爭之下，好的 “專案管理環境”是指在有限資源、時間與預算下完成整個專案執行。目前中小企業利用專案管理，透過專案委外策略交付供應商執行，使中小企業能與其他廠商合作，可以降低成本並具有更好競爭力。整個策略性委外專案作業起動，需要透過專案需求建議書(RFP)來說明業主需求，進而給潛在承包商討論與提案的機會。通常，一份RFP資料具有下列功能：指定業主需求、說明整個工程內容、提案內容具體描述及限制條件。因此，整個專案需求建議書有四個構面的主要功能：法律方面、合作方面，限制條件方面和評估方面。傳統業主憑自身的經驗及知識，掌握整個專案管理運作流程，但有時業主判斷錯誤，會造成公司莫大損失。本研究是針對傳統RFP流程的問題，提出一套自動化專案管理RFP系統。本研究實際開發一個網頁化RFP系統，其主要功能在於提供一個專案管理前置規劃的溝通平台。經由系統實際測試，結果顯示中小企業可因此自動化RFP系統，提昇專案執行效益。

Project management is an important function for the enterprise to carry out product development and flow control during the product life cycle. To meet the global competition, a good “project management environment” is required to complete the project under the limitation of resource, time and budget. The issue of project management is particularly received attention for the small and medium enterprise (SME). Through the strategy of outsourcing project to outside providers, SMEs can cooperate with others and obtain benefit of cost saving and better competitiveness. To initiate an outsourcing project, a request for proposal (RFP) is used to publish the project specification by the buyer, and then the potential suppliers submit their offers. Usually, a RFP document has the function of to specify the buyer’s needs, to officially announce the project intention, and to describe specific constraints regarding the contents of the proposal. Therefore, four aspects can be expected in a RFP: legal aspect, collaborative aspect, constraint aspect, and evaluation aspect. This paper addresses the problem of traditional RFP process, and proposes an automatic project management RFP system. A web-based RFP system is developed in this paper. The basic role of this system provides the function of preparing official RFP and managing the exchange of messages. Result shows that the proposed automatic system speed the procedure of RFP process and reach project specification more effectively.

中文摘要-------------------------------------------------------------I
英文摘要------------------------------------------------------------II
誌謝---------------------------------------------------------------III
目錄----------------------------------------------------------------IV
圖目錄-------------------------------------------------------------VII
表目錄--------------------------------------------------------------IX
第一章緒論------------------------------------------------------- 1
1.1研究動機--------------------------------------------- 1
1.2研究目的----------------------------------------------------- 2
1.3研究流程----------------------------------------------------- 3
第二章文獻探討--------------------------------------------------- 5
2.1中小企業定義與現況-------------------------------------------- 5
2.2 委外策略--------------------------------------------------- 7
2.3 企業流程再造------------------------------------------------- 10
2.4 專案管理--------------------------------------------------- 12
2.4.1專案需求建議書-------------------------------------- 16
2.4.2專案需求建議書建置步驟---------------------------------- 17
2.4.3專案需求建議書功能-------------------------------------- 18
2.4.4專案需求建議書內容-------------------------------------- 18
2.4.5專案供應商管理------------------------------------------ 19
2.5 自動化資訊技術------------------------------------------- 23
2.6 小結----------------------------------------------------------26
第三章 自動化RFP系統方法論---------------------------------------- 27
3.1 方法論----------------------------------------------------- 27
3.2 系統導入方法及步驟------------------------------------------- 29
3.2.1 起始程序----------------------------------------------- 30
3.2.2 規劃程序----------------------------------------------- 32
3.2.3 執行程序----------------------------------------------- 34
3.2.4 控制程序----------------------------------------------- 37
3.2.5 結案程序----------------------------------------------- 40
3.3 小結-------------------------------------------------------- 42

第四章 自動化RFP系統分析------------------------------------------ 43
4.1 專案需求建議書系統模組建立----------------------------------- 44
4.1.1 專案需求建議書週期------------------------------------- 45
4.1.2 專案需求建議書結構------------------------------------- 46
4.1.3 專案需求建議書權限------------------------------------- 46
4.2 系統情境塑模------------------------------------------------- 47
4.2.1 企業流程塑模------------------------------------------- 47
4.2.2使用案例塑模-------------------------------------------- 49
4.2.3使用案例具體描述---------------------------------------- 50
4.2.4 找出候選服務------------------------------------------- 54
4.2.5 物件類別塑模------------------------------------------- 56
4.2.6 物件互動塑模------------------------------------------- 58
4.2.7 企業元件塑模------------------------------------------- 61
4.2.8 元件部署塑模------------------------------------------- 61
4.3 小結-------------------------------------------------------- 61
第五章 自動化RFP系統建立實例--------------------------------------- 63
5.1系統實作----------------------------------------------------- 63
5.1.1 系統主畫面說明----------------------------------------- 64
5.1.2 系統身份代碼維護--------------------------------------- 64
5.1.3 系統功能維護------------------------------------------- 65
5.1.4 使用者名單--------------------------------------------- 66
5.1.5 密碼變更作業------------------------------------------- 66
5.1.6 廠商資料內容作業--------------------------------------- 67
5.1.7 專案維護----------------------------------------------- 68
5.1.8 專案篩選----------------------------------------------- 68
5.1.9 專案通知----------------------------------------------- 69
5.1.10 專案查詢---------------------------------------------- 70
5.1.11 條件維護---------------------------------------------- 70
5.1.12 條件項目維護-------------------------------------------71
5.1.13 專案決策---------------------------------------------- 72
5.1.14 專案進度維護作業---------------------------------------72
5.1.15 專案文件上傳作業---------------------------------------73
5.1.16 意見反應---------------------------------------------- 74
5.2 小結-------------------------------------------------------- 75
第六章 自動化RFP系統效益評估--------------------------------------- 76
6.1 個案公司簡介------------------------------------------------- 76
6.1.1 公司行銷策略------------------------------------------- 77
6.2 自動化RFP系統導入效益分析----------------------------------- 78
6.2.1 改善效果確認------------------------------------------- 79
6.3 系統規劃及導入心得------------------------------------------- 82
第七章 結論------------------------------------------------------ 83
7.1 建議------------------------------------------------------- 83
參考文獻-------------------------------------------------------- 85
簡歷------------------------------------------------------------ 89
已發表論文------------------------------------------------------- 90

[英文文獻部分]
[1]K. A. Artto and K. Wikstorm, “What is project business?,” International Journal of Project Management, vol.2 , no.23, pp.243-253, Jan. 2005.
[2]D. K. Anderson and T. Merna,“ Project management strategy – project management represented as a based set of management domains and the consequences of project management strategy, ” International Journal of Project Management, vol.2 , no.23, pp.387-393, Sep. 2003.
[3] B. Cova and R. Salle, “Six key points to merge project management into project management,” International Journal of Project Management, vol.2, no.23, pp.354-359, June. 2005.
[4]L. Crawford, “Senior management perceptions of project management competence,” International Journal of Project Management, vol.4, no.23, pp.7-16, Mar. 2005.
[5]T. H. Davenport, J. E. Short, “The new industrial engineering: Information technology and business process redesign,” Sloan Management Review, vol. 31 , no.4, pp.11-27, 1990.
[6]W. R .Duncan, “A Guide to the Project Management Body of Knowledge,” International Journal of Project Management, vol.4, no.23, pp.7-16., Mar. 2005.
[7]D. P. Donk and J. Riezebos, “Exploring the knowledge inventory in project-based organizations: a case study,” International Journal of Project Management, vol.3, no.23, pp.75-83, Apr, 2005
[8] R. Evaristo and P. C. Fenema, “A typology of project management: emergence and evolution of new forms, ”International Journal of Project Management, vol.17, no.5, pp.275-281, 1999.
[9] B. Frederic and V. Christine, “XML Documents Production for an Electronic Platform of Requests for Proposals,” in Proceedings of 18th IEEE Symposium on Reliable Distributed Systems,1999,pp.330.
[10] J. Fortune and D. White, “Framing of project critical success factors by a systems model,” International Journal of Project Management, vol.3, no.24, pp.53-65, Mar. 2006.
[11]V. Govindarajan and A. K. Gupta, “Strategic Innovation: A Conceptual Road Map”, Business Horizons, vol.44, no.4, pp.3-12, Aug. 2001.
[12]M. Hammer, J.A. Champy, Reengineering the Corporation:A Manifesto for Business Revolution, Harper Collins, New York, 1993.
[13]A. Jennitta, “An Agile Request for Proposal (RFP) Process,” in Proceedings of Jennitta Andrea, 2003, pp.152-162.
[14]H. Kerzner, Project Management: a systems approach to planning, scheduling, and controlling, 8th ed., John Wiley & Sons, Inc., p.558, 2003.
[15] M.M. Klein, “IEsll facilitator role in benchmarking operationsto improve performance,” Industrial Engineering, vol.25, no9, pp.40-43,1993.
[16] H. C. Linderoth and G.. Pellefrino, “Frames and inscriptions: tracing a way to understand IT-dependent change projects,” International Journal of Project Management, vol.5, no.29, pp.415-420, Mar. 2005.
[17]R. J. Meredith and S. J. Jr., Project Management: A Managerial Approach, 5th ed., John Wiley & Sons, Inc., P.62, 2003.
[18] R.L. Manganelli, “Dene re-engineer,” Computerworld, vol. 27, no.29, pp 86-87, 1993.
[19]PMI, A Guide to the Project Management Body of Knowledge, 2000.
[20]M. R. Rotab,“Business process reengineering of an air cargo handling process,” International Journal of Production Economics, vol.4, no.2, pp.99-108, Jan.1999.
[21] S. K. Sia and B. S. Neo, “The impacts of business process re-engineering on organizational controls,” International Journal of Project Management, vol6, no.6, pp.341-348, Jan. 1996.
[22] V. Voropajev, “Change management-A key integrative function of PM in transition economics, ”International Journal of Project Management, vol.16, no.1, pp.15-19., 1998.
[23] H. J. Wu and K. K. Huang, “Buliding automatic project management RFP system, ”the 36th International Conference on computers and Industrial Engineering, 2006.

[中文文獻部分]
[1]王本正、林余任，中小企業導入知識網提昇競爭力之關鍵因素研究，第七屆網路運輸協會研討會，2002。
[2]王志傑、張克章，以UML改良整合專案管理程序之研究，中華管理評論，卷5，期2，頁143~156，1999。
[3]中華專案管理學會，專案管理基礎知識與應用實務，初版，台北：博鴻，2005。
[4]企業專案管理的關鍵時(2005) http://www.microsoft.com/taiwan/office/project。
[5]杜雯蓉(譯)，委外革命，初版，台北：城邦，2006。
[6]余峻瑜(譯)，企業外包致勝，初版，台北：培生，2003。
[7]李昌雄，商業自動化與電子商務，初版，台北:智勝，2004。
[8]林信惠、黃明祥，軟體專案管理研究架構及趨勢，資訊管理研究，卷4，期1，頁31~64，2002。
[9]周明憲，eXtreme Programming理論與實務，初版，台北：博碩，2003。
[10]政府機關資訊委外知識網（2005）http://web.rdec.gov.tw/cisa。
[11]政府資訊作業委外服務實施手冊（2005）http://www.sinica.edu.tw/info/obs。
[12]范綱志(譯)，極制軟體制程專案應用，初版，台北：培生，2003。
[13]黃哲明，劉世興、蔡明洲，能力成熟度模式導入組織專案辦公室之研究，產業論壇期刊，卷7，期3，2004。
[14]黃大偉，圖書館自動化之路，佛教圖書館館訊，期2，1995。
[15]經濟部中小企業處，中小企業白皮書，初版，台北：經濟部，2004。
[16]經濟部商業司(2005) http://www.ec.org.tw/bpr/doc/doc.htm。
[17]彈性委外策略白皮書(2006) http://www.eds.com。
[18]劉孟華(譯)，專案管理聖經，初版，台北：臉譜，2004。