US Codex
Bill
Notes

Division E — Federal Information Technology Acquisition Reform

H.R. 4435 · 113th Congress · Jun 5, 2014 · Lineage

E Federal Information Technology Acquisition Reform

Sec. 5001 Short title

This division may be cited as the “Federal Information Technology Acquisition Reform Act”.

Sec. 5002 Table of contents

The table of contents for this division is as follows:

Sec. 5003 Definitions

In this division:
(1)
Chief acquisition officers council— The term “Chief Acquisition Officers Council” means the Chief Acquisition Officers Council established by section 1311(a) of title 41, United States Code.
(2)
Chief information officer— The term “Chief Information Officer” means a Chief Information Officer (as designated under section 3506(a)(2) of title 44, United States Code) of an agency listed in section 901(b) of title 31, United States Code.
(3)
Chief information officers council— The term “Chief Information Officers Council” or “CIO Council” means the Chief Information Officers Council established by section 3603(a) of title 44, United States Code.
(4)
Director— The term “Director” means the Director of the Office of Management and Budget.
(5)
Federal agency— The term “Federal agency” means each agency listed in section 901(b) of title 31, United States Code.
(6)
Federal chief information officer— The term “Federal Chief Information Officer” means the Administrator of the Office of Electronic Government established under section 3602 of title 44, United States Code.
(7)
Information technology or it— The term “information technology” or “IT” has the meaning provided in section 11101(6) of title 40, United States Code.
(8)
Relevant congressional committees— The term “relevant congressional committees” means each of the following:
(A)
The Committee on Oversight and Government Reform and the Committee on Armed Services of the House of Representatives.
(B)
The Committee on Homeland Security and Governmental Affairs and the Committee on Armed Services of the Senate.

LI Management of Information Technology Within Federal Government

Sec. 5101 Increased authority of agency Chief Information Officers over information technology

(a)
Presidential appointment of CIOs of certain agencies—
(1)
In general— Section 11315 of title 40, United States Code, is amended—
(A)
by redesignating subsection (a) as subsection (e) and moving such subsection to the end of the section; and
(B)
by inserting before subsection (b) the following new subsection (a):

“(a) Presidential appointment or designation of certain chief information officers

“(1) In general—There shall be within each agency listed in section 901(b)(1) of title 31 an agency Chief Information Officer. Each agency Chief Information Officer shall—

“(A)

“(i) be appointed by the President; or

“(ii) be designated by the President, in consultation with the head of the agency; and

“(B) be appointed or designated, as applicable, from among individuals who possess demonstrated ability in general management of, and knowledge of and extensive practical experience in, information technology management practices in large governmental or business entities.

“(2) Responsibilities—An agency Chief Information Officer appointed or designated under this section shall report directly to the head of the agency and carry out, on a full-time basis, responsibilities as set forth in this section and in section 3506(a) of title 44 for Chief Information Officers designated under paragraph (2) of such section.”

(2)
Conforming amendments— Section 3506(a)(2) of title 44, United States Code, is amended—
(A)
by striking “(A) Except as provided under subparagraph (B), the head of each agency” and inserting “The head of each agency, other than an agency with a Presidentially appointed or designated Chief Information Officer as provided in section 11315(a)(1) of title 40,”; and
(B)
by striking subparagraph (B).
(b)
Authority relating to budget and personnel— Section 11315 of title 40, United States Code, is further amended by inserting after subsection (c) the following new subsection:

“(d) Additional authorities for certain CIOs

“(1) Budget-related authority

“(A) Planning—Notwithstanding any other provision of law, the head of each agency listed in section 901(b)(1) or 901(b)(2) of title 31 and in section 102 of title 5 shall ensure that the Chief Information Officer of the agency has the authority to participate in decisions regarding the budget planning process related to information technology or programs that include significant information technology components.

“(B) Allocation—Notwithstanding any other provision of law, amounts appropriated for any agency listed in section 901(b)(1) or 901(b)(2) of title 31 and in section 102 of title 5 for any fiscal year that are available for information technology shall be allocated within the agency, consistent with the provisions of appropriations Acts and budget guidelines and recommendations from the Director of the Office of Management and Budget, in such manner as specified by, or approved by, the Chief Information Officer of the agency in consultation with the Chief Financial Officer of the agency and budget officials.

“(2) Personnel-related authority—Notwithstanding any other provision of law, the head of each agency listed in section 901(b)(1) or 901(b)(2) of title 31 shall ensure that the Chief Information Officer of the agency has the authority necessary to approve the hiring of personnel who will have information technology responsibilities within the agency and to require that such personnel have the obligation to report to the Chief Information Officer in a manner considered sufficient by the Chief Information Officer.”

(c)
Single chief information officer in each agency—
(1)
Requirement— Section 3506(a)(3) of title 44, United States Code, is amended—
(A)
by inserting “(A)” after “(3)”; and
(B)
by adding at the end the following new subparagraph:

“(B) Each agency shall have only one individual with the title and designation of “Chief Information Officer”. Any bureau, office, or subordinate organization within the agency may designate one individual with the title “Deputy Chief Information Officer”, “Associate Chief Information Officer”, or “Assistant Chief Information Officer”.”

(2)
Effective date— Section 3506(a)(3)(B) of title 44, United States Code, as added by paragraph (1), shall take effect as of October 1, 2014. Any individual serving in a position affected by such section before such date may continue in that position if the requirements of such section are fulfilled with respect to that individual.

Sec. 5102 Lead coordination role of Chief Information Officers Council

(a)
Lead coordination role— Subsection (d) of section 3603 of title 44, United States Code, is amended to read as follows:

“(d) Lead interagency forum

“(1) In general—The Council is designated the lead interagency forum for improving agency coordination of practices related to the design, development, modernization, use, operation, sharing, performance, and review of Federal Government information resources investment. As the lead interagency forum, the Council shall develop cross-agency portfolio management practices to allow and encourage the development of cross-agency shared services and shared platforms. The Council shall also issue guidelines and practices for infrastructure and common information technology applications, including expansion of the Federal Enterprise Architecture process if appropriate. The guidelines and practices may address broader transparency, common inputs, common outputs, and outcomes achieved. The guidelines and practices shall be used as a basis for comparing performance across diverse missions and operations in various agencies.

“(2) Report—Not later than December 1 in each of the 6 years following the date of the enactment of this paragraph, the Council shall submit to the relevant congressional committees a report (to be known as the “CIO Council Report”) summarizing the Council’s activities in the preceding fiscal year and containing such recommendations for further congressional action to fulfill its mission as the Council considers appropriate.

“(3) Relevant congressional committees—For purposes of the report required by paragraph (2), the relevant congressional committees are each of the following:

“(A) The Committee on Oversight and Government Reform and the Committee on Armed Services of the House of Representatives.

“(B) The Committee on Homeland Security and Governmental Affairs and the Committee on Armed Services of the Senate.”

(b)
References to administrator of E-Government as federal chief information officer—
(1)
References— Section 3602(b) of title 44, United States Code, is amended by adding at the end the following: “The Administrator may also be referred to as the Federal Chief Information Officer.”.
(2)
Definition— Section 3601(1) of such title is amended by inserting “or Federal Chief Information Officer” before “means”.

Sec. 5103 Reports by Government Accountability Office

(a)
Requirement to examine effectiveness— The Comptroller General of the United States shall examine the effectiveness of the Chief Information Officers Council in meeting its responsibilities under section 3603(d) of title 44, United States Code, as added by section 5102, with particular focus on whether agencies are actively participating in the Council and heeding the Council’s advice and guidance.
(b)
Reports— Not later than 1 year, 3 years, and 5 years after the date of the enactment of this Act, the Comptroller General shall submit to the relevant congressional committees a report containing the findings and recommendations of the Comptroller General from the examination required by subsection (a).

LII Data Center Optimization

Sec. 5201 Purpose

The purpose of this title is to optimize Federal data center usage and efficiency.

Sec. 5202 Definitions

In this title:
(1)
Federal data center optimization initiative— The term “Federal Data Center Optimization Initiative” or the “Initiative” means the initiative developed and implemented by the Director, through the Federal Chief Information Officer, as required under section 5203.
(2)
Covered agency— The term “covered agency” means any agency included in the Federal Data Center Optimization Initiative.
(3)
Data center— The term “data center” means a closet, room, floor, or building for the storage, management, and dissemination of data and information, as defined by the Federal Chief Information Officer under guidance issued pursuant to this section.
(4)
Federal data center— The term “Federal data center” means any data center of a covered agency used or operated by a covered agency, by a contractor of a covered agency, or by another organization on behalf of a covered agency.
(5)
Server utilization— The term “server utilization” refers to the activity level of a server relative to its maximum activity level, expressed as a percentage.
(6)
Power usage effectiveness— The term “power usage effectiveness” means the ratio obtained by dividing the total amount of electricity and other power consumed in running a data center by the power consumed by the information and communications technology in the data center.

Sec. 5203 Federal data center optimization initiative

(a)
Requirement for initiative— The Federal Chief Information Officer, in consultation with the chief information officers of covered agencies, shall develop and implement an initiative, to be known as the Federal Data Center Optimization Initiative, to optimize the usage and efficiency of Federal data centers by meeting the requirements of this division and taking additional measures, as appropriate.
(b)
Requirement for plan— Within 6 months after the date of the enactment of this Act, the Federal Chief Information Officer, in consultation with the chief information officers of covered agencies, shall develop and submit to Congress a plan for implementation of the Initiative required by subsection (a) by each covered agency. In developing the plan, the Federal Chief Information Officer shall take into account the findings and recommendations of the Comptroller General review required by section 5205(e).
(c)
Matters covered— The plan shall include—
(1)
descriptions of how covered agencies will use reductions in floor space, energy use, infrastructure, equipment, applications, personnel, increases in multiorganizational use, server virtualization, cloud computing, and other appropriate methods to meet the requirements of the initiative; and
(2)
appropriate consideration of shifting Federally owned data center workload to commercially owned data centers.

Sec. 5204 Performance requirements related to data center consolidation

(a)
Server utilization— Each covered agency may use the following methods to achieve the maximum server utilization possible as determined by the Federal Chief Information Officer:
(1)
The closing of existing data centers that lack adequate server utilization, as determined by the Federal Chief Information Officer. If the agency fails to close such data centers, the agency shall provide a detailed explanation as to why this data center should remain in use as part of the submitted plan. The Federal Chief Information Officer shall include an assessment of the agency explanation in the annual report to Congress.
(2)
The consolidation of services within existing data centers to increase server utilization rates.
(3)
Any other method that the Federal Chief Information Officer, in consultation with the chief information officers of covered agencies, determines necessary to optimize server utilization.
(b)
Power usage effectiveness— Each covered agency may use the following methods to achieve the maximum energy efficiency possible as determined by the Federal Chief Information Officer:
(1)
The use of the measurement of power usage effectiveness to calculate data center energy efficiency.
(2)
The use of power meters in facilities dedicated to data center operations to frequently measure power consumption over time.
(3)
The establishment of power usage effectiveness goals for each data center.
(4)
The adoption of best practices for managing—
(A)
temperature and airflow in facilities dedicated to data center operations; and
(B)
power supply efficiency.
(5)
The implementation of any other method that the Federal Chief Information Officer, in consultation with the Chief Information Officers of covered agencies, determines necessary to optimize data center energy efficiency.

Sec. 5205 Cost savings related to data center optimization

(a)
Requirement To track costs—
(1)
In general— Each covered agency shall track costs resulting from implementation of the Federal Data Center Optimization Initiative within the agency and submit a report on those costs annually to the Federal Chief Information Officer. Covered agencies shall determine the net costs from data consolidation on an annual basis.
(2)
Factors— In calculating net costs each year under paragraph (1), a covered agency shall use the following factors:
(A)
Energy costs.
(B)
Personnel costs.
(C)
Real estate costs.
(D)
Capital expense costs.
(E)
Maintenance and support costs such as operating subsystem, database, hardware, and software license expense costs.
(F)
Other appropriate costs, as determined by the agency in consultation with the Federal Chief Information Officer.
(b)
Requirement To track savings—
(1)
In general— Each covered agency shall track realized and projected savings resulting from implementation of the Federal Data Center Optimization Initiative within the agency and submit a report on those savings annually to the Federal Chief Information Officer. Covered agencies shall determine the net savings from data consolidation on an annual basis.
(2)
Factors— In calculating net savings each year under paragraph (1), a covered agency shall use the following factors:
(A)
Energy savings.
(B)
Personnel savings.
(C)
Real estate savings.
(D)
Capital expense savings.
(E)
Maintenance and support savings such as operating subsystem, database, hardware, and software license expense savings.
(F)
Other appropriate savings, as determined by the agency in consultation with the Federal Chief Information Officer.
(3)
Public availability— The Federal Chief Information Officer shall make publicly available a summary of realized and projected savings for each covered agency. The Federal Chief Information Officer shall identify any covered agency that failed to provide the annual report required under paragraph (1).
(c)
Requirement To use cost-Effective measures— Covered agencies shall use the most cost-effective measures to implement the Federal Data Center Optimization Initiative, such as using estimation to measure or track costs and savings using a methodology approved by the Federal Chief Information Officer.
(d)
Government accountability office review— Not later than 6 months after the date of the enactment of this Act, the Comptroller General of the United States shall examine methods for calculating savings from the Initiative and using them for the purposes identified in subsection (d), including establishment and use of a special revolving fund that supports data centers and server optimization, and shall submit to the Federal Chief Information Officer and Congress a report on the Comptroller General’s findings and recommendations.

Sec. 5206 Reporting requirements to Congress and the Federal Chief Information Officer

(a)
Agency requirement To report to CIO—
(1)
In general— Except as provided in paragraph (2), each covered agency each year shall submit to the Federal Chief Information Officer a report on the implementation of the Federal Data Center Optimization Initiative, including savings resulting from such implementation. The report shall include an update of the agency’s plan for implementing the Initiative.
(2)
Department of Defense— The Secretary of Defense shall comply with paragraph (1) each year by submitting to the Federal Chief Information Officer a report with relevant information collected under section 2867 of Public Law 112–81 (10 U.S.C. 2223a note) or a copy of the report required under section 2867(d) of such law.
(b)
Federal chief information officer requirement To report to congress— Each year, the Federal Chief Information Officer shall submit to the relevant congressional committees a report that assesses agency progress in carrying out the Federal Data Center Optimization Initiative and updates the plan under section 5203. The report may be included as part of the annual report required under section 3606 of title 44, United States Code.

LIII Elimination of Duplication and Waste in Information Technology Acquisition

Sec. 5301 Inventory of information technology software assets

(a)
Plan— The Director shall develop a plan for conducting a Governmentwide inventory of information technology software assets.
(b)
Matters covered— The plan required by subsection (a) shall cover the following:
(1)
The manner in which Federal agencies can achieve the greatest possible economies of scale and cost savings in the procurement of information technology software assets, through measures such as reducing the procurement of new software licenses until such time as agency needs exceed the number of existing and unused licenses.
(2)
The capability to conduct ongoing Governmentwide inventories of all existing software licenses on an application-by-application basis, including duplicative, unused, overused, and underused licenses, and to assess the need of agencies for software licenses.
(3)
A Governmentwide spending analysis to provide knowledge about how much is being spent for software products or services to support decisions for strategic sourcing under the Federal strategic sourcing program managed by the Office of Federal Procurement Policy.
(c)
Availability— The inventory of information technology software assets shall be available to Chief Information Officers and such other Federal officials as the Chief Information Officers may, in consultation with the Chief Information Officers Council, designate.
(d)
Deadline and submission to congress— Not later than 180 days after the date of the enactment of this Act, the Director shall complete and submit to Congress the plan required by subsection (a).
(e)
Implementation— Not later than two years after the date of the enactment of this Act, the Director shall complete implementation of the plan required by subsection (a).
(f)
Review by comptroller general— Not later than two years after the date of the enactment of this Act, the Comptroller General of the United States shall review the plan required by subsection (a) and submit to the relevant congressional committees a report on the review.

Sec. 5302 Website consolidation and transparency

(a)
Website consolidation— The Director shall—
(1)
in consultation with Federal agencies, and after reviewing the directory of public Federal Government websites of each agency (as required to be established and updated under section 207(f)(3) of the E-Government Act of 2002 (Public Law 107–347; 44 U.S.C. 3501 note)), assess all the publicly available websites of Federal agencies to determine whether there are duplicative or overlapping websites; and
(2)
require Federal agencies to eliminate or consolidate those websites that are duplicative or overlapping.
(b)
Website transparency— The Director shall issue guidance to Federal agencies to ensure that the data on publicly available websites of the agencies are open and accessible to the public.
(c)
Matters covered— In preparing the guidance required by subsection (b), the Director shall—
(1)
develop guidelines, standards, and best practices for interoperability and transparency;
(2)
identify interfaces that provide for shared, open solutions on the publicly available websites of the agencies; and
(3)
ensure that Federal agency Internet home pages, web-based forms, and web-based applications are accessible to individuals with disabilities in conformance with section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d).
(d)
Deadline for guidance— The guidance required by subsection (b) shall be issued not later than 180 days after the date of the enactment of this Act.

Sec. 5303 Transition to the cloud

(a)
Sense of congress— It is the sense of Congress that transition to cloud computing offers significant potential benefits for the implementation of Federal information technology projects in terms of flexibility, cost, and operational benefits.
(b)
Governmentwide application— In assessing cloud computing opportunities, the Chief Information Officers Council shall define policies and guidelines for the adoption of Governmentwide programs providing for a standardized approach to security assessment and operational authorization for cloud products and services.
(c)
Additional budget authorities for transition— In transitioning to the cloud, a Chief Information Officer of an agency listed in section 901(b) of title 31, United States Code, may establish such cloud service Working Capital Funds, in consultation with the Chief Financial Officer of the agency, as may be necessary to transition to cloud-based solutions. Any establishment of a new Working Capital Fund under this subsection shall be reported to the Committees on Appropriations of the House of Representatives and the Senate and relevant Congressional committees.

Sec. 5304 Elimination of unnecessary duplication of contracts by requiring business case analysis

(a)
Purpose— The purpose of this section is to leverage the Government’s buying power and achieve administrative efficiencies and cost savings by eliminating unnecessary duplication of contracts.
(b)
Requirement for business case approval—
(1)
In general— Chapter 33 of title 41, United States Code, is amended by adding at the end the following new section:

“3312. Requirement for business case approval for new Governmentwide contracts

“(a) In general—An executive agency may not issue a solicitation for a covered Governmentwide contract unless the agency performs a business case analysis for the contract and obtains an approval of the business case analysis from the Administrator for Federal Procurement Policy.

“(b) Review of business case analysis

“(1) In general—With respect to any covered Governmentwide contract, the Administrator for Federal Procurement Policy shall review the business case analysis submitted for the contract and provide an approval or disapproval within 60 days after the date of submission. Any business case analysis not disapproved within such 60-day period is deemed to be approved.

“(2) Basis for approval of business case—The Administrator for Federal Procurement Policy shall approve or disapprove a business case analysis based on the adequacy of the analysis submitted. The Administrator shall give primary consideration to whether an agency has demonstrated a compelling need that cannot be satisfied by existing Governmentwide contract in a timely and cost-effective manner.

“(c) Content of business case analysis—The Administrator for Federal Procurement Policy shall issue guidance specifying the content for a business case analysis submitted pursuant to this section. At a minimum, the business case analysis shall include details on the administrative resources needed for such contract, including an analysis of all direct and indirect costs to the Federal Government of awarding and administering such contract and the impact such contract will have on the ability of the Federal Government to leverage its purchasing power.

“(b) Definitions—In this section:

“(1) Covered Governmentwide contract—The term “covered Governmentwide contract” means any contract, blanket purchase agreement, or other contractual instrument for acquisition of information technology or other goods or services that allows for an indefinite number of orders to be placed under the contract, agreement, or instrument, and that is established by one executive agency for use by multiple executive agencies to obtain goods or services. The term does not include—

“(A) a multiple award schedule contract awarded by the General Services Administration;

“(B) a Governmentwide acquisition contract for information technology awarded pursuant to sections 11302(e) and 11314(a)(2) of title 40;

“(C) orders under Governmentwide contracts in existence before the effective date of this section; or

“(D) any contract in an amount less than $10,000,000, determined on an average annual basis.

“(2) Executive agency—The term “executive agency” has the meaning provided that term by section 105 of title 5.”

(2)
Clerical amendment— The table of sections for chapter 33 of title 41, United States Code, is amended by adding after the item relating to section 3311 the following new item:
(c)
Report— Not later than June 1 in each of the next 6 years following the date of the enactment of this Act, the Administrator for Federal Procurement Policy shall submit to the relevant congressional committees a report on the implementation of section 3312 of title 41, United States Code, as added by subsection (b), including a summary of the submissions, reviews, approvals, and disapprovals of business case analyses pursuant to such section.
(d)
Guidance— The Administrator for Federal Procurement Policy shall issue guidance for implementing section 3312 of such title.
(e)
Revision of FAR— Not later than 180 days after the date of the enactment of this Act, the Federal Acquisition Regulation shall be amended to implement section 3312 of such title.
(g)
Effective date— Section 3312 of such title is effective on and after 180 days after the date of the enactment of this Act.

LIV Strengthening IT Acquisition Workforce

Sec. 5411 Expansion of training and use of information technology acquisition cadres

(a)
Purpose— The purpose of this section is to ensure timely progress by Federal agencies toward developing, strengthening, and deploying personnel with highly specialized skills in information technology acquisition, including program and project managers, to be known as information technology acquisition cadres.
(b)
Report to congress— Section 1704 of title 41, United States Code, is amended by adding at the end the following new subsection:

“(j) Strategic plan on information technology acquisition cadres

“(1) Five-year strategic plan to congress—Not later than June 1 following the date of the enactment of this subsection, the Director shall submit to the relevant congressional committees a 5-year strategic plan (to be known as the “IT Acquisition Cadres Strategic Plan”) to develop, strengthen, and solidify information technology acquisition cadres. The plan shall include a timeline for implementation of the plan and identification of individuals responsible for specific elements of the plan during the 5-year period covered by the plan.

“(2) Matters covered—The plan shall address, at a minimum, the following matters:

“(A) Current information technology acquisition staffing challenges in Federal agencies, by previous year’s information technology acquisition value, and by the Federal Government as a whole.

“(B) The variety and complexity of information technology acquisitions conducted by each Federal agency covered by the plan, and the specialized information technology acquisition workforce needed to effectively carry out such acquisitions.

“(C) The development of a sustainable funding model to support efforts to hire, retain, and train an information technology acquisition cadre of appropriate size and skill to effectively carry out the acquisition programs of the Federal agencies covered by the plan, including an examination of interagency funding methods and a discussion of how the model of the Defense Acquisition Workforce Development Fund could be applied to civilian agencies.

“(D) Any strategic human capital planning necessary to hire, retain, and train an information acquisition cadre of appropriate size and skill at each Federal agency covered by the plan.

“(E) Governmentwide training standards and certification requirements necessary to enhance the mobility and career opportunities of the Federal information technology acquisition cadre within the Federal agencies covered by the plan.

“(F) New and innovative approaches to workforce development and training, including cross-functional training, rotational development, and assignments both within and outside the Government.

“(G) Appropriate consideration and alignment with the needs and priorities of the acquisition intern programs.

“(H) Assessment of the current workforce competency and usage trends in evaluation technique to obtain best value, including proper handling of tradeoffs between price and nonprice factors.

“(I) Assessment of the current workforce competency in designing and aligning performance goals, life cycle costs, and contract incentives.

“(J) Assessment of the current workforce competency in avoiding brand-name preference and using industry-neutral functional specifications to leverage open industry standards and competition.

“(K) Use of integrated program teams, including fully dedicated program managers, for each complex information technology investment.

“(L) Proper assignment of recognition or accountability to the members of an integrated program team for both individual functional goals and overall program success or failure.

“(M) The development of a technology fellows program that includes provisions for recruiting, for rotation of assignments, and for partnering directly with universities with well-recognized information technology programs.

“(N) The capability to properly manage other transaction authority (where such authority is granted), including ensuring that the use of the authority is warranted due to unique technical challenges, rapid adoption of innovative or emerging commercial or noncommercial technologies, or other circumstances that cannot readily be satisfied using a contract, grant, or cooperative agreement in accordance with applicable law and the Federal Acquisition Regulation.

“(O) The use of student internship and scholarship programs as a talent pool for permanent hires and the use and impact of special hiring authorities and flexibilities to recruit diverse candidates.

“(P) The assessment of hiring manager satisfaction with the hiring process and hiring outcomes, including satisfaction with the quality of applicants interviewed and hires made.

“(Q) The assessment of applicant satisfaction with the hiring process, including the clarity of the hiring announcement, the user-friendliness of the application process, communication from the hiring manager or agency regarding application status, and timeliness of the hiring decision.

“(R) The assessment of new hire satisfaction with the onboarding process, including the orientation process, and investment in training and development for employees during their first year of employment.

“(S) Any other matters the Director considers appropriate.

“(3) Annual report—Not later than June 1 in each of the 5 years following the year of submission of the plan required by paragraph (1), the Director shall submit to the relevant congressional committees an annual report outlining the progress made pursuant to the plan.

“(4) Government accountability office review of the plan and annual report

“(A) Not later than 1 year after the submission of the plan required by paragraph (1), the Comptroller General of the United States shall review the plan and submit to the relevant congressional committees a report on the review.

“(B) Not later than 6 months after the submission of the first, third, and fifth annual report required under paragraph (3), the Comptroller General shall independently assess the findings of the annual report and brief the relevant congressional committees on the Comptroller General’s findings and recommendations to ensure the objectives of the plan are accomplished.

“(5) Definitions—In this subsection:

“(A) The term “Federal agency” means each agency listed in section 901(b) of title 31.

“(B) The term “relevant congressional committees” means each of the following:

“(i) The Committee on Oversight and Government Reform and the Committee on Armed Services of the House of Representatives.

“(ii) The Committee on Homeland Security and Governmental Affairs and the Committee on Armed Services of the Senate.”

Sec. 5412 Plan on strengthening program and project management performance

(a)
Plan on strengthening program and project management performance— Not later than June 1 following the date of the enactment of this Act, the Director, in consultation with the Director of the Office of Personnel Management, shall submit to the relevant congressional committees a plan for improving management of IT programs and projects.
(b)
Matters covered— The plan required by subsection (a) shall include, at a minimum, the following:
(1)
Creation of a specialized career path for program management.
(2)
The development of a competency model for program management consistent with the IT project manager model.
(3)
A career advancement model that requires appropriate expertise and experience for advancement.
(4)
A career advancement model that is more competitive with the private sector and that recognizes both Government and private sector experience.
(c)
Combination with other cadres plan— The Director may combine the plan required by subsection (a) with the IT Acquisition Cadres Strategic Plan required under section 1704(j) of title 41, United States Code, as added by section 5411.

Sec. 5413 Personnel awards for excellence in the acquisition of information systems and information technology

(a)
In general— Not later than 180 days after the date of the enactment of this Act, the Director of the Office of Personnel Management shall develop policy and guidance for agencies to develop a program to recognize excellent performance by Federal Government employees and teams of such employees in the acquisition of information systems and information technology for the agency.
(b)
Elements— The program referred to in subsection (a) shall, to the extent practicable—
(1)
obtain objective outcome measures; and
(2)
include procedures for—
(A)
the nomination of Federal Government employees and teams of such employees for eligibility for recognition under the program; and
(B)
the evaluation of nominations for recognition under the program by 1 or more agency panels of individuals from Government, academia, and the private sector who have such expertise, and are appointed in such a manner, as the Director of the Office of Personal Management shall establish for purposes of the program.
(c)
Award of cash bonuses and other incentives— In carrying out the program referred to in subsection (a), the Director of the Office of Personnel Management, in consultation with the Director of the Office of Management and Budget, shall establish policies and guidance for agencies to reward any Federal Government employee or teams of such employees recognized pursuant to the program—
(1)
with a cash bonus, to the extent that the performance of such individual or team warrants the award of such bonus and is authorized by any provision of law;
(2)
through promotions and other nonmonetary awards;
(3)
by publicizing—
(A)
acquisition accomplishments by individual employees; and
(B)
the tangible end benefits that resulted from such accomplishments, as appropriate; and
(4)
through other awards, incentives, or bonuses that the head of the agency considers appropriate.

LV Additional Reforms

Sec. 5501 Maximizing the benefit of the Federal strategic sourcing initiative

Not later than 180 days after the date of the enactment of this Act, the Administrator for Federal Procurement Policy shall prescribe regulations providing that when the Federal Government makes a purchase of services and supplies offered under the Federal Strategic Sourcing Initiative (managed by the Office of Federal Procurement Policy) but such Initiative is not used, the contract file for the purchase shall include a brief analysis of the comparative value, including price and nonprice factors, between the services and supplies offered under such Initiative and services and supplies offered under the source or sources used for the purchase.

Sec. 5502 Governmentwide software purchasing program

(a)
In general— The Administrator of General Services, in collaboration with the Department of Defense, shall identify and develop a strategic sourcing initiative to enhance Governmentwide acquisition, shared use, and dissemination of software, as well as compliance with end user license agreements.
(b)
Examination of methods— In developing the initiative under subsection (a), the Administrator shall examine the use of realistic and effective demand aggregation models supported by actual agency commitment to use the models, and supplier relationship management practices, to more effectively govern the Government’s acquisition of information technology.
(c)
Governmentwide user license agreement— The Administrator, in developing the initiative under subsection (a), shall allow for the purchase of a license agreement that is available for use by all executive agencies as one user to the maximum extent practicable and as appropriate.

Sec. 5503 Promoting transparency of blanket purchase agreements

(a)
Price information To be treated as public information— The final negotiated price offered by an awardee of a blanket purchase agreement shall be treated as public information.
(b)
Publication of blanket purchase agreement information— Not later than 180 days after the date of the enactment of this Act, the Administrator of General Services shall make available to the public a list of all blanket purchase agreements entered into by Federal agencies under its Federal Supply Schedules contracts and the prices associated with those blanket purchase agreements. The list and price information shall be updated at least once every 6 months.

Sec. 5504 Additional source selection technique in solicitations

Section 3306(d) of title 41, United States Code, is amended—
(1)
by striking “or” at the end of paragraph (1);
(2)
by striking the period and inserting “; or” at the end of paragraph (2); and
(3)
by adding at the end the following new paragraph:

“(3) stating in the solicitation that the award will be made using a fixed price technical competition, under which all offerors compete solely on nonprice factors and the fixed award price is pre-announced in the solicitation.”

Sec. 5505 Enhanced transparency in information technology investments

(a)
Public availability of information about IT investments— Section 11302(c) of title 40, United States Code, is amended—
(1)
by redesignating paragraph (2) as paragraph (3); and
(2)
by inserting after paragraph (1) the following new paragraph:

“(2) Public availability

“(A) In general—The Director shall make available to the public the cost, schedule, and performance data for all of the IT investments listed in subparagraph (B), notwithstanding whether the investments are for new IT acquisitions or for operations and maintenance of existing IT.

“(B) Investments listed—The investments listed in this subparagraph are the following:

“(i) At least 80 percent (by dollar value) of all information technology investments Governmentwide.

“(ii) At least 60 percent (by dollar value) of all information technology investments in each Federal agency listed in section 901(b) of title 31.

“(iii) Every major information technology investment (as defined by the Office of Management and Budget) in each Federal agency listed in section 901(b) of title 31.

“(C) Quarterly review and certification—For each investment listed in subparagraph (B), the agency Chief Information Officer and the program manager of the investment within the agency shall certify, at least once every quarter, that the information is current, accurate, and reflects the risks associated with each listed investment. The Director shall conduct quarterly reviews and publicly identify agencies with an incomplete certification or with significant data quality issues.

“(D) Continuous availability—The information required under subparagraph (A), in its most updated form, shall be publicly available at all times.

“(E) Waiver or limitation authority—The applicability of subparagraph (A) may be waived or the extent of the information may be limited—

“(i) by the Director, with respect to IT investments Governmentwide; and

“(ii) by the Chief Information Officer of a Federal agency, with respect to IT investments in that agency;”

(b)
Additional report requirements— Paragraph (3) of section 11302(c) of such title, as redesignated by subsection (a), is amended by adding at the end the following: “The report shall include an analysis of agency trends reflected in the performance risk information required in paragraph (2).”.

Sec. 5506 Enhanced communication between government and industry

Not later than 180 days after the date of the enactment of this Act, the Federal Acquisition Regulatory Council shall prescribe a regulation making clear that agency acquisition personnel are permitted and encouraged to engage in responsible and constructive exchanges with industry, so long as those exchanges are consistent with existing law and regulation and do not promote an unfair competitive advantage to particular firms.

Sec. 5507 Clarification of current law with respect to technology neutrality in acquisition of software

(a)
Purpose— The purpose of this section is to establish guidance and processes to clarify that software acquisitions by the Federal Government are to be made using merit-based requirements development and evaluation processes that promote procurement choices—
(1)
based on performance and value, including the long-term value proposition to the Federal Government;
(2)
free of preconceived preferences based on how technology is developed, licensed, or distributed; and
(3)
generally including the consideration of proprietary, open source, and mixed source software technologies.
(b)
Technology neutrality— Nothing in this section shall be construed to modify the Federal Government’s long-standing policy of following technology-neutral principles and practices when selecting and acquiring information technology that best fits the needs of the Federal Government.
(c)
Guidance— Not later than 180 days after the date of the enactment of this Act, the Director, in consultation with the Chief Information Officers Council, shall issue guidance concerning the technology-neutral procurement and use of software within the Federal Government.
(d)
Matters covered— In issuing guidance under subsection (c), the Director shall include, at a minimum, the following:
(1)
Guidance to clarify that the preference for commercial items in section 3307 of title 41, United States Code, includes proprietary, open source, and mixed source software that meets the definition of the term “commercial item” in section 103 of title 41, United States Code, including all such software that is used for non-Government purposes and is licensed to the public.
(2)
Guidance regarding the conduct of market research to ensure the inclusion of proprietary, open source, and mixed source software options.
(3)
Guidance to define Governmentwide standards for security, redistribution, indemnity, and copyright in the acquisition, use, release, and collaborative development of proprietary, open source, and mixed source software.
(4)
Guidance for the adoption of available commercial practices to acquire proprietary, open source, and mixed source software for widespread Government use, including issues such as security and redistribution rights.
(5)
Guidance to establish standard service level agreements for maintenance and support for proprietary, open source, and mixed source software products widely adopted by the Government, as well as the development of Governmentwide agreements that contain standard and widely applicable contract provisions for ongoing maintenance and development of software.
(e)
Report to congress— Not later than 2 years after the issuance of the guidance required by subsection (b), the Comptroller General of the United States shall submit to the relevant congressional committees a report containing—
(1)
an assessment of the effectiveness of the guidance;
(2)
an identification of barriers to widespread use by the Federal Government of specific software technologies; and
(3)
such legislative recommendations as the Comptroller General considers appropriate to further the purposes of this section.

Sec. 5508 No additional funds authorized

No additional funds are authorized to carry out the requirements of this division and the amendments made by this division. Such requirements shall be carried out using amounts otherwise authorized or appropriated.