joint military requirements within the Joint Staff or with-
in the Armed Force concerned. 
(c) MATTERS COVERED.—The program developed pur-
suant to subsection (a) shall: 
(1) Measure the following in relation to each 
joint military requirement: 
(A) The time a requirements document 
takes to receive validation through the require-
ments process. 
(B) The quality of cost information associ-
ated with the requirement and the extent to 
which cost information was considered during 
the requirements process. 
(C) The extent to which the requirements 
process established a meaningful level of priority 
for the requirement. 
(D) The extent to which the requirements 
process considered trade-offs between cost, sched-
ule, and performance objectives. 
(E) 
The 
quality 
of 
information 
on 
sustainment associated with the requirement and 
the extent to which sustainment information was 
considered during the requirements process. 
(F) Such other matters as the Secretary 
shall determine appropriate. 
VerDate Nov 24 2008 
21:26 Apr 23, 2010
Jkt 089200
PO 00000
Frm 00018
Fmt 6652
Sfmt 6203
E:\BILLS\H5013.RH
H5013
srobinson on DSKHWCL6B1PROD with BILLS
(2) Achieve, to the maximum extent practicable, 
the following outcomes in the requirements process: 
(A) Timeliness in delivering capability to 
the warfighter. 
(B) Mechanisms for controlling require-
ments creep. 
(C) Responsiveness to fact-of-life changes oc-
curring after the approval of a requirements doc-
ument, including changes to the threat environ-
ment, the emergence of new capabilities, or 
changes in the resources estimated to procure or 
sustain a capability. 
(D) The development of the personnel skills, 
capacity, and training needed for an effective 
and efficient requirements process. 
(E) Such other outcomes as the Secretary 
shall determine appropriate. 
(d) IMPLEMENTATION.—The program required by sub-
section (a) shall be developed and initially implemented not 
later than one year after the date of the enactment of this 
Act and shall apply to requirements documents entering the 
requirements process after the date of initial implementa-
tion. 
(e) INITIAL REPORT.—Not later than 90 days after the 
initial implementation of the program required by sub-
VerDate Nov 24 2008 
21:26 Apr 23, 2010
Jkt 089200
PO 00000
Frm 00019
Fmt 6652
Sfmt 6203
E:\BILLS\H5013.RH
H5013
srobinson on DSKHWCL6B1PROD with BILLS
section (a), the Secretary shall submit to the congressional 
defense committees a report on the steps taken to develop 
and implement the performance management program for 
joint military requirements. The report shall address the 
measures specified in subsection (c)(1). 
(f) FINAL REPORT.—Not later than four years after 
the initial implementation of the program required by sub-
section (a), the Secretary shall submit to the congressional 
defense committees a report on the effectiveness of the pro-
gram for joint military requirements in achieving the out-
comes specified in subsection (c)(2). 
(g) DEFINITIONS.—In this section: 
(1) REQUIREMENTS
PROCESS.—The term ‘‘re-
quirements process’’ means the Joint Capabilities In-
tegration and Development System (JCIDS) process 
or any successor to such process established by the 
Chairman of the Joint Chiefs of Staff to support the 
statutory responsibility of the Joint Requirements 
Oversight Council in advising the Chairman and the 
Secretary of Defense in identifying, assessing, and 
validating joint military capability needs, with their 
associated operational performance criteria, in order 
to successfully execute missions. 
(2) REQUIREMENTS DOCUMENT.—The term ‘‘re-
quirements document’’ means a document produced in 
VerDate Nov 24 2008 
21:26 Apr 23, 2010
Jkt 089200
PO 00000
Frm 00020
Fmt 6652
Sfmt 6203
E:\BILLS\H5013.RH
H5013
srobinson on DSKHWCL6B1PROD with BILLS
the requirements process that is provided for an ac-
quisition program to guide the subsequent develop-
ment, production, and testing of the program and 
that— 
(A) justifies the need for a materiel ap-
proach, or an approach that is a combination of 
materiel and non-materiel, to satisfy one or more 
specific capability gaps; 
(B) details the information necessary to de-
velop 
an 
increment 
of 
militarily 
useful, 
logistically supportable, and technically mature 
capability, including key performance param-
eters; or 
(C) identifies production attributes required 
for a single increment of a program. 
(3) REQUIREMENTS CREEP.—The term ‘‘require-
ments creep’’ means the addition of new technical or 
operational specifications after a requirements docu-
ment is approved. 
(h) DISCRETIONARY
IMPLEMENTATION
AFTER
YEARS.—After the date that is five years after the initial 
implementation of the performance management program 
under this section, the requirement to implement a program 
under this section shall be at the discretion of the Secretary 
of Defense. 
VerDate Nov 24 2008 
21:26 Apr 23, 2010
Jkt 089200
PO 00000
Frm 00021
Fmt 6652
Sfmt 6203
E:\BILLS\H5013.RH
H5013
srobinson on DSKHWCL6B1PROD with BILLS