Browse Arkansas Code titles and sections
6 U.S.C. § 571 — Acquisition justification and reports
Federal law — U.S. Code and appendices · legal_authorities
**(a) Acquisition justification** Before the Administration implements any security-related technology acquisition, the Administrator, in accordance with the Department’s policies and directives, shall determine whether the acquisition is justified by conducting an analysis that includes—
(1) an identification of the scenarios and level of risk to transportation security from those scenarios that would be addressed by the security-related technology acquisition;
(2) an assessment of how the proposed acquisition aligns to the Plan;
(3) a comparison of the total expected lifecycle cost against the total expected quantitative and qualitative benefits to transportation security;
(4) an analysis of alternative security solutions, including policy or procedure solutions, to determine if the proposed security-related technology acquisition is the most effective and cost-efficient solution based on cost-benefit considerations;
(5) an assessment of the potential privacy and civil liberties implications of the proposed acquisition that includes, to the extent practicable, consultation with organizations that advocate for the protection of privacy and civil liberties;
(6) a determination that the proposed acquisition is consistent with fair information practice principles issued by the Privacy Officer of the Department;
(7) confirmation that there are no significant risks to human health or safety posed by the proposed acquisition; and
(8) an estimate of the benefits to commercial aviation passengers.
**(b) Reports and certification to Congress**
(1) **In general** — Not later than the end of the 30-day period preceding the award by the Administration of a contract for any security-related technology acquisition exceeding $30,000,000, the Administrator shall submit to th
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 571
Stored review status: release_metadata_unconfirmed. A text match is a research starting point; applicability is not established.
Original supplied file — preserved unchanged
Download original Markdown file
File SHA-256: 7f2a6a7373ceb720f43cc4c70284c3e22e954a2778b8d00311952680bfd85067. The original may include catalog metadata, neighboring provisions, or embedded records outside this collection's scope. Search shows only the selected federal record. Historical editions and unverified snapshots are not a statement of current law.
Authority boundary: historical or unconfirmed source not current law verified.
Open the recorded source website ↗
Record provenance
Stable record: federal_law:legal_authorities:record_usc_182c2b359a07eda0c4e25c52
Source file: Laws/federal/codes/united-states-code/title-6/section-571-acquisition-justification-and-reports--ca6130af12.md
Pages: Not recorded – Not recorded
Passage SHA-256: f470536d09fa43381de6d486d58835e20946f320a8ef096f534ac63f98b556f8
Source location: Title 6, Chapter 1, § 571; chapter-001-homeland-security-organization.md
Stored source content
**(a) Acquisition justification** Before the Administration implements any security-related technology acquisition, the Administrator, in accordance with the Department’s policies and directives, shall determine whether the acquisition is justified by conducting an analysis that includes—
(1) an identification of the scenarios and level of risk to transportation security from those scenarios that would be addressed by the security-related technology acquisition;
(2) an assessment of how the proposed acquisition aligns to the Plan;
(3) a comparison of the total expected lifecycle cost against the total expected quantitative and qualitative benefits to transportation security;
(4) an analysis of alternative security solutions, including policy or procedure solutions, to determine if the proposed security-related technology acquisition is the most effective and cost-efficient solution based on cost-benefit considerations;
(5) an assessment of the potential privacy and civil liberties implications of the proposed acquisition that includes, to the extent practicable, consultation with organizations that advocate for the protection of privacy and civil liberties;
(6) a determination that the proposed acquisition is consistent with fair information practice principles issued by the Privacy Officer of the Department;
(7) confirmation that there are no significant risks to human health or safety posed by the proposed acquisition; and
(8) an estimate of the benefits to commercial aviation passengers.
**(b) Reports and certification to Congress**
(1) **In general** — Not later than the end of the 30-day period preceding the award by the Administration of a contract for any security-related technology acquisition exceeding $30,000,000, the Administrator shall submit to the Committee on Commerce, Science, and Transportation of the Senate and the Committee on Homeland Security of the House of Representatives—
(A) the results of the comprehensive acquisition justification under subsection (a); and
(B) a certification by the Administrator that the benefits to transportation security justify the contract cost.
(2) **Extension due to imminent terrorist threat** — If there is a known or suspected imminent threat to transportation security, the Administrator—
(A) may reduce the 30-day period under paragraph (1) to 5 days to rapidly respond to the threat; and
(B) shall immediately notify the Committee on Commerce, Science, and Transportation of the Senate and the Committee on Homeland Security of the House of Representatives of the known or suspected imminent threat.
Cross-references
Connections may be documented source relationships, shared citations or nearby passages. Each explains its basis; a connection alone does not establish applicability to your situation.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Clarification of responsibilities** The Director of the Office for Interoperability and Compatibility shall—
(1) assist the Secretary in developing and implementing the science and technology aspects of the program described in subparagraphs (D), (E), (F), and (G) of [section 194(a)(1) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section194/a/1&num=0&edition=prelim);
(2) in coordination with the Federal Communications Commission, the National Institute of Standards and Technology, and other Federal departments and agencies with responsibility for standards, support the creation of national voluntary consensus standards for interoperable emergency communications;
(3) establish a comprehensive research, development, testing, and evaluation program for improving interoperable emergency communications;
(4) establish, in coordination with the Director for Emergency Communications,11 See Change of Name note below. requirements for interoperable emergency communications capabilities, which shall be nonproprietary where standards for such capabilities exist, for all public safety radio and data communications systems and equipment purchased using homeland security assistance administered by the Department, excluding any alert and warning device, technology, or system;
(5) carry out the Department’s responsibilities and authorities relating to research, development, testing, evaluation, or standards-related elements of the SAFECOM Program;
(6) evaluate and assess new technology in real-world environments to achieve interoperable emergency communications capabilities;
(7) encourage more efficient use of existing resources, including equipment, to achieve interoperable emergency communications capabilities;
(8) test public safety
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 195g
Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) In general**
(1) **Establishment** — The Secretary, acting through the Assistant Director for Emergency Communications (referred to in this section as the “Assistant Director”), and in coordination with the Federal Communications Commission and the Secretary of Commerce, shall establish an International Border Community Interoperable Communications Demonstration Project (referred to in this section as the “demonstration project”).
(2) **Minimum number of communities** — The Assistant Director shall select no fewer than 6 communities to participate in a demonstration project.
(3) **Location of communities** — No fewer than 3 of the communities selected under paragraph (2) shall be located on the northern border of the United States and no fewer than 3 of the communities selected under paragraph (2) shall be located on the southern border of the United States.
**(b) Conditions** The Assistant Director, in coordination with the Federal Communications Commission and the Secretary of Commerce, shall ensure that the project is carried out as soon as adequate spectrum is available as a result of the 800 megahertz rebanding process in border areas, and shall ensure that the border projects do not impair or impede the rebanding process, but under no circumstances shall funds be distributed under this section unless the Federal Communications Commission and the Secretary of Commerce agree that these conditions have been met.
**(c) Program requirements** Consistent with the responsibilities of the Emergency Communications Division under [section 571 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section571&num=0&edition=prelim), the Assistant Director shall foster local, tribal, State, and Federal interoperable emergency communication
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 594
Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
Page 283
TITLE 6—DOMESTIC SECURITY
§ 571
§ 571. Emergency Communications Division
(a) In general
There is established in the Department an
Emergency Communications Division. The Divi-
sion shall be located in the Cybersecurity and
Infrastructure Security Agency.
(b) Executive Assistant Director
The head of the Division shall be the Execu-
tive Assistant Director for Emergency Commu-
nications (in this section referred to as the ‘‘Ex-
ecutive Assistant Director’’). The Executive As-
sistant Director shall report to the Director of
the Cybersecurity and Infrastructure Security
Agency. All decisions of the Executive Assistant
Director that entail the exercise of significant
authority shall be subject to the approval of the
Director of the Cybersecurity and Infrastructure
Security Agency.
(c) Responsibilities
The Executive Assistant Director shall—
(1) assist the Secretary in developing and
implementing the program described in sec-
tion 194(a)(1) of this title, except as provided
in section 195 of this title;
(2) administer the Department’s responsibil-
ities
and
authorities
relating
to
the
SAFECOM Program, excluding elements re-
lated to research, development, testing, and
evaluation and standards;
(3) administer the Department’s responsibil-
ities and authorities relating to the Integrated
Wireless Network program;
(4) conduct extensive, nationwide outreach
to support and promote the ability of emer-
gency response providers and relevant govern-
ment officials to continue to communicate in
the event of natural disasters, acts of ter-
rorism, and other man-made disasters;
(5) conduct extensive, nationwide outreach
and foster the development of interoperable
emergency communications capabilities by
State, regional, local, and tribal governm
Source: Supplied 2024 U.S. Code historical extraction · 6 U.S.C. § 571
Stored review status: historical_2024_not_currentness_verified. Same stored citation; legal effect and authority still require review.