Browse Arkansas Code titles and sections
10 U.S.C. § 8669b — Senior Technical Authority for each naval vessel class
Federal law — U.S. Code and appendices · legal_authorities
**(a) Senior Technical Authority.—**
(1) **Designation for each vessel class required.—** — The Secretary of the Navy shall designate, in writing, a Senior Technical Authority for each class of naval vessels as follows:
(A) In the case of a class of vessels which has received Milestone A approval, an approval to enter into technology maturation and risk reduction, or an approval to enter into a subsequent Department of Defense or Department of the Navy acquisition phase as of the date of the enactment of the National Defense Authorization Act for Fiscal Year 2020, not later than 30 days after such date of enactment.
(B) In the case of any class of vessels which has not received any approval described in subparagraph (A) as of such date of enactment, at or before the first of such approvals.
(2) **Individuals eligible for designation.—** — Each individual designated as a Senior Technical Authority under paragraph (1) shall be an employee of the Navy in the Senior Executive Service in an organization of the Navy that—
(A) possesses the technical expertise required to carry out the responsibilities specified in subsection (b); and
(B) reports directly to the portfolio acquisition executive, established under [section 1732 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section1732&num=0&edition=prelim).
(3) **Term.—** — Each Senior Technical Authority shall be designated for a fixed term, not shorter than the time anticipated to establish demonstrated successful performance of the class of vessels concerned in accordance with its approved capabilities document, as determined by the Secretary at the time of designation.
(4) **Voluntary departure.—** — If an individual designated as a Senior Technical Authority voluntarily
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 8669b
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: 77f8e59e93f32811a811f8db1a3b0fa5513889e13f98fb579e08dd173698b78a. 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_a75aea9b5e00dbfc57c0f9e2
Source file: Laws/federal/codes/united-states-code/title-10/section-8669b-senior-technical-authority-for-each-naval-vessel-class--92b4ad6092.md
Pages: Not recorded – Not recorded
Passage SHA-256: 93a30ac518fcf660aafd1e324ed085f8a4dc5d90d2306b58d9d68c03fff2c16d
Source location: Title 10, Chapter 863, § 8669b; chapter-863-naval-vessels.md
Stored source content
**(a) Senior Technical Authority.—**
(1) **Designation for each vessel class required.—** — The Secretary of the Navy shall designate, in writing, a Senior Technical Authority for each class of naval vessels as follows:
(A) In the case of a class of vessels which has received Milestone A approval, an approval to enter into technology maturation and risk reduction, or an approval to enter into a subsequent Department of Defense or Department of the Navy acquisition phase as of the date of the enactment of the National Defense Authorization Act for Fiscal Year 2020, not later than 30 days after such date of enactment.
(B) In the case of any class of vessels which has not received any approval described in subparagraph (A) as of such date of enactment, at or before the first of such approvals.
(2) **Individuals eligible for designation.—** — Each individual designated as a Senior Technical Authority under paragraph (1) shall be an employee of the Navy in the Senior Executive Service in an organization of the Navy that—
(A) possesses the technical expertise required to carry out the responsibilities specified in subsection (b); and
(B) reports directly to the portfolio acquisition executive, established under [section 1732 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section1732&num=0&edition=prelim).
(3) **Term.—** — Each Senior Technical Authority shall be designated for a fixed term, not shorter than the time anticipated to establish demonstrated successful performance of the class of vessels concerned in accordance with its approved capabilities document, as determined by the Secretary at the time of designation.
(4) **Voluntary departure.—** — If an individual designated as a Senior Technical Authority voluntarily departs the position before demonstrated successful performance of the class of vessels concerned, the Secretary shall designate, in writing, a replacement, and shall notify, in writing, the congressional defense committees not later than 90 days after such departure.
(5) **Removal.—** — An individual may be removed involuntarily from designation as a Senior Technical Authority only by the Secretary. Not later than 15 days after the involuntary removal of an individual from such designation, the Secretary shall notify, in writing, the congressional defense committees of the removal, including the reasons for the removal. Not later than 90 days after the involuntary removal, the Secretary shall designate, in writing, a replacement, and shall notify, in writing, the congressional defense committees of such designation.
(6) **Reassignment for mission needs.—** — Subject to paragraphs (4) and (5), the Secretary may reassign a Senior Technical Authority or remove an individual from designation as a Senior Technical Authority in furtherance of Department of the Navy mission needs.
**(b) Responsibilities and Authority.—**
(1) Each Senior Technical Authority shall be responsible for, and have the authority to, establish, monitor, and approve technical standards, tools, and processes for the class of naval vessels for which designated under this section in conformance with applicable laws and Department of Defense and Department of the Navy policies, requirements, architectures, and standards.
(2) Each Senior Technical Authority shall also be responsible for the determination that all design requirements for a vessel class are directly related to a key performance parameter or key system attribute established in the capability development document for such class. Any such requirement that the Senior Technical Authority determines is unnecessary to meet a key performance parameter or key system attribute shall not be approved.
**(c) Limitation on Obligation of Funds on Lead Vessel in Vessel Class.—**
(1) **In general.—** — On or after January 1, 2021, funds authorized to be appropriated for Shipbuilding and Conversion, Navy or Other Procurement, Navy may not be obligated for the first time on the lead vessel in a class of naval vessels unless the Secretary of the Navy certifies as described in paragraph (2).
(2) **Certification elements.—** — The certification on a class of naval vessels described in this paragraph is a certification containing each of the following:
(A) The name or names of the individual or individuals designated as the Senior Technical Authority for such class of vessels, and the qualifications and professional biography or biographies of the individual or individuals so designated.
(B) A description by the Senior Technical Authority of the systems engineering, technology, and ship integration risks for such class of vessels.
(C) The designation by the Senior Technical Authority of each critical hull, mechanical, electrical, propulsion, and combat system of such class of vessels, including systems relating to power generation, power distribution, and key operational mission areas.
(D) The date on which the Senior Technical Authority approved the systems engineering, engineering development, and land-based engineering and testing plans for such class of vessels.
(E) A description by the Senior Technical Authority of the key technical knowledge objectives and demonstrated system performance of each plan approved as described in subparagraph (D).
(F) A determination by the Senior Technical Authority that such plans are sufficient to achieve thorough technical knowledge of critical systems of such class of vessels before the start of detail design and construction.
(G) A determination by the Senior Technical Authority that actual execution of activities in support of such plans as of the date of the certification have been and continue to be effective and supportive of the acquisition schedule for such class of vessels.
(H) A description by the Senior Technical Authority of other technology maturation and risk reduction efforts not included in such plans for such class of vessels taken as of the date of the certification.
(I) A certification by the Senior Technical Authority that each critical system covered by subparagraph (C) has been demonstrated through testing of a prototype or identical component in its final form, fit, and function in a realistic environment.
(J) A determination by the Secretary that the plans approved as described in subparagraph (D) are fully funded and will be fully funded in the future-years defense program for the fiscal year beginning in the year in which the certification is submitted.
(K) A determination by the Secretary that the Senior Technical Authority will approve, in writing, the ship specification for such class of vessels before the request for proposals for detail design, construction, or both, as applicable, is released.
(3) **Deadline for submittal of certification.—** — The certification required by this subsection with respect to a class of naval vessels shall be submitted, in writing, to the congressional defense committees not fewer than 30 days before the Secretary obligates for the first time funds authorized to be appropriated for Shipbuilding and Conversion, Navy or Other Procurement, Navy for the lead vessel in such class of naval vessels.
**(d) Definitions.—** In this section:
(1) The term “class of naval vessels”—
(A) means any group of similar undersea or surface craft procured with Shipbuilding and Conversion, Navy or Other Procurement, Navy funds, including manned, unmanned, and optionally-manned craft; and
(B) includes—
(i) a substantially new class of craft (including craft procured using “new start” procurement); and
(ii) a class of craft undergoing a significant incremental change in its existing class (such as a next “flight” of destroyers or next “block” of attack submarines).
(2) The term “future-years defense program” has the meaning given that term in [section 221 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section221&num=0&edition=prelim).
(3) The term “Milestone A approval” means a decision to enter into technology maturation and risk reduction pursuant to guidance prescribed by the Secretary of Defense for the management of Department of Defense acquisition programs.
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
**(a) Acquisition Strategy Required.—** There shall be an acquisition strategy for each major defense acquisition program and each major system approved by a decision authority.
**(b) Responsible Official.—** For each acquisition strategy required by subsection (a), the Under Secretary of Defense for Acquisition and Sustainment, or the decision authority, when the decision authority is the service acquisition executive of the military department that is managing the program, is responsible for issuing and maintaining the requirements for—
(1) the content of the strategy; and
(2) the review and approval process for the strategy.
**(c) Considerations.—**
(1) In issuing requirements for the content of an acquisition strategy for a major defense acquisition program or major system, the Under Secretary, or the decision authority, when the decision authority is the service acquisition executive of the military department that is managing the program, shall ensure that—
(A) the strategy clearly describes the proposed business case and capability management approach for the program or system, and to the maximum extent practicable, describes how capability requirements will be met through delivery of such program or system;
(B) the strategy contains a clear explanation of the resources, such as time, funding, and management capacity, necessary to meet capability requirements;
(C) the strategy is tailored to address program requirements and constraints; and
(D) the strategy considers the items listed in paragraph (2).
(2) Each strategy shall, where appropriate, consider the following:
(A) An approach that delivers required capabilities in increments, each depending on available mature technology, and that recognizes up front the need for future capability imp
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4211
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
**(a)** The Secretary of Defense shall submit to Congress each year, not later than five days after the date on which the President’s budget is submitted to Congress that year under [section 1105(a) of title 31](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title31-section1105/a&num=0&edition=prelim), a future-years defense program (including associated annexes) reflecting the estimated expenditures and proposed appropriations included in that budget. Any such future-years defense program shall cover the fiscal year with respect to which the budget is submitted and at least the four succeeding fiscal years.
**(b)**
(1) The Secretary of Defense shall ensure that amounts described in subparagraph (A) of paragraph (2) for any fiscal year are consistent with amounts described in subparagraph (B) of paragraph (2) for that fiscal year.
(2) Amounts referred to in paragraph (1) are the following:
(A) The amounts specified in program and budget information submitted to Congress by the Secretary in support of expenditure estimates and proposed appropriations in the budget submitted to Congress by the President under [section 1105(a) of title 31](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title31-section1105/a&num=0&edition=prelim) for any fiscal year, as shown in the future-years defense program submitted pursuant to subsection (a).
(B) The total amounts of estimated expenditures and proposed appropriations necessary to support the programs, projects, and activities of the Department of Defense included pursuant to paragraph (5) of [section 1105(a) of title 31](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title31-section1105/a&num=0&edition=prelim) in the budget submitted to Congress under that section for any fiscal year.
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 221
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
**(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
**(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. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Annual Naval Vessel Construction Plan and Certification.—** The Secretary of the Navy shall include with the defense budget materials for a fiscal year each of the following:
(1) A plan for the construction of naval vessels developed in accordance with this section for each of the following classes of ships:
(A) Combatant and support vessels.
(B) Auxiliary vessels.
(2) A certification by the Secretary that both the budget for that 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 the construction of naval vessels at a level that is sufficient for the procurement of the vessels provided for in the plan under paragraph (1) on the schedule provided in that plan, together with the views of the Chief of Naval Operations and Commandant of the Marine Corps on the budget.
(3) The unaltered assessment of the Chief of Naval Operations and the Commandant of the Marine Corps of the plan required under paragraph (1).
**(b) Annual Naval Vessel Construction Plan.—**
(1) The annual naval vessel construction plan developed for a fiscal year for purposes of subsection (a)(1) shall be designed so that the naval vessel force provided for under that plan supports the national security strategy of the United States as set forth in the most recent national security strategy report of the President under section 108 of the National Security Act of 1947 ([50 U.S.C. 3043](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title50-section3043&num=0&edition=prelim)), except that, if at the time such plan is submitted with the defense budget materials for that fiscal y
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 231
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
**(a) Responsibilities.—** Before granting Milestone B approval for a major defense acquisition program or major subprogram, the milestone decision authority for the program or subprogram shall ensure that—
(1) information about the program or subprogram is sufficient to warrant entry of the program or subprogram into the engineering and manufacturing development phase;
(2) appropriate trade-offs among cost, schedule, technical feasibility, and performance objectives have been made to ensure that the program or subprogram is affordable when considering the per-unit cost and the total life-cycle cost, and the Secretary of the military department concerned and the Chief of the armed force concerned concur with these trade-offs; and
(3) there are sound plans for progression of the program or subprogram to the production phase.
**(b) Factors to Be Considered for Milestone B Approval.—** A major defense acquisition program or major subprogram may not receive Milestone B approval until the milestone decision authority confirms the following factors were considered in the decision to grant Milestone B approval:
(1) The program or subprogram has received a preliminary design review and a formal post-preliminary design review or an equivalent assessment was conducted.
(2) The technology in the program or subprogram has been demonstrated in a relevant environment.
(3) The program or subprogram is affordable when considering the ability of the Department of Defense to accomplish the program’s or subprogram’s general mission using alternative systems.
(4) Reasonable lifecycle cost and schedule estimates have been developed to execute, with the concurrence of the Director of Cost Assessment and Program Evaluation, the plan under the program or subprogram.
(5) The estimated
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4252
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
**(a) In General.—** Not later than 45 days after the date of the delivery of the first ship in a new class of battle force ships, the Secretary of the Navy shall submit to the congressional defense committees a report on the employment, maintenance, and manning baseline plans for the class, including a description of the following:
(1) The sustainment and maintenance plans for the class that encompass the number of years the class is expected to be in service, including—
(A) the allocation of maintenance tasks among organizational, intermediate, depot, or other activities;
(B) the planned duration and interval of maintenance for all depot-level maintenance availabilities; and
(C) the planned duration and interval of drydock maintenance periods.
(2) Any contractually required integrated logistics support deliverables for the ship, including technical manuals, and an identification of—
(A) the deliverables provided to the Government on or before the delivery date; and
(B) the deliverables not provided to the Government on or before the delivery date and the expected dates those deliverables will be provided to the Government.
(3) The planned maintenance system for the ship, including—
(A) the elements of the system, including maintenance requirement cards, completed on or before the delivery date;
(B) the elements of the system not completed on or before the delivery date and the expected completion date of those elements; and
(C) the plans to complete planned maintenance from the delivery date until all elements of the system have been completed.
(4) The coordinated shipboard allowance list for the class, including—
(A) the items on the list onboard on or before the delivery date; and
(B) the items on the list not onboard on or before t
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 8697
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
Page 3324
TITLE 10—ARMED FORCES
§ 8669b
(Added Pub. L. 97–295, § 1(48)(A), Oct. 12, 1982, 96
Stat. 1298, § 7299a; amended Pub. L. 99–661, div. A,
title XII, § 1201(a), Nov. 14, 1986, 100 Stat. 3967;
Pub. L. 100–180, div. A, title XI, § 1101, Dec. 4,
1987, 101 Stat. 1145; Pub. L. 101–510, div. A, title
XIV, § 1422, Nov. 5, 1990, 104 Stat. 1682; Pub. L.
102–484, div. A, title X, § 1016, Oct. 23, 1992, 106
Stat. 2485; Pub. L. 114–328, div. A, title X, § 1021,
Dec. 23, 2016, 130 Stat. 2388; renumbered § 8669a,
Pub. L. 115–232, div. A, title VIII, § 807(d)(2), Aug.
13, 2018, 132 Stat. 1836; Pub. L. 118–159, div. A,
title X, § 1023(a), Dec. 23, 2024, 138 Stat. 2052.)
HISTORICAL AND REVISION NOTES
Revised
section
Source (U.S. Code)
Source (Statutes at Large)
7299a .......
10:7291 (note).
June 11, 1965, Pub. L.
89–37, §§ 302, 303, 79
Stat. 128.
In subsection (a), the words ‘‘combatant vessels’’ are
substituted for ‘‘warships’’ for consistency in title 10
and because of 1:3. The words ‘‘for which appropriations
are authorized by this Act and hereafter’’ are omitted
as unnecessary.
Editorial Notes
AMENDMENTS
2024—Subsec. (c)(4). Pub. L. 118–159 substituted ‘‘12
months’’ for ‘‘10 months’’.
2018—Pub. L. 115–232 renumbered section 7299a of this
title as this section.
2016—Subsec. (c)(4). Pub. L. 114–328 substituted ‘‘10
months’’ for ‘‘six months’’.
1992—Subsec. (a). Pub. L. 102–484, § 1016(a), (b)(1), re-
designated subsec. (b) as (a) and struck out former sub-
sec. (a) which read as follows: ‘‘The distribution of as-
signments and contracts for the construction of com-
batant vessels and escort vessels is subject to the Act
of March 27, 1934 (ch. 95, 48 Stat. 503), requiring that the
first and each succeeding alternate vessel be con-
structed in a
Source: Supplied 2024 U.S. Code historical extraction · 10 U.S.C. § 8669b
Stored review status: historical_2024_not_currentness_verified. Same stored citation; legal effect and authority still require review.