Description
A technique to identify risks associated with a given system concept and design. Suggested by the Risk Management Guide for DoD Acquisition.
Background
A technique to identify risks associated with a given system concept and design.
Supporting Documentation
Risk Planning and Management - B-2 Systems Engineering Case Study
Primary Benefit Reduced Schedule
Net Impact Cost Don't know
Net Impact Quality Don't know
Net Impact Schedule Reduced Schedule
Schedule Comments It was an indirect effect of the work done during the entire process.
Enablers Risks as Part of WBS The program was structured so that all risks affecting the configuration concept for the viability of the weapons system concept were identified at contract award and were structured as part of the program WB's work plans. These initial risks were comprised of those “normal” risks associated with a large complex weapons system development as well as the new technology and processes necessary to mature the program to low to medium risk at PDR.(Page 50) Risk Closure Plans The initial risks were closed prior to PDR 2. The risk closure process continued throughout development and identified new risks and continuously identified new risk closure plans. Most importantly, the work associated with risk closure for each plan was integrated into each WBS task team’ work plans. These detailed plans showed all analyses, tests, and tasks necessary to close the identified risks and were maintained and statused as part of the normal design/program reporting activity. The Risk Closure Plans were reviewed at QPMR and the leader of the WBS task team had to get the agreement of all the participants from all the sides of the program before it could be presented to the program management team. This forced a major systems integration/systems engineering activity to assure agreement before the recommendation and alternatives were presented. (Page 51)
Risk Management Guide for DoD Acquisition
This link will take you to the August 2006 Risk Management Guide for DoD Acquisitions. The purpose of this guide is to assist Department of Defense (DoD) Program Managers (PMs), program offices, and their Integrated Product Teams (IPTs) in effectively managing risks within their acquisition programs. This guide contains baseline information and explanations for a well structured risk management program. The management concepts and ideas presented here encourage the use of risk-based management practices and suggest a process to address program risks without prescribing specific methods or tools. Since this is a guide, none of this risk management information is mandatory, but PMs are encouraged to apply the fundamentals presented here to all acquisition efforts-both large and small-and to all elements of a program (system, subsystem, hardware, and software). Risk management is a fundamental program management tool for effectively managing future uncertainties associated with system acquisition. Program Managers should tailor their risk management approaches to fit their acquisition programs and statutory requirements. This Risk Management Guide should be used in conjunction with related directives, instructions, policy memoranda, or regulations issued to implement mandatory requirements. Previous editions of the Risk Management Guide provided invaluable risk management information, but in such detail that some users found it difficult to quickly digest. This guide, by comparison, has been restructured to provide a basic understanding of risk management concepts and processes. It offers clear descriptions and concise explanations of core steps to assist in managing risks in acquisition programs.arison, has been restructured to provide a basic understanding of risk management concepts and processes. It offers clear descriptions and concise explanations of core steps to assist in managing risks in acquisition programs.
https://acc.dau.mil/communitybrowser.aspx?id=108780
WBS Technique
The first step is to review the Work Breakdown Structure (WBS) elements down to an appropriate level and identify risk events. This review should consider the critical areas (design and engineering, technology, logistics) that may help to describe risk events. Using information from a variety of sources, such as program plans, prior risk assessments and expert interviews, the WBS elements are examined to identify specific risks in each critical area. The elements of the WBS must be examined relative to threat, requirements, design, test and evaluation, modeling and simulation, technology, etc. to identify the program risk events. The risk events are analyzed to determine probability of occurrence and consequences/impacts, along with any interdependencies and risk event priorities. Several techniques and tools are available to help do portions of the assessment, including, among others, technology assessments, modeling and simulation
https://acc.dau.mil/CommunityBrowser.aspx?id=38273
