484 
•HR 1585 EH1S 
(2) CLERICAL AMENDMENT.—The table of sec-
tions at the beginning of such chapter is amended 
by adding at the end the following new item: 
‘‘125a. Core competencies.’’. 
(b) REPORT ON CORE COMPETENCIES.—The Sec-
retary of Defense shall submit to the Committees on 
Armed Services of the Senate and the House of Represent-
atives a report on the core competencies identified under 
section 125a of title 10, United States Code, as added by 
subsection (a), not later than the date on which the budget 
for fiscal year 2009 is submitted to Congress by the Presi-
dent under section 1105(a) of title 31, United States 
Code. 
SEC. 943. REVIEW OF CAPABILITIES OF THE MILITARY DE-
PARTMENTS AND OTHER ENTITIES. 
(a) REVIEW REQUIRED.—The Secretary of Defense 
shall conduct a review of the capabilities that each of the 
following entities is performing or developing: 
(1) Each military department. 
(2) The Office of the Secretary of Defense. 
(3) Each Defense Agency. 
(4) Each Department of Defense Field Activity. 
(5) Each combatant command with acquisition 
authority. 
(b) MATTERS COVERED.—In conducting the review, 
the Secretary of Defense—
485 
•HR 1585 EH1S 
(1) shall determine whether any such capabili-
ties are outside the entity’s core competencies (as 
identified under section 125a of this title) or outside 
a core mission area of the Department of Defense 
(as identified pursuant to the quadrennial roles and 
missions review under section 118b of this title); 
(2) shall determine whether any core com-
petencies required to effectively perform the core 
mission areas of the Department of Defense are not 
being performed or developed in any entity listed in 
subsection (a); and 
(3) shall determine whether there is any dupli-
cation of a capability within a core mission area, and 
provide a justification for such duplication. 
(c) REPORT TO CONGRESS; LIMITATION.—Not later 
than June 1, 2009, the Secretary shall submit to the Com-
mittees on Armed Services of the Senate and the House 
of Representatives a report on the review. No new major 
defense acquisition programs may be started in the De-
partment of Defense after June 1, 2009, until the report 
has been submitted to such committees. 
SEC. 944. JOINT REQUIREMENTS OVERSIGHT COUNCIL AD-
DITIONAL DUTIES RELATING TO CORE MIS-
SION AREAS. 
(a) REVISIONS IN MISSION.—
486 
•HR 1585 EH1S 
(1) REVISIONS.—Subsection (b) of section 181 
of title 10, United States Code, is amended to read 
as follows: 
‘‘(b) MISSION.—In addition to other matters assigned 
to it by the President or Secretary of Defense, the Joint 
Requirements Oversight Council shall— 
‘‘(1) assist the Chairman of the Joint Chiefs of 
Staff— 
‘‘(A) in identifying, assessing, and approv-
ing joint military requirements (including exist-
ing systems and equipment) to meet the na-
tional military strategy; and 
‘‘(B) in identifying the core mission area 
associated with each such requirement; 
‘‘(2) assist the Chairman in establishing and 
assigning priority levels for joint military require-
ments; 
‘‘(3) assist the Chairman in estimating the level 
of resources required in the fulfillment of each joint 
military requirement and in ensuring that such re-
source level is consistent with the level of priority as-
signed to such requirement; and 
‘‘(4) assist the Chairman in considering alter-
natives to any acquisition program that has been 
identified to meet joint military requirements by
487 
•HR 1585 EH1S 
evaluating the cost, schedule, and performance cri-
teria of each alternative and of the identified pro-
gram.’’. 
(2) DEFINITIONS.—Section 181 of such title is 
amended by adding at the end the following new 
subsection: 
‘‘(e) DEFINITIONS.—In this section: 
‘‘(1) The term ‘joint military requirement’ 
means a capability necessary to fulfill a gap in a 
core mission area of the Department of Defense. 
‘‘(2) The term ‘core mission area’ means a core 
mission area of the Department of Defense identi-
fied under the most recent quadrennial roles and 
missions review pursuant to section 118b of this 
title.’’. 
(b) ADDITIONAL MEMBERS
OF JOINT REQUIRE-
MENTS OVERSIGHT COUNCIL.—Section 181(c) of title 10, 
United States Code, is amended— 
(1) by redesignating subparagraphs (B), (C), 
(D), and (E) as subparagraphs (D), (E), (F), and 
(G), respectively; and 
(2) by inserting after subparagraph (A) the fol-
lowing new subparagraphs: 
‘‘(B) the Under Secretary of Defense for Acqui-
sition, Technology, and Logistics;
488 
•HR 1585 EH1S 
‘‘(C) the Director of the Office of Program 
Analysis and Evaluation;’’. 
(c) ORGANIZATION.—Section 181 of such title is 
amended— 
(1) by redesignating subsections (d) and (e) (as 
added by subsection (a)) as subsections (e) and (f), 
respectively; and 
(2) by inserting after subsection (c) the fol-
lowing new subsection (d): 
‘‘(d) ORGANIZATION.—The Joint Requirements Over-
sight Council shall organize its activities according to the 
core missions areas of the Department of Defense. In any 
review of a core mission area, the officer or official as-
signed to lead the review shall have a deputy from a dif-
ferent military department.’’. 
(d) DEADLINES.—Effective June 1, 2009, all joint 
military requirements documents of the Joint Require-
ments Oversight Council produced to carry out its mission 
under section 181(b)(1) of title 10, United States Code, 
shall conform to the core mission areas organized and de-
fined under section 118b of such title. Not later than Oc-
tober 1, 2009, all such documents produced before June 
1, 2009, shall conform to such structure. 
(e) REVISED FUNCTION OF CHAIRMAN OF JOINT 
CHIEFS OF STAFF.—Section 153(a)(4)(F) of title 10,
489 
•HR 1585 EH1S 
United States Code, is amended by striking ‘‘Assessing 
military requirements for defense acquisition programs.’’ 
and inserting ‘‘Advising the Secretary on the effective and 
efficient coordination of all military requirements for de-
fense acquisition programs.’’. 
SEC. 945. REQUIREMENT FOR CERTIFICATION OF MAJOR 
SYSTEMS PRIOR TO TECHNOLOGY DEVELOP-
MENT. 
(a) REQUIREMENT FOR CERTIFICATION.— 
(1) IN
GENERAL.—Chapter 139 of title 10, 
United States Code, is amended by inserting after 
section 2366a the following new section: 
‘‘§ 2366b. Major systems: requirement for Joint Re-
quirements 
Oversight 
Council 
certifi-
cation 
‘‘(a) CERTIFICATION.—Before the start of technology 
development for a major system, the Joint Requirements 
Oversight Council shall certify— 
‘‘(1) that the system fulfills an approved initial 
capabilities document; 
‘‘(2) that the system is being executed by an 
entity with a relevant core competency as identified 
by the Secretary of Defense under section 125a of 
this title;
490 
•HR 1585 EH1S 
‘‘(3) if the system duplicates a capability al-
ready provided by an existing system, the duplica-
tion provided by such system is necessary and ap-
propriate; and 
‘‘(4) that a cost estimate for the system has 
been submitted and that the level of resources re-
quired to develop and procure the system is con-
sistent with the level of resources estimated by the 
Joint Requirements Oversight Council for the initial 
capabilities document identified under paragraph 
(1). 
‘‘(b) NOTIFICATION.—With respect to a major sys-
tem certified by the Joint Requirements Oversight Council 
under subsection (a), if the projected cost of the system, 
at any time prior to Milestone B approval, exceeds the 
cost estimate for the system submitted to the Council at 
the time of the certification by at least 25 percent, the 
Secretary of the military department concerned, or in the 
case of Office of the Secretary of Defense, a Defense 
Agency, or a Department of Defense Field Activity, the 
Secretary of Defense, shall notify the Joint Requirements 
Oversight Council. Upon receipt of such notification, the 
Council shall consider whether to recommend that the pro-
gram be continued or that the program be terminated. 
‘‘ (c) DEFINITIONS.—In this section:
491 
•HR 1585 EH1S 
‘‘(1) The term ‘major system’ has the meaning 
provided in section 2302(5) of this title. 
‘‘(2) The term ‘initial capabilities document’ 
means any capabilities requirement document ap-
proved by the Joint Requirements Oversight Council 
that establishes the need for a materiel approach to 
resolve a capability gap. 
‘‘(3) The term ‘technology development pro-
gram’ means a coordinated effort to assess tech-
nologies and refine user performance parameters to 
fulfill a capability gap identified in an initial capa-
bilities document. 
‘‘(4) The term ‘entity’ means an entity listed in 
section 125a(a) of this title. 
‘‘(5) The term ‘Milestone B approval’ has the 
meaning provided that term in section 2366(e)(7) of 
this title.’’. 
(2) CLERICAL AMENDMENT.—The table of sec-
tions at the beginning of such chapter is amended 
by adding at the end the following new item: 
‘‘2366b. Major systems: requirement for Joint Requirements Oversight Council 
certification.’’. 
(b) EFFECTIVE DATE.—Section 2366b of title 10, 
United States Code, as added by subsection (a), shall 
apply to major systems on and after March 1, 2008.
492 
•HR 1585 EH1S 
SEC. 946. PRESENTATION OF FUTURE-YEARS MISSION 
BUDGET BY CORE MISSION AREA. 
(a) TIME OF SUBMISSION OF FUTURE-YEARS MIS-
SION BUDGET.—The second sentence of section 222(a) of 
title 10, United States Code, is amended to read as fol-
lows: ‘‘That budget shall be submitted for any fiscal year 
with the future-years defense program submitted under 
section 221 of this title.’’. 
(b) ORGANIZATION
OF
FUTURE-YEARS
MISSION 
BUDGET.—The second sentence of section 222(b) of such 
title is amended by striking ‘‘on the basis’’ and all that 
follows through the end of the sentence and inserting the 
following: ‘‘on the basis of both major force programs and 
the core mission areas identified under the most recent 
quadrennial roles and missions review pursuant to section 
118b of this title.’’. 
(c) EFFECTIVE DATE.—The amendments made by 
this section shall apply with respect to the future-years 
mission budget for fiscal year 2010 and each fiscal year 
thereafter. 
SEC. 947. FUTURE CAPABILITY PLANNING BY JOINT RE-
QUIREMENTS OVERSIGHT COUNCIL. 
(a) REQUIREMENT FOR EXTENDED PLANNING AN-
NEXES.—Section 181 of title 10, United States Code, as 
amended by this subtitle, is further amended—
493 
•HR 1585 EH1S 
(1) by redesignating subsection (f) as sub-
section (g); and 
(2) by inserting after subsection (e) the fol-
lowing new subsection (f): 
‘‘(f) FUTURE CAPABILITY PLANNING.—(1)(A) The 
Secretary of Defense shall direct the commanders of com-
batant commands to prepare extended planning annexes 
to all operational and contingency plans. Each extended 
planning annex shall— 
‘‘(i) include the commander’s assessment of the 
capabilities needed to successfully accomplish the 
missions for which the operational and contingency 
plans were created; 
‘‘(ii) use a 15-year planning horizon and take 
into account expected changes in threats, the geo-
political environment, and doctrine, training, and 
operational concepts; and 
‘‘(iii) provide capability assessments for the 
year in which the annex is submitted and for the 
5th, 10th, and 15th years after such year. 
‘‘(B) The extended planning annexes shall be sub-
mitted to the Secretary of Defense and the Chairman of 
the Joint Chiefs of Staff biannually. 
‘‘(2) The Joint Requirements Oversight Council 
shall—
494 
•HR 1585 EH1S 
‘‘(A) in consultation with the office responsible 
for program analysis and evaluation within the Of-
fice of the Secretary of Defense and the Office of 
the Under Secretary of Defense for Acquisition, 
Technology, and Logistics, match— 
‘‘(i) the capabilities that are expected to be 
provided by the acquisition programs in exist-
ence during the period covered by the most re-
cent extended planning annexes, including clas-
sified and compartmentalized programs, and 
the science and technology programs in exist-
ence during that period, with 
‘‘(ii) capability needs identified in the ex-
tended planning annexes prepared under para-
graph (1); 
‘‘(B) in coordination with the commanders of 
the combatant commands, and within 30 days after 
submission of the extended planning annexes, iden-
tify gaps in capabilities not likely to be closed by ex-
isting acquisition programs and science and tech-
nology programs described in subparagraph (A)(i), 
assign priorities for addressing such gaps, and iden-
tify areas where such programs are expected to pro-
vide capability beyond that which is required; and