CommLawCenter

Posted January 12, 2012

By Paul A. Cicelski

It is clear to anyone paying attention that the FCC (along with FEMA) has been working diligently to improve the Nation's Emergency Alert System (EAS). In the last few years alone, the FCC has, among other things, initiated proceedings requiring EAS Participants to accept messages using a common EAS messaging protocol (CAP) for the next generation of EAS delivery; provided guidance regarding "live code" testing of EAS; adopted standards for wireless carriers to receive and deliver emergency alerts via mobile devices; and conducted the first ever nationwide test of the Emergency Alert System.

In its latest effort, the FCC issued a Report and Order earlier this week revising the FCC's Part 11 EAS Rules to specify the manner in which EAS Participants must be able to receive CAP-formatted alert messages, and making other changes to clarify and streamline the Part 11 Rules. As I reported previously, all EAS Participants are required to be able to receive CAP-formatted EAS alerts no later than June 30, 2012.

The FCC's latest Order focuses on the steps necessary to ensure that CAP messages can be processed in the same manner as the currently-used protocol, Specific Area Message Encoding (SAME). The FCC concludes that, for at least the time being, it should maintain the existing legacy EAS daisy chain, including using the legacy SAME protocol, because switching over to a fully CAP-centric EAS system is currently technolocigally infeasible given that most EAS Participants can receive, but are unable to pass along, messages using CAP. Thus, the FCC has a adopted a "CAP-in, SAME-out" transitional approach where EAS equipment will be required to receive and convert CAP-formatted messages into a SAME-compliant message to be sent downstream. In doing so, the FCC agreed with a majority of the commenters in the proceeding, including the National Association of Broadcasters, who argued that "there is a definite value in retaining the current 'daisy-chain' EAS distribution system as a proven, redundant method of delivering public alerts." The FCC's decision is also consistent with comments filed by a consortium of the State Broadcasters Associations, who stated that "it makes little sense for the FCC to adopt sweeping Next Generation EAS rule changes at this time when legacy EAS, as governed by the Commission's current Part 11 Rules, is going to be around for the foreseeable future."

While the FCC's Order is limited in scope, it is not limited in length, coming in at 130 pages. Highlights of the Order that are of particular interest for EAS Participants include the following:

• EAS Participants will be required to use the procedures for message conversion in the EAS-CAP Industry Group's (ECIG's) ECIG Implementation Guide, which was adopted by FEMA on September 30, 2010. Among other things, the ECIG Guide outlines how parties can convert CAP-formatted messages into SAME-compliant messages.
• The FCC has decided that it would be unrealistic to require EAS Participants to use a specific technical standard for CAP monitoring. As a result, while EAS Participants will be required to monitor FEMA's Integrated Public Alert and Warning System (IPAWS) system for federal CAP-formatted alert messages, they will be permitted to do so using whatever interface technology is appropriate for them as long as the equipment used is able to interface with IPAWS.
• The Order states that the FCC will allow EAS Participants to meet their obligation to receive and process CAP messages by using intermediary devices (stand-alone devices capable of decoding CAP-formatted messages) in tandem with their existing legacy EAS equipment.
• Among a series of Part 11 Rule revisions, the FCC is amending Part 11 to require EAS Participants to use the enhanced rich text data in CAP messages to create video crawl displays.
• The Order indicates that the FCC will allow parties to file for waivers of the requirement to monitor, receive, and process CAP-formatted messages. The FCC indicates that a lack of broadband Internet access will create a presumption in favor of a waiver. However, it is important to note that the FCC has limited such waivers to six months, with the option to renew if circumstances do not change.
• As part of a lengthy discussion, the Order adopts streamlined procedures for EAS equipment certification that take into account the standards and testing procedures adopted by the current FEMA IPAWS Conformity Assessment Program for CAP products. In doing so, the FCC is also incorporating conformance with the ECIG Implementation Guide into the certification process.
• The Order also streamlines rules governing the processing of Emergency Action Notifications (EAN) and eliminates several provisions of Part 11, including the Emergency Action Termination (EAT) event code and Non-Participating National (NN) status.

As even the highly condensed summary above indicates, the FCC's Order is lengthy, very technical at times, and includes many rule changes and tweaks that EAS Participants will need to learn. EAS Participants should therefore become very familiar with the Order if they are going to be able to comply with these requirements going forward. They will also need to stay tuned for further developments in this rapidly changing area. With the June 30, 2012, CAP-compliance deadline growing nearer every day, EAS will remain a lively area for the FCC in the coming months.

Posted December 22, 2011

By Paul A. Cicelski

In what now seems like ages ago, the FCC and FEMA conducted the first nationwide test of the Emergency Alert System back on November 9, 2011. While the FCC and FEMA are continuing to review and analyze what went right and what went wrong during the national test, EAS Participants should not forget that their work may not be done. As we discussed immediately following the test, the FCC has mandated that EAS Participants submit the full results of their test to the FCC, either online or on paper, no later than December 27, 2011.

I reported back in October that the FCC created three separate forms for purposes of reporting a station's test results. Stations should have completed Form 1 prior to the test, providing background information regarding the station's facilities and equipment, and Form 2 on or as close as possible to the November 9 test date, providing information on whether or not the station received the national test alert and whether the alert was passed along.

In Form 3, the FCC has asked for more detailed information on the success or failure of the test. We were the first to point out publicly that there is a conflict in dates between the FCC's form page on the website which indicates that the deadline is December 24, and the FCC's National EAS Test Public Notice which indicates that the deadline is December 27. However, the FCC's filing rules and discussions we have had with FCC staff confirm that the official deadline is December 27.

So if you have not done so already, make sure to submit the required information about the success or failure of your EAS equipment during the national test prior to next week's deadline.

Posted November 11, 2011

By Scott R. Flick and Paul Cicelski

In its various incarnations -- CONELRAD, the Emergency Broadcast System, the Emergency Alert System, and soon, the EAS CAP system -- America's public warning system has much in common with a vintage automobile that has been taken out of the garage only for short trips. In those short trips (mostly state and local tests and alerts), it has performed adequately, but until this week's national test, we never had a chance to take it out on the open road and see what it could really do.

Now that the first national EAS test is behind us, we know that the system isn't broken, but that it definitely will benefit from this breaking in process. That process, which necessarily includes extensive analysis of this week's test, will reveal numerous ways in which the system can be tweaked for better and more reliable performance under open road conditions. The basic system appears to have run fine; the message got out to the public (though obviously better in some locations than others).

Unlike the relative simplicity of an automobile, however, the EAS system is one of the largest pieces of machinery in the world, having immense geographic scope and a staggering number of components. Getting all of those components to function smoothly together is a complex task that requires much more effort than the typical automotive tune up. Its performance grows more impressive when you remember that most of those components are independently (and privately) owned and operated, and are not supported by federal funding. The EAS system is perhaps the ultimate public-private partnership.

While it is too early to provide a detailed assessment of the areas where the functioning of the system went astray, as we indicated previously, the purpose of the test was to help FEMA, the FCC, and EAS Participants determine the reliability of the EAS system and where it needs improvement, and the test certainly accomplished that. There were a number of issues uncovered with regard to cable and satellite alerts, as well as individual radio and television stations in Oregon and a number of other locations apparently not receiving the test, excessive background audio noise in the test message, some television stations receiving video but no audio, and header codes apparently being sent twice. While the press has understandably focused on areas where problems arose, initial reports seem to indicate that the alert was heard in the vast majority of locations, and that the next area to focus on is ensuring that the content of the alert itself is clear and understandable to the public.

According to the FCC, it and FEMA will now use the results of the test "to identify gaps and generate a comprehensive set of data to help strengthen our ability to communicate during real emergencies. Based on preliminary data, media outlets in large portions of the country successfully received the test message, but it wasn't received by some viewers or listeners. We are currently in the process of collecting and analyzing data, and will reach a conclusion when that process is complete."

EAS Participants should remember that just because the national test is over, their work is not done. As we discussed in October, the FCC is encouraging online reporting of each Participant's test results as soon as possible and has mandated that the information be submitted to the FCC no later than December 27, 2011 (either online or on paper).

In the meantime, that noise you hear coming from the nation's garage will be thousands of EAS Participants, EAS equipment manufacturers, and government officials tuning and tweaking the EAS system for its next run on the open road.

Posted November 3, 2011

By Scott R. Flick

FEMA has indicated that the audio of the November 9th national EAS test is being shortened from its original two and a half minute length to thirty seconds. Originally, the government had indicated the entire test would run as long as three and a half minutes, but current indications are that the shortened audio will reduce the length of the overall EAS test to 45-60 seconds.

While FEMA's reasoning behind the change is not currently known, I note that the National Cable and Telecommunications Association filed a request with FEMA on October 21, 2011 seeking to delay the national test because many cable systems are not ready for it. The problem is that because the proposed test will use the Presidential Emergency Action Notification code, the video will state that "This is an Emergency Action Notification," and will not give any indication that it is a test. While the audio will make clear that it is a test, those unable to hear the audio (for example, the deaf/hard of hearing or people in a bar where the TV is on but the sound is turned down) could reasonably conclude that an actual emergency is occurring.

While TV broadcasters will generally be inserting a visual crawl indicating that it is only a test, many cable systems do not have that technical capability. NCTA has therefore asked that the test be delayed while the cable industry explores how best technically to insert a visual message over the EAS test assuring viewers that it is indeed only a test.

Given the massive amount of effort that has gone into setting up and preparing for this first ever national EAS test, as well as in notifying the public that there will be a test, delaying it could generate more confusion than just proceeding with the test. It is therefore possible that FEMA's decision to shorten the test is a pragmatic compromise between either delaying the test or scaring the daylights out of the deaf and hard of hearing community. Presumably, a shorter message is less likely to cause confusion, as it won't seem as unusual as an emergency message that runs for over three minutes. At a minimum, it will shorten the period of panic, as those watching will see normal programming resume in less than a minute.

Whether the system can be fully tested by the shorter message is already being debated, and some confusion is now unavoidable, given that that the public and first responders have already been told to expect and plan for a test that runs well over three minutes. At the moment, FEMA is trying to get the word out about the shortened test, hoping to reduce that confusion before November 9th arrives.

UPDATE (1:25pm): The FCC has released a new EAS Handbook in light of the shortened test. The Public Notice announcing the new handbook can be found here, and the new EAS Handbook can be found here. The Public Notice indicates that this new version supersedes the version released last week and should be used for all matters related to the November 9 National EAS Test.

Posted October 31, 2011

By Scott R. Flick and Christine A. Reilly

Pillsbury's communications lawyers have published FCC Enforcement Monitor monthly since 1999 to inform our clients of notable FCC enforcement actions against FCC license holders and others. This month's issue includes:

• Cable Operator Subject to $25,000 Fine for EAS and Signal Leakage Violations
• Late-filed Renewals Garner $26,000 Fine

Interfering Signal Leakage Proves Costly for Florida Cable Television Operator

The FCC issued a Notice of Apparent Liability for Forfeiture ("NAL") to the operator of a Florida cable television system for multiple violations of the FCC's rules. The NAL proposes a $25,000 forfeiture for the system based upon violation of the FCC's cable signal leakage standards, failure to submit the required registration form to the FCC, and failure to maintain operational Emergency Alert System ("EAS") equipment.

During a 2011 inspection of the system, agents from the Tampa Office of the FCC's Enforcement Bureau discovered extensive signal leakage. In order to protect aeronautical frequencies from interference, Sections 76.605 and 76.611 of the FCC's Rules establish a maximum cable signal leakage standard of 20 microvolts per meter ("µV/m") for any point in the system and a maximum Cumulative Leak Index ("CLI") of 64. Inspection of the cable system revealed twenty signal leaks, fourteen of which were over 100 µV/m, with the highest measuring 1,023 µV/m. In addition, the system's CLI measured 64.88, exceeding the maximum permitted level of 64. The operator also acknowledged the system had not maintained cable leakage logs or performed routine maintenance as required by the FCC. The base forfeiture for these violations is $8,000.

The FCC also found two other violations. In 2010, FCC agents discovered the cable system had not filed its required registration statement with the FCC. In the 2011 inspection, the owner admitted the station had not submitted the required form, and, as of the date of the NAL, had still not filed the form. Section 76.1801 of the FCC's Rules specifies a base forfeiture of $3,000 for failing to file required forms. Since the system had still not submitted the form more than a year after being instructed to do so, the FCC ordered an upward adjustment of the fine by $1,500.

Continue reading "FCC Enforcement Monitor"

Posted October 26, 2011

By: Paul A. Cicelski

As I mentioned last week, the FCC has been creating an online reporting system for EAS Participants to use to report their results in connection with the first ever nationwide EAS test, which is set to take place on November 9, 2011. In addition, the FCC has been preparing a new EAS Handbook that is designed to be used during the nationwide EAS test in place of the old Handbook. The FCC has now completed both tasks and issued a Public Notice today announcing the activation of the online reporting system and the release of the Handbook. The reporting system and the Handbook can be accessed on the FCC's Public Safety & Homeland Security Bureau's EAS Nationwide Test Landing Page.

With respect to the reporting system, the FCC is asking that EAS Participants populate the database in advance of the test with items like station call letters, license identification numbers, geographic coordinates, EAS assignments (i.e., LP or NP status, etc.), EAS monitoring assignments, and the emergency contact representative of the EAS Participant. The FCC is also requesting that EAS Participants input immediate test results, (e.g., was the EAN received and was it passed on) on the day of the test. While the FCC is encouraging rapid online reporting of each Participant's test results, it is mandatory that the information be submitted to the FCC within 45 days following the test (either online or on paper).

The FCC has created three separate forms which, together, request the following information:

• Form 1: Prior to November 9, please provide background information on your facilities and equipment.
• Form 2: On November 9, please provide information on whether you received the alert and whether you passed on the alert.
• Form 3: Between November 10 and December 24, please provide more detailed information on the success or failure of the test. (Please note that there is a conflict in dates between the FCC's form page on the website which indicates that the deadline is December 24, while the FCC's Public Notice indicates that the deadline is December 27).

Don't forget that a great deal of additional useful information on the national test can be found at the National Alliance of State Broadcasters Associations' EAS Alert website and at the National Association of Broadcasters' EAS National Test website. Both will greatly assist EAS Participants in successfully completing the national test.

Posted October 20, 2011

By Paul A. Cicelski

As reported previously, FEMA, along with the FCC and NOAA, will conduct the first nationwide Emergency Alert System (EAS) Test on November 9, at 2:00 p.m. Eastern. The EAS has never been tested on a national level. Needless to say, it is important for EAS Participants to educate the public in advance of the test so as to avoid panic when the test airs.

The FCC and FEMA have produced public service announcements (PSAs) to increase public awareness of the test. The National Association of Broadcasters recommends that all EAS Participants air one or more of these PSAs, starting at least a week prior to the test, and then increase the frequency of the PSAs as the November 9 deadline draws near. Video and audio PSAs that can be used to educate the public are located on the FCC's National EAS Test website.

In addition, the National Alliance of State Broadcasters Associations and the NAB have put together very useful EAS websites here and here that can greatly assist EAS Participants in conducting the national test. The NAB has put together a checklist that provides tips to ensure that EAS equipment is ready for the test, and outlines specific actions EAS Participants should take before and after the test. Also, FEMA has put together a just released "EAS Best Practices Guide" that provides helpful information for improving the effectiveness of EAS going forward. On the day of the test, stations should follow the procedures set forth in the FCC's soon-to-be-released new EAS Handbooks, and disregard prior versions of the Handbooks.

The FCC is currently in the process of completing an electronic EAS reporting system to allow EAS participants to electronically report on their experience in participating in the national test (what went right and what went wrong at their facility). As soon as it becomes available, the FCC is encouraging EAS Participants to log in and populate the system with as much "pre-fill" information as possible in advance of the test so as to facilitate the rapid submission of reports by EAS Participants once the test has concluded.

While EAS Participants are not required to submit their EAS test reports electronically, the FCC is encouraging electronic filing to provide the FCC with "real time results" from the test. As soon as practicable following the test, the FCC is urging EAS Participants to let the FCC know whether they (1) received the Emergency Action Notification and (2) if required to do so, were able to rebroadcast the test. Within 45 days following the test, all EAS Participants must provide a comprehensive and detailed diagnostic report to the FCC on the results of their participation in the test. This mandatory report can be filed either electronically or on paper.

Perhaps the most important action EAS Participants can take beyond educating the public (and hopefully state and local officials) in advance of the test, is to make sure that their EAS equipment is functioning properly and is actually attended by someone when the national test message is received on November 9. While the equipment is designed to automatically receive and retransmit test messages, nothing beats having someone there to monitor the process and ensure the test is relayed smoothly.

Stay tuned for further details on the test as they become available, including a discussion of the soon-to-be-operational FCC national test filing database and the not-yet-released EAS Handbooks to be used during the national test. Both should be made public any day now.

Posted October 6, 2011

By Paul A. Cicelski

As we previously reported here and here, the Federal Emergency Management Agency (FEMA), along with the Federal Communications Commission (FCC) and the National Oceanic and Atmospheric Administration (NOAA), will conduct the first nationwide Emergency Alert System (EAS) Test on November 9, at 2:00 p.m. Eastern.

FEMA and the FCC have strongly urged EAS Participants to get advance word of the test out to the public in order to avoid an Orson Welles "War of the Worlds" type of panic when the national test is initiated. To that end, FEMA has produced a Public Service Announcement (PSA) that EAS Participants can use to forewarn the public of the national test. The FCC has indicated that it will soon be making scripts available on its website for EAS participants to use to warn the public.

An interesting issue that has arisen in connection with broadcasters and other EAS Participants using the PSAs is whether the spots require sponsorship identification under the FCC's sponsorship identification rules. Even though it is reasonable to argue that no "money, service or other valuable consideration [will be] directly or indirectly paid, or promised to or charged or accepted" for airing the PSA, recent FCC sponsorship identification decisions involving Video News Releases have fined parties for using spots (unrelated to EAS) provided free of charge by third parties (in this case, FEMA).

Given the public service nature of the spot, and the fact that it is being provided by the Federal Government, it seems unlikely that the FCC will have an appetite for pursuing those who air the spot without adding sponsorship identification. However, in light of the FCC's decisions finding fault with airing even a portion of a third party Video News Release without including sponsorship identification, those airing FEMA spots might want to consider adding sponsorship ID tags to them.

It is also important to remember that the FCC will be requiring EAS Participants to file reports on the results of the test, including whether, and from whom, parties received the alert message and whether they were able to rebroadcast the test message. The FCC is in the process of establishing an electronic filing system on its website to allow EAS Participants to file the reports in as close to real time as possible following the test. Although only paper filing of the reports is required under the FCC's rules, the FCC is strongly encouraging parties to file electronically in order to allow FEMA and the FCC to review the results as quickly as possible. This will allow them to determine sooner rather than later if there are any problems with the EAS system that need to be addressed.

While the FCC has left open the question of whether it may take enforcement action against parties reporting problems in fulfilling their EAS obligations during the national test, it is clear is that the FCC will have little sympathy for parties who fail to actually participate in the test at all. Also, given that the FCC's rules currently require weekly and monthly EAS tests, EAS Participants should ensure that their EAS equipment is operating in compliance with FCC rules now so that they have no unhappy surprises to report to the FCC following the national test.

More information regarding the details of the national test can be found on the FCC's website here, and on FEMA's website here. The national EAS test date is drawing near, and the time for resolving these preparatory questions is running out.

Posted September 16, 2011

Paul A. Cicelski

As I reported last month, my colleague Dick Zaragoza and I filed a Petition with the FCC asking for a further extension of the deadline for EAS Participants to implement the Common Alerting Protocol (CAP) standard for the Emergency Alert System (EAS).

We filed the Petition on behalf of representatives of all EAS Participants, which included the State Broadcasters Associations, representing all fifty States and the District of Columbia, the National Association of Broadcasters, the Broadcast Warning Working Group, the National Cable and Telecommunications Association, the American Cable Association, National Public Radio, the Association of Public Television Stations, and the Public Broadcasting Service. Today, the FCC released an Order agreeing with the need for an extension and changing the CAP deadline from September 30, 2011 to June 30, 2012.

The extension means that the thousands of EAS Participants across the country now have additional time to acquire and install the equipment needed to become CAP-compliant. In its Order, the FCC agreed with the arguments made in the Petition by the broadcast and cable industries that a later deadline was necessary in light of the regulatory uncertainty that remains regarding what is necessary for CAP compliance, particularly because the FCC's EAS Third Further Notice of Proposed Rulemaking (released in May and which we reported on here) will undoubtedly lead to significant EAS rule changes that could alter the requirements for EAS Participants in a way that would impact the manner in which they will go about buying, installing, testing and operating new CAP-compliant EAS equipment. In short, the extension will enable EAS Participants to review and adapt to the final rules adopted or altered in the EAS proceeding.

According to the FCC's Order, the extension is warranted because "until the Commission has completed its rulemaking process, it cannot meaningfully impose a deadline by which EAS Participants must be able to receive CAP-formatted alerts." The Commission further stated that no one "can comply with section 11.56 yet, because the Commission has not finalized all the key technical specifics necessary for receiving CAP-formatted alerts" and that it is "unlikely that the Commission can address all of the issues raised in the Third FNPRM and ensure that the corresponding Part 11 rule amendments are adopted and effective prior to the current September 30, 2011 deadline." Primarily for these reasons, the FCC extended the deadline to allow "adequate time to evaluate the impact of any changes to Part 11 before being required to comply with regulations the full impact of which cannot yet be known."

On another positive note, the Commission's extension of the CAP-compliance deadline may allow the first-ever National EAS Test scheduled by FEMA and the FCC (set for November 9, 2011) to run more smoothly. The hope is that, as argued in the Petition, the extension of the CAP-compliance deadline until June of next year will allow participants in the scheduled November 9, 2011 National EAS test to focus on the success of that test instead of being concerned with the functioning of newly-installed EAS equipment. For those interested in more background on the National EAS test, we previously reported on it here and here). With this most recent extension of the EAS CAP deadline, we hope we will be able to later report that the national test went smoothly.

Posted August 2, 2011

By Paul A. Cicelski

As we reported previously, in an atypical display of unity among broadcasters and the cable industry, the parties found common ground and filed a Petition with the FCC seeking to extend the deadline for implementing the Common Alerting Protocol (CAP) standard.

Last week, that unified front continued when we filed a further extension request with the FCC on behalf of an even greater assembly of EAS Participants, including the State Broadcasters Associations, representing all fifty States and the District of Columbia, the National Association of Broadcasters, the Broadcast Warning Working Group, the National Cable and Telecommunications Association, the American Cable Association, National Public Radio, the Association of Public Television Stations, and the Public Broadcasting Service. The Petition asks the FCC to grant a further extension of at least 180 days beyond the current September 30, 2011 CAP compliance deadline, with the 180 days to run from the effective date of the Commission's amendment of its Part 11 rules pursuant to its recently released Third Further Notice of Proposed Rulemaking. (Our discussion of the Third Further Notice can be found here).

In granting the earlier request for an extension of the CAP deadline, the FCC acknowledged that if it failed to extend the 180-day deadline, it could "lead to an unduly rushed, expensive, and likely incomplete process." As a result, the Commission issued its Order giving EAS Participants until September 30, 2011, to acquire and install equipment able to accept CAP-formatted EAS messages.

In their Petition seeking a further extension of the CAP deadline, the broadcast and cable industries assert that a later deadline is warranted given the regulatory uncertainty that remains regarding CAP compliance. The Petition notes the nearly unanimous view of those who commented on the Third Further Notice that the deadline should be further extended because the FCC has not yet decided whether it will itself conduct EAS equipment certification in addition to the certification being done by FEMA. The Petition also notes that the Third Further Notice may lead to Part 11 rule changes altering the current obligations of EAS Participants in ways that would affect the purchase, installation and operation of new EAS equipment.

The Petition also states that a further extension will allow participants in the scheduled November 9, 2011, National EAS Test to focus their limited engineering resources on ensuring the success of the nationwide test. (We previously reported on the first National EAS Test here and here).

It remains to be seen whether a further extension will be granted, but if the Petition and the majority of comments recently filed in response to the FCC's Third Further Notice in the EAS proceeding are any indication, EAS Participants -- including broadcasters, cable operators and many others -- feel strongly that a further extension of the deadline is essential.

Posted July 15, 2011

By Paul A. Cicelski

As we reported last month, the federal government has decided to conduct the first-ever national test of the Emergency Alert System. On June 9, 2011, FEMA and the FCC announced that the natiowide test is scheduled to occur on November 9, 2011, at 2pm Eastern Standard Time.

In an effort to answer questions about the test, the FCC has launched a helpful "Emergency Alert System Nationwide Test" information page which can be found here. The page includes a countdown clock (117 days and counting!) and provides the who, what, when, where and why regarding the first national test.

Last month we also reported that the FCC has implemented a rulemaking proposing sweeping changes to the Part 11 EAS Rules in order to codify the obligation that EAS Participants begin formatting EAS messages using the Common Alerting Protocol (CAP). The FCC's Third Further Notice of Proposed Rulemaking raises a host of questions, the most immediate of which is whether the current September 30, 2011 deadline for implementing CAP should be extended. For the vast majority of EAS Participants trying to meet that deadline, the answer to the FCC's question appears to be a resounding "yes". Among other issues, installing new EAS equipment just a month before the first national EAS test is likely to result in a national test beset by the "teething pains" of getting the new equipment functioning smoothly.

If you wish to respond to this or any of the other CAP-related questions being considered by the FCC, remember that comments are due at the FCC next Wednesday, July 20.

Posted June 9, 2011

By Scott R. Flick

As I wrote back in February, the federal government has decided to conduct the first-ever national test of the Emergency Alert System. Today, FEMA and the FCC announced that the test will occur on November 9, 2011, at 2pm Eastern Standard Time. On that date, the public will hear a message indicating "This is a test," but FEMA and the FCC indicate that the entire test could last up to three and a half minutes.

Because the test is a presidential EAS test, it must be retransmitted by radio and television broadcasters, cable operators, satellite radio service providers, direct broadcast satellite service providers, and wireline video service providers. In the announcement, FEMA took pains to note that the test will not simply be a pass/fail exercise, but an opportunity to find out what is working and what isn't, so that the system can be tweaked and improved.

It is likely that the national EAS test will become an annual event following this initial test. One issue that was not discussed in the announcement, however, is how the current September 30, 2011 deadline for EAS participants to install EAS equipment compatible with the Common Alerting Protocol (CAP) could affect the test. The FCC had originally said that the intent of a national test was to assess the existing EAS operation, as opposed to testing the implementation and functionality of the new CAP-compliant EAS equipment soon to being purchased and installed by broadcast, cable, and satellite operators.

As the FCC just last week announced the commencement of a rulemaking to adopt rules and processes for the implementation of CAP, there is a growing feeling that the September 30, 2011 CAP implementation deadline may need to be extended in order to prevent a situation where EAS participants are required to immediately purchase and install new EAS equipment that may or may not comply with the CAP requirements ultimately adopted by the FCC. Whether intended or not, a national EAS test just six weeks after the CAP deadline will likely end up being more about the teething pains of CAP implementation than about how reliably the current EAS infrastructure functions.

As a result, preventing the national test from being sidelined by the inevitable implementation glitches of CAP may be the strongest reason yet for extending the CAP implementation deadline to a date beyond November 9, 2011. It will be good to know how the never-before-tested national EAS infrastructure functions before adding the additional complexities of CAP-compliant EAS equipment to it.

Posted June 2, 2011

By Paul A. Cicelski

Last week, the FCC released its long-awaited Third Further Notice of Proposed Rulemaking, the goal of which is to modify Part 11 of the FCC's Rules in order to allow for Common Alerting Protocol (CAP) delivery of the "next generation" Emergency Alert System (EAS). A copy of the NPRM can be found here.

EAS Participants (e.g., radio and television stations, wired and wireless cable television systems, DBS and SDARS services) have been anxiously waiting for the FCC to release this NRPM since at least the end of last year. The primary reason for this, as we previously reported here and here, is that CAP-compliant EAS encoders/decoders must be purchased, installed and operational by September 30 of this year. The hope of EAS Participants has been that this proceeding will provide them with much needed guidance to make informed decisions regarding what equipment they should obtain and install to ensure compliance with CAP and the revised Part 11 rules. The NPRM also gives EAS Participants the opportunity to comment on the proposed rules and to provide input regarding how CAP and next generation EAS will impact their operations going forward.

The NPRM is a lengthy 203 paragraphs (with an additional 18 pages of proposed new rules) and it asks for public comment on many items related to revising and streamlining the FCC's Part 11 rules and how the FCC should codify the requirements for processing emergency alerts using CAP. A few of the NPRM's highlights are summarized below.

Continue reading "FCC Releases Long-Awaited Emergency Alert System NPRM"

Posted February 3, 2011

By Scott R. Flick

Late today, the FCC released an Order laying the groundwork for the first national test of the Emergency Alert System. As we noted in an earlier post, the FCC began this process nearly a year ago, when it released a Notice of Proposed Rulemaking seeking public comment on the implementation of regular national EAS tests. Today's order modifies the FCC's Rules to authorize such tests as well as to establish the ground rules for conducting them.

Specifically, the Order:

• Requires all EAS participants to participate in national EAS tests scheduled by the FCC in consultation with the Federal Emergency Management Agency;


• Requires that the first national test use the Emergency Alert Notification code, the live event code used for nationwide Presidential alerts;


• Provides that the national test replaces the monthly and weekly EAS tests in the month and week it is held;


• Requires the Public Safety and Homeland Security Bureau of the FCC provide at least two months' public notice prior to a national test;


• Requires EAS participants to submit test-related data within 45 days of the test;


• Requires that test data received from EAS participants be treated as presumptively confidential, but allows it to be shared on a confidential basis with other federal agencies and state emergency management agencies that have confidentiality protection at least equal to that provided by the Freedom of Information Act; and


• Delegates authority to the Public Safety and Homeland Security Bureau, in consultation with FEMA and other EAS stakeholders, to establish various administrative procedures for national tests, including the location codes to be used in the alerts and the pre-test outreach to be conducted.

While many following this proceeding had anticipated that the FCC might hold off on a national test until it had modified its rules to incorporate Common Alerting Protocol and the deadline for EAS participants to install CAP-compliant equipment had passed, it appears the first national test could occur as early as this Fall. The order specifically notes that the first "national EAS test is strictly of the legacy EAS system and is independent of the transition to CAP."

The Order notes the need for significant public outreach prior to the test (to avoid public panic), and acknowledges that, at least for the first test, EAS participants will likely get more than the minimum two months' warning to accomplish that public education objective.

Of particular note to EAS participants is the requirement that they record and submit to the FCC within 45 days of the test a fair amount of detail regarding that participant's performance during the test (e.g., was the alert received and passed on successfully, what equipment was used, what was the cause of any problems that occurred, etc.). In order to facilitate the submission of that data, the FCC also announced that it will be creating an electronic filing system that EAS participants may elect to use to comply with the reporting requirement.

Because the FCC wishes to encourage EAS participants to be honest in reporting failures that occur during national tests, it did note that it would treat the required submissions as a "voluntary disclosure". In the past, the FCC has considered a licensee's voluntary disclosure of a rule violation to be a mitigating factor that can merit a reduction in the fine or other sanction imposed. Notably, however, the FCC did not foreclose itself from issuing fines or taking other action against an EAS participant reporting a failure of its equipment/performance in the national test, particularly where the violation is "repeated, egregious, or not promptly remedied."

As a result of today's Order, and the wheels it puts in motion, broadcasters, cable providers, and other EAS participants will need to make sure they and their EAS equipment are ready to participate in a national EAS test as early as this Fall. The FCC, FEMA and other governmental agencies also have much to do before a national test can occur. However, today's action clears the initial obstacles away, and will allow the FCC to achieve its goal of assessing "for the first time, the readiness and effectiveness of the EAS from top-to-bottom, i.e., from origination of an alert by the President and transmission through the entire EAS daisy chain, to reception by the American public." That assessment has been a long time coming, and while it does present some regulatory risks for EAS participants, most will be pleased to have confirmation that the EAS equipment they have maintained day in and day out, year after year, will serve its intended purpose should a national emergency require it.

Posted January 20, 2011

By Scott R. Flick and Christine A. Reilly

Pillsbury's communications lawyers have published FCC Enforcement Monitor monthly since 1999 to inform our clients of notable FCC enforcement actions against FCC license holders and others. This month's issue includes:

• Antenna Structure Owner's Failure to Act Results in $25,000 Fine


• FCC Fines Microwave Licensee $15,000 for Late-Filed Renewal


• AM Broadcaster Receives Reduced Fine for EAS Violation

In January 2010, a Houston Field Office agent responding to a complaint inspected a 253 foot antenna structure located in Yorktown, Texas. According to the Notice of Apparent Liability ("NAL") issued by the Federal Communications Commission ("FCC"), the antenna structure was unlit and unidentifiable at the time of inspection, in violation of Section 17.51 and Section 17.4 of the FCC's Rules. The field agent later determined that the antenna structure owner had failed to notify (1) the Federal Aviation Administration ("FAA") of the lack of tower lighting, thereby violating Section 17.48 of the FCC's Rules, and (2) the FCC of a change in ownership of the antenna structure, which violated Section 17.57 of the FCC's Rules.

Following the initial inspection, in an effort to maintain public safety and avoid hazards to aircraft, the field agent requested that the FAA issue a Notice to Airman ("NOTAM") about the tower's lack of lighting. The field agent also contacted the antenna structure owner to discuss the violations discovered during the inspection. In a subsequent inspection, some eight months later, the field agent determined that none of the violations had been cured by the antenna structure owner. Again, the field agent contacted the FAA with a request to reissue another NOTAM regarding the unlit antenna structure.

Section 17.51 establishes that obstruction lighting must be functioning between sunset and sunrise. Section 17.4 requires antenna structure owners to display the ASR number in a "conspicuous place so that it is readily visible near the base of the antenna structure." Section 17.48 requires antenna structure owners to notify the FAA in the event that a structure's lights are malfunctioning or inoperable for more than 30 minutes. Section 17.57 establishes, among other things, that an antenna owner must immediately notify the FCC of any change in the ownership of the structure.

The base fines for the violations discussed above are $10,000 (lighting and FAA notification), $2,000 (displaying ASR) and $3,000 (failure to notify FCC of ownership change). Based on the antenna owner's lack of responsiveness, the FCC upwardly adjusted the fines to $15,000, $4,000 and $6,000, for a total forfeiture of $25,000.

Continue reading "FCC Enforcement Monitor"