« PreviousContinue »
(4) To increase efforts to provide timely response by the Department of Defense to acquisition proposals (including unsolicited proposals) submitted to the Department by small businesses and by nontraditional defense contractors regarding research activities and new technologies described in subsection (b), including through the use of electronic transactions to facilitate the processing of such proposals.
(d) REVIEW PANEL.—(1) The Secretary shall appoint, under the outreach program, a panel for the review and evaluation of acquisition proposals described in subsection (c)(4).
(2) The panel shall be composed of qualified personnel from the military departments, relevant Defense Agencies, industry, academia, and other private sector organizations.
(3) Under procedures prescribed by the Under Secretary of Defense for Acquisition, Technology, and Logistics, a small business or nontraditional defense contractor may submit acquisition proposals for consideration under the program through the unsolicited proposal process or in response to a broad agency announcement. The Under Secretary shall issue on an annual basis not less than one such broad agency announcement inviting parties to submit proposals.
(4) Under procedures prescribed by the Under Secretary, the panel shall review and evaluate acquisition proposals selected by the panel. An acquisition proposal shall be selected for review and evaluation if the panel determines that the acquisition proposal may present a unique and valuable approach for meeting a defense requirement or technology development goal of the Department of Defense that relates to the mission of the Department of Defense to combat terrorism. In carrying out its duties under this paragraph, the panel may act through representatives designated by the panel. (5) The panel shall
(A) not later than 60 days after the date on which the panel receives an acquisition proposal described in subsection (c)(4), transmit to the small business or nontraditional defense contractor that submitted the proposal a notification regarding whether the acquisition proposal has been selected under paragraph (4) for review and evaluation;
(B) to the maximum extent practicable, complete the review and evaluation of each selected acquisition proposal not later than 120 days after the date on which such proposal is selected under paragraph (4); and
(C) after completing the review and evaluation of an acquisition proposal, transmit the results of that review and evaluation to the small business or nontraditional defense contractor that submitted the proposal.
(6) The Secretary shall ensure that the panel, in reviewing and evaluating acquisition proposals under this subsection, has the authority to obtain assistance, to a reasonable extent, from the appropriate technical resources of the laboratories, research, development, and engineering centers, test and evaluation activities, and other elements of the Department of Defense.
(7) If, after completing review and evaluation of an acquisition proposal, the panel determines that such proposal represents a unique and valuable approach for meeting a defense requirement
or technology development goal of the Department of Defense that relates to the mission of the Department of Defense to combat terrorism, the panel shall submit that determination to the Under Secretary of Defense for Acquisition, Technology, and Logistics, together with any recommendations that the panel considers appropriate regarding such proposal.
(8) The Under Secretary of Defense for Acquisition, Technology, and Logistics may provide funding for acquisition proposals with respect to which the panel has submitted a determination under paragraph (7) through appropriate accounts of the military departments, Defense Agencies, the Small Business Innovative Research program, or any other acquisition program.
(9) The Secretary of Defense shall ensure that a member of the panel has no conflict of interest with respect to the review and evaluation of an acquisition proposal by the panel.
(e) NONTRADITIONAL DEFENSE CONTRACTOR DEFINED.-In this section, the term “nontraditional defense contractor” means an entity that has not, for at least one year prior to the date of the enactment of this Act, entered into, or performed with respect to, any contract described in paragraph (1) or (2) of section 845(e) of the National Defense Authorization Act for Fiscal Year 1994 (10 U.S.C. 2371 note).
TITLE VIII-ACQUISITION POLICY, AC
QUISITION MANAGEMENT, AND RELATED MATTERS
SEC. 803. (10 U.S.C. 2430 note] SPIRAL DEVELOPMENT. UNDER MAJOR
DEFENSE ACQUISITION PROGRAMS. (a) AUTHORITY.—The Secretary of Defense is authorized to conduct major defense acquisition programs as spiral development programs.
(b) LIMITATION ON SPIRAL DEVELOPMENT PROGRAMS.-A research and development program for a major defense acquisition program of a military department or Defense Agency may not be conducted as a spiral development program unless the Secretary of Defense approves the spiral development plan for that research and development program in accordance with subsection (c). The Secretary of Defense may delegate authority to approve the plan to the Under Secretary of Defense for Acquisition, Technology, and Logistics, or to the senior acquisition executive of the military department or Defense Agency concerned, but such authority may not be further delegated.
(c) SPIRAL DEVELOPMENT PLANS.—A spiral development plan for a research and development program for a major defense acquisition program shall, at a minimum, include the following matters:
(1) A rationale for dividing the research and development program into separate spirals, together with a preliminary identification of the spirals to be included.
(2) A program strategy, including overall cost, schedule, and performance goals for the total research and development program.
(3) Specific cost, schedule, and performance parameters, including measurable exit criteria, for the first spiral to be conducted.
(4) A testing plan to ensure that performance goals, parameters, and exit criteria are met.
(5) An appropriate limitation on the number of prototype units that may be produced under the research and development program.
(6) Specific performance parameters, including measurable exit criteria, that must be met before the major defense acquisition program proceeds into production of units in excess of the limitation on the number of prototype units.
(d) GUIDANCE.-Not later than 120 days after the date of the enactment of this Act, the Secretary of Defense shall issue guidance for the implementation of spiral development programs authorized by this section. The guidance shall include appropriate processes for ensuring the independent validation of exit criteria being met, the operational assessment of fieldable prototypes, and the management of spiral development programs.
(e) REPORTING REQUIREMENT.—The Secretary shall submit to Congress by September 30 of each of 2003 through 2008 a status report on each research and development program that is a spiral development program. The report shall contain information on unit costs that is similar to the information on unit costs under major defense acquisition programs that is required to be provided to Congress under chapter 144 of title 10, United States Code, except that the information on unit costs shall address projected prototype costs instead of production costs.
(f) APPLICABILITY OF EXISTING LAW.—Nothing in this section shall be construed to exempt any program of the Department of Defense from the application of any provision of chapter 144 of title 10, United States Code, section 139, 181, 2366, 2399, or 2400 of such title, or any requirement under Department of Defense Directive 5000.1, Department of Defense Instruction 5000.2, or Chairman of the Joint Chiefs of Staff Instruction 3170.01B in accordance with the terms of such provision or requirement. (g) DEFINITIONS.—In this section:
(1) The term “spiral development program”, with respect to a research and development program, means a program that
(A) is conducted in discrete phases or blocks, each of which will result in the development of fieldable prototypes; and
(B) will not proceed into acquisition until specific performance parameters, including measurable exit criteria, have been met.
(2) The term “spiral” means one of the discrete phases or blocks of a spiral development program.
(3) The term "major defense acquisition program" has the meaning given such term in section 139(a)(2)(B) of title 10,
-United States Code. SEC. 804. [10 U.S.C. 2302 note] IMPROVEMENT OF SOFTWARE ACQUISI.
TION PROCESSES. (a) ESTABLISHMENT OF PROGRAMS.—(1) The Secretary of each military department shall establish a program to improve the software acquisition processes of that military department.
(2) The head of each Defense Agency that manages a major defense acquisition program with a substantial software component shall establish a program to improve the software acquisition processes of that Defense Agency.
(3) The programs required by this subsection shall be established not later than 120 days after the date of the enactment of this Act.
(b) PROGRAM REQUIREMENTS.-A program to improve software acquisition processes under this section shall, at a minimum, include the following:
(1) A documented process for software acquisition planning, requirements development and management, project management and oversight, and risk management.
(2) Efforts to develop appropriate metrics for performance measurement and continual process improvement.
(3) A process to ensure that key program personnel have an appropriate level of experience or training in software acquisition.
(4) A process to ensure that each military department and Defense Agency implements and adheres to established processes and requirements relating to the acquisition of software.
(c) DEPARTMENT OF DEFENSE GUIDANCE. – The Assistant Secretary of Defense for Command, Control, Communications, and Intelligence, in consultation with the Under Secretary of Defense for Acquisition, Technology, and Logistics, shall
(1) prescribe uniformly applicable guidance for the administration of all of the programs established under subsection (a) and take such actions as are necessary to ensure that the military departments and Defense Agencies comply with the guid
(2) assist the Secretaries of the military departments and the heads of the Defense Agencies to carry out such programs effectively by
(A) ensuring that the criteria applicable to the selection of sources provides added-emphasis on past performance of potential sources, as well as on the maturity of the software products offered by the potential sources; and
(B) identifying, and serving as a clearinghouse for information regarding, best practices in software development and acquisition in both the public and private sec
(1) The term “Defense Agency" has the meaning given the term in section 101(a)(11) of title 10, United States Code.
(2) The term "major defense acquisition program” has the meaning given such term in section 139(a)(2)(B) of title 10, United States Code.
SEC. 806. [10 U.S.C. 2302 note] RAPID ACQUISITION AND DEPLOYMENT
PROCEDURES. (a) REQUIREMENT TO ESTABLISH PROCEDURES.-Not later than 180 days after the date of the enactment of this Act, the Secretary of Defense shall prescribe procedures for the rapid acquisition and deployment of items that are
(1) currently under development by the Department of Defense or available from the commercial sector; and
(2) urgently needed to react to an enemy threat or to respond to significant and urgent safety situations.
(b) ISSUES TO BE ADDRESSED.—The procedures prescribed under subsection (a) shall include the following:
(1) A process for streamlined communications between the Chairman of the Joint Chiefs of Staff, the acquisition community,
and the research and development community, including
(A) a process for the commanders of the combatant commands and the Joint Chiefs of Staff to communicate their needs to the acquisition community and the research and development community; and
(B) a process for the acquisition community and the research and development community to propose items that meet the needs communicated by the combatant commands and the Joint Chiefs of Staff.
(2) Procedures for demonstrating, rapidly acquiring, and deploying items proposed pursuant to paragraph (1)(B), including —
(A) a process for demonstrating performance and evaluating for current operational purposes the existing capability of an item;
(B) a process for developing an acquisition and funding strategy for the deployment of an item; and
(C) a process for making deployment determinations based on information obtained pursuant to subparagraphs
(A) and (B). (c) TESTING REQUIREMENT.—(1) The process for demonstrating performance and evaluating for current operational purposes the existing capability of an item prescribed under subsection (b)(2)(A) shall include
(A) an operational assessment in accordance with procedures prescribed by the Director of Operational Test and Evaluation, and
(B) a requirement to provide information about any deficiency of the item in meeting the original requirements for the item (as stated in an operational requirements document or similar document) to the deployment decisionmaking authority.
(2) The process may not include a requirement for any deficiency of an item to be the determining factor in deciding whether to deploy the item.