DOD 5000.2-R
DOD 5000.2-R
This paper discusses DOD 5000.2-R, mandatory procedures for Major Defense Acquisition Programs (MDAPS) and Major Automated Information System (MAIS) Acquisition Programs.
2,010 words (
approx. 8 pages) |
3 sources |
MLA | 2004
Paper Summary:
The purpose of the DOD Regulation 5000.2-R of 1996 is to establish a simplified and flexible management framework for translating mission needs into stable, affordable, and well-managed programs. The author points out that the DoD Directive 5000.2-R applies to all elements of the DoD; its procedures are mandatory for Major Defense Acquisition Programs (MDAPs), Major Automated Information System (MAIS) Acquisition Programs. and others specified in the Regulation, as well as serving as a general model for other than MDAPs and MAISs. The paper presents RiskTrak, a Windows-based tool, which enables users to identify, estimate, analyze, report, communicate. and manage risk throughout the duration of the Acquisition Program.
Table of Contents
Overview of DOD 5000.2-R
Analysis of DOD 500.2-R in Relation to Systems Engineering
Evaluation of Requirements Based on Commercial Market Potential
Open Systems
Commercial and Non-Developmental Items
Critical Product and Technology Competition
Competition
Best Practices
Open Systems Design
Software Engineering
Interoperability
Work Breakdown Structure (WBS)
Integrated Product Teams (IPTs)
Assessing the Value of DOD 5000.2-R: "RiskTrak and the Critical Role of Risk Management in DoD Directive 5000.2-R"
RiskTrak and DoD 5000.2-R Program Structure
RiskTrak and DoD 5002-R Program Design
RiskTrak and DoD 5002-R Program Assessments & Decision Reviews
From the Paper:
"PMs shall avoid imposing government-unique requirements that significantly increase industry compliance costs. Examples of practices designed to accomplish this direction include: open systems approach that emphasizes commercially supported practices, products, specifications, and standards; best value evaluation and award criteria; use of past performance in source selection, results of software capability evaluations; government-industry partnerships; and the use of pilot programs to explore innovative practices."
DOD 5000.2-R (2012, January 15). Retrieved February 10, 2012, from http://www.academon.com/Essay-DOD-5000-2-R/54716
"DOD 5000.2-R" 15 January 2012. Web. 10 Feb. 2012. <http://www.academon.com/Essay-DOD-5000-2-R/54716>