Sec. 409. Joint Requirements Council
552 words·~3 min read·
/bill/117/hr/4357/ih/section-409A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
Subtitle H of title VIII of the Homeland Security Act of 2002 ( 6 U.S.C. 451 et seq. ), as amended by this Act, is further amended by adding at the end the following new section: The Secretary shall establish a council to be known as the Joint Requirements Council within the Department (referred to in this section as the Joint Requirements Council ). The Joint Requirements Council shall— develop Department-wide policies relating to identifying, validating, and prioritizing capability gaps and requirements that reduce duplication and increase opportunities for efficiencies in meeting mission needs of the Department; assess and validate documentation outlining proposed capability gaps and requirements for all acquisition programs to ensure— alignment with the strategic goals of the Department; and requirements are operationally relevant, well-defined, measurable, achievable, and cost-informed; implement portfolio reviews to identify common capability gaps or mission needs among offices and components of the Department to harmonize investments and prevent unnecessary overlap and duplication; assist with developing joint requirements for any common capability gaps or mission needs identified pursuant to paragraph (3); prioritize new and existing requirements identified pursuant to paragraph
(4)to make recommendations with respect to the annual budget development process of the Department to the Secretary, Deputy Secretary, or Associate Secretary; track any changes to existing requirements, including the reasons for the changes, to identify opportunities to improve the requirements generation process across the Department; and provide technical support and assistance to components, including reviewing component-level policies for identifying, validating, and prioritizing capability gaps and requirements to ensure alignment with the Department-wide policies established under paragraph (2)(A). The Secretary shall appoint a chairperson of the Joint Requirements Council, for a term of not more than four years, from among senior officials from components of the Department or other senior officials as designated by the Secretary. The Secretary shall ensure participation of relevant senior officials representing components of the Department and other senior officials as designated by the Secretary. The Secretary shall designate a full-time employee of the Department to serve as the executive secretariat of the Council. The Secretary shall ensure that the Future Years Homeland Security Program required under section 874 is consistent with any recommendations of the Joint Requirements Council required under subsection (b)(5). Not later than one year after the date of the enactment of this section and annually thereafter, the chairperson of the Joint Requirements Council shall submit to the appropriate congressional committees a report relating to the activities of the Joint Requirements Council for the previous fiscal year. Each report required under paragraph
(1)shall include a list of documents validated by the Council that identifies— the type of document validated; the relevant components that submitted such document; the document version, if previously validated, and reason for revision; and the dates of initial submission and final validation. In this subsection, the term joint requirement means a condition or need of more than one office or component of the Department that is required to be met or possessed by a system, product, or service to satisfy an operational mission. . The table of contents in section 1(b) of the Homeland Security Act of 2002, as amended by this Act, is further amended by inserting after the item relating to section 890C the following new item: Sec. 890D. Joint Requirements Council. .
Connectionstraces to 1
Traces to 1 document
U.S. Code
Citation graph
cites case law
Sec. 409
Joint Requirements Council
Cites 1Cited by 0 across 0 sources