(a)
(1) The development of requirements for equipping the armed force concerned (subject, where appropriate, to validation by the Joint Requirements Oversight Council pursuant to section 181 of this title).
(2) Decisions regarding the balancing of resources and priorities, and associated trade-offs among cost, schedule, technical feasibility, and performance on major defense acquisition programs.
(3) The coordination of measures to control requirements creep in the defense acquisition system.
(4) The recommendation of trade-offs among life-cycle cost, schedule, and performance objectives, and procurement quantity objectives, to ensure acquisition programs deliver best value in meeting the approved military requirements.
(5) Termination of development or procurement programs for which life-cycle cost, schedule, and performance expectations are no longer consistent with approved military requirements and levels of priority, or which no longer have approved military requirements.
(6) The development and management of career paths in acquisition for military personnel (as required by section 1722a of this title).
(7) The assignment and training of contracting officer representatives when such representatives are required to be members of the armed forces because of the nature of the contract concerned.
(b)
(2) Consistent with the performance of duties under subsection (a), the Chief of the armed force concerned, or in the case of a joint program the chiefs of the armed forces concerned, with respect to major defense acquisition programs, shall—
(A) concur with the need for a materiel solution as identified in the Materiel Development Decision Review prior to entry into the Materiel Solution Analysis Phase under Department of Defense Instruction 5000.02;
(B) concur with the cost, schedule, technical feasibility, and performance trade-offs that have been made with regard to the program before Milestone A approval is granted under section 2366a of this title;
(C) concur that appropriate trade-offs among cost, schedule, technical feasibility, and performance objectives have been made to ensure that the program is affordable when considering the per unit cost and the total life-cycle cost before Milestone B approval is granted under section 2366b of this title; and
(D) concur that the requirements in the program capability document are necessary and realistic in relation to program cost and fielding targets as required by paragraph (1) before Milestone C approval is granted.
(c)
(d)
(1) The term "requirements creep" means the addition of new technical or operational specifications after a requirements document is approved by the appropriate validation authority for the requirements document.
(2) The term "requirements document" means a document produced in the requirements process that is provided for an acquisition program to guide the subsequent development, production, and testing of the program and that—
(A) justifies the need for a materiel approach, or an approach that is a combination of materiel and non-materiel, to satisfy one or more specific capability gaps;
(B) details the information necessary to develop an increment of militarily useful, logistically supportable, and technically mature capability, including key performance parameters; or
(C) identifies production attributes required for a single increment of a program.
(3) The term "program capability document" has the meaning provided in section 2446a(b)(5) of this title.
Prior Provisions
A prior section 2547 was renumbered section 2557 of this title.
Amendments
2019—Subsec. (b)(2)(A). Pub. L. 116–92 substituted "materiel" for "material" and "Materiel" for "Material" in two places.
2018—Subsec. (c). Pub. L. 115–232 substituted "section 7014(c)(1)(A), section 8014(c)(1)(A), or section 9014(c)(1)(A)" for "section 3014(c)(1)(A), section 5014(c)(1)(A), or section 8014(c)(1)(A)".
2017—Subsec. (b). Pub. L. 115–91 designated existing provisions as par. (1) and added par. (2).
2016—Subsecs. (b), (c). Pub. L. 114–328, §807(c)(1), (2), added subsec. (b) and redesignated former subsec. (b) as (c). Former subsec. (c) redesignated (d).
Subsec. (d). Pub. L. 114–328, §807(c)(1), redesignated subsec. (c) as (d).
Subsec. (d)(3). Pub. L. 114–328, §807(c)(3), added par. (3).
2015—Subsec. (a)(2) to (5). Pub. L. 114–92, §802(b)(1), (2), added par. (2) and redesignated former pars. (2) to (4) as (3) to (5), respectively. Former par. (5) redesignated (6).
Subsec. (a)(6). Pub. L. 114–92, §802(b)(1), (3), redesignated par. (5) as (6) and substituted "The development and management" for "The development". Former par. (6) redesignated (7).
Subsec. (a)(7). Pub. L. 114–92, §802(b)(1), redesignated par. (6) as (7).
2013—Subsec. (a)(1). Pub. L. 112–239, §951(c)(1), substituted "of requirements for equipping the armed force concerned" for "of requirements relating to the defense acquisition system".
Subsec. (a)(3) to (6). Pub. L. 112–239, §951(c)(2), (3), added pars. (3) and (4) and redesignated former pars. (3) and (4) as (5) and (6), respectively.
Effective Date of 2018 Amendment
Amendment by Pub. L. 115–232 effective Feb. 1, 2019, with provision for the coordination of amendments and special rule for certain redesignations, see section 800 of Pub. L. 115–232, set out as a note preceding section 3001 of this title.
Tried the LawStack mobile app?
Join thousands and try LawStack mobile for FREE today.
- Carry the law offline, wherever you go.
- Download CFR, USC, rules, and state law to your mobile device.
