Browse Arkansas Code titles and sections

10 U.S.C. § 3101 — Definitions

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 3101 — Definitions

In this chapter: (1) The term “best value” means, with respect to an acquisition, the optimal combination of cost, quality, technical capability or solution quality, and delivery schedule. (2) The term “capability requirement” means a capability that is critical or essential to address an operational problem. (3) The term “cost-effective” means, with respect to an acquisition, delivering superior end-user results at equal or lower cost compared to alternatives. (4) The term “operational problem” means— (A) a challenge of a military department in achieving an assigned military objective based on current doctrine, emerging threats, or future concepts; and (B) may include limitations in capabilities, capacity, resources, or the ability to effectively and efficiently coordinate across the joint force, with another combatant command, or among military capabilities. (5) The term “service chief” means— (A) the Chief of Staff of the Army, with respect to matters concerning the Army; (B) the Chief of Naval Operations, with respect to matters concerning the Navy; (C) the Commandant of the Marine Corps, with respect to matters concerning the Marine Corps; (D) the Chief of Staff of the Air Force, with respect to matters concerning the Air Force; and (E) the Chief of Space Operations, with respect to matters concerning the Space Force.

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3101

Stored review status: release_metadata_unconfirmed. A text match is a research starting point; applicability is not established.

Original supplied file — preserved unchanged

Download original Markdown file

File SHA-256: acc4004fbcc032c3772415f675cb24cc742ad183860ea3f80efbbfb6c0a4096c. The original may include catalog metadata, neighboring provisions, or embedded records outside this collection's scope. Search shows only the selected federal record. Historical editions and unverified snapshots are not a statement of current law.

Authority boundary: historical or unconfirmed source not current law verified.

Open the recorded source website ↗

Record provenance

Stable record: federal_law:legal_authorities:record_usc_b22297f43bea863f4f3c9eb1
Source file: Laws/federal/codes/united-states-code/title-10/section-3101-definitions--f0325c3365.md
Pages: Not recorded – Not recorded
Passage SHA-256: afdfad666f0012dea91d6092467722a8df3f47eda55470e8b4c6308580b9241a

Source location: Title 10, Chapter 205, § 3101; chapter-205-defense-acquisition-system.md

Stored source content

Cross-references

Connections may be documented source relationships, shared citations or nearby passages. Each explains its basis; a connection alone does not establish applicability to your situation.

Federal law — U.S. Code and appendices · legal_authorities

41 U.S.C. § 131 — Acquisition

In division B, the term “acquisition”— (1) means the process of acquiring, with appropriated amounts, by contract for purchase or lease, property or services (including construction) that support the missions and goals of an executive agency, from the point at which the requirements of the executive agency are established in consultation with the chief acquisition officer of the executive agency; and (2) includes— (A) the process of acquiring property or services that are already in existence, or that must be created, developed, demonstrated, and evaluated; (B) the description of requirements to satisfy agency needs; (C) solicitation and selection of sources; (D) award of contracts; (E) contract performance; (F) contract financing; (G) management and measurement of contract performance through final delivery and payment; and (H) technical and management functions directly related to the process of fulfilling agency requirements by contract.

Source: Supplied U.S. Code snapshot — release unconfirmed · 41 U.S.C. § 131

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 2545 — Renumbered § 3101]

### Statutory Notes #### Codification Section was also transferred or copied in large part to [section 3001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3001&num=0&edition=prelim) by Pub. L. 116–283, § 1806(a)(2)–(4). #### Prior Provisions A prior section 2545 was renumbered [section 2555 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2555&num=0&edition=prelim).

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2545

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 3001 — Defense acquisition system; element of the defense acquisition system

**(a) Defense Acquisition System.—** In this part, the term “defense acquisition system” means— (1) the workforce engaged in carrying out the acquisition of property and services for the Department of Defense; (2) the management structure responsible for directing and overseeing the acquisition of property and services for the Department of Defense; and (3) the statutory, regulatory, and policy framework that guides the acquisition of property and services for the Department of Defense. **(b) Element of the Defense Acquisition System.—** In this part, the term “element of the defense acquisition system” means an organization that— (1) employs members of the acquisition workforce; (2) carries out acquisition functions; and (3) focuses primarily on acquisition. **(c) Acquisition.—** In this part, the term “acquisition” has the meaning provided in [section 131 of title 41](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title41-section131&num=0&edition=prelim).

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3001

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 1732 — Portfolio acquisition executive

**(a) In General.—** A portfolio acquisition executive is the senior acquisition official designated by the component acquisition executive or the service acquisition executive of the military department concerned, as applicable, to lead a portfolio of capabilities, with authority for plans, budgets, and execution of programs assigned to the portfolio, including life-cycle management. **(b) Reporting Relationships.—** To ensure streamlined accountability for management, the following relationships shall apply: (1) Each program manager (as defined in [section 1737 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section1737&num=0&edition=prelim)) for a defense acquisition program shall report directly to the portfolio acquisition executive for such program unless otherwise directed by the component acquisition executive or service acquisition executive of the military department concerned (as applicable). (2) Each portfolio acquisition executive shall report directly to the component acquisition executive or the service acquisition executive of the military department concerned (as applicable). (3) The component acquisition executive or service acquisition executive of the military department concerned (as applicable) shall oversee the designation of, performance of, and resource allocation for all portfolio acquisition executives. **(c) Responsibilities.—** For the defense acquisition programs assigned to a portfolio acquisition executive, such portfolio acquisition executive shall— (1) ensure that activities carried out under such programs are aligned with, and are conducted in a manner that supports, the objectives of the defense acquisition system established pursuant to [section 3102 of this title](https://uscode.house.gov/vi

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 1732

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 1733 — Product support manager

**(a) In General.—** A product support manager is the individual responsible for managing product support required to field and maintain the readiness and operational capability of a covered system throughout the life cycle of the covered system. **(b) Designation.—** The Secretary of Defense shall designate a product support manager for each covered system who shall be coequal with the program manager for such covered system and report directly to the portfolio acquisition executive responsible for such covered system. **(c) Objectives.—** The product support manager shall seek to achieve the objectives of the defense acquisition system established pursuant to [section 3102 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3102&num=0&edition=prelim) and shall identify, develop, implement, incentivize, and measure quantifiable best value outcome-based product support that optimizes life-cycle cost, readiness, and operational capability of a covered system. **(d) Specific Responsibilities.—** A product support manager shall be responsible for the following with respect to a covered system: (1) Developing and executing the product support strategy required under [section 4324 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4324&num=0&edition=prelim). (2) Providing product support and subject matter expertise to the relevant program manager and portfolio acquisition executive. (3) 11 So in original. There are two pars. (3). Collaborating with chief engineers and systems engineers— (A) in developing the life-cycle sustainment plan and product support strategy required under [section 4324 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4324&

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 1733

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 1746 — Defense Acquisition University

**(a) Defense Acquisition University Structure.—** The Secretary of Defense, acting through the Under Secretary of Defense for Acquisition and Sustainment, shall establish and maintain a defense acquisition university structure to provide for— (1) the professional educational development and training of the acquisition workforce; and (2) research and analysis of defense acquisition policy issues from an academic perspective. **(b) Civilian Faculty Members.—** (1) The Secretary of Defense may employ as many civilians as professors, instructors, and lecturers in the defense acquisition university structure as the Secretary considers necessary. (2) The Secretary of Defense shall ensure the defense acquisition university structure includes relevant expert lecturers from extramural institutions (as defined in [section 1746a(g) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section1746a/g&num=0&edition=prelim)), industry, or federally funded research and development centers to advance acquisition workforce competence regarding commercial business interests, acquisition process-related innovations, and other relevant leading practices of the private sector. (3) The compensation of persons employed under this subsection shall be as prescribed by the Secretary. (4) In this subsection, the term “defense acquisition university” includes the Defense Systems Management College. **(c) Curriculum Development.—** The President of the Defense Acquisition University shall work with the relevant professional schools and degree-granting institutions of the Department of Defense and military departments, and with extramural institutions (as defined in [section 1746a(g) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-ti

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 1746

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 181 — Joint Requirements Oversight Council

**(a) In General.—** There is a Joint Requirements Oversight Council in the Department of Defense. **(b) Mission.—** In addition to other matters assigned to it by the President or Secretary of Defense, the Joint Requirements Oversight Council shall assist the Chairman of the Joint Chiefs of Staff in— (1) evaluating global trends, emerging threats, and adversary capabilities to inform understanding of joint operational problems and to shape joint force design; (2) coordinating with commanders of combatant commands to compile, refine, and prioritize joint operational problems; (3) continuously reviewing and assessing joint military capabilities of elements of the Department of Defense listed in [section 111(b) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section111/b&num=0&edition=prelim) in a manner that meets applicable requirements in the national defense strategy under [section 113(g) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section113/g&num=0&edition=prelim); (4) identifying and prioritizing gaps and opportunities in joint military capabilities, including making recommendations for changes to address such capability and capacity gaps; (5) identifying advances in technology, innovative commercial solutions, and concepts of operation that could improve the military advantage of the joint force; (6) recommending joint capability requirements that— (A) describe the joint operational problem to provide necessary context for the joint capability requirement; (B) proposes nonprescriptive solutions to joint operational problems; and (C) ensures system interoperability, where appropriate, between and among joint military capabilities; (7) designing the joint force in a manner t

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 181

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 2820 — Development of infrastructure improvement plan for each military department

**(a) In General.—** Not later than the date on which the budget of the President for fiscal year 2027 is submitted to Congress pursuant to [section 1105 of title 31](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title31-section1105&num=0&edition=prelim), and once every five years thereafter, each Secretary concerned shall submit to the congressional defense committees each of the following: (1) A detailed plan with respect to the improvement of infrastructure and facilities under the jurisdiction of the Secretary concerned during the 20-year period beginning after the date on which the plan is submitted that includes— (A) a summary of major efforts of the Secretary concerned to be carried out pursuant to the plan; (B) milestones and specific goals for such major efforts; (C) a description of objectives of the Secretary concerned to manage and improve such infrastructure and facilities during such period, including— (i) utility systems (electric, water and wastewater systems, energy distribution systems, transportation, and communication networks); and (ii) all physical structures located on a military installation under the jurisdiction of the Secretary concerned. (2) A certification that the budget of the President for the applicable fiscal year and the future-years defense program submitted to Congress in relation to such budget under [section 221 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section221&num=0&edition=prelim) provide for funding of planning, design, and construction at a level that is sufficient to meet the requirements specified in the plan under paragraph (1) on the schedule provided in such plan. **(b) Elements.—** Each plan submitted by a Secretary concerned under subsectio

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2820

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 3102 — Objectives of the defense acquisition system

**(a) In General.—** The Secretary of Defense shall ensure that the defense acquisition system expeditiously provides the armed forces with the capabilities necessary to operate effectively, to address evolving threats, and to sustain the military advantage of the United States in the most cost-effective manner practicable. **(b) Guidance.—** The Secretary of Defense shall issue guidance to carry out subsection (a) and shall ensure that the defense acquisition system prioritizes the needs of end users and is validated by direct engagement, experimentation, and iteration. Such guidance shall require the following: (1) All activities of the defense acquisition system contribute to the expeditious delivery of capabilities to enhance the operational readiness of the armed forces and enable the missions of the Department of Defense. (2) A leadership culture and organizational structure that empowers individuals in the management of the defense acquisition system and encourages appropriate delegation authority, collaboration, and mission-focused risk-taking. (3) Sufficient numbers of members of the acquisition workforce to support the defense acquisition system, and that such members are properly trained and assigned. (4) Resource decisions for the defense acquisition system to prioritize best value and seek to balance life-cycle costs, schedule, performance, and quantity through continuous trade-off analysis informed by prototyping and direct feedback from end users. (5) Adoption and integration in the defense acquisition system of advanced approaches in digital engineering, model-based engineering, and simulation environments to enable rapid, iterative designs and technology insertion to maximize mission outcomes. (6) Active pursuit of innovative solutions to enhance

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3102

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 4172 — Major systems and munitions programs: survivability testing and lethality testing required before full-scale production

**(a) Requirements.—** (1) The Secretary of Defense shall provide that— (A) a covered system may not proceed beyond low-rate initial production until realistic survivability testing of the system is completed in accordance with this section and the report required by subsection (d) with respect to that testing is submitted in accordance with that subsection; and (B) a major munition program or a missile program may not proceed beyond low-rate initial production until realistic lethality testing of the program is completed in accordance with this section and the report required by subsection (d) with respect to that testing is submitted in accordance with that subsection. (2) The Secretary of Defense shall provide that a covered product improvement program may not proceed beyond low-rate initial production until— (A) in the case of a product improvement to a covered system, realistic survivability testing is completed in accordance with this section; and (B) in the case of a product improvement to a major munitions program or a missile program, realistic lethality testing is completed in accordance with this section. **(b) Test Guidelines.—** (1) Survivability and lethality tests required under subsection (a) shall be carried out sufficiently early in the development phase of the system or program (including a covered product improvement program) to allow any design deficiency demonstrated by the testing to be corrected in the design of the system, munition, or missile (or in the product modification or upgrade to the system, munition, or missile) before proceeding beyond low-rate initial production. (2) The costs of all tests required under that subsection shall be paid from funds available for the system being tested. **(c) Waiver Authority.—** (1) T

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4172

Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.