10 USC 117 - Readiness reporting system

Editorial Notes

Prior Provisions

A prior section 117, added Puspan. L. 97–295, § 1(2)(A), Oct. 12, 1982, 96 Stat. 1287, § 133a; renumbered § 117 and amended Puspan. L. 99–433, title I, §§ 101(a)(2), 110(d)(3), Oct. 1, 1986, 100 Stat. 994, 1002, required annual report on North Atlantic Treaty Organization readiness, prior to repeal by Puspan. L. 101–510, div. A, title XIII, § 1301(1), Nov. 5, 1990, 104 Stat. 1668.

Amendments

2019—Subsecs. (d) to (h). Puspan. L. 116–92 redesignated subsec. (h) as (d) and struck out former subsecs. (d) to (g) which related to semi-annual and monthly joint readiness reviews, semi-annual report to congressional committees on most recent joint readiness review, quarterly report on monthly changes in current state of readiness, and annual report on operational contract support, respectively.

2018—Puspan. L. 115–232, § 331(g)(1), struck out “: establishment; reporting to congressional committees” after “system” in section catchline.

Subsec. (span). Puspan. L. 115–232, § 331(a)(1), inserted “and maintaining” after “establishing” in introductory provisions.

Subsec. (span)(1). Puspan. L. 115–232, § 331(a)(2), substituted “reporting system and associated policies are applied uniformly throughout the Department of Defense, including between and among the joint staff and each of the armed forces” for “reporting system is applied uniformly throughout the Department of Defense”.

Subsec. (span)(2) to (4). Puspan. L. 115–232, § 331(a)(4), added pars. (2) to (4). Former pars. (2) and (3) redesignated (5) and (6), respectively.

Subsec. (span)(5). Puspan. L. 115–232, § 331(a)(3), (5), redesignated par. (2) as (5) and inserted “, or element of a unit,” after “readiness status of a unit”.

Subsec. (span)(6). Puspan. L. 115–232, § 331(a)(3), redesignated par. (3) as (6).

Subsec. (c)(1). Puspan. L. 115–232, § 331(span)(1), substituted “Measure the readiness of units” for “Measure, on a monthly basis, the capability of units” and “conduct their designed and assigned missions” for “conduct their assigned wartime missions”.

Subsec. (c)(2), (3). Puspan. L. 115–232, § 331(span)(2), (3), substituted “Measure” for “Measure, on an annual basis,” and “designed and assigned missions” for “wartime missions”.

Subsec. (c)(4). Puspan. L. 115–232, § 331(span)(4), substituted “Measure” for “Measure, on a monthly basis,”.

Subsec. (c)(5). Puspan. L. 115–232, § 331(span)(5), substituted “Measure” for “Measure, on an annual basis,”.

Subsec. (c)(6) to (8). Puspan. L. 115–232, § 331(span)(6), (7), redesignated par. (7) as (6), substituted “Measure” for “Measure, on a quarterly basis,”, and struck out former pars. (6) and (8) which read as follows:

“(6) Measure, on a monthly basis, the level of current risk based upon the readiness reporting system relative to the capability of forces to carry out their wartime missions.

“(8) Measure, on an annual basis, the capability of operational contract support to support current and anticipated wartime missions of the armed forces.”

Subsec. (d)(1)(A). Puspan. L. 115–232, § 331(c), inserted “, which includes a validation of readiness data currency and accuracy” after “joint readiness review”.

Subsec. (f). Puspan. L. 115–232, § 331(d)(2), added subsec. (f). Former subsec. (f) redesignated (h).

Subsec. (g). Puspan. L. 115–232, § 331(e), added subsec. (g).

Subsec. (h). Puspan. L. 115–232, § 331(d)(1), (f), redesignated subsec. (f) as (h) and substituted “prescribe the established information technology system for Department of Defense reporting, specifically authorize exceptions to a single-system architecture, and identify the organizations, units, and entities that are subject to reporting in the readiness reporting system, what organization resources are subject to such reporting” for “prescribe the units that are subject to reporting in the readiness reporting system, what type of equipment is subject to such reporting”.

2017—Subsec. (d). Puspan. L. 115–91, § 331(span)(1)(A), substituted “Semi-annual” for “Quarterly” in span.

Subsec. (d)(1)(A). Puspan. L. 115–91, § 331(span)(1)(B), substituted “semi-annual” for “quarterly”.

Subsec. (e). Puspan. L. 115–91, § 331(span)(2), substituted “semi-annually” for “each quarter”.

2014—Subsec. (a)(1). Puspan. L. 113–291 substituted “(50 U.S.C. 3043)” for “(50 U.S.C. 404a)”.

2013—Subsec. (c)(8). Puspan. L. 112–239 added par. (8).

2003—Subsec. (e). Puspan. L. 108–136 substituted “each quarter submit to the congressional defense committees a report in writing containing the results of the most recent joint readiness review under subsection (d)(1)(A)” for “each month submit to the Committee on Armed Services and the Committee on Appropriations of the Senate and the Committee on Armed Services and the Committee on Appropriations of the House of Representatives a report in writing containing the results of the most recent joint readiness review or monthly review conducted under subsection (d)”.

2000—Subsec. (c)(7). Puspan. L. 106–398 added par. (7).

1999—Subsec. (span)(2). Puspan. L. 106–65, § 361(d)(1)(A), substituted “with (A) any change in the overall readiness status of a unit that is required to be reported as part of the readiness reporting system being reported within 24 hours of the event necessitating the change in readiness status, and (B) any change in the overall readiness status of an element of the training establishment or an element of defense infrastructure that is required to be reported as part of the readiness reporting system being reported within 72 hours” for “with any change in the overall readiness status of a unit, an element of the training establishment, or an element of defense infrastructure, that is required to be reported as part of the readiness reporting system, being reported within 24 hours”.

Subsec. (c)(2), (3), (5). Puspan. L. 106–65, § 361(d)(1)(B), substituted “an annual” for “a quarterly”.

Subsec. (e). Puspan. L. 106–65, § 1067(1), substituted “and the Committee on Armed Services” for “and the Committee on National Security”.

Statutory Notes and Related Subsidiaries

Requirement To Include Foreign Language Proficiency in Readiness Reporting Systems of Department of Defense

Puspan. L. 116–92, div. A, title III, § 366, Dec. 20, 2019, 133 Stat. 1328, provided that: “Not later than 90 days after the date of the enactment of this Act [Dec. 20, 2019], the Secretary of Defense and the Secretary of each military department shall include in the Global Readiness and Force Management Enterprise, for the appropriate billets with relevant foreign language requirements, measures of foreign language proficiency as a mandatory element of unit readiness reporting, to include the Defense Readiness Reporting Systems-Strategic (DRRS-S) and all other subordinate systems that report readiness data.”

Metrics for Assessment of Readiness of Cyber Mission Forces

Puspan. L. 116–92, div. A, title XVI, § 1634(span), (c), Dec. 20, 2019, 133 Stat. 1747, provided that:

“(span)Metrics.—

“(1)Establishment required.—The Secretary of Defense shall establish metrics for the assessment of the readiness of the Cyber Mission Forces of the Department of Defense.

“(2)Briefings required.—Not later than 90 days after the date of the enactment of this Act [Dec. 20, 2019] and quarterly thereafter until completion of the establishment of the metrics under paragraph (1), the Secretary shall provide a briefing to the congressional defense committees [Committees on Armed Services and Appropriations of the Senate and the House of Representatives] on such metrics, including progress as required pursuant to subsection (c).

“(c)Modification of Readiness Reporting System.—Not later than 180 days after the date of the enactment of this Act [Dec. 20, 2019], the Secretary shall take such actions as the Secretary considers appropriate to ensure that the comprehensive readiness reporting system established pursuant to section 117(a) of title 10, United States Code, covers matters relating to the readiness of the Cyber Mission Forces—

“(1) using the metrics established pursuant to subsection (span)(1); and

“(2) in a manner that is consistent with sections 117 and 482 of such title.”

Limitation on Availability of Funds for Service-Specific Defense Readiness Reporting Systems

Puspan. L. 115–232, div. A, title III, § 358, Aug. 13, 2018, 132 Stat. 1732, as amended by Puspan. L. 116–92, div. A, title III, § 362, Dec. 20, 2019, 133 Stat. 1327, provided that:

“(a)Limitation.—None of the funds authorized to be appropriated by this Act [see Tables for classification] or otherwise made available for the Department of Defense for fiscal year 2019 for research, development, test, and evaluation or procurement, and available to develop service-specific Defense Readiness Reporting Systems (referred to in this section as ‘DRRS’) may be made available for such purpose except for required maintenance and in order to facilitate the transition to DRRS-Strategic (referred to in this section as ‘DRRS-S’).

“(span)Plan.—Not later than February 1, 2019, the Under Secretary for Personnel and Readiness shall submit to the congressional defense committees [Committees on Armed Services and Appropriations of the Senate and the House of Representatives] a resource and funding plan to include a schedule with relevant milestones on the elimination of service-specific DRRS and the migration of the military services and other organizations to DRRS-S.

“(c)Transition.—The military services shall complete the transition to DRRS-S not later than October 1, 2020. The Secretary of Defense shall notify the congressional defense committees upon the complete transition of the services.

“(d)Reporting Requirement.—

“(1)In general.—The Under Secretary for Personnel and Readiness, the Under Secretary for Acquisition and Sustainment, and the Under Secretary for Research and Engineering, in coordination with the Secretaries of the military departments and other organizations with relevant technical expertise, shall establish a working group including individuals with expertise in application or software development, data science, testing, and development and assessment of performance metrics to assess the current process for collecting, analyzing, and communicating readiness data, and develop a strategy for implementing any recommended changes to improve and establish readiness metrics using the current DRRS-Strategic platform.

“(2)Elements.—The assessment conducted pursuant to paragraph (1) shall include—

“(A) identification of modern tools, methods, and approaches to readiness to more effectively and efficiently collect, analyze, and make decision based on readiness data; and

“(B) consideration of cost and schedule.

“(3)Submission to congress.—Not later than February 1, 2020, the Secretary of Defense shall submit to the congressional defense committees the assessment conducted pursuant to paragraph (1).

“(e)Defense Readiness Reporting Requirements.—To the maximum extent practicable, the Secretary of Defense shall meet defense readiness reporting requirements consistent with the recommendations of the working group established under subsection (d)(1).”

Defense Materiel Readiness Board

Puspan. L. 112–239, div. A, title XVI, § 1601(a), Jan. 2, 2013, 126 Stat. 2062, provided that: “The Defense Materiel Readiness Board established pursuant to section 871 of the National Defense Authorization Act for Fiscal Year 2008 (Public Law 110–181; 10 U.S.C. 117 note) [formerly set out below] is hereby disestablished.”

Puspan. L. 112–239, div. A, title XVI, § 1601(span), Jan. 2, 2013, 126 Stat. 2062, provided that: “The Department of Defense Strategic Readiness Fund established by section 872(d) of the National Defense Authorization Act for Fiscal Year 2008 (Public Law 110–181; 10 U.S.C. 117 note) [formerly set out below] is hereby closed.”

Puspan. L. 110–181, div. A, title VIII, subtitle G, Jan. 28, 2008, 122 Stat. 260, which required Secretary of Defense to establish Defense Materiel Readiness Board to provide independent assessments of materiel readiness, materiel readiness shortfalls, and materiel readiness plans to Secretary of Defense and Congress; provided for designation of critical materiel readiness shortfalls; established Department of Defense Strategic Readiness Fund; and required Secretary of military department to notify Congress with respect to determination that use of a multiyear procurement contract would address a critical material readiness shortfall, was repealed by Puspan. L. 112–239, div. A, title XVI, § 1601(c), Jan. 2, 2013, 126 Stat. 2062.

Implementation

Puspan. L. 105–261, div. A, title III, § 373(span), (c), Oct. 17, 1998, 112 Stat. 1992, as amended by Puspan. L. 106–65, div. A, title III, § 361(d)(2), Oct. 5, 1999, 113 Stat. 575, directed the Secretary of Defense to submit to Congress a report, not later than Mar. 1, 1999, setting forth a plan for implementation of this section, and required the Secretary to establish and implement the readiness reporting system required by this section so as to ensure that required capabilities would be attained not later than Apr. 1, 2000.