國防科技專案管理(iv) f

2007/07/06 1

國防科技專案管理 (IV) - 政府與企業體籌獲需求規劃與專案管理

國防工業發展協會科技顧問(2007 年 7 月 ) 尹守紀

E-mail:[email protected]

2007/07/06 2

Part IV- 美國國防籌獲系統之『專案管理』

2007/07/06 3

目錄1. 美國國防部之 PMBOK 版本2. WBS 在專案管理之角色：界定出 Project 的“ Products”3. EVMS 在專案管理之角色：針對“ cost” 、“ schedule” 、“ work

scope”的 Performance Management4. 與籌獲管理相關之要求：

1) 工程管理採用 IPPD2) 生命週期模式採用 EASD （ Evolutional Acquisition & Spiral

Development)3) 基於模擬的採購 SMA4) 要求採用績效服務採購 PBSA5) 志願性共識標準 Voluntary Consensus Standards （ VCS)6) 專案管理之教育訓練

5. 專案管理實例Attachment：美軍武器系統籌獲程序 (Procurement Management) - 「徵求建議書 (RFP) 架構」

2007/07/06 4

1.1- U.S. Department of Defense Extension to: A Guide to the Project Management Body of

Knowledge (PMBOK® Guide) 2003 年美國國防部以 2000 年版本之 PMBOK 發行國防部的擴充版本，該版本除延續 PMBOK之 9 大 knowledge area ，另增訂5 項國防系統之需求：

- Project Systems Engineering Management- Project Software Acquisition Management- Project Logistics Management- Project Test and Evaluation Management- Project Manufacturing Management

“Chapter 4 Project scope management” 係針對聯合能力整合與發展系統 (JCIDS) “Chapter 7 Project cost management” 係針對規畫、計畫、預算與執行制度 (PPBE) “Chapter 12 Project procurement management” 係針對國防籌獲系統 DoD 5000 Series 另於 Defense Acquisition Guides 文件中有 PMBOK 其他

chapters 之導引各項 Knowledge area 必須反映於 RFP或 Contract ，否則失去其管理意義

2007/07/06 5

U.S. Department of Defense Extension to: A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

The Project Management Knowledge Areas：

4. Project integration management

5. Project scope management6. Project time management7. Project cost management 8. Project quality management9. Project human resource

management10. Project communication

management11. Project risk management12. Project procurement

management

2007/07/06 6

U.S. Department of Defense Extension to: A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

Defense Acquisition Knowledge Areas：

13. Project Systems Engineering Management

14. Project Software Acquisition Management

15. Project Logistics Management

16. Project Test and Evaluation Management

17. Project Manufacturing Management

2007/07/06 7

1.2- Acquisition Framework： Little “A” and Big “A”

聯合能力整合與發展系統(JCIDS)

CJCS 3170.01C24 June 03

Chapter 4 ： Project scope management

Chapter 7 ：Project cost management

Chapter 12 ： Project procurement management

國防籌獲系統Defense

AcquisitionSystem

DoD 5000 Series12 May 03 Revision

規畫、計畫、預算與執行制度 (PPBE) PPBE

22 May 03

2007/07/06 8

1.3-Defense Acquisition Guidebook

2007/07/06 9

1.3-Defense Acquisition Guidebook

2007/07/06 10

1.4-Project integration management在RFP 之章節

Section J Contract Data Requirements ListCDRL： xxxxTITLE： Earned Value Management Data FREQUENCY：Monthly, beginning one (1) month following contract award. To be delivered on thirteenth (13th) business day following the close of the developer’s fiscal month. COMMENTS： In accordance with Section J, Attachment 14, CDRL Data Item Descriptions and Guidelines, Earned Value Management Data (EVM) Guidelines

Section G – Contract Administration DataG-9 Earned Value management System (EVMS) Assessment“…Contractor shall show evidence of approval of their EVMS process on an annual basis. The goal of the monitoring will be to ensure that the developer’s EVMS processes are being followed and that those processes comply with EIA Standard EIA- 748-A, Earned Value Management Systems, January 2002. …”

2007/07/06 11

2.1- 專案與Work、 Cost、 Schedules、 Products、…

1. 有『工（ Works）』才有『價（ Cost）』，因此 Contractors 必須將公司執行各種屬性合約所必須參與的『工』於 Proposal 階段反映至 RFP 中的“ Statement of Works（ SOW）” 2. 政府採購可在『工作分解結構（Work Breakdown Structures

(WBS)）』的 Level-2 中敘述可引用的『工』，諸如一般在 MIL-HDBK-881 中所提及的“ WBS Common elements” ：1) integration, assembly, test, and checkout efforts2) systems engineering and program management3) training 4) data 5) system test and evaluation 6) peculiar support equipment7) common support equipment8) operational and site activation9) industrial facilities 10)initial spares and repair parts

2007/07/06 12

專案與Work、 Cost、 Schedules、 Products、…

3. “ Systems Engineering ” 一項可包括： value engineering, configuration management, Human Systems Integration (Human factors engineering; Personnel; Habitability; Manpower; Training; Environment, Safety and Occupational Health; Survivability), vulnerability, maintainability, reliability, standardization, system analysis, logistic support analysis, etc.

4. “ Program Management” 一項可包括： Cost, schedule, performance measurement management, warranty administration, contract management, data management, vendor liaison, subcontract management, etc.

5. “ SOW” 不敘述與 Requirements 相關的Performance、 technical 、定性與定量規格

2007/07/06 13


6. Requirements 相關的 Performance、 technical standards於 Specification 中或 Requirements Documents 中敘述

7. 合約採購之數量於 RFP之 Section B – Supplies or Services and Price 中敘述

8. 對於需求不是很明確之購案，以採用 Statement of Objectives (SOO) 方式敘述其 Goals and outcomes ，將SOW 交由 Offer 完成，此通常配合 Evolutional Acquisition Model 執行

9. SOO 不屬於合約內容（屬於 RFP Part L ），一般建議以 4 頁之內完成，其內容應滿足 mission need statement, operational requirement document, program management directive, acquisition strategy 等之範圍，採用 SOO 方式，等於保留給 Offer 最大的發揮空間，特別是在成本方面

2007/07/06 14


10. “ 工”必須以“ products” 顯現，包括文件類（諸如 SRS、 SDD、 SDDD、 ICD、…）、裝備類（諸如 PC 、測試儀具、）、工程類（諸如 system engineering、 software engineering ）

11. 文件類的 products 必須於 Proposal 中敘述所參用的 Data Item Description

12. 裝備類的 products 必須於 Proposal 中敘述所參用的Standards （諸如 safety 可參用 MIL-STD-882C 、 power 可參用 MIL-STD-704D、…）

13. 工程類的 products 必須於 Proposal 中敘述所參用的Standards （諸如 IEEE/EIA-12207、 ISO/IEC-15288、 ANSI/EIA-632、…）

2007/07/06 15


14) 各項“ products ” 應於 schedule 中標定完成日期，並於相關 review/audit 中進行審查（諸如 SRR 必須審查Software Requirements Specification、 PCA 必須稽核生產件、 .. ）

2007/07/06 16

2.2- WBS在 Project Management 之角色 PMP 重点专题的深入学习 (WBS, EVM)

“PMI 比较强调两个的知识要点 WBS, 和 EVM. WBS 几乎是所有 process 的基本 , 而 EVM 的方法和工具 , 又是贯穿于所有 Process 的脉络 . 可以通过研究 PMI 提供的best practice 或者 NASA 的网站上获取更广泛的 study material. ”

The WBS provides the framework for program and technical planning, cost estimating, resource allocation, performance measurement, technical assessment, and status reporting. In particular, the contract WBS provides the reporting structure used in contract management reports (such as cost performance reports or reports in the contractor cost data reporting (CCDR) system).

2007/07/06 17

2.3- Work Breakdown Structure:The Key to Integration

WBSWBS

100

1

Risk ProfileProgress Plan

COST SCHEDULE

TECHNICALPERFORMANCE RISK

MIL-HDBK-881

2007/07/06 18

What、Who、 How、When

2007/07/06 19

Convert WBS to Schedule (IMP & IMS)

Requirement WBS Elements SOW Task

System Specification

1000 Air Vehicle

1100 Airframe

1110 Wing

1000 Air Vehicle

1100 Airframe

1110 Wing••

1189 Landing Gear

3.1 Air Vehicle (WBS 1000)

Design, develop, produce and verify, complete air vehicles, defined as airframe propulsion, avionics and other installed equipment.

Integrated Master Plan

Management Plan Events Accomplishment Criteria1.Preliminary Design Review PDR 1.a. Duty Cycle Defined

b. Preliminary Analysis Complete

Integrated Master Schedule

Detailed Tasks 20XXProgram Events

1. Preliminary Design completeDuty Cycle Defined

20XX 20XX

PDR CDR

20XX 20XX

Requirement WBS Elements SOW Task

System Specification

1000 Air Vehicle

1100 Airframe

1110 Wing

1000 Air Vehicle

1100 Airframe

1110 Wing••

1189 Landing Gear

3.1 Air Vehicle (WBS 1000)

Design, develop, produce and verify, complete air vehicles, defined as airframe propulsion, avionics and other installed equipment.

Integrated Master Plan

Management Plan Events Accomplishment Criteria1.Preliminary Design Review PDR 1.a. Duty Cycle Defined

b. Preliminary Analysis Complete

Integrated Master Schedule

Detailed Tasks 20XXProgram Events

1. Preliminary Design completeDuty Cycle Defined

20XX 20XX

PDR CDR

20XX 20XX

2007/07/06 20

WBS code field

由 CWBS轉換為MS-Project圖 (Gantt Chart)

2007/07/06 21

“ Managerial levels” v.s. “Technical levels”

Level Description

ManagerialLevels

TechnicalLevels

123

456

Total ProgramProject

Task

SubtaskWork Package

Level of Effort

Proj

ect S

umm

ary

WB

SC

ontra

ct W

BS

2007/07/06 22

CWBS 由 PWBS Level-3開始銜接Relationship of Program WBS with Contract WBS

PROGRAM WBS1 2 3 4 5FX AIRCRAFT

AIR VEHICLEAIRFRAMEPROPULSION (SK-PW-52D)COMMUNICATIONS/IDENTIFICATION

NAVIGATION/GUIDANCEFIRE CONTROL

RADARRECEIVERTRANSMITTERANTENNARADAR APPLICATIONS S/W (TO CSCI LEVEL)RADAR SYSTEM S/W (TO CSCI LEVEL)RADAR INTEG, ASSY, TEST AND CHECKOUT CONTRACT WBS

SYSTEMS TEST AND EVALUATION 1(3) 2(4) 3(5) 4(6) 5(7)

DEVELOPMENT TEST AND EVALUATION FIRE CONTROLOPERATIONAL TEST AND EVALUATION RADARMOCKUPS RECEIVERTEST AND EVALUATION SUPPORT TRANSMITTERTEST FACILITIES ANTENNA

SYSTEMS ENGINEERING/PROGRAM MANAGEMENT RADAR APPLICATIONS S/WSYSTEMS ENGINEERING BUILD 1PROGRAM MANAGEMENT CSCI 1...nACQUISITION LOGISTICS CSCI TO CSCI INTEG. AND CHKOUT

PECULIAR SUPPORT EQUIPMENT BUILD 2...nTEST AND MEASUREMENT EQUIPMENT CSCI 1...nSUPPORT AND HANDLING EQUIPMENT CSCI TO CSCI INTEG. AND CHKOUT

COMMON SUPPORT EQUIPMENT RADAR APPLICATIONS S/W INTEG., ASSEMBLY, TEST, & CHKOUT TRAINING RADAR SYSTEM S/W

MAINTENANCE TRAINING BUILD 1AIRCREW TRAINING DEVICE CSCI 1...nTRAINING COURSE MATERIALS CSCI TO CSCI INTEG. AND CHKOUT

DATA BUILD 2...nTECHNICAL PUBLICATIONS CSCI 1...nENGINEERING DATA CSCI TO CSCI INTEG. AND CHKOUTMANAGEMENT DATA RADAR SYSTEM S/W INTEG. ASSEMBLY, TEST AND CHECKOUTSUPPORT DATA RADAR INTEG., ASSEMBLY, TEST AND CHECKOUTDATA REPOSITORY PLATFORM INTEGRATION

OPERATIONAL/SITE ACTIVATION SYSTEMS ENGINEERING/PROGRAM MANAGEMENTCONTRACTOR TECHNICAL SUPPORT SYSTEM TEST AND EVALUATION

INITIAL SPARES AND REPAIR PARTS TRAININGDATAPECULIAR SUPPORT EQUIPMENTCOMMON SUPPORT EQUIPMENTINITIAL SPARES AND REPAIR PARTS

PWBS的Level-3為CWBS的Level-1

WBS/ 23/9180

“ Family tree“ 是一種圖示表達方式，輔助讀者易於了解下層Components 如何組成上層

Components。“ Major Element”, or

“Prime Mission

Equipment”, or “Prime Mission

Product”

Common WBS

Elements

Aircraft SystemsWork Breakdown Structure 範例

Aircraft System

Air Vehicle Training Peculiar Support

Equipment

SystemT&E

Sys Eng./ Program

Mgmt

Data Opn'l/SiteActivation

CommonSupport

Equipment

IndustrialFacilities

InitialSpares

& RepairParts

Level 1(Program Level)

Level 2(Project Level)

Equipment

Services

Facilities

DT&E

OT&E

Mockups

T&ESupport

TestFacilities

Construction/Conversion/Expansion

EquipmentAcquisitionor Mod

Maintenance

Level 3(System Level)

AirframePropulsionApplication SoftwareSystem SoftwareComm's/IdentificationNavigation/GuidanceCentral ComputerFire ControlData Display & ControlsSurvivabilityReconnaissanceAutomatic Flight ControlCentral IntegratedCheckoutAntisubmarine WarfareArmamentWeapons DeliveryAuxiliary Equipment

Test &MeasurementEquipmentSupport &HandlingEquipment

TechPubsEngDataSupportDataManagementDataDataDepository

Test &MeasurementEquipmentSupport &HandlingEquipment

Sys Assembly,Installation &Checkout onSiteContractorTech SupportSiteConstructionSite/ShipVehicleConversion

“ Major Program

”

2007/07/06 24

By Functional Approach - General

FireControl

Training

Contract WorkBreakdown Structure

ApplicationsS/W

ReceiverGroup

Radar

Antenna

Receiver SidelobeCanceller

ControlAccount

ControlAccount

ControlAccount

MechanicalDesign

ElectricalDesign

Drafting/Checking

Work Packages

FunctionalOrganization

Level 1

Level 2

Level 3

Note: This example depicts a functional organization. It could easily be any other type of organization structure.

Level 4

FireControl

Training


ApplicationsS/W

ReceiverGroup

Radar

Antenna


ControlAccount

ControlAccount

ControlAccount

MechanicalDesign

ElectricalDesign

Drafting/Checking

Work PackagesWork Packages


Level 1

Level 2

Level 3



Level 4

Functional Group

Control Account

每一 Control Account 可涵括數個work

package

2007/07/06 25

By Functional Approach - CSCI Fire

Control

Training


ApplicationsS/W

ReceiverGroup

Radar

Antenna


ControlAccount

ControlAccount

ControlAccount

S/W QualityAssurance

S/W Engineering

S/W ConfigControl


Level 1

Level 2

Level 3

Level 4

CSCI 1 CSCI 2 CSCI 3Requirements

Analysis(Job Code xxx.SW_)

Design(Job Code xxx.SW_)

Work PackagesCode & Test

(Job Code xxx.SW_)Integration &

Test(Job Code xxx.SW_)

FireControl

Training


ApplicationsS/W

ReceiverGroup

Radar

Antenna


ControlAccount

ControlAccount

ControlAccount

S/W QualityAssurance

S/W Engineering

S/W ConfigControl


Level 1

Level 2

Level 3

Level 4

CSCI 1 CSCI 2 CSCI 3Requirements

Analysis(Job Code xxx.SW_)

Design(Job Code xxx.SW_)

Work PackagesCode & Test

(Job Code xxx.SW_)Integration &

Test(Job Code xxx.SW_)

Functional Group

表述 CSCI相關之Phase

Activities

System Breakdown Structure (SBS)

2007/07/06 26

Software Project WBS

Build(1..N)

CSCI #1

CSCI #2

CSCI #3

CSCI to CSCIIntegration &

Check out

Coding &Design Entity

TestingDesignRequirements

AnalysisDesign EntityIntegration &

TestingCSCI

TestingSPCR

Resolution

Design EntityRe-integration

& Testing

Recoding &Design Entity

TestingRedesign

LL SOFTWARE WBS ELEMENTS

Subsystem#N

PMPApplicationSoftware

AIRCRAFTSYSTEM

HardwareComponent

Prime MissionProduct (PMP)

Subsystem#N + 1

SoftwareComponent

PMPSystem

Software

Integration,Assembly, Test

& Checkout

LL LL

LL

LL = Lower Lever ExtensionCSCI = Computer Software Configuration ItemSPCR = Software Problem Change ReportDesign Entities = Computer Software Components, Objects, Modules, etc.

標示出 Software Life Cycle 相關

Phase

2007/07/06 27

System of Systems (SoS) Generic WBS Level 1 Level 2 Level 3 Level 4System of Systems

Aircraft SystemAir Vehicle (AV)

Reference Appendix A – Level 3Systems Engineering/Program ManagementSystem Test and Evaluation

Development Test and EvaluationOperational Test and EvaluationMock-upsTest and Evaluation SupportTest Facilities

TrainingData

•Electronic/Automated Software System

•Prime Mission Product (PMP)•Reference Appendix B – Level 3

•Platform Integration•Systems Engineering/Program Management•System Test and Evaluation

•Development Test and Evaluation•Operational Test and Evaluation•Mock-ups/System Integration Labs (SILs)•Test and Evaluation Support•Test Facilities

•Training•Equipment•Services•Facilities

2007/07/06 28

System of Systems (SoS) Generic WBS Level 1 Level 2 Level 3 Level 4

• Data

UAV SystemAir Vehicle

Reference Appendix H– Level 3Payload (1….n)

Reference Appendix H– Level 3Ground Segment

Reference Appendix H– Level 3UAV System Integration,

Assembly, Test and Checkout

Systems Engineering/Program Management

System Test and EvaluationSystem of Systems

Engineering/Program Management

System of Sys Test and Evaluation

Development Test and Evaluation

Operational Test and Evaluation

Mock-ups/System Integration Labs (SILs)

Test and Evaluation SupportTest Facilities

Initial Spares/Repair Parts

2007/07/06 29

By IPT approach

FireControl

Training


ApplicationsS/W

ReceiverGroup

Radar

Antenna


ControlAccount

ControlAccount

ControlAccount

MechanicalDesign

ElectricalDesign

Drafting/Checking

Work Packages

IPTOrganization

Level 1

Level 2

Level 3

Des

ign

Man

ufac

turin

gS

E/P

MTe

st

Rad

ar IP

T

Level 4

FireControl

Training


ApplicationsS/W

ReceiverGroup

Radar

Antenna


ControlAccount

ControlAccount

ControlAccount

MechanicalDesign

ElectricalDesign

Drafting/Checking

Work PackagesWork Packages

IPTOrganization

Level 1

Level 2

Level 3

Des

ign

Man

ufac

turin

gS

E/P

MTe

st

Rad

ar IP

T

Level 4

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. 302007/07/06 PC Docs 53460

PEODeputy PEO

Technical Director

Air Vehicle IPT

Autonomic LogisticsIPT

PropulsionIPT

Operations Contracting Security InternationalField Site Directors

Senior War Fighters[1/Service] (SMO-JSF, DCS(A), N-78, InternationalPartners)

Not co-located with main office

ContractorSite

Director

BFM

Integrated TestForce

Systems EngineeringIPT

Legal Public Affairs

International Participation in JSF Management Structure

Executive Committee (EC)

http://www.fotw.net/images/a/au.gif



2007/07/06 31

CWBS Dictionary 範例 WORK BREAKDOWN DICTIONARY

CONTRACT NUMBERIndex Item No. 2 WBS Level 2 F33657-72-C-0923

WBS ELEMENT

A10100

WBS TITLE

Air Vehicle

Specification No.

689E078780028

DATE Revision No. Revision Auth Approved Chg

SPECIFICATION TITLE:Prime Item DevelopmentSpecification For AGM 86A Air Vehicle/Airframe

ContractLine Item:

0001, 0001AA, 0001AB, 0001AC, 0001AD0001AE, 0001AF, 0001AG, 0001AH

ELEMENT TASK DESCRIPTIONTechnical Content:The Air Vehicle element task description refers to theeffort required to develop, fabricate , integrate and testthe airframe segment, portions of the Navigation/Guidance element, and Airborne Development TestEquipment and Airborne Operational Test Equip-ment and to the integration assembly and check-out of these complete elements, together with theEngine Segment, to produce the complete Air Vehicle.The lower level elements included and summarizedin the Air Vehicle element are: Airframe Segment (A11100), Navigation/Guidance Segment (A32100), Airborne Development Test Equipment (A61100, and Airborne Operational Test Equipment (A61200)

COST DESCRIPTIONMPC/PMC Work Order/Work Auth

A10100 See lower level WBS Elements

Applicable SOW Paragraph:3.6.2

Cost Content - System Contractor

The cost to be accumulated against this element include a summarization of all costs required to plan, develop,fabricate, assemble, integrate and perform developmenttesting, analysis and reporting for the air vehicle. It also includes all costs associated with the required efforts inintegrating, assembling and checking our GFP requiredto create this element.

2007/07/06 32

CWBS 格式 :CWBS Dictionary

CONTRACT WORKBREAKDOWN STRUCTURE

DICTIONARY

PROGRAM: LF - 08Project NVZR-97-9934

RFP NO: DO 03CONTRACT: 01-D-8966

DATE:1 Jun 03

LEVEL OF CWBS CWBS ELEMENT CWBS DEFINITION

Level 3 01.A1.03.01Work Plan - This element includes all preparatory work including word processing, CAD drawings, editing, and management review and approval.

Cost content - $4,500 - Labor - 63 man-hours and $3,780 - Support - $720 - Analysis - N/A - Travel - N/A

Subcontractor - N/A“ CWBS Definition” 敘述每一 CWBS element 的 “ technical” 與” cost”內容 . 包含 efforts, tasks, tests, components,… 等

預算金額

預劃工時

工作事項

2007/07/06 33

“CWBS Index” 範例#

CWBS ELEMENT CWBS CODE CONTRACT LINE ITEM(S)

STATEMENT OF WORK (SOW) PARAGRAPH

NUMBER(S) PHASE and LEVEL NAME

1 2 3 4 5 6 1 2 3TL DO Summary Top Line 99 NA (SUMMARY)1 DO Sum-Project 7002-XYZZ A1 N/A (SUMMARY)2 X X Site Investiation OU-2 01.A1 N/A (SUMMARY)3 X Project Management 01.A1.02 CLIN 0001 3.1.14 X Proj Mgmt/Support/Admin 01.A1.02.01 CLIN 0001 3.1.1.35 X Community Relations 01.A1.02.02 CLIN 0001 3.1.1.56 X Preparation of Plans 01.A1.03 CLIN 0001 3.27 X Work Plan 01.A1.03.01 CLIN 0001 3.2.18 X X Feasibility Study OU-2 02.A1 N/A (SUMMARY)9 X Project Management 02.A1.02 CLIN 0001 5.1.110 X Proj Mgmt/Support/Admin 02.A1.02.01 CLIN 0001 5.1.1.311 X Community Relations 02.A1.02.02 CLIN 0001 5.1.1.512 X Preparation of Plans 01.A1.03 CLIN 0001 5.213 X Work Plan 01.A1.03.01 CLIN 0001 5.2.1

2007/07/06 34

Mapping WBS for Cost Management

ORGANIZATION

WBS• Plan• Budget• Schedule• Corrective Action

CAs under IPTs as appropriate

2007/07/06 3535© Northrop Grumman Corp, All Rights Reserved. Presenters: R. Scordino / F. Fontanet.

Example IMP Structure

IMP Reference Number: - First Digit- Event- Second and Third Digit - SA- Fourth and Fifth Digit- Criteria- Sixth to Ninth Digits- WBS

Activity Name

IMP - Accomplishment Criteria

IMP- Significant Accomplishment

IMP- Major Program Event

IPT and WBS Reference

Common Formats


Example of IMS Structure - Gantt

Schedule Dates

Activity Name

SOW Reference (OPTIONAL)WBS

IMP Reference Number: First Digit- Event, Second and Third Digit - SA, Fourth and Fifth Digit- Criteria

IMP# WBS SOW Name Start FinishA (A) System Requirements Review (SRR) 12/15/99 12/15/99

A01 2200 3.2.1 Preliminary SEMP Complete 11/1/99 12/14/99

A0101 3200 3.1.7 Preliminary Software Mangement Plan 11/1/99 12/14/99

A010101 4200 3.1.7 Determine Software Mamangement Requirements 11/1/99 11/19/99

A010102 4200 3.1.7 Develop Preliminary Software Mamangement Plan11/22/99 12/14/99

A0102 4301 3.1.2 CAIV Process Established 11/1/99 12/14/99

A010201 4301 3.1.2 Develop CAIV Process 11/1/99 12/14/99

(A) System Requirements Review (SRR)

Oct Nov Dec Jan Feb Mar Apr May Jun Jul2000

Major Program EventSignificant AccomplishmentAccomplishment Criteria

Tasks


IMP No. L4 WBS L6 WBS IPT Task Name Cat. Start Dur FinishA (A) SYSTEMREQUIREMENTS& DESIGNTIM 10/1/01 0d 10/1/01

A06 EXPL O&C Subsystem Preliminary Design Initiated 11/1/99 185d 8/2/00

A0601 EXPL O&C Prototype PlanUpdated 11/1/99 184d 8/1/00

A060101 4-320 6-323 EXPL DevelopDraft O&CPrototypePlanUpdates M 11/1/99 124d 5/1/00

A060102 4-320 6-323 EXPL DevelopFinalO&CPrototypePlanUpdates M 5/2/00 60d 8/1/00

10/1 (A) SYSTEM REQUIREMENTS

8/2

1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 21999 2000 2001 2002 2003 20

WBS DictionaryO&C Design - This element includes all efforts necessary for Software to support the development of thesystem specifications such as Subsystem Specification and Computer Program Configuration ItemsSpecifications, Functional Interface Documents/Interface Requirements Documents, Verification Cross-Reference Matrices and Requirements Traceability Matrices for the O&C Subsystem. Develop the softwarearchitecture and design by performing preliminary and detailed design. Preliminary design consists ofconverting software requirements into high-level software design to the task (execution unit) level. Allpreliminary design products are reviewed for product assurance

Requirements(SOO)

WBS

Integrated Master Plan (IMP)

Integrated Master Schedule (IMS)

Statement Of Objectivesfor the

Radar Technology Insertion Program (RTIP)

2.0 OBJECTIVES

The objectives of the RTIP development program are to:

2.1 Specify an operational RTIP system by means of cost-benefit trades, in which Cost As an IndependentVariable and a warfighter perspective are used to establish system threshold and objective performanceparameters; (Pre-EMD/EMD)

2.2 Define an architectural foundation for continuous evolution and growth in operational capability usinga modular/scaleable design approach. This capability is to incrementally meet threshold, objective andP3I requirements for the minimum non-recurring and recurring cost throughout the life cycle of thesystem; (Pre-EMD/EMD)

2.3 Develop a cost effective design and sustainment strategy to continuously reduce cost of ownershipthroughout the life cycle of the system, while continuously improving operational availability; (Pre-EMD/EMD)

2.4 Prove threshold operational performance, and as a minimum, in a system of hardware, software,people, training, maintenance and other infrastructure that is certified to be operationally suitable andeffective, as the basis for a production decision; (EMD)

2.5 Deliver for a production milestone decision a production-ready system, to include cost estimates andplans for production infrastructure including ground support systems, within the cost and scheduleallocated to perform the RTIP development program; (EMD)

2.6 Plan for, and if directed, prepare a reprocurement data package for the RTIP radar subsystem; (Pre-EMD/EMD)

2.7 DeletedPrepare and submit, when necessary, Engineering Change Proposals (ECPs), Deviations, Waivers, andContract Change Proposals (CCPs). (Pre-EMD/EMD)

MPE IPT WBS L4 WBS L6

(A) SRDT A06 O&C Subsystem Preliminary Design Initiated EXPL A0601 O&C Prototype Plan Updated 4-320 6-323

(A) SRDT A06 O&C Subsystem Preliminary Design Initiated EXPL A0602 O&C Prototype Software Preliminary Design Completed 4-320 6-323

Significant Accomplishment Accomplishment Criteria

Significant AccomplishmentAccomplishment Criteria

Tasks Plans

The link is established between the IMS and the WBS at the task level

The Task contains the entire Life Cycle of each IPT processes that lead to the IMS Products. Schedules Will Be Linked to Identify Critical Path and Slack, and to Form the Basis for Schedule Risk Analysis

LEVEL - 4 LEVEL-6

4-320 6-320 O&C IPT ManagementOperations and Control 6-321 O&C Design

Subsystem (O&C) 6-322 O&C Studies and Analysis"A" 6-323 O&C Risk Reduction

6-324 O&C Integration6-325 O&C Subsystem Qualification Testing

Major Program Event

IMP/IMS Common Numbering

IMP/ IMS - A Fully Integrated Framework


Statement Of Objectivesfor the

Radar Technology Insertion Program (RTIP)2.0 OBJECTIVESThe objectives of the RTIP development program are to:2.1 Specify an operational RTIP system by means of cost-benefit

trades, in which Cost As an Independent Variable and a warfighter perspective are used to establish system threshold and objective performance parameters; (Pre-EMD/EMD)

2.2 Define an architectural foundation for continuous evolution and growth in operational capability using a modular/scaleable design approach. This capability is to incrementally meet threshold, objective and P3I requirements for the minimum non-recurring and recurring cost throughout the life cycle of the system; (Pre-EMD/EMD)

2.3 Develop a cost effective design and sustainment strategy to continuously reduce cost of ownership throughout the life cycle of the system, while continuously improving operational availability; (Pre-EMD/EMD)

2.4 Prove threshold operational performance, and as a minimum, in a system of hardware, software, people, training, maintenance and other infrastructure that is certified to be operationally suitable and effective, as the basis for a production decision; (EMD)

2.5 Deliver for a production milestone decision a production-ready system, to include cost estimates and plans for production infrastructure including ground support systems, within the cost and schedule allocated to perform the RTIP development program; (EMD)

2.6 Plan for, and if directed, prepare a reprocurement data package for the RTIP radar subsystem; (Pre-EMD/EMD)

2007/07/06 39

3.1- 實獲值管理系統 (EVMS) 實獲值管理系統 (Earned Value Management System) 係以量化方式顯示出計畫有關時程與成本方面之執行現況，以充分揭示 Project Health。此包括計畫整體或個別分項是否較原定計劃超前或是落後，預算是否超支？計畫主持人可依據此等資訊，調配其可用資源以補足進度落後之項目。也可用以面對可能發生的問題達到預警之功效，以及估計完工的時間與成本。由於 EVMS是以量化為基準，因此可對類似專案進行評比。 EVMS 經由Planned Value（ PV ）、 Earned Value（ EV ）、 Actual Cost（ AC ）可顯現出對專案計劃成本與時效掌控分析的重要性。

但美國採購管理協會 (Contract Services Association of America (CSA)) 建議 EVMS 應僅限於合約金額在 USD 20M 以上，且不適用於商用件 (commercial item acquisitions) 、絕對固定計價合約 (firm-fixed price) 、各項固定計價合約 (fixed price level of-effort) 、工時材料合約 (time and materials contracts) ，此亦為各國防採購單位所引用

2002 Business Manager’s Conference -- EV Fundamentals # 40 B C – May 02

Scope

Schedule tasksSequenceInterdependenciesFloat / ‘Critical Path’

Budget TasksApply ‘Appropriate’ EV TechniqueCalculate BCWSCumulative

Schedule Work40

10060

Integrated Program Management SystemApproved MNS / ORD / APBID ‘Contract’ Req’sExtend ‘Measurable’ WBS Products to control account [Mil Hdbk 881] ‘planning & work packages’

Action&

Reports

Negotiated Contract Co$tMR

PMB

$

Time

Allocate Budgets40

10060

CWBS為 EVMS之基礎

2007/07/06 41

實獲值專案管控模式 (EVMS)

Management Reserve

Total Allocated Budget

ACWPC BCWPC

BCWSC

$

TimeNow Completion

Date

Schedule VarianceC

Cost VarianceC

PROJECTED

SLIPPAGE

PMB

OverBudget

EACThe Program at a Glance

REQUIREMENTS MNS / ORD / APB / Contract“RISK MANAGEMENT” Customer / PO / Ktr

ACQ STRATEGY w/ PPB$ (POM / BES / PB)

OBL & EXPEXIT CRITERIAISSUES w/ PRIORTIZED SOLUTIONSIMPLEMENTATION [Plan] ??

What do WE do ?

Indices

Cost Performance Index Mom & Pop FO5601-86-C-0023 RDTE CPIF/AFElement: 1000 Name: LAIR

CUMCURTC-BACTC-LRE

OCT1994

NOVDECJAN1995

FEBMARAPRMAYJUN JULAUG

0.60

0.70

0.80

0.90

1.00

1.10

1.20

0.88 0.88 1.00 1.00

0.94 0.96 1.00 1.01

0.93 0.90 1.01 1.07

0.89 0.70 1.01 1.00

0.88 0.84 1.01 0.98

0.87 0.80 1.02 1.01

0.86 0.75 1.02 0.98

0.89 1.16 1.02 0.97

0.89 0.88 1.02 0.92

0.90 1.00 1.02 0.96

0.90 0.90 1.03 0.97

BAC / LRE / EACCPI / SPITCPILRE / EAC / BAC

2007/07/06 42

EVMS Executive Summary of CSA Recommendations

Contract type. Use of EVMS shall be limited to cost-type and fixed-price incentive contracts; EVMS shall not be required on commercial item acquisitions and firm-fixed price, fixed price level of-effort, or time and materials contracts.

Threshold for applicability of EVMS. There shall be a single, government wide, bright-line dollar threshold of $20 million in procurement and/or RDT&E contracts and/or task/delivery orders, excluding options and value of subcontracts, for application of EVMS.

(Contract Services Association of America (CSA) )

43

EVM: An Acquisition Strategy Decision

“Nature of the work” is key determinant for applying EVM

FFPContract

Yes

EVM is a Risk- Based Decision

Nature of the Work

Time & Material Level of Effort

EVM Not Recommended

Implement EVM in Accordance with

DoDI 5000.2

Yes

No

No

2007/07/06 44

4.1- 整合產品與流程發展 IPPD

IPPD為源自於同步工程（ Concurrent Engineering ），其概念為將工程設計事項涵括〝 business analysts、 customers、 suppliers〞等相關 process予以整合。由於國防工程或航太工程牽涉眾多之專業組織以及包含有User、Maintainer、 Developer、 Designer、Manufacture等角色，因此如何將前述專業組織與不同角色成員能適當的組合，以針對問題能適時暨適當的解決，為 IPPD 之主要精神。 IPPD 之主要特徵為組成不同層級之 Integrated Product Team（ IPT ）以達成前述之精神。其明顯之效益為縮短〝 Time to Market〞，因此對於大型計畫再成本方面具有極佳之節省效益。 IPPD 之成敗關鍵在於 IPT之組成，其運作方式不同於距陣編組模式，由簽約開始之 WBS即與距陣編組模式之 WBS 有異。

波音 (Boeing) 公司在波音 777 計畫組成了 238個 IPT ，有關產品於研發過程中產生的所有問題都在 IPT内部協商解决。由於將製造提前介入設計過程，减少了製造與工程變更的數量，確保產品設計與製造一次成功之機率，因此缩短了設計時程，减少了工程修改，提高了產品品質，在市場競爭時程方面提供了極大效益。該成功範例對於全球航空制造業具有非常大的示範作用。

2007/07/06 45

Integrated Product Team（ IPT ）

2007/07/06 46

4.2- Evolutionary Acquisition –Incremental & Spiral Development

- Incremental

- Spiral

Warfighter Capability

Known increment

Known increment

Known increment

Known increment

Partially known

increment

Not known increment

Not known increment

==

First Fielded Capability

Technology Demos

Feedback from warfighter

2007/07/06 47Time

Cap

abili

ty

Evolutionary Acquisition

Initial Operationally

Useful Capability

Technology BaseRequirementsCapability

Time

NO CAPABILITY

Cap

abili

ty

Single Step ApproachTechnology Base

Requirements

CapabilityFOCIOC

2007/07/06 48

4.3- 基於模擬的採購 (SBA: What Is It?)

… stored in a distributed repository to assist in defining, evaluating and managing a weapon system’s entire lifecycle

CG47DD963

DDG51CG47

DD963DDG51

PLAT

SIG/KINE

C2

COMMSDATAFUSION

SENS 1

SENS 2SENS 3

SENS 4

Conceptual DevelopmentFunctional Design

MNS

ORDSYSTEM

CONCEPTS

Top Level SystemRequirements

Physical & Info System (HW/SW) Design

Cost, Schedule &Program Management

DRIVERS

Concept Exploration & Definition

Demonstration / Validation

Engineering Manufacturing & Development

Production & Deployment

Upgrade and

Replacent

PHASE

1000

10010

MGMT

Jan Apr Jul Oct

Structural / HME

Structural / HME

Distributed InformationRepository

OtherSystem

OtherSystem

T&E Engineering Development& Manufacturing

Operations, Logistics& Training

ADVANCED COMBAT SYSTEMS

ADVANCED PLATFORMS

ADVANCED SENSORS AND WEAPONS

Shared Data is Key to Integrated Product Development

2007/07/06 49

4.4- 績效服務契約 (PBSA)

採用績效服務契約 (Performance Based Service Contracting) ，以量化的 Performance Quantity 規範 Quality；由於 PBSA條款，大部分美國政府的採購案已轉成採購單位只寫 Statement of Objectives而由競標廠家寫 Performance Based Statement of Works （ PSW ）與 CDRL ，因為採用量化方式，因此有助於採購的品質監控與驗收。

甲方採購策略為：需求事項僅敘述終端之功能及量化之產品品質特性（ PBSA ）、由乙方建議專案執行之參用標準、遂行專案發展過程之效能監控（ EVMS ）、 RFP 須說明專案執行之相關程序事項（ SOW ）、 RFP 須說明專案應交付物件（ CDRL ）、 RFP 須說明交付文件之參考內容標準（ DID ）、以工作分解結構（ WBS ）為骨幹、 ..。

PM 在參用 PBSA時，應一併規劃採購計畫書 AP (Acquisition Assurance Plan) ， AP 有關 Performance 之敘述可包括下列事項：1. 效能目標 Performance Objectives2. 效能標準 Performance Standards3. 允收標準水平 Acceptable Quality Levels4. 檢視方法 Methods of inspection5. 檢視頻率 Frequency of inspection6. 獎勵金計算準則 Incentives

2007/07/06 50

PBSA 績效服務採購 (Old Versus New Process)

Traditional Process

Government Solves the Problem

Performance-Based Process

Contractor Solves the Problem Tight SOW

Rigid Solution

Routine Tasks

FormalSystems

CompetitiveStrategy

Use SOW•PWS•SOO

Innovative Solutions

ShareInformation

Collaboration Strategy

EmpowerAcquisitionTeams

Learning Bureaucratic

OrganizationalChange in service Of Performance

2007/07/06 51

Performance Requirements Summary Sample

Provide qualified Family Practice Physician.

PWS 3.3.2.4Provide qualified Family Practice Physician on required start date.

No more than X days late. Observation by COR.X% reduction in invoice for CLIN 000X for first full (30 day) monthly invoice.

Provide qualified Family Practice Physician.

PWS 3.3.2.4 Provide qualified Family Practice Physician on required start date.

Each X days prior to required date.

Observation by COR.

X% increase in invoice for CLIN 000X for first full (30 day) monthly invoice for each 5 day period prior to required date.

Provide quality Family Practice Medicine Services.

X% reduction in invoice for CLIN 000X for monthly invoice following month in which substantiated complaints confirmed.

Customer Survey cards or other documented complaints.

PWS 3.3.5.2 Provide Family Practice Medicine Services without substantiated customer complaints at XYZ MTF.

No more than X substantiated complaints per X Days.

2007/07/06 52

Critical Technical ParametersSupported

Operational Requirement

(Include ORD

reference)

Technical Parameter

Developmental Stage Event

Threshold Value

DecisionSupported

In most cases a measure of effectiveness or suitability from paragraph 1d.

Technical measure(s) derived to support operational requirement.

Developmental stage events (Described in TEMP Part III) designed to measure system performance against technical parameters.

Minimum value required at each developmental event. Most parameters will show growth as the system progress through testing. Final value should reflect level of performance necessary to satisfy the operational requirement.

May be any decision marking the entrance into a new acquisition phase or may be a readiness for operational test decision.

Example:

Main Gun Probability of Hit, 94 % at 1,500 meters (ORD para. xxx.x)

Example:

Auxiliary sight Boresight accuracy

Example:

System Demo Test-Accuracy Test

Prod Readiness Test-Accuracy

Prod Qual Test

Example:

+/- 5 mils

+/- 3 mils

+/- 1 mil

Example:

Milestone B

MS C (Low-Rate Initial Production Decision)

FRP DR

2007/07/06 53

4.5- 志願性共識標準 Voluntary Consensus Standards （ VCS)

標準（ Standards ）是美國聯邦政府採購計畫用以取得買賣雙方共識的重要準繩，早期國防部的 MIL-STD-xxx、 DoD-STD-xxx、MIL-HDBK-xxx、 ... 等標準文件為系統或軟體業界最常引用的，第一份可引用的系統工程 MIL-STD-499 與軟體工程 MIL-STD-1679 標準分別於 1969與 1968 年頒布，其他眾所知悉的 ISO/IEC-12207 與 IEEE/EIA-12207 分別於 1995 年與 1998 年制定。

標準有其重要性，但維護標準卻所費不貲，因此美國軍方在國會相關法案下（ FASA、 FARA ）已於 1993 年逐漸將軍規文件維護轉移給民間執行。但對於標準的選用影響最大的是 1996 年通過的國家技術移轉和促進法中規定的“自願性共識標準 Voluntary Consensus Standards （ VCS ））”，該法案規定除了國會法案強制、重大公眾利益和公共資源領域，如無線通信的频率使用方式、食品監督、藥品監督、飛安、環境保護等（事實上此等應歸類為法令 (Codes ）而非標準（ Standards ）， Codes與 Standards差異在於強制性與自願性 )，政府仍將執行強制性的技術標準（即法令）以外，其他不損及生命與公眾利益項目，政府單位不再執行強制性標準，採購案中的執行技術標準必須取得雙方自願性共識，但在政府採購案中如果是屬於新技術或新發明領域，可以由政府單位訂定指導性技術標準，其前提是訂定單位必須經由白宮預算辦公室 (OMB) 審查並經國會通過方可執行，其目標是增强企業自治，解除政府管制。

2007/07/06 54

志願性共識標準 Voluntary Consensus Standards （ VCS)

上述法案由美國國家標準和技術研究院 (The National Institute of Standards and Technology， NIST)承擔起和產業界合作的職責，促進技術、測量方法和標準的應用，諸如資訊系統安全自我評鑑指引、聯邦資訊系統安全驗證與認證指導綱要等文件即由 NIST 所制定頒布；但在所謂自願性共識標準之選用與認定則由美國國家標準學會(ANSI) 執行管理和協調， ANSI 並非政府機構是屬於非營利性團體，其本身扮演 third-party ，在國會法案下選用各組織（約 200家）所訂定的標準予以鑑定 (accreditation) 可否納入自願性共識標準，因此見到的標準編號會是 ANSI/RIA R15.05-1-1990、 ANSI/IEEE C57.117-1986、 ANSI/IEEE 729-1983、 ANSI/IEEE Std 1042… 等，比較值得注意的是系統工程標準目前有 ANSI/EIA-632，而 IEEE 1220與 ISO/IEC 15288似乎尚未納入 ANSI鑑可項目， ISO/IEC-12207被 ANSI鑑可在 ANSI Joint Standard 016 項目（或是稱為 IEEE-1498 ），但僅有 Development Process ，目前則尚未看到將 IEEE/EIA-12207鑑可為 ANSI 文件（由 NIST 會議資料所知，有諸如政府出版辦公室 (GPO)單位認為 IEEE/EIA-12207在Quality Assurance 方面不如 MIL-STD-498 ，因此反對將 12207納入 VCS ）；國防部在此法案下，只要是有符合自願性共識標準的民間版標準，美國國防部即將相關軍規標準予以汰除（但仍可使用，只是不再執行維護與 Q/A ）。

2007/07/06 55

志願性共識標準 Voluntary Consensus Standards （ VCS)

在前述有關自願性共識標準法案之下，美國政府單位的Acquisition Policy 有了相當程度的影響，諸如在美國國家檔案及文件總署的一項購案 RFP 中即要求競標商須提出執行該案所將引用的 Standards ，其文如下『 Specify or describe the standards that the Offeror intends to apply to this effort. The standards must be voluntary consensus standards accepted industry-wide such as those published and controlled by the American National Standards Institute (ANSI) or other ANSI certified organization such as the Institute of Electrical and Electronics Engineers (IEEE) or the Electronic Industries Alliance (EIA). The IEEE/EIA 12207.0-1996, Industry Implementation of International Standard ISO/IEC 12207.1:1995, (ISO/IEC 12207) Standard for Information Technology — Software life cycle processes and the IEEE Std 1220 -1998, IEEE Standard for Application and Management of the Systems Engineering Process is NARA’s preferred software process standard. 』，該計畫之 PM既使想獨戀於 12207或 1220 標准，但也僅能在RFP 中闡明 12207與 1220 是計劃心儀的標準。

2007/07/06 56

4.6- 專案管理之教育訓練

COURSE NUMBER/SCHEDULE DAU COURSE TITLE AND DESCRIPTION

ACQ 101(On line) Fundamentals of Systems Acquisition ManagementsACQ 201A(On line) Intermediate Systems AcquisitionACQ 201B Intermediate Systems AcquisitionPMT 352B Program Management OfficePMT 401 The Program Manager's Course

SYS 203 Intermediate Systems Planning, Research, Development and Engineering, Part II

SYS 302 Technical Leadership in Systems EngineeringTST 101(On line) Introduction to Acquisition Workforce Test and EvaluationSAM 201 Intermediate Software Acquisition ManagementSAM 301 Advanced Software Acquisition Management

國防採購大學之採購訓練課程除一般依據聯邦採購政策辦公室 (Office of Federal Procurement Policy)指定聯邦採購學院 (Federal Acquisition Institute， FAI)所規劃之訓練課程外，另依據國會所通過之國防採購改善計畫規劃有其他專業課程，特別是在軟體工程、系統工程、建構管理、後勤工程、風險管理…等

此等課程亦開放給國防合約之承約商、民用政府部門合約之承約商、民用政府部門合約之計畫人員、一般民間公司參與

2007/07/06 57

Training Requirements:Project ManagementKnowledge and Performance

COTR Level

1

COTR Level

2

COTR Level

3

Point of

Contact/Order Contact

Scope Management R R R AD

Schedule Management R R R AD

Cost Management R R R AD

Quality Management R R R AD

Risk Management R R R AD

Required Project Management Course Topics

Procurement Project Management

R R R AD

R=Required AD=As Directed by the Contracting Officer

12 18 24 12 Minimum Number of Project Management Course Hours 6 hours = 1 training day

2007/07/06 58

專案管理實例

2007/07/06 59

專案實例 1： 2003 年國內某公共工程案例 -軟體可靠度 MTBF某公共工程之規格書需求： Equipment Reliability Requirements All Relevant Failures including software errors shall be used in

computation of demonstrated MCBF/MTBF. Reliability Requirements (Mean-Time-Between-Failure ， MTBF) for

Equipment and all PCs： 50,000 hours The Contractor shall provide product information and reliability

calculation to demonstrate that the reliability and availability requirements are met.

前述案例之電腦的 MTBF 需求為 50,000小時， 2005 年聯想電腦公佈通過世界記錄之 60,000小時 PC 測試報告， 2004 年之測試紀錄為45,000小時。如果將硬體 (Hardware Configuration Item， HWCI)可靠度與軟體 (Computer Software Configuration Item， CSCI) 可靠度視為獨立之串聯系統，載入應用軟體後之系統可靠度以最簡單公式1/MTBFsystem = 1/MTBFHWCI+1/MTBFCSCI表示，若欲達到 1/MTBFsystem =1/ 50,000 hours 之可靠度需求必須是 MTBFHWCI或MTBFCSCI >50,000小時。

2007/07/06 60

專案實例 1(續 )： CSCI Reliability Domain

目前並無統一之 software reliability 定義，以 50,000 hours MTBF或 1.5 fails/per 40 CPU hours或…表示 ?

如果可參用 HWCI之MTBF觀念，最佳理想模式為將 HWCI與CSCI視為 independent component

套用最佳之數學公式： 1/(MTBFsystem) =1/(MTBFHWCI) + 1/(MTBFCSCI) ，亦即MTBFCSCI>50,000 hours、 MTBFHWCI> 50,000 hours

假設MTBFHWCI =MTBFCSCI，則 MTBFHWCI =100,000 hours 如何在 180天 (4320 hours)驗證 100,000 hours的 CSCI’s 或 HWCI’s的MTBF值 ?

2007/07/06 61

專案實例 1(續 ) ：另增 System Process Domain

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

Software Reliability

Engineering

硬體發展

軟體發展

2007/07/06 62

專案實例 1(續 ) ： Test 前述需求依據可信度 90%之 GEM (General Exponential Model)

table ， MTBFsystem=100,000 hours ：No. of Failure(r) Test Ratio(M) Total Test Time(hr)

0 2.3026 100,000*2.3026=230,260(hr)

1 3.8897 100,000*3.8897=388,970

2 5.3223 100,000*5.3223=532,230

3 6.6808 100,000*6.6808=668,080

4 7.9936 799,360

5 9.2747 927,470

6 10.5321 1,053,210

7 11.7709 1,177,090

8 12.9947 1,299,470

9 14.2060 1,420,600

10 15.4088 1,540,880

• 依據上述 MTBF 需求、 180天 (4320 hours)Demonstration Test與 GEM表格，單一中央資料處理系統 (100,000 hours MTBF) 要達到 230,260 hours “0” failure 之允收標準將是一項 non-feasible之 test item

2007/07/06 63

專案實例 2 (續 ) ： Life Cycle Model 2.3 專案生命週期本專案之軟體開發生命週期是採用瀑布式 (Waterfall)/螺旋式

(Spiral) 模型開發方式。由於瀑布式模型之前提為在設計階段開始前，使用者已明確定義出所有的使用者需求。然而，根據過去許多的研究文獻與相關資料可發現，在軟體專案發展週期中會有許多新增與變更的需求產生，故需要使用者大力地配合與不斷反覆的訪談，才能將使用者真正的需求釐清與定義。完善的使用者訪談為本專案後段系統設計的主要關鍵，並可能對未來系統開發造成嚴重的影響，因此本公司也界定在系統分析與設計階段給予使用者訪談足夠的時間進行。依照本專案的特性，螺旋式模型強調在設計開發時因為需求的變更有時需要回去到早期的階段。由於螺旋式模型實際上是屬於短期的瀑布式開發模型，導致每個螺旋式模型所完成的原型品代表瀑布式模型的各項階段。因此，本公司認為此開發模型不僅可在早期的開發週期即能完備地證明 Proof of Concept (POC) 的觀念，並且更能有效控制專案發展時雜亂或混亂的情況。

2007/07/06 64

Questions?