Arkansas Legal Resource Navigator

10 U.S.C. § 2221 — Untitled legal text

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

10 U.S.C. § 2221 — Untitled legal text

Page 1762 TITLE 10—ARMED FORCES [§ 2221 days after the date on which such final regulations are published.’’ PILOT PROGRAMS FOR TESTING PROGRAM MANAGER PERFORMANCE OF PRODUCT SUPPORT OVERSIGHT RE- SPONSIBILITIES FOR LIFE CYCLE OF ACQUISITION PRO- GRAMS Pub. L. 105–261, div. A, title VIII, § 816, Oct. 17, 1998, 112 Stat. 2088, authorized the Secretary of Defense to designate 10 acquisition programs of the military de- partments as pilot programs on program manager re- sponsibility for product support and required report to Congress by Feb. 1, 1999. ENHANCED SYSTEM OF PERFORMANCE INCENTIVES Pub. L. 103–355, title V, § 5001(b), Oct. 13, 1994, 108 Stat. 3350, provided that, within one year after Oct. 13, 1994, the Secretary of Defense should review the incentives and personnel actions available for encouraging excel- lence in the management of defense acquisition pro- grams and provide an enhanced system of incentives, including pay for performance, to facilitate the achievement of goals approved or defined pursuant to subsec. (a) of this section. RECOMMENDED LEGISLATION Pub. L. 103–355, title V, § 5001(c), Oct. 13, 1994, 108 Stat. 3350, directed the Secretary of Defense, not later than one year after Oct 13, 1994, to submit to Congress any recommended legislation that the Secretary considered necessary to carry out this section and otherwise to fa- cilitate and enhance management of Department of De- fense acquisition programs on the basis of performance. [§ 2221. Repealed. Pub. L. 105–261, div. A, title IX, § 906(f)(1), Oct. 17, 1998, 112 Stat. 2096] Section, added Pub. L. 104–106, div. A, title IX, § 914(a)(1), Feb. 10, 1996, 110 Stat. 412; amended Pub. L. 104–201, div. A, title X, § 1008(a), Sept. 23, 1996, 110 Stat. 2633; Pub. L. 105–85, div.

Source: Supplied 2024 U.S. Code historical extraction · 10 U.S.C. § 2221

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

Original supplied file — preserved unchanged

Download original Markdown file

File SHA-256: 10d6fcbe57cfd3e6ed9984bac448ebf73be5d02bb58b340cfa1a514f0f6aaf25. 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:usc2024-e6fe9bef263dd9d21bd9f7c3
Source file: Laws/federal/codes/united-states-code-2024/title-10/section-2221-untitled-legal-text--28b653172d.md
Pages: Not recorded – Not recorded
Passage SHA-256: 80bf6ad4395225e3d28a00e3775435ff3ffe467c79d186f09bd1a6ca13e05662

Source location: USCODE-2024-title10-subtitleA-partIV-chap131-sec2221.pdf

Stored source content

Page 1762 TITLE 10—ARMED FORCES [§ 2221 days after the date on which such final regulations are published.’’ PILOT PROGRAMS FOR TESTING PROGRAM MANAGER PERFORMANCE OF PRODUCT SUPPORT OVERSIGHT RE- SPONSIBILITIES FOR LIFE CYCLE OF ACQUISITION PRO- GRAMS Pub. L. 105–261, div. A, title VIII, § 816, Oct. 17, 1998, 112 Stat. 2088, authorized the Secretary of Defense to designate 10 acquisition programs of the military de- partments as pilot programs on program manager re- sponsibility for product support and required report to Congress by Feb. 1, 1999. ENHANCED SYSTEM OF PERFORMANCE INCENTIVES Pub. L. 103–355, title V, § 5001(b), Oct. 13, 1994, 108 Stat. 3350, provided that, within one year after Oct. 13, 1994, the Secretary of Defense should review the incentives and personnel actions available for encouraging excel- lence in the management of defense acquisition pro- grams and provide an enhanced system of incentives, including pay for performance, to facilitate the achievement of goals approved or defined pursuant to subsec. (a) of this section. RECOMMENDED LEGISLATION Pub. L. 103–355, title V, § 5001(c), Oct. 13, 1994, 108 Stat. 3350, directed the Secretary of Defense, not later than one year after Oct 13, 1994, to submit to Congress any recommended legislation that the Secretary considered necessary to carry out this section and otherwise to fa- cilitate and enhance management of Department of De- fense acquisition programs on the basis of performance. [§ 2221. Repealed. Pub. L. 105–261, div. A, title IX, § 906(f)(1), Oct. 17, 1998, 112 Stat. 2096] Section, added Pub. L. 104–106, div. A, title IX, § 914(a)(1), Feb. 10, 1996, 110 Stat. 412; amended Pub. L. 104–201, div. A, title X, § 1008(a), Sept. 23, 1996, 110 Stat. 2633; Pub. L. 105–85, div. A, title X, § 1006(a), Nov. 18, 1997, 111 Stat. 1869; Pub. L. 105–261, div. A, title X, § 1069(b)(2), Oct. 17, 1998, 112 Stat. 2136, related to Fisher House trust funds. See section 2493 of this title. Statutory Notes and Related Subsidiaries EFFECTIVE DATE OF REPEAL Repeal effective 90 days after Oct. 17, 1998, see section 906(f)(3) of Pub. L. 105–261, set out as an Effective Date of 1998 Amendment note under section 1321 of Title 31, Money and Finance. § 2222. Defense business systems: business proc- ess reengineering; enterprise architecture; management (a) DEFENSE BUSINESS PROCESSES GEN- ERALLY.—The Secretary of Defense shall ensure that defense business processes are reviewed, and as appropriate revised, through business process reengineering to match best commercial practices, to the maximum extent practicable, so as to minimize customization of commercial business systems. (b) DEFENSE BUSINESS SYSTEMS GENERALLY.— The Secretary of Defense shall ensure that each covered defense business system developed, de- ployed, and operated by the Department of De- fense— (1) supports efficient business processes that have been reviewed, and as appropriate re- vised, through business process reengineering; (2) is integrated into a comprehensive de- fense business enterprise architecture; (3) is managed in a manner that provides vis- ibility into, and traceability of, expenditures for the system; and (4) uses an acquisition and sustainment strategy that prioritizes the use of commer- cial software and business practices. (c) ISSUANCE OF GUIDANCE.— (1) SECRETARY OF DEFENSE GUIDANCE.—The Secretary shall issue guidance to provide for the coordination of, and decision making for, the planning, programming, and control of in- vestments in covered defense business sys- tems. (2) SUPPORTING GUIDANCE.—The Secretary shall direct the Chief Information Officer of the Department of Defense, the Under Sec- retary of Defense for Acquisition and Sustainment, and the Chief Information Offi- cer of each of the military departments to issue and maintain supporting guidance, as ap- propriate and within their respective areas of responsibility, for the guidance of the Sec- retary issued under paragraph (1). (d) GUIDANCE ELEMENTS.—The guidance issued under subsection (c) shall include the following elements: (1) Policy to ensure that the business proc- esses of the Department of Defense are con- tinuously reviewed and revised— (A) to implement the most streamlined and efficient business processes practicable; and (B) to eliminate or reduce the need to tai- lor commercial off-the-shelf systems to meet or incorporate requirements or interfaces that are unique to the Department of De- fense. (2) A process to establish requirements for covered defense business systems. (3) Mechanisms for the planning and control of investments in covered defense business systems, including a process for the collection and review of programming and budgeting in- formation for covered defense business sys- tems. (4) Policy requiring the periodic review of covered defense business systems that have been fully deployed, by portfolio, to ensure that investments in such portfolios are appro- priate. (5) Policy to ensure full consideration of sus- tainability and technological refreshment re- quirements, and the appropriate use of open architectures. (6) Policy to ensure that best acquisition and systems engineering practices are used in the procurement and deployment of commercial systems, modified commercial systems, and defense-unique systems to meet Department of Defense missions. (7) Policy to ensure a covered defense busi- ness system is in compliance with the Depart- ment’s auditability requirements. (8) Policy to ensure approvals required for the development of a covered defense business system. (e) DEFENSE BUSINESS ENTERPRISE ARCHITEC- TURE.— (1) BLUEPRINT.—The Secretary, working through the Chief Information Officer of the Department of Defense, shall develop and maintain a blueprint to guide the development

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

10 U.S.C. § 2221 — Repealed. Pub. L. 105–261, div. A, title IX, § 906(f)(1), Oct. 17, 1998, 112 Stat. 2096]

### Statutory Notes Section, added Pub. L. 104–106, div. A, title IX, § 914(a)(1), Feb. 10, 1996, 110 Stat. 412; amended Pub. L. 104–201, div. A, title X, § 1008(a), Sept. 23, 1996, 110 Stat. 2633; Pub. L. 105–85, div. A, title X, § 1006(a), Nov. 18, 1997, 111 Stat. 1869; Pub. L. 105–261, div. A, title X, § 1069(b)(2), Oct. 17, 1998, 112 Stat. 2136, related to Fisher House trust funds. See [section 2493 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2493&num=0&edition=prelim). #### Effective Date of Repeal Repeal effective 90 days after Oct. 17, 1998, see section 906(f)(3) of Pub. L. 105–261, set out as an Effective Date of 1998 Amendment note under [section 1321 of Title 31](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title31-section1321&num=0&edition=prelim), Money and Finance.

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

Stored review status: release_metadata_unconfirmed. Same stored citation; legal effect and authority still require review.