Sec. 802. Capstone requirements
493 words·~2 min read·
/bill/119/s/2296/es/section-802A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
Chapter 221 of title 10, United States Code, is amended by adding at the end the following new section: The Secretary of each military department shall establish a capstone requirement approach for three or more portfolio acquisition executives for which that official has responsibility to enable greater speed, agility, and innovation in fielding military capabilities. Each such capstone requirement shall be established in consultation with the Joint Requirements Oversight Council. Under the capstone requirements for an acquisition portfolio, the Secretary of the military department shall— develop a general set of requirements for the acquisition portfolio in accordance with subsection
(c)under which programs or projects may be initiated; authorize the portfolio acquisition executive or similar portfolio manager for the portfolio to change the scope and requirements for programs within the portfolio, subject to subsection (d); assign representatives of operational forces to the acquisition portfolio and authorize them to perform the functions specified in subsection (e); maximize commercial market research, the use of commercial and nondevelopmental items, and minimum viable products to shape capability scope and requirements; authorize the portfolio acquisition executive or similar portfolio manager to resource and acquire commercial or non-developmental items under the capstone requirement by validating the need with the representatives assigned under paragraph (3); manage information technology requirements using dynamically prioritized lists of user needs rather than large static requirements documents; and iteratively define, prioritize, and refine requirements at the portfolio, program, and iteration levels based on user input, previous deliveries, and continuous commercial market research. The capstone set of requirements for an acquisition portfolio developed under subsection (b)(1) shall be designed— to guide the iterative delivery of an integrated suite of capabilities to maximize operational impact; to provide enduring themes based on strategic needs and relevant concepts of operation, not system-specific; to include measures of force effectiveness for a force mix of capabilities to be measured against; and to include kill chains, effects chains, vignettes of operational scenarios, the effect of timely delivery of capability, and related mission engineering initiatives across the Department of Defense. The authority under subsection (b)(2)— shall be carried out in consultation with operational commands and the Joint Requirements Oversight Council; and does not include authority to change key performance parameters for a major defense acquisition program. An operational representative assigned to an acquisition portfolio under subsection (b)(3) shall be provided authority— to shape the vision and priorities for key capability areas; to provide the acquisition community and developers insights into operations; to provide feedback on interim developments; to validate the suitability of existing commercial or non-developmental items, or the likelihood that the commercial market may be enticed to produce those items, or, as a last resort, validate that no commercial vendor will ever produce a suitable product and a developmental program is necessary; to foster collaboration among the acquisition community, developers, and users of the capability to be fielded; and to provide advice to the portfolio acquisition executive or similar portfolio manager. .