Je veux savoir à propos de…

Federal Register / Vol. 86, No. 159 / Friday, August 20, 2021 / Rules and Regulations and of any details that they may have concerning the event.
3 Compliance datesparagraph d2 of this section contains an information-collection and recordkeeping requirement. Compliance with paragraph d2 will not be required until after approval by the Office of Management and Budget. The Commission will publish a document in the Federal Register announcing compliance dates with this paragraph and revising this paragraph accordingly.

PART 11EMERGENCY ALERT
SYSTEM EAS
9. The authority citation for part 11 is revised to read as follows:

Authority: 47 U.S.C. 151, 154 i and o, 303r, 544g, 606, 1201, 1206.

10. Section 11.21 is amended by revising the introductory text and paragraph a introductory text and adding paragraphs a8 and g to read as follows:

khammond on DSKJM1Z7X2PROD with RULES

11.21 State and Local Area plans and FCC Mapbook.

EAS plans contain guidelines which must be followed by EAS Participants personnel, emergency officials, and National Weather Service NWS
personnel to activate the EAS. The plans include the EAS header codes and messages that will be transmitted by key EAS sources NP, LP, SP and SR. State and local plans contain unique methods of EAS message distribution such as the use of the Radio Broadcast Data System RBDS. The plans also include information on actions taken by EAS
Participants, in coordination with state and local governments, to ensure timely access to EAS alert content by nonEnglish speaking populations. The plans must be reviewed and approved by the Chief, Public Safety and Homeland Security Bureau Bureau, prior to implementation to ensure that they are consistent with national plans, FCC
regulations, and EAS operation. The plans are administered by State Emergency Communications Committees SECC. The Commission encourages the chief executive of each State to establish an SECC if their State does not have an SECC, and if the State has an SECC, to review the composition and governance of the SECC. The Bureau will review and approve plans, including annual updated plans, within 60 days of receipt, provided that no defects are found requiring the plan to be returned to the SECC for correction and resubmission. If a plan submitted for approval is found defective, the SECC will be notified of the required
VerDate Sep<11>2014

16:42 Aug 19, 2021

Jkt 253001

corrections, and the corrected plan may be resubmitted for approval, thus starting the 60-day review and approval period anew. The approval dates of State EAS Plans will be listed on the Commissions website.
a State EAS Plans contain guidelines that must be followed by EAS
Participants personnel, emergency officials, and National Weather Service NWS personnel to activate the EAS.
The Plans include information on actions taken by EAS Participants, in coordination with state and local governments, to ensure timely access to EAS alert content by non-English speaking populations. State EAS Plans must be updated on an annual basis.
State EAS Plans must include the following elements:

8 Certification by the SECC
Chairperson or Vice-Chairperson that the SECC met in person, via teleconference, or via other methods of conducting virtual meetings at least once in the twelve months prior to submitting the annual updated plan to review and update the plan.

g Compliance datesthe introductory text and paragraphs a introductory text and a8 of this section contain information-collection and recordkeeping requirements adopted in the Report and Order and Further Notice of Proposed Rulemaking, Amendment of the Commissions Rules Regarding the Emergency Alert System;
Wireless Emergency Alerts, PS Docket Nos. 1591 and 1594, FCC 2177 June 17, 2021. Compliance with the introductory text and paragraphs a introductory text and a8 will not be required until after approval by the Office of Management and Budget. The Commission will publish a document in the Federal Register announcing compliance dates with those paragraphs and revising those paragraphs accordingly.

11. Section 11.44 is added to read as follows:

46791

this process. If the re-originated alert is intended to reflect a valid time period consistent with the original, the valid time period code the +TTTT header code identified in 11.31c set for the re-originated alert should be adjusted to account for the elapsed time between the original and re-originated alerts.
Alert originators should be aware that repeating alerts routinely may cause alert fatigue among the public.
12. Section 11.45 is amended by revising paragraph b and adding paragraphs c and d to read as follows:

11.45 Prohibition of false or deceptive EAS transmissions.

b No later than twenty-four 24
hours of an EAS Participants discovery i.e., actual knowledge that it has transmitted or otherwise sent a false alert to the public, the EAS Participant shall send an email to the Commission at the FCC Ops Center at FCCOPS@
fcc.gov, informing the Commission of the event and of any details that the EAS Participant may have concerning the event.
c If the Administrator of the Federal Emergency Management Agency or a State, local, Tribal, or territorial government entity becomes aware of transmission of an EAS false alert to the public, they are encouraged to send an email to the Commission at the FCC Ops Center at FCCOPS@fcc.gov, informing the Commission of the event and of any details that they may have concerning the event.
d Compliance datesparagraph c of this section contains an informationcollection and recordkeeping requirement. Compliance with paragraph c will not be required until after approval by the Office of Management and Budget. The Commission will publish a document in the Federal Register announcing compliance dates for this paragraph and revising this paragraph accordingly.
FR Doc. 202115175 Filed 81921; 8:45 am
11.44

Alert Repetition.

An alert originator may repeat an alert by releasing the alert anewi.e., re-originating the alertat least one minute subsequent to the time the message was initially released by the originator, as reflected in the repeat alerts JJJHHMM header code. Because alerts take time to activate across the EAS alert distribution chain, alert originators should consider an interval between the original and re-originated alert that is long enough to account for
PO 00000

Frm 00031

Fmt 4700

Sfmt 9990

BILLING CODE 671201P

E:FRFM20AUR1.SGM

20AUR1