1 year ago

Department of Defense INSTRUCTION


DoDI 5000.02, January 7,

DoDI 5000.02, January 7, 2015 c. Component Acquisition Executive (CAE). The CAE will serve as the decision authority for DBS programs that do not meet the MAIS threshold in Table 1 in Enclosure 1, are not expected to exceed those thresholds, have not been designated special interest, or are not otherwise under OSD oversight. The capability requirements and acquisition processes and procedures for such programs will be consistent with applicable statute, regulation, and this enclosure. d. Functional Sponsors (1) Functional sponsors are the OSD or DoD Component executives responsible for: (a) Representing user community interests through the formulation of capability requirements. (b) Ensuring funding availability for DBS investments, to include the process of capability requirements definition. (c) Sponsoring the Problem Statement and the implementation of the non-materiel portions of the overall DOTMLPF-P solution. d) Defining threshold and objective measures for capability requirements. (e) Supporting the Program Manager in development of the program acquisition strategy, accomplishing effective business process re-engineering (BPR), and implementing the materiel portion of the DOTMLPF-P solution. (f) Validating that Initial Operational Capability has been achieved in alignment with KPPs and other applicable measures. (g) Validating that threshold KPPs are met before the Full Deployment Decision. (2) The Functional Sponsor will regularly review threshold capability requirements, including KPPs, as appropriate and, if substantive changes are required, submit such changes for approval before a certification or acquisition decision. e. Military Department Chief Management Officers (CMOs). The Military Department CMOs of the Department of Defense are the Service-level executives responsible for: (1) Serving as the AAO for their Department. In that capacity, the Military Department CMO/AAO will conduct a review of non-priority DBS and determine whether the programs should be certified. If the CMO determines that a program cannot be certified, the CMO will notify the MDA and recommend corrective action. (2) Reviewing and prioritizing all DBS capability requirements in their respective portfolios. Change 2, 02/02/2017 158 ENCLOSURE 12

DoDI 5000.02, January 7, 2015 (3) Approving DBS capability requirements in the form of Problem Statements for nonpriority DBS. f. AAO. The AAOs of the Department of Defense are typically either the DCMO or the Military Department CMO (unless otherwise specified by the Secretary of Defense). The DCMO or Military Department CMOs may designate additional AAOs as necessary. (1) A DBS AAO must conduct an initial approval review in accordance with 10 U.S.C. 2222 (Reference (h)) which, at minimum, determines: (a) That a business need and its recommended solution are or will be: 1. Compliant with the Business Enterprise Architecture (BEA). 2. Consistent with established portfolio priorities. (b) Appropriate BPR has been conducted. (c) The elimination of unique software requirements and unique interfaces has been maximized to the greatest extent practicable. (2) The AAO’s initial approval also serves as a certification as required by 10 U.S.C. 2222 (Reference (h)). The certification must occur before a DBS program begins development (or subsequent program stages, if there is no development). (3) A DBS AAO must conduct an annual program certification for any fiscal year in which funds are expended for development or sustainment on a covered DBS program. The current certification must be provided to the MDA before any program decision review. If the program cannot be certified, the AAO will notify the MDA and provide a recommendation for corrective action. 4. PROBLEM STATEMENT. DBS generally do not employ JCIDS procedures for the development and validation of capability requirements documents. Instead, functional sponsors will analyze a perceived business need, capability gap, or opportunity and document the results of the analysis in a Problem Statement. The approved Problem Statement supports development of the acquisition strategy in subsequent phases of the program. Approval authorities are defined in paragraphs 3b(1)(c) and 3e(3). a. The Problem Statement is the output of an analytic process and will include definition of: the business need; the desired end-state; enablers and/or constraints; measurable business outcomes which will serve as indicators of progress toward achievement of the end-state; the DOTMLPF-P capabilities required to solve the business need; a rough order of magnitude cost estimate for the effort; and a projected or anticipated return on investment, which may include Change 2, 02/02/2017 159 ENCLOSURE 12

Joint Pub 6-02 - United States Department of Defense
Quadrennial Defense Review (QDR) - United States Department of ...
department of defense more disciplined use of resources
Download PDF - Department of Navy Chief Information Officer - U.S. ...
DHS - S&T Chemical and Biological Defense Programs - Sandia ...
Operating instructions
joint program management handbook - Defense Acquisition University
Major Management Challenges Facing the Department of ...
Instruction Manual - Cole-Parmer
OVERVIEW W - Office of the Under Secretary of Defense (Comptroller)
Executive summary (pdf - 175KB) - National Audit Office
Download WS-6909 Instruction Manual - MultiMedia Systems
Developing Operational Requirements - U.S. Department of ...
Department of Defense (DoD) Information Enterprise Strategic Plan
Joint Service Chemical and Biological Defense Program FY00-02 ...
USAF ILA Handbook - ACC Practice Center - Defense Acquisition ...
Navy Cyber Power 2020 - Defense Innovation Marketplace