Browse Arkansas Code titles and sections
6 U.S.C. § 576 — Diversified security technology industry marketplace
Federal law — U.S. Code and appendices · legal_authorities
**(a) In general** Not later than 120 days after October 5, 2018, the Administrator shall develop and submit to the Committee on Commerce, Science, and Transportation of the Senate and the Committee on Homeland Security of the House of Representatives a strategy to promote a diverse security technology industry marketplace upon which the Administrator can rely to acquire advanced transportation security technologies or capabilities, including by increased participation of small business innovators.
**(b) Contents** The strategy required under subsection (a) shall include the following:
(1) Information on how existing Administration solicitation, testing, evaluation, piloting, acquisition, and procurement processes impact the Administrator’s ability to acquire from the security technology industry marketplace, including small business innovators that have not previously provided technology to the Administration, innovative technologies or capabilities with the potential to enhance transportation security.
(2) Specific actions that the Administrator will take, including modifications to the processes described in paragraph (1), to foster diversification within the security technology industry marketplace.
(3) Projected timelines for implementing the actions described in paragraph (2).
(4) Plans for how the Administrator could, to the extent practicable, assist a small business innovator periodically during such processes, including when such an innovator lacks adequate resources to participate in such processes, to facilitate an advanced transportation security technology or capability being developed and acquired by the Administrator.
(5) An assessment of the feasibility of partnering with an organization described in [section 501(c)(3) of title 26](https://uscode.
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 576
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: 265dad50a10536229fcc84779d96382a91a6d8bd62d2e05b51a87613ae2e5c17. 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_92b2f3615fab6b45261bd398
Source file: Laws/federal/codes/united-states-code/title-6/section-576-diversified-security-technology-industry-marketplace--017cd04fc4.md
Pages: Not recorded – Not recorded
Passage SHA-256: bbe1f85d5e530dba6ff4f27ad738d5e58a4c87d7edec45eee4deaea3566e9079
Source location: Title 6, Chapter 1, § 576; chapter-001-homeland-security-organization.md
Stored source content
**(a) In general** Not later than 120 days after October 5, 2018, the Administrator shall develop and submit to the Committee on Commerce, Science, and Transportation of the Senate and the Committee on Homeland Security of the House of Representatives a strategy to promote a diverse security technology industry marketplace upon which the Administrator can rely to acquire advanced transportation security technologies or capabilities, including by increased participation of small business innovators.
**(b) Contents** The strategy required under subsection (a) shall include the following:
(1) Information on how existing Administration solicitation, testing, evaluation, piloting, acquisition, and procurement processes impact the Administrator’s ability to acquire from the security technology industry marketplace, including small business innovators that have not previously provided technology to the Administration, innovative technologies or capabilities with the potential to enhance transportation security.
(2) Specific actions that the Administrator will take, including modifications to the processes described in paragraph (1), to foster diversification within the security technology industry marketplace.
(3) Projected timelines for implementing the actions described in paragraph (2).
(4) Plans for how the Administrator could, to the extent practicable, assist a small business innovator periodically during such processes, including when such an innovator lacks adequate resources to participate in such processes, to facilitate an advanced transportation security technology or capability being developed and acquired by the Administrator.
(5) An assessment of the feasibility of partnering with an organization described in [section 501(c)(3) of title 26](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title26-section501/c/3&num=0&edition=prelim) and exempt from tax under [section 501(a) of title 26](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title26-section501/a&num=0&edition=prelim) to provide venture capital to businesses, particularly small business innovators, for commercialization of innovative transportation security technologies that are expected to be ready for commercialization in the near term and within 36 months.
**(c) Feasibility assessment** In conducting the feasibility assessment under subsection (b)(5), the Administrator shall consider the following:
(1) Establishing an organization described in [section 501(c)(3) of title 26](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title26-section501/c/3&num=0&edition=prelim) and exempt from tax under [section 501(a) of title 26](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title26-section501/a&num=0&edition=prelim) as a venture capital partnership between the private sector and the intelligence community to help businesses, particularly small business innovators, commercialize innovative security-related technologies.
(2) Enhanced engagement through the Science and Technology Directorate of the Department of Homeland Security.
**(d) Rule of construction** Nothing in this section may be construed as requiring changes to the Transportation Security Administration standards for security technology.
**(e) Definitions** In this section:
(1) **Intelligence community** — The term “intelligence community” has the meaning given the term in [section 3003 of title 50](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title50-section3003&num=0&edition=prelim).
(2) **Small business concern** — The term “small business concern” has the meaning described under [section 632 of title 15](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title15-section632&num=0&edition=prelim).
(3) **Small business innovator** — The term “small business innovator” means a small business concern that has an advanced transportation security technology or capability.
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) Reports** On a biennial basis until the date that is 10 years after March 15, 2022, the Director of National Intelligence shall submit to the congressional intelligence committees a comprehensive report on the activities, prioritization, and responsibilities of the intelligence community with respect to foreign biological threats emanating from the territory of, or sponsored by, a covered country.
**(b) Matters included** Each report under subsection (a) shall include, with respect to foreign biological threats emanating from the territory of, or sponsored by, a covered country, the following:
(1) A detailed description of all activities relating to such threats undertaken by each element of the intelligence community, and an assessment of any gaps in such activities.
(2) A detailed description of all duties and responsibilities relating to such threats explicitly authorized or otherwise assigned, exclusively or jointly, to each element of the intelligence community, and an assessment of any identified gaps in such duties or responsibilities.
(3) A description of the coordination among the relevant elements of the intelligence community with respect to the activities specified in paragraph (1) and the duties and responsibilities specified in paragraph (2).
(4) An inventory of the strategies, plans, policies, and interagency agreements of the intelligence community relating to the collection, monitoring, analysis, mitigation, and attribution of such threats, and an assessment of any identified gaps therein.
(5) A description of the coordination and interactions among the relevant elements of the intelligence community and non-intelligence community partners.
(6) An assessment of foreign malign influence efforts relating to such threats, including any foreign
Source: Supplied U.S. Code snapshot — release unconfirmed · 50 U.S.C. § 3003
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Small business concerns**
(1) **In general** — For the purposes of this chapter, a small-business concern, including but not limited to enterprises that are engaged in the business of production of food and fiber, ranching and raising of livestock, aquaculture, and all other farming and agricultural related industries, shall be deemed to be one which is independently owned and operated and which is not dominant in its field of operation.
(2) **Establishment of size standards**
(A) *In general* — In addition to the criteria specified in paragraph (1) and subject to the requirements specified under subparagraph (C), the Administrator may specify detailed definitions or standards by which a business concern may be determined to be a small business concern for the purposes of this chapter or any other Act.
(B) *Additional criteria* — The standards described in paragraph (1) may utilize number of employees, dollar volume of business, net worth, net income, a combination thereof, or other appropriate factors.
(C) *Requirements* — Unless specifically authorized by statute, no Federal department (including the Administration when acting pursuant to subparagraph (A)) or agency may prescribe a size standard for categorizing a business concern as a small business concern, unless such proposed size standard—
(i) is proposed after an opportunity for public notice and comment;
(ii) provides for determining—
(I) the size of a manufacturing concern as measured by the manufacturing concern’s average employment based upon employment during each of the manufacturing concern’s pay periods for the preceding 24 months;
(II) the size of a business concern providing services on the basis of the annual average gross receipts of the business concern over
Source: Supplied U.S. Code snapshot — release unconfirmed · 15 U.S.C. § 632
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) In general** The Secretary, acting through the Assistant Director for Emergency Communications, and in cooperation with the Department of National Communications System (as appropriate), shall, in cooperation with State, local, and tribal governments, Federal departments and agencies, emergency response providers, and the private sector, develop not later than 180 days after the completion of the baseline assessment under [section 573 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section573&num=0&edition=prelim), and periodically update, a National Emergency Communications Plan to provide recommendations regarding how the United States should—
(1) support and promote the ability of emergency response providers and relevant government officials to continue to communicate in the event of natural disasters, acts of terrorism, and other man-made disasters; and
(2) ensure, accelerate, and attain interoperable emergency communications nationwide.
**(b) Coordination** The Emergency Communications Preparedness Center under [section 576 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section576&num=0&edition=prelim) shall coordinate the development of the Federal aspects of the National Emergency Communications Plan.
**(c) Contents** The National Emergency Communications Plan shall—
(1) include recommendations developed in consultation with the Federal Communications Commission and the National Institute of Standards and Technology for a process for expediting national voluntary consensus standards for emergency communications equipment for the purchase and use by public safety agencies of interoperable emergency communications equipment and technologies;
(2) identify the appropriate capabilities
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 579
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
In this title— 11 See References in Text note below.
(1) the term “Administrator” means the Administrator of the Agency;
(2) the term “Agency” means the Federal Emergency Management Agency;
(3) the term “appropriate committees of Congress” means—
(A) the Committee on Homeland Security and Governmental Affairs of the Senate; and
(B) those committees of the House of Representatives that the Speaker of the House of Representatives determines appropriate;
(4) the term “catastrophic incident” means any natural disaster, act of terrorism, or other man-made disaster that results in extraordinary levels of casualties or damage or disruption severely affecting the population (including mass evacuations), infrastructure, environment, economy, national morale, or government functions in an area;
(5) the term “Department” means the Department of Homeland Security;
(6) the terms “emergency” and “major disaster” have the meanings given the terms in [section 5122 of title 42](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section5122&num=0&edition=prelim);
(7) the term “emergency management” means the governmental function that coordinates and integrates all activities necessary to build, sustain, and improve the capability to prepare for, protect against, respond to, recover from, or mitigate against threatened or actual natural disasters, acts of terrorism, or other man-made disasters;
(8) the term “emergency response provider” has the meaning given the term in [section 101 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section101&num=0&edition=prelim);
(9) the term “Federal coordinating officer” means a Federal coordinating officer as described in [section 5143 of title 42](https://uscode.house.gov/view.xhtml?
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 711
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 288
TITLE 6—DOMESTIC SECURITY
§ 576
1 So in original. Subsection (b) of this section does not contain
a paragraph (1).
1439; amended Pub. L. 115–278, § 2(g)(6)(B), Nov.
16, 2018, 132 Stat. 4179.)
Editorial Notes
CODIFICATION
Another section 1805 of Pub. L. 107–296 was renum-
bered section 1905 and was classified to section 595 of
this title, prior to repeal by Pub. L. 115–387, § 2(a)(4),
Dec. 21, 2018, 132 Stat. 5163.
AMENDMENTS
2018—Subsec. (d)(2). Pub. L. 115–278 substituted ‘‘As-
sistant Director for Emergency Communications’’ for
‘‘Director for Emergency Communications’’.
Statutory Notes and Related Subsidiaries
CHANGE OF NAME
Reference to the Assistant Director for Emergency
Communications deemed to be a reference to the Exec-
utive Assistant Director for Emergency Communica-
tions, see section 571(g) of this title, enacted Jan. 1,
2021.
§ 576. Emergency Communications Preparedness
Center
(a) Establishment
There is established the Emergency Commu-
nications Preparedness Center (in this section
referred to as the ‘‘Center’’).
(b) Operation
The Secretary, the Chairman of the Federal
Communications Commission, the Secretary of
Defense, the Secretary of Commerce, the Attor-
ney General of the United States, and the heads
of other Federal departments and agencies or
their designees shall jointly operate the Center
in accordance with the Memorandum of Under-
standing entitled, ‘‘Emergency Communications
Preparedness Center (ECPC) Charter’’.
(c) Functions
The Center shall—
(1) serve as the focal point for interagency
efforts and as a clearinghouse with respect to
all relevant intergovernmental information to
support and promote (including specifically by
working to avoid duplication, hindrances, and
counteractive efforts among the pa
Source: Supplied 2024 U.S. Code historical extraction · 6 U.S.C. § 576
Stored review status: historical_2024_not_currentness_verified. Same stored citation; legal effect and authority still require review.