美國聯邦採購法之Rfp法規 cisanet-f1

2006/7/251

「美國聯邦採購法 (FAR) 」之「徵求建議書 (RFP) 」法規應用

2006 年 8 月

國防工業發展協會科技顧問尹守紀

E-mail:[email protected]

2006/7/252

內容1. 有關 FAR 、 RFP 之定位關係2. FAR 有關 RFP 之定義3. RFP 內容說明4. RFP 選商準則5. 國內案例

2006/7/253

1.1 - FAR 與國會法案 (Acts) 及行政規定 (Circulars) 、行政命令 (Executive Orders) 等法令之從屬關係1. Legislation

Clinger-Cohen Act Paperwork Reduction Act of 1995

(P.L. 104-13) 2.1.1.3 Federal Acquisition Streamlining Act of 1994 (P.L. 103-355)

Government Performance and Results Act of 1993 (P.L. 103-62)

Competition in Contracting Act (P.L. 98-369)

Office of Federal Procurement Policy Act

(P.L. 93-400, as amended) (41 U.S.C. §401 et seq.)

Other Laws2. Policy and Regulation

Executive Orders Office of Management and Budget

Circulars Office of Federal Procurement Policy

(OFPP) Policy Letters Raines’ Rules Federal Acquisition Regulation (FAR)

http://www.acquisition.gov/citizens_fpdsng.cfm

http://www.acquisition.gov/citizens_fpdsng.cfm

2006/7/254

1.2 - Pre-Acquisition Model Example

1

Acquisition Process Model

Cross-reference Matrix

RFPProgram

Objectives(SOO)

ACQUISITION STRATEGY

Contract Type/LengthMajor Milestones/EventsCompetition ApproachBudget/Reqmt Refinement

EvalCriteria

ITO

RD

Proposals

Proposals

Sour

ce

Sele

ctio

n

CONTRACTAWARD &

EXECUTION

SSP Factors

Proposals

RFP DEVELOPMENT

ModelContract

ASP PRAG

POST AWARD PLANNING& RISK MITIGATION

Resources

Schedule

Industry Base

Direction

Technology

Requirements Document

User

Funding

Program Office Size/IMP/IMS/WBSSAMP/Acq PlanEarned Value ManagementDCMC OversightTest Planning/Tech Program MeasuresCDRLs/MetricsIncentive/Disincentive Eval

RiskAssess-

ment

RFP 過程應集中於 RFP 所應涵蓋之“ Requirem

ents” 內容

5

Acquisition Program

Requirements

Technologies

Transition

ACQUISITIONDECISION

IOC

Integrated Engineering & Production(Block I)

S&TProjects

6.5/6.7/Procurement6.1/6.2/6.3 6.3/6.4/6.7

DemonstrationProjects

Disciplined ProcessFlexible Process

ATDs, ACTDs, JWEs,prototyping & risk reduction

The Proposed New Approach

2006/7/256

1.3 - Acquisition 在 Life Cycle 之程序關係 (1)

Disciplined

Flexible

Maturity Level

Maturity Level?????

2006/7/257

1.3 - Acquisition 在 Life Cycle 之程序關係 (2)Technology

Opportunities &User Needs

CRate Production &

DeploymentSystem

IntegrationSystem Demo

Risk Reduction & Demonstration

IOC

Concept & Tech Development

A B B

Review

Review

BA 2 or 3 BA 3 BA 5 BA 5/Proc Proc/Operations & MaintenanceFunding BA 4

Research Category 6.1/6.2/6.3a 6.3a 6.3b 6.4 6.4

Production Readiness & LRIP Support

Technology Maturation

S&T Rolefor software

intensive systems

CommitOutyear Funding

Review

Demonstrated technology Approved ORD & assured interoperability Affordability assessment Strategy in place for evolutionary

approach, production readiness, and supportability

MileStone (MS) C EXIT CRITERIA

AAdvanced

DevelopmentConcept

Exploration

Production & Deployment

Multiple entry points possible depending on technical/concept maturity

Three basic options at each decision point: Proceed into next phase; do additional work; terminate effort

Reviews are in-phase decision/progress points held as necessary

MS A: Initiation of exploration phase

MS B: Demonstration phase.

MS C: Commitment to rapid acquisition.

BLOCK II

BLOCK III

Continuous communication with usersEarly & continuous testing

Technology Transition Technology InsertionBasic Research

34.005-3 Concept exploration contracts

34.005-4 Demonstration contracts.

34.005-5 Full-scale development contracts

34.005-6 Full production

8© 2006, Booz Allen Hamilton, Inc.

Verify &Validate

O&M

Planning &Requirements

Design, Develop, Integrate

Systems Lifecycle

Phase 2 Phase 2

Phase 1Phase 1

Phase 4 Phase 4

Phase 3Phase 3

C&A* Lifecycle* Systems Security Certification and Accreditation

Integrating security engineering into the systems engineering lifecycle enables successful information assurance implementation

AccreditedOperationalCapability

CertifiableFieldableSystem

SecurityComponents

SecurityArchitecture

& DesignSecurity

Requirements

SecurityCONOP

SecurityAssessment& Feedback

UnderstandProblem

Determine Needs

Develop Design

BuildTest &

Integrate Solution

FieldIncrementalCapability

Operation & Maintenance

Assess Operational

Security

Security Lifecycle

ACQUISITION

9© 2006, Booz Allen Hamilton, Inc.

What is Software Acquisition?What is Software Acquisition?

Risk Management

UnderstandThe

AcquisitionNeed

Plan theAcquisition

Strategy

GenerateDetailed

AcquisitionPlans

Solicitation,Evaluation,Negotiation,

Recommendation

Project Tracking & Oversight

完全掌握 User’s Needs 為

Acquisition 成功之根源

2006/7/2510

1.4 - RFP 在籌獲過程 (Acquisition Process) 之關係(Solicitation)(1)Solicitation)(1) Steps In The Solicitation Process

Planning & Requirements

Preparation & Review of

Procurement Package

Issue RFP

Proposal Preparation

Proposal Evaluation

Negotiations

• Formulate Strategies

• Make Plans• Gather/Specify

Requirements• Collaborate w/

Stakeholders• Develop

Evaluation and Scoring Criteria

• Prepare Procurement Package

• Stakeholder Review of Package

• Prepare Request for Proposal

• Solicit Potential Providers• Send RFP to Providers• Screen Providers for

Prerequisites

• Providers Prepare Providers Prepare ProposalsProposals

• Providers Submit Providers Submit ProposalsProposals • Evaluate/Score

Proposals• Solicit Additional

Information (as Desired)

• Solicit Best and Final Offers (as Desired)

• Select Provider(s))

• Update Offers• Seek

Concessions• Alter Terms &

Conditions (asRequired)

• Solicit BAFO

2006/7/2511

1.4 - RFP 在籌獲過程 (Acquisition Process) 之關係(2)

1. Acquisition Planning2. Preparation of procurement request and

package3. Synopsize (advertise) the requirement4. Develop & issue draft solicitation, address

comments, and finalize solicitation5. Issue Solicitation (IFB, RFP, RFO)6. Bid/Proposal/Offer Receipt7. Technical/cost/business evaluation8. Negotiations/discussions, if applicable9. Contract Award

2006/7/2512

1.5- RFP 與 Contract 關係

Requirements

Documented specific

ops needs

Evaluation Contract

Source selection evaluation

guide

Source selection

plan

Source selection

facility

Model contract

(B–J + Att)

CSOW

Sy ste m-level specification

IMP

CWBS

CDRLs

CLINs

MNS/SONORD/CRDCONOPs

STARTEMP

RFPModel

contract (A–K + Att)

Section L-2

Section M

Sys perf rqmts

SOO

WBS

Data rqmts

CLINs

SAMP, Acq Plan or IPS SE Portions

P

cT

A

CLINs

Proposal

erms and cond lauses

Modify

dd (optional)

ropose options

Model contract

(B–K + Att)

Proposal volumes

CSOW

System-level specification

IMP/IMS

IMP risk approach

CWBS

CDRLs

Contractor Team SEPolicies and Practices

Page 13112/05/01 下午 11:33The Johns Hopkins University Applied Physics Laboratory CVISN System Design Description

The ITS/CVO Architecture is Part of the National ITS Architecture

• Architecture is a framework which lays out a blueprint for construction. The architecture defines:

– the functions associated with ITS user services,

– the physical entities or subsystems within which such functions reside,

– the data interfaces and information flows between physical subsystems, and

– the communications requirements associated with information flows.

Architectural Framework: A Way to Manage Complex Systems

Intelligent Transportation Systems (ITS)

Commercial Vehicle

Operations (CVO)

ITS/CVO

CVISN

International Trade

Modernization

Commercial Vehicle

Systems and Networks (CVISN)

Architecture

National ITS Architecture

1 Introduction ITS/CVO in the National Architecture

美國交通部CVISN 計畫以Architecture Framwwork 進行需求想定

美國政府部門之新進趨勢 --“Architecture Framework”

2006/7/2514

2.1-FAR 有關 RFP 之定義FAR 15.203 Requests for proposals.

(a) Requests for proposals (RFPs) are used in negotiated acquisitions to communicate Government requirements to prospective contractors and to solicit proposals.

適用於協商籌獲程序之方式，用以告知有投標意願廠家有關政府之籌獲需求暨徵求建議書。相關購案之 RFP 資訊可由聯邦 Federal Business

Opportunities 無償取得，網址如下：http://www.fbo.gov/spg/USAF/AFMC/AAC/Reference

%2DNumber%2DYUK%2DDSU%2D33%2D2005/Attachments.html

http://www.fbo.gov/spg/USAF/AFMC/AAC/Reference-Number-YUK-DSU-33-2005/Attachments.html

2006/7/2515

2.2- RFP 必須詳述需求 (Requirements)

“需求 (requirements)” 係籌獲者 (Acquirer 或 Agency) 針對使用者 (Users) “ 需要 (Needs)” 解決所面臨“問題(Problems)” 的 Solution 或構想 (Concept) ，因此整個採購或籌獲的最後目標為“… meets user’s needs” 。

RFP 文件中應表述之需求包括：1. 合約之標的物需求：敘述希望獲得之物件 (Products) 及 / 或勞務

(Service) ，以及伴隨之手冊 (Manuals) 與報告 (Reports)2. 標的物之工作 / 執行需求：敘述物件及 / 或勞務之詳細說明

(description) 及 / 或規格 (specification)3. 標的物之包裝需求：敘述包裝、儲放、標示、…等4. 標的物之品質需求：敘述檢視、驗收、品質、可靠度、…等5. 標的物之交付與執行需求：敘述交付時間、地點、方法、…等6. 標的物之法規需求：敘述合約所必須依循法令7. Security Requirements8. …. 等

2006/7/2516

2.3 - “ 需求”之敘述原則 FAR 11.1—SELECTING AND DEVELOPING

REQUIREMENTS DOCUMENTS(i) State requirements with respect to an acquisition of

supplies or services in terms of— (A) Functions to be performed; (B) Performance required; or (C) Essential physical characteristics;

A function specification ： The Government require the contractor to provide a means to get a given mix and amount of traffic across the river. A performance specification: The Government specifies a bridge to carry

that mix and amount of traffic, (but leaves the details to the contractor (suspension or draw, stone or steel, two lane or four) An essential physical characteristic specification: The Government

specifies that it needs a bridge and further specifies interface requirements and known customer preferences, e.g. gray, steel, draw bridge meeting all applicable statutory and regulatory requirements, then the is considered to be. If the Government provides a complete drawing package for the bridge,

then the specification is detail/design.

2006/7/2517

2.4- RFP 屬性1. 對政府最有利 (Best Value)

除價錢之外尚需考量其他因素 (Award based on evaluation factors other than price)

Best Value 之定義 (FAR Part 2 – Definition) “Best value” means the expected outcome of an acquisition that, in the Government’s estimation, provides the greatest overall benefit in response to the requirement.

Consumers Reports is an example of best value determination

可考量之因素 (Evaluation Factors): 執行績效紀錄 (Past Performance) 技術 (Technical) 價格 (Price)

2. 為“權衡選擇”屬性 Tradeoff process (based on evaluation factors )

2006/7/2518

2.5- RFP 為籌獲類型 (Contracting Methods) 之一1. 小額籌獲 (Micro-Purchases, Part 13)：

金額少於 $ 2,500 適用2. 簡易籌獲 (Simplified Acquisitions, Part 13)

金額介於 $ 2,500 至 $100,000 之間適用 >$2,500 但 <$25,000 (3 份報價書 ( 3 bids)) >$25,000 (必須在聯邦籌獲網公告 (Requires publication

notice in FedBizOpps http://www.fbo.gov/)3. 大型籌獲 (Large Contracts )

金額大於 $100,000 以上必須採公開招標籌獲方式 (Bid/Solicitation Types)

Invitation for Bid (IFB, Part 14) – Used for sealed bids– Advertisement is required– Negotiations are not permitted

Request for Proposal (RFP,Part 15)– Used when seeking creativity, different ideas or new

ways of accomplishing a task– Advertisement is required– Negotiations are permitted

2006/7/2519

REFERRED TO ON THE CDRL FORM

Section L (Instructions)Offeror shall provideexperience in developing training programs, etc.

2.6- RFP 之 SPEC-SOW-CDRL-DID 的關係OPERATIONALREQUIREMENT

WORK TO BEPERFORMED

PERFORMANCEPARAMETERS

REQUEST FOR PROPOSAL (RFP)

SPECIFICATION

STATEMENTOF WORK

(SOW)

“3.5 The Vendor shall develop a training planIAW....”

Section M (Evaluation)Specifies importanceof training programs ect.

SECTION CRFP SECTION B

RFP SECTION JCDRL FORM

DD1423CLIN 0004

001............002...........003...........004 Training Plan005............

Training plan

DATA ITEMDESCRIPTION

Training Plan

10. PREPARATION INSTRUCTIONS

REQUEST FOR PROPOSAL (RFP)

SPECIFICATION

STATEMENTOF WORK

(SOW)

“3.5 The Vendor shall develop a training planIAW....”

SECTION C

CLIN 0004

2006/7/2520

SolicitationSolicitation

Sample Tracking of Typical Acquisition Documents

2006/7/2521

3.1- RFP 內容說明 Part I – The Schedule

A. Solicitation/Contract FormB. Supplies or Services and PricesC. Description/Scope of Work/SpecificationD. Packaging and MarkingE. Inspection and AcceptanceF. Deliveries and PerformanceG. Contract Administration DataH. Special Contract Requirements

Part II – Contract ClausesI. Contract Clauses

Part III – List of Documents, Exhibits & Other AttachmentsJ. List of Documents, Exhibits, & Other Attachments

Part IV – Representations and InstructionsK. Representations, Certifications & Other StatementsL. Instructions, Conditions, and Notice to BiddersM. Evaluation Factors for Award

( 以美國國家檔案暨紀錄管理處（ National Archives and Record Administration ，簡稱 NARA ）之 RFP 提供範例 )

22

TRD

Document Flow into the RFP Document Flow into the RFP Parts of an RFP

Section A Solicitation / Contract Form

Section B Supplies or Services / Prices /Costs

Section C Description / Specs / Work Statement

Section D Packaging and Marking

Section E Inspection and Acceptance

Section F Deliveries or Performance

Section G Contract Administration Data

Section H Special Contract Requirements

Section I Contract Clauses

Section J List of Attachments

Section K Contractor Representations & Certifications

Section L Instructions, Conditions, and Notices to Offerors

Section M Evaluation Factors for Award

APB/ADM

ICDCDD

SOO/SOW

Acquisition Strategy Panel (ASP)

MarketResearch

WBSTRD

RiskMgt

EvalCriteria

Acq. Strategy or

Acq. Plan/SAMP

SectionsA - M

(Use to develop)

(Reference)

(Included)

(As Applicable)

2006/7/2523

3.2- Interrelationship Scrub

SOO/SOW

TRD

CDRLS

Section M(evaluation criteria)

Section L(instructions)

Section F(delivery)

Section E(inspection)Section D

(packaging)

Section B(supplies)

Doing work that supports the requirements

SOW establishes tasks; CDRLS specifies document; cross references between

We’re asking for the information that matters to us and we’re evaluating what’s important

Each CLIN has a specified delivery date and place; no conflict in specified dates

What CLINs need inspection or a DD250?

Section G(funding)

ACRNs and fund cites are consistent

Section H (special requirements)

What we ask for and what we evaluate match

All products are covered

2006/7/2524

3.3- RFP Cross Reference Matrix

C = CriticalS = SeriousMo = ModerateMi = MinorN = NegligibleCon = Consequence (importance)Prob = ProbabilityRat = Rating ( High, Medium, or Low)

2006/7/2525

3.4 – 範例說明： NAMA-03-R-0018 買方（ NARA ）所提供文件1. Contract Line Item Number (CLIN) 2. Statement of Objectives (SOO)3. ERA Requirements Document (RD)4. Down-select Criteria5. Contract Data Requirements List (CDRL)6. Non-Disclosure Agreement7. Past Performance Questionnaire8. List of Acronyms9. Award Fee Template10. NARA’s Contractor Interface Methodology11. DD-254 Form12. Program Work Breakdown Structure (PWBS)13. List of Government Furnished Information (GFI)14. Cost Element Structure Data Dictionary15. CDRL Data Item Descriptions and Guidelines16. Program Milestones

2006/7/2526

3.4.1- Section B ：合約之標的物需求 (..\Section B.doc)

SECTION B – Supplies or Services and Price The Contactor shall provide the following products and services. B.1 Contract Base Period

Contract Line Item Number

(CLIN) Supplies and/or Services Quantity Unit Amount

0001 System Analysis and Design: The Contractor shall perform System Analysis and Design of the Electronic Records Archives (ERA) System in accordance with the Statement of Objectives (SOO), Section J, Attachment 1 and Performance Work Statement (PWS) on a Firm Fixed Price basis. Provide data and reports in accordance with the Contract Data Requirements List (CDRL)

1

Lot

$

Firm Fixed Price, System Analysis and Design Phase $

2006/7/2527

3.4.2 - Section C ：標的物之工作 / 執行需求 SOO 範例 (..\Section C.doc) (..\Attachment 1 to Section J.doc)

SOO ExampleProgram Objective: The objective of the XYZ modification is for the offeror to design, test, and manufacture a modification that allows increased reliability and maintainability of the existing ABC system at the most affordable cost to the government.

Contract Objectives:

1.1 Establish the best commercial practices to build and install the XYZ modification on 95 ABC systems without impact to the operational readiness of the XXX fleet.

1.2 Provide flexibility to adapt to contingencies resulting from changing modification schedule and workload requirements.

Management Objective: The management objective is to allow the offeror the maximum flexibility to innovatively manage the projected schedule, performance, risks, warranties, subcontracts, and data to provide the XYZ modification that satisfies the government’s performance requirements.

Note: There is no standard format for

a SOO# 1

2006/7/2528

3.4.3- Section C ：標的物之工作 / 執行需求 SOW 範例 (..\new-sow-test.doc)

1. Software development 2. Conferences and

Reviews .3. Reliability and

Maintainability (R&M) tasks

4. Commercial and Non-Developmental Items (CaNDI)

5. Parts standardization System safety tasks .

6. Electrostatic Discharge (ESD) control

7. Quality management system requirements

8. Product assurance source audits and surveillance inspections

9. System Test and Evaluation (T&E) Integrated Logistics Support (ILS) Program

10. Configuration Management (CM) Program

11. Electromagnetic Environmental Effects (E3)

12. Facility requirements13. IUID Assignment

可說明有關競標商執行工程設計所應涵蓋之工程事項

2006/7/2529

3.5- Section D 、 E 、 F

1. Section D - Packaging and Marking ：標的物之包裝需求：敘述包裝、儲放、標示、…等 (..\Section D.doc)

2. Section E - Inspection and Acceptance ：標的物之品質需求：敘述檢視、驗收、品質、可靠度、…等 (..\Section E.doc)3. Section F - Deliveries or Performance ：標的物之交付與執行需求：敘述交付時間、地點、方法、執行處所…等 (..\Section F.doc)

2006/7/2530

3.6- Section G ：履約監控 (..\Section G.doc)

Contract Administration Data ：由買方指定履約監控代表 Contracting Officer’s Representative (COR) COR 必須確認暨掌控政府端與承約商確實依據合約需求執行確認承約商發票依據交付須知開立監審承約商發票、文檔交付、承約商之執行工時是否確實、專案執行報告是否正確完整監控承約商之工程執行績效專案執行問題提報及改善建議專案執行之工程修改變更、偏異、棄行 ( change, deviation,

or waiver ) 之掌控與了解履約付款之核可、承約商未依約執行之工程扣款執行技術執行暨品質需求之單點實獲值工程管理 (EVMS) 監控及 Integrated Baseline Reviews

(IBRs) 會議代表

2006/7/2531

3.7- Section H ：特殊合約需求 (..\Section H.doc)

Special Contract Requirements 規範承約商參與專案關鍵人員 Key Personnel 之條件規範不得於專案執行特定時間內更換關鍵人員，特殊情形下須經政府之 CO核可方得更換資訊安全查核門禁管制新聞資訊發布權限保密切結專案成員保險專案產品之智財權防毒及禁酒規定工作紀律 …..

2006/7/2532

3.8 - Section I ：合約條款 (..\Section I.doc)

52.204-2 Security Requirements.As prescribed in 4.404(a), insert the following clause:SECURITY REQUIREMENTS (AUG 1996)(a) This clause applies to the extent that this contract involves access to

information classified “Confidential,” “Secret,” or “Top Secret.”(b) The Contractor shall comply with— (1) The Security Agreement (DD Form 441), including the National

Industrial Security Program Operating Manual (DoD 5220.22-M); and (2) Any revisions to that manual, notice of which has been furnished to

the Contractor.(c) If, subsequent to the date of this contract, the security classification or

security requirements under this contract are changed by the Government and if the changes cause an increase or decrease in security costs or otherwise affect any other term or condition of this contract, the contract shall be subject to an equitable adjustment as if the changes were directed under the Changes clause of this contract.

(d) The Contractor agrees to insert terms that conform substantially to the language of this clause, including this paragraph (d) but excluding any reference to the Changes clause of this contract, in all subcontracts under this contract that involve access to classified information.

(End of clause)

2006/7/2533

3.9- Section J ：文件、清單、及其他附件 (..\Section J.doc)

List of Documents, Exhibits, and Other Attachments 1. 計畫目標說明書 Statement of Objectives (SOO) (Attachment 1 to Section J.doc)2. ERA 計劃需求規格書 ERA Requirements Document (RD) (Attachment 2 to

Section J.doc) (requirements.doc)3. 系統分析暨設計階段先期合約選商準則 Down-select Criteria (Attachment 3 to

Section J.doc )4. 合約文件 Contract Data Requirements List (CDRL) (Attachment 4 to Section)

J.doc)5. 保密切結書 Non-Disclosure Agreement (Attachment 5 to Section J.doc)6. 廠商專案執行記錄 Past Performance Questionnaire (Attachment 6 to Section

J.doc)7. 縮寫字 List of Acronyms (Attachment 7 to Section J.doc)8. 獎勵金計算範例 Award Fee Template (Attachment 8 to Section J.doc)9. NARA’s Contractor Interface Methodology (Attachment 9 to Section J.doc)10. DD-254 Form (Attachment 10 to Section J.doc)11. 計畫工作分解結構 Program Work Breakdown Structure (PWBS)

(Attachment 11 to Section J.doc)12. 政府文件 List of Government Furnished Information (GFI) (Attachment 12

to Section J.doc)13. 工程定義 Cost Element Structure Data Dictionary (Attachment 13 to Section

J.doc)14. 合約文件標準格式 CDRL Data Item Descriptions and Guidelines

(Attachment 14 to Section J.doc)

2006/7/2534

3.10- Section Ｋ、 L (..\Section K.doc) (..\Section L.doc) Section K ： Representations, Certifications &

Other Statements of offerors or respondents 要求競標商提示相關證照、認證之需求

Section L ： Instructions, conditions, and notices to offerors or respondents 告知廠家有關準備競標建議書 (RFP 、 IFB) 或廠家資訊

(RFI) 之格式可包括：

管理組織資訊 Administrative;工程管理建議書 Management;技術建議書 Technical;履約紀錄 Past performance; 及價格建議書 Cost or pricing data

2006/7/2535

3.11- Section M ：說明選商準則 (Section M.doc)Evaluation factors for award ：1. Minimum Requirement for Acceptability

Failure to provide evidence OF SW-CMM/CMMI Level 3 (or higher) compliance shall result in the Offeror’s proposal being rejected.

2. Basis of Award Factor (1) - Technical,

Subfactor 1, Technical Solution Subfactor 2, System and Software Engineering Methodology

Factor (2) - Management, Subfactor 1, Management Team Subfactor 2, Management Plan and Approach

Factor (3) - Past Performance and Factor (4) - Cost/Price.

Base Contract Price Options- Cost reimbursement and Award Fees

2006/7/2536

4.1- RFP 選商準則 Evaluation Criteria

Most important, most difficult, develop first Represents about 95% of entire acquisition strategy Rules of selection; forms a pact with offerors:

“Say what you are going to do in Sec M; then, during source selection, do what you said you were going to do.”

Failure to follow what you said you were going to do in Section M is the leading cause of sustained protests

Evaluation Criteria are included in the Source Selection Plan, which must be approved by the Source Selection Authority

2006/7/2537

4.2- Evaluation Process

Evaluation Criteria

+Proposal

Meets Req’t (Criteria)

Exceeds Req’t (Criteria)

Does Not Clearly Meet Req’t (Criteria)

Does Not Meet Req’t (Criteria)

“Suggested”Strength (Benefit)

“Suggested”Proposal Inadequacy

“Suggested”MC Deficiency

“Recommended”EN

?

Advisor Recommendations via “Comments”

May involve reviewing

several parts of the

proposal!

“Recommended”EN

38

Data & Analysis Center for Software (DACS)

Software Acquisition for Software Intensive Systems

AFRL Information Directorate

Technical Proposal EvaluationTechnical Proposal Evaluation General Criteria for Technical Proposal Evaluation

(2) Adherence to Relevant FARs Key Personnel Resumes Oral Presentations

Bidders are Evaluated Against Point Assignment Criteria

Rating (R):Excellent = 90-100 Good = 80-89 Acceptable = 70-79 Marginal = 60-69 Unacceptable = 0-59

http://www.mccabe.com/metrics.php

39




Technical Proposal EvaluationTechnical Proposal Evaluation Proposal Categories of Weight/Rating/Score

Technical Management Past Performance Price


40




Technical Proposal EvaluationTechnical Proposal Evaluation Example of Proposal Scores

Score Price Score ePerformancPast Score Management Score Technical Score Final

Price ProposalCurrent PriceLowest * Weight Price Score Price

:Score Price gDetermininfor Formula Generic

Note that, for this example, Past Performance is a pass/fail factor


41




Best Value AnalysisBest Value Analysis “Best Value” = Government Cost/Technical Trade-

Off Analysis to Determine Best Value Bidder Proposal

Best Value FormulaQuinn, David P., “Best Value Formula”, Crosstalk, August 2002, pp. 26-28

WeightePerformancPast Weight Management Weight TechnicalScore ePerformancPast Score Management Score Technical Ratio ValueBest

WeightPrice * RatioFactor Best Factor ValueBest

Evaluated Being PriceCurrent BidLowest *Factor ValueBest Score) Price(or Score ValueBest


42




Best Value AnalysisBest Value Analysis Example of Best Value Analysis Results

- Quinn, David P., “Best Value Formula”, Crosstalk, August 2002, pp. 26-28

Best Value Analysis shifted award away from

“low ball” cost bidder (Bid 5) to bidder with highest technical/management

scores (Bid 3) resulting in best value for the

government (lowest program risk at most

reasonable price)

Use MS Excel file“Best Value Analysis for Acquisition.xls” to perform Best Value Analysis


43




Evaluating and Recording Contractor PerformanceEvaluating and Recording Contractor Performance Contractor

Past PerformanceReport (Front Page)

Circle rating in far right column and provide a brief narrative for each of the categories rates. Indicate the contract

requirements that were exceeded or not met by the Contractor, and by how much. Then, calculate the mean score

of the ratings.


44





Past PerformanceReport (Back Page)

Adjust the ratings assigned in Block 7, if appropriate, based on any

comments, rebuttals, or additional information provided by the Contractor

and, if necessary, by the agency review. Calculate the adjusted mean

score of the Contractor’s performance

8. Key Personnel (Attach any comments for each of the key personnel – Optional) Name:___________________________________ Employment Date:_______________ Project Manager Name:___________________________________ Employment Date:_______________ Name:___________________________________ Employment Date:_______________ 9. Would you select this contractor again? Please explain. (For contract completion

only) 7

10. _____________________________ _____________________________________ Contracting Officer Representative (Print) Signature _____________________________ _____________________________________ Phone/Fax Date _______________________________ _____________________________________ Contracting Officer (Print) Signature _______________________________ _____________________________________ Phone/Fax Date 11. Contractor Review. Are comments, rebuttals or additional information provided? ( ) No ( ) Yes Please attach comments.

_______________________________ _____________________________________ Contractor Name (Print) Signature _______________________________ _____________________________________ Phone/Fax Date If no contractor rebuttal was received, no further action is required. Report is final based on signatures and ratings in Blocks 10 and 7, respectively 12. Agency Review. Were Contractor comments reviewed at a level above the

Contracting Officer? ( ) No ( ) Yes Please attach comments

13. Final Ratings. Re-assess ratings given in Block 7 and revise, if appropriate. Quality____ Cost Control____ Timeliness____ Business Relations____ Customer Satisfaction____ Mean Score (Add the above ratings and divide by number of areas rated): _______________________________ _____________________________________ Supervisory Contracting Officer (Print) Signature _______________________________ _____________________________________ Phone/Fax Date


45





Past PerformanceRating Guidelines

This area defines This area defines the attributes being the attributes being looked for in each looked for in each

of the five of the five categoriescategories

This area defines This area defines the level of the level of Contractor Contractor

performance in performance in meeting those meeting those

attributesattributes

BONUSBONUS


2006/7/2546

5.1- 南科減振工程法律適用的探討 “….. 針對這種只有任務目標，而解決方案無法事先規範的重大公共工程籌獲，美國聯邦籌獲法 (FAR—Federal Acquisition Regulation)特立專章於其 34 章 (Part 34) 中對於重大系統籌獲 (Major System

Acquisition) 以及 35 章 (Part 35) 中對於研究發展合約 (Research and Development Contracting) 詳加規定。”

? Market Research

Market Research: a continuous process

for gathering data

plus analysis of that data

PRODUCTCHARACTERISTICS　　　　　　 SUPPLIERS’

CAPABILITIES

MARKET LEVERAGE &

BUSINESS PRACTICES

2006/7/2547

5.2- 某公共工程案例 -軟體可靠度 MTBF(1)

No. of Failure(r) Test Ratio(M) Total Test Time(hr)0 2.3026 40,000*2.3026=92,240(hr)1 3.8897 40,000*3.8897=155,5882 5.3223 40,000*5.3223=212,8923 6.6808 40,000*6.6808=267,2324 7.9936 319,7445 9.2747 370,9886 10.5321 421,2847 11.7709 470,8368 12.9947 519,7889 14.2060 568,240

10 15.4088 616,352• 依據上述 MTBF 需求、 180 天 (4320 hours)Demonstration Test 與 GEM 表格，單一中央資料處理系統 (20,000 hours MTBF) 要達到 92,104 hours “0”

failure 之允收標準將是一項 non-feasible 之 test item

• 某公共工程之規格書需求：『包含軟體錯誤之所有關聯故障均應納入驗證平均故障間隔週期 /平均故障時間之計算。』及『中央資料處理系統MTBF = 20,000 小時』

• 前述需求依據可信度 90% 之 GEM (General Exponential Model) table ：

2006/7/2548

5.2- 某公共工程案例 -軟體可靠度 MTBF(2)

HardwareRequirements

Analysis

SystemRequirementsAnalysis and

Design

HardwarePreliminary

Design

HardwareDetailedDesign

Fabrication HWCI Test SystemIntegrationand Test

SoftwareRequirements

Analysis

SoftwarePreliminary

Design

SoftwareDetailedDesign

Codingand Unit

Test

CSCIntegration

Test CSCI Test

SystemReliability

Requirements

System HW/SW

ReliabilityModel

System HW/SW Reliability

Allocations

ReDesign Activity

Design Activity

HW/SWReliability

Predictions

Progress Evaluation

AssessmentReport

Program Review Board Activity

HW/SW Growth Testing

Evaluate Growth

HW/SWDemo Test

EvaluateResults

AssessmentReport

Design Correction

Reallocation Needed

Reassign Resources

Not OK

To Program Managerand Engineering Manager

To Program Manager and Engneering manager

硬體發展

軟體發展

軟體品質因子(MTBF)

2006/7/2549

2006/7/2550

RFP 之特殊說明Subchapter F 特種簽約類型 (Special Categories of Contracting) Part 34 主要系統籌獲 (Major System Acquisition)

34.005-3 Concept exploration contracts. 34.005-4 Demonstration contracts. 34.005-5 Full-scale development contracts. 34.005-6 Full production.

Part 35 研究發展籌獲 (Research and Development Contracting)Part 36 工程營造及建築籌獲 (Construction and Architect-Engineering Contracts)Part 37 服務籌獲 (Service Contracting)Part 38 聯邦政府經常性供給籌獲 (Federal Supply Schedule Contracting)Part 39 資訊資源籌獲 (Acquisition of Information Resources)Part 40 (保留 )Part 41 公用設施服務籌獲 (Acquisition of Utility Services)

2006/7/25 51

Market

Research

Yes

Roadmap to the Commerciality Determination

Need canbe modified? Need can

be modified?

CommercialItem?

No

Conduct Part 12Commercial Item

Solicitation

Yes

No

Do NotConductPart 12

SolicitationYes

NewDevelopment

No

YesN

o

NEED

NDI

27 of 28

2006/7/2552

RFP 與 Performance based RFP

The primary elements of a typical RFP may include:1. Statement of Work 2. Specification 3. CDRL 4. Work Breakdown Structure 5. Contract Schedule

Or in a perfomance based contracting approach the RFP may include:

1. Statement of Objectives 2. Systems Requirement Document 3. Guide specification 4. CDRL 5. Work Breakdown Structure 6. Contract Schedule

2006/7/2553

與 RFP 有關之 FAR parts

Acquisition Planning (Part 7), Market Research (Part 10), Description of needs (Part 11), and Contract administration (Part 42).

2006/7/2554

Spiral Model

• 在 Development 過程為 Water Fall Model

• By Boehm, 1988 (TRW)• Risk Management Focused• End requirements not known

但 Spiral Model 對於EVMS 有極大的 Impact