不同評選模式對軟體整合系統採購之效益分析

The effects analysis of different acquisition evaluation model for a software intensive system

李焜瑩(Kun Ying, Lee)

指導教授 ： 張百棧

元智大學/工程學院/工業工程與管理學系/碩士(2003年)

摘要

對多數軟體整合系統採購的管理者而言，投標廠商建議書評選是一項極為艱巨的挑戰，本研究從文獻探討及政府採購法所規範的招標方式中，規納出兩種軟體整合系統採購之評選模式，即「三段標」評選模式與「最有利標」評選模式，並透過案例研究，探討不同商源評選模式在實務上的應用及對軟體整合系統採構之影響。基此，本研究從獲得策略、採購程序、評選模式、評選組織等四個面相，探討「三段標」評選模式與「最有利標」評選模式對軟體整合系統採購之效益。研究結果發現，「三段標評選模式」無法有效解決軟體整合系統採購之風險辨識問題；亦即，「最有利標」對軟體整合系統採購評選之效益優於「規格標」評選模式。

關鍵字

軟體整合系統 ； 三段標 ； 商源評選 ； 最有利標

並列摘要

For most managers in charge of new software intensive system procurement, the review and evaluation of tender proposal is a critical challenge. The purpose of this paper is to examine the performance and effectiveness in different acquisition evaluation processes and methodologies. This research starts by reviewing problems and opportunities for improving evaluation model of source selection for a software intensive system. The software acquisition evaluation model then presents an outline of the acquisition strategy planing, selection process, score methodology, evaluation criteria, and the evaluation committee based on acquisition practice, techniques and government procurement law. A review of the finding from the acquisition case study is also presented. Two evaluation models are used for case study include multi-step opening and the most advantageous opening. This research compares the findings obtained from these two approaches and focuses on the effects of software intensive system acquisition, contracting and performance measurement. We find that the multi-step-opening process can hardly identify the risk of proposal, and conclude that most advantageous opening process is the best approach for the acquisition evaluation of a software intensive system.

並列關鍵字

software intensive system ； multi-step opening ； source selection ； most advantageous opening

參考文獻

[2] Edmund H. Conrow & Patricia S. Shishido, Implementing Risk Management on Software Intensive Projects, IEEE Software, 1997

[4] Guidelines for Successful Acquisition and Management of Software Intensive System V-3.0，Department of the Air Force, USA, May 2000.

[5] Guidelines for Successful Acquisition and Management of Software Intensive System V-3.0，Department of the Air Force, USA, May 2000.

[7] IEEE Recommended Practice for Architectural Description of Software-Intensive System，IEEE Std 1471-2000, IEEE-SA Standard Board, 21 Sep. 2000

[9] Guidelines for Successful Acquisition and Management of Software Intensive System V-3.0，Department of the Air Force, USA, May 2000.