Views
1 year ago

Department of Defense INSTRUCTION

x9tnk

DoDI 5000.02, January 7,

DoDI 5000.02, January 7, 2015 3. POLICY. The overarching management principles and mandatory policies that govern the Defense Acquisition System are described in Reference (a). This instruction provides the detailed procedures that guide the operation of the system. 4. RESPONSIBILITIES a. Defense Acquisition Executive (DAE). The DAE is the Under Secretary of Defense for Acquisition, Technology, and Logistics (USD(AT&L)). The DAE will act as the MDA for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System (MAIS) programs. In accordance with Table 1 in Enclosure 1 of this instruction, the DAE may delegate authority to act as the MDA to the head of a DoD Component, who may further delegate the authority to the Component Acquisition Executive (CAE). The DAE may also delegate MDA authority to another OSD official as the DAE considers appropriate. b. MDA. The MDA will establish procedures for assigned programs using this instruction as guidance. MDAs should limit mandatory procedures applicable to all assigned programs so as to not exceed the requirements for MDAPs or MAIS programs and other acquisition programs governed by this instruction or DoD Directive 5000.01 (Reference (a)). MDAs should tailor regulatory procedures in the document consistent with sound business practice and the risks associated with the product being acquired. c. Heads of the DoD Components. The DoD Component Head will implement the procedures in this instruction and Reference (a). Component-required procedures will not exceed those specified in this instruction. When necessary, waivers or requests for exceptions to the provisions of this instruction will be submitted to the DAE, the DoD Chief Information Officer (DoD CIO), the Director, Operational Test and Evaluation (DOT&E), or the Director, Cost Assessment and Program Evaluation (DCAPE), via the CAE. Statutory requirements cannot be waived unless the statute permits. d. Secretaries of the Military Departments. In addition to the responsibilities described in paragraph 4.c., the Secretary of the Military Department acquiring an MDAP will represent the customer (i.e., the DoD Component(s) fielding the system). The Secretary concerned, in coordination with the Chief of the Military Service fielding the system, will balance resources against priorities and ensure appropriate trade-offs are made among cost, schedule, technical feasibility, and performance throughout the life of the program. e. Chiefs of the Military Services. The Chiefs of the Military Services fielding MDAPs will represent the customer and, with the Secretary of the Military Department acquiring the MDAP, balance resources against priorities and ensure that appropriate trade-offs are made among cost, schedule, technical feasibility, and performance throughout the life of the program. The Chief concerned will advise the MDA on trade-offs before Milestones A and B. As part of the MDA’s Written Determination before Milestone A and Certification and Determination before Milestone B (these milestone information requirements are detailed in Table 2 in Enclosure 1), Change 2, 02/02/2017 2

DoDI 5000.02, January 7, 2015 the MDA must determine that the Chief and the Secretary concur with the cost, schedule, technical feasibility, and performance trade-offs that have been made. 5. PROCEDURES a. Overview (1) Program Categories. The statutes governing defense acquisition programs are complex, and the categories into which a program falls will impact acquisition procedures. The designation of a program as an MDAP, a MAIS program, or a Major Weapons System; and the determination that the program is an Information System, a Defense Business System, or responds to an urgent need affect program procedures and policies. (2) Program Structure. The structure of a DoD acquisition program and the procedures used should be tailored as much as possible to the characteristics of the product being acquired, and to the totality of circumstances associated with the program including operational urgency and risk factors. (a) MDAs will tailor program strategies and oversight, including program information, acquisition phase content, the timing and scope of decision reviews and decision levels, based on the specifics of the product being acquired, including complexity, risk factors, and required timelines to satisfy validated capability requirements. (b) When there is a strong threat-based or operationally driven need to field a capability solution in the shortest time, MDAs are authorized to implement streamlined procedures designed to accelerate acquisition system responsiveness. Statutory requirements will be complied with, unless waived in accordance with relevant provisions. (c) In accordance with Section 806 of Public Law 114-92 (Reference (d)), the Secretary of Defense may waive acquisition law or regulation to acquire a capability that would not otherwise be available to the DoD Components. This waiver authority may not be delegated. Detailed provisions and requirements for this waiver are identified in Table 6 in Enclosure 1 of this instruction. (3) Program Acquisition Categories (ACATs) and Types. All defense acquisition programs are designated by an ACAT (i.e., ACAT I through III) and type (e.g., MDAP, MAIS, or Major System). MDAPs are either estimated to achieve the statutorily defined MDAP cost threshold, or are designated as an MDAP by the DAE. Similarly, MAIS programs are either estimated to achieve the statutorily defined MAIS program cost threshold, or are designated a MAIS program by the DAE. MAIS programs are software intensive and typically have a lower investment level than MDAPs. A MAIS program that is estimated to attain the MDAP cost thresholds may be designated by the DAE as either an MDAP or a MAIS program. MDAP and MAIS program designations carry the greatest consequences in terms of management level, reporting requirements, and documentation and analysis to support program decisions. Enclosure 1 of this instruction identifies the information requirements associated with all Change 2, 02/02/2017 3

  • Page 1: The linked image cannot be displaye
  • Page 5 and 6: DoDI 5000.02, January 7, 2015 DAB r
  • Page 7 and 8: DoDI 5000.02, January 7, 2015 c. Ge
  • Page 9 and 10: DoDI 5000.02, January 7, 2015 a. Th
  • Page 11 and 12: DoDI 5000.02, January 7, 2015 (b) M
  • Page 13 and 14: DoDI 5000.02, January 7, 2015 (d) M
  • Page 15 and 16: DoDI 5000.02, January 7, 2015 (e) M
  • Page 17 and 18: DoDI 5000.02, January 7, 2015 3. Fi
  • Page 19 and 20: DoDI 5000.02, January 7, 2015 1. Mi
  • Page 21 and 22: DoDI 5000.02, January 7, 2015 by a
  • Page 23 and 24: DoDI 5000.02, January 7, 2015 (e) S
  • Page 25 and 26: DoDI 5000.02, January 7, 2015 addre
  • Page 27 and 28: DoDI 5000.02, January 7, 2015 (a) T
  • Page 29 and 30: DoDI 5000.02, January 7, 2015 syste
  • Page 31 and 32: DoDI 5000.02, January 7, 2015 appro
  • Page 33 and 34: DoDI 5000.02, January 7, 2015 e. Ad
  • Page 35 and 36: DoDI 5000.02, January 7, 2015 TABLE
  • Page 37 and 38: DoDI 5000.02, January 7, 2015 SOFTW
  • Page 39 and 40: DoDI 5000.02, January 7, 2015 Affor
  • Page 41 and 42: DoDI 5000.02, January 7, 2015 Safeg
  • Page 43 and 44: DoDI 5000.02, January 7, 2015 REFER
  • Page 45 and 46: DoDI 5000.02, January 7, 2015 (ar)
  • Page 47 and 48: DoDI 5000.02, January 7, 2015 (ck)
  • Page 49 and 50: DoDI 5000.02, January 7, 2015 Table
  • Page 51 and 52: DoDI 5000.02, January 7, 2015 (8)
  • Page 53 and 54:

    DoDI 5000.02, January 7, 2015 Table

  • Page 55 and 56:

    DoDI 5000.02, January 7, 2015 Table

  • Page 57 and 58:

    DoDI 5000.02, January 7, 2015 INFOR

  • Page 59 and 60:

    DoDI 5000.02, January 7, 2015 Table

  • Page 61 and 62:

    DoDI 5000.02, January 7, 2015 INFOR

  • Page 63 and 64:

    DoDI 5000.02, January 7, 2015 INFOR

  • Page 65 and 66:

    DoDI 5000.02, January 7, 2015 INFOR

  • Page 67 and 68:

    DoDI 5000.02, January 7, 2015 Table

  • Page 69 and 70:

    DoDI 5000.02, January 7, 2015 5. RE

  • Page 71 and 72:

    DoDI 5000.02, January 7, 2015 Table

  • Page 73 and 74:

    DoDI 5000.02, January 7, 2015 Table

  • Page 75 and 76:

    DoDI 5000.02, January 7, 2015 Table

  • Page 77 and 78:

    DoDI 5000.02, January 7, 2015 Table

  • Page 79 and 80:

    DoDI 5000.02, January 7, 2015 (3)c.

  • Page 81 and 82:

    DoDI 5000.02, January 7, 2015 a. If

  • Page 83 and 84:

    DoDI 5000.02, January 7, 2015 6. CC

  • Page 85 and 86:

    DoDI 5000.02, January 7, 2015 comma

  • Page 87 and 88:

    DoDI 5000.02, January 7, 2015 (2) P

  • Page 89 and 90:

    DoDI 5000.02, January 7, 2015 suffi

  • Page 91 and 92:

    DoDI 5000.02, January 7, 2015 (e) A

  • Page 93 and 94:

    DoDI 5000.02, January 7, 2015 secon

  • Page 95 and 96:

    DoDI 5000.02, January 7, 2015 for s

  • Page 97 and 98:

    DoDI 5000.02, January 7, 2015 For A

  • Page 99 and 100:

    DoDI 5000.02, January 7, 2015 softw

  • Page 101 and 102:

    DoDI 5000.02, January 7, 2015 assoc

  • Page 103 and 104:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 105 and 106:

    DoDI 5000.02, January 7, 2015 e. Pr

  • Page 107 and 108:

    DoDI 5000.02, January 7, 2015 gover

  • Page 109 and 110:

    DoDI 5000.02, January 7, 2015 destr

  • Page 111 and 112:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 113 and 114:

    DoDI 5000.02, January 7, 2015 b. Le

  • Page 115 and 116:

    DoDI 5000.02, January 7, 2015 (c) C

  • Page 117 and 118:

    DoDI 5000.02, January 7, 2015 7. OT

  • Page 119 and 120:

    DoDI 5000.02, January 7, 2015 10. R

  • Page 121 and 122:

    DoDI 5000.02, January 7, 2015 (b) F

  • Page 123 and 124:

    DoDI 5000.02, January 7, 2015 test

  • Page 125 and 126:

    DoDI 5000.02, January 7, 2015 14. T

  • Page 127 and 128:

    DoDI 5000.02, January 7, 2015 7014)

  • Page 129 and 130:

    DoDI 5000.02, January 7, 2015 c. Th

  • Page 131 and 132:

    DoDI 5000.02, January 7, 2015 a. Ma

  • Page 133 and 134:

    DoDI 5000.02, January 7, 2015 meeti

  • Page 135 and 136:

    DoDI 5000.02, January 7, 2015 and s

  • Page 137 and 138:

    DoDI 5000.02, January 7, 2015 b. Af

  • Page 139 and 140:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 141 and 142:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 143 and 144:

    DoDI 5000.02, January 7, 2015 Repor

  • Page 145 and 146:

    DoDI 5000.02, January 7, 2015 a. Do

  • Page 147 and 148:

    DoDI 5000.02, January 7, 2015 (4) T

  • Page 149 and 150:

    DoDI 5000.02, January 7, 2015 (1) T

  • Page 151 and 152:

    DoDI 5000.02, January 7, 2015 d. Ap

  • Page 153 and 154:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 155 and 156:

    DoDI 5000.02, January 7, 2015 (f) S

  • Page 157 and 158:

    DoDI 5000.02, January 7, 2015 b. Th

  • Page 159 and 160:

    DoDI 5000.02, January 7, 2015 (3) A

  • Page 161 and 162:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 163 and 164:

    DoDI 5000.02, January 7, 2015 4. RA

  • Page 165 and 166:

    DoDI 5000.02, January 7, 2015 (d) F

  • Page 167 and 168:

    DoDI 5000.02, January 7, 2015 (i) A

  • Page 169 and 170:

    DoDI 5000.02, January 7, 2015 and f

  • Page 171 and 172:

    DoDI 5000.02, January 7, 2015 ENCLO

  • Page 173 and 174:

    DoDI 5000.02, January 7, 2015 d. Sy

  • Page 175 and 176:

    DoDI 5000.02, January 7, 2015 (2) A

  • Page 177 and 178:

    DoDI 5000.02, January 7, 2015 (13)

  • Page 179 and 180:

    DoDI 5000.02, January 7, 2015 throu

  • Page 181 and 182:

    DoDI 5000.02, January 7, 2015 (5) I

  • Page 183 and 184:

    DoDI 5000.02, January 7, 2015 updat

  • Page 185 and 186:

    DoDI 5000.02, January 7, 2015 Table

  • Page 187 and 188:

    DoDI 5000.02, January 7, 2015 Table

joint program management handbook - Defense Acquisition University
OVERVIEW W - Office of the Under Secretary of Defense (Comptroller)
Joint Pub 6-02 - United States Department of Defense
Department of Defense (DoD) Information Enterprise Strategic Plan
MITRE-Defense-Agile-Acquisition-Guide
USAF ILA Handbook - ACC Practice Center - Defense Acquisition ...
Developing Operational Requirements - U.S. Department of ...
Department of Defense Nonlethal Weapons and Equipment Review
DEFENSE ACQUISITION GUIDEBOOK - AcqNotes.com
Navy Cyber Power 2020 - Defense Innovation Marketplace
Quadrennial Defense Review (QDR) - United States Department of ...
JP 4-02 Health Service Support - DMRTI - Defense Medical ...
department of defense more disciplined use of resources
Department of Defense Nonlethal Weapons and Equipment Review
COL Mike Zarbo - PEO STRI - U.S. Army
department of defense agency financial report fiscal year 2012
department of defense agency financial report fiscal year 2012
Volume 5, Number 1 - Space and Missile Defense Command - U.S. ...
JP 3-01 Countering Air and Missile Threats - Defense Innovation ...
Joint Service Chemical and Biological Defense Program FY00-02 ...
Space Acquisition - Air Force Space Command
Mission: Possible - Chief Information Officer