Don't Forget FCC Report on Nationwide EAS Test - Due December 27

All broadcasters and other EAS participants need to remember to file their reports on whether or not they received the Nationwide EAS Test by December 27.  With everyone preparing for the holidays, and with much of the publicity about that test having died down, it may be very easy for some to have forgotten that the test was conducted in early November, and that all stations and other EAS participants have an obligation to file with the FCC by December 27 reports on their experience with the test.  The FCC Forms are available on its website.  As we wrote after the test was completed, there were many problems in the transmission of the test, and the failure of your station to receive or rebroadcast the test in unlikely to have a regulatory penalty - the effectiveness of the test being what the whole exercise was designed to measure.  But the failure to file the form to give the FCC the information to assess the effectiveness of the test and to locate problem areas, could well cause enforcement issues.  So, in your holiday scrambles, make time to remember to let the FCC know about your station's experience with the Nationwide EAS test by next Tuesday's deadline.   

FCC Extends Deadline for Emergency Alert System (EAS) CAP Compliance Until June 30, 2012

The FCC today announced that it is extending the deadline for participants to comply with the new EAS CAP (Common Alerting Protocol) rules until June 30, 2012.  The deadline had previously been set for just two weeks from now, September 30th; however, in light of the fact that the FCC had yet to finalize all of the new EAS CAP rules, it decided to extend the deadline until next June.  Thus, according to today's Order, available here, EAS participants will be required to be able to receive CAP-formatted EAS alerts no later than June 30, 2012.  Such an extension had been widely supported by EAS participants and commenters in the current EAS CAP rule making proceeding.  The FCC expects to adopt the CAP-based revisions to its Emergency Alert System rules in a subsequent order, and it expects those new rules to be out sufficiently in advance of the June 30, 2012 deadline in order to allow EAS participants ample time to come into compliance with those new rules. 

In addition, the Commission's Order urges EAS participants that have purchased or are considering purchasing any type of EAS equipment to verify with the manufacturer or vendor that the equipment fully complies with the FCC rules.  As the FCC has yet to rule on many issues related to the use of intermediary devices -- i.e., devices that connect in some fashion with previously certified EAS equipment to allow receipt of CAP-formatted alerts -- including whether such intermediary equipment must be certified under the FCC's rules or whether they fully satisfy the new CAP requirements, it is not clear whether such intermediary devices will ultimately satisfy all elements of the Commission's new EAS CAP rules.  So until the FCC issues its subsequent Report and Order addressing such issues, buyer beware.  See our earlier postings here for more information about the new EAS CAP rules. 

Hurricanes and Earthquakes - Emergency Communications In the Spotlight With CAP Conversion and National EAS Test Coming Soon (Though, For CAP, Maybe Not As Soon As We Thought)

There has been much focus on emergency communications recently, with the East Coast earthquake re-igniting the debate over FM-enabled mobile phones, and with Hurricane Irene forcing stations to gear up for emergency coverage in the coming days.  But even without these unusual events, the emergency communications world has been much in the news, given the current requirement for broadcast stations to be ready for the new Common Alerting Protocol ("CAP"), an Internet-based alerting system, by the end of September, and with the first-ever test of the National EAS system scheduled for November.  The CAP conversion date has recently been the subject of debate in a number of FCC filings - and there seems like a good chance that the September 30 deadline will be delayed - if for no other reason than the fact that the FCC has yet to adopt final rules for the equipment required for such compliance.  The National Test, however, should go on as scheduled.  More on all of these subjects below.

First, the coming hurricane should prompt stations to be ready for potential emergency operations.  The FCC in the past has publicized its Disaster Information Reporting System (DIRS).  Stations can voluntarily register with DIRS to give the FCC a contact person to assess damage after the storm, and to notify the FCC of the need for any aide that the Commission might be able to provide.  During the aftermath of Hurricane Katrina, I was personally involved in discussions with FCC personnel who coordinated with other government agencies to get clearance for diesel tanker trucks to gain access to restricted area to deliver fuel to a client's radio station that was still operational (on generator power) providing emergency information to Mississippi's Gulf Coast. The FCC personnel can be of great assistance in such situations, so DIRS registrations may be worth considering.  The FCC's website also provides helpful information about planning for disaster recovery  and about hurricanes specifically.  FCC emergency contact information is also on their site.

In thinking about emergencies, TV stations need to remember the requirements that they visually provide any information about an immediate emergency threatening discreet groups of viewers.  In the heat of the moment, when rushing to get out information about a tornado that could be spun out of a storm or some other imminent catastrophe, station personnel may not think about their obligation to provide information visually to those who have a hearing impairment.  But, whether through the use of captioning or even a white board, if you are telling viewers in a given area to take cover or any other specific action, or warning them about a specific threat to their safety - provide that information visually as well.  For the visually impaired, you need to run an audible tone before any video-only caption that you may be running to provide an alert that emergency information is about to run.  There are well-organized citizen's groups who have been known to file complaints about stations who do not provide such information - so remember to provide it to avoid facing an FCC penalty because you did good work, but forgot to make sure that your good information was available to all segments of your audience.

Should there be damage to station facilities, the FCC is also good about giving temporary authority to stations to operate with emergency equipment or from unlicensed locations or with a different power than licensed.  Look for other FCC emergency information to be publicized soon if Irene continues on her current track.

In the longer term, there are two notable events upcoming for the EAS system. The first is the conversion to CAP, delayed last year until September 30 of this year.  However, as we wrote earlier this summer, the FCC is still considering specific rules governing the CAP system, and that proceeding raises a number of issues.  One big issue for many rural stations has been the fact that the system needs an always-on, high-speed Internet connection to work - and some stations do not have access to such connections.  Reply comments in that proceeding were only submitted at the beginning of this month, so the Commission has not yet completed its review of the issues.  Because there are no rules, a number of broadcast groups have asked for a 180 day extension of the deadline. Even FEMA (the Federal Emergency Management Agency, which is developing the alerting system) has suggested that the FCC not penalize until early next year any station that is not fully CAP compliant.  Only some equipment manufacturers have suggested that the September deadline be kept in place.  We would look for some word from the FCC soon, and if we would have to bet, we'd expect to see some extension of the deadline in the cards (though one never knows for sure...)

The first nationwide test of the EAS system is also on the horizon - scheduled for November 9.  This is not a test of the CAP system, but will use the traditional "daisy chain" alert that is passed from one station to another (a system that will remain in place after CAP implementation to provide redundancy in the system).  The FCC just published more information about this test.  Many states will be testing their systems before the nationwide test to ensure that systems are fully operational. Check your station's facilities now, as there will be a post-test report filed with the FCC by all stations, and you don't want to be a station that has to report that an avoidable problem that made your station miss the test. 

Finally, there is the debate about whether mobile phones should be enabled to receive broadcast signals, especially in the time of emergency.  The NAB has made much of the fact that cell phone reception in areas affected by this week's earthquake were tied up for some time, while broadcasters were able to get information out to the public. Broadcasting obviously is designed to get a single message out to a mass audience, rather than to provide the one-to-one communication of a phone or even an IP-based system.  Any attempt to require phones to legislatively mandate enabled FM chips in mobile devices is likely to continue to be vociferously opposed by the wireless and consumer electronics industries.  But, as in the case of the earthquake, broadcasters (and Federal emergency managers - see the video here) should continue to get the word out of the importance of broadcasting in emergencies - so that consumer demand can drive the adoption of enabled radios in mobile devices. 

FCC Rule Making Suggesting Changes to EAS Rules has been Published in the Federal Register; Deadline for Comments is July 20

The FCC’s recent Notice of Proposed Rule Making outlining changes to the FCC's Part 11 Rules governing the Emergency Alert System ("EAS") was published in the Federal Register today.  Today's publication establishes the timing for submitting Comments in this proceeding.  Comments will be due by July 20, with Reply Comments due by August 4th.  By its Third Further Notice of Proposed Rulemaking, released on May 26, 2011 (“NPRM”), the Commission suggested changes to its EAS rules intended to integrate Common Alerting Protocol or "CAP" based alert messaging into the existing EAS while laying the foundation for transitioning to next generation alert mechanisms. The current "SAME" protocol ("Specific Area Message Encoding") will continue to be used.  But CAP messaging, which allows for more information to be conveyed with each alert, would be overlaid on the system.  CAP is an IP based system, with messages delivered to stations by the Internet, and then converted into SAME for broadcast by the participating stations. 

Please see our longer article from last week, which can be found here, discussing in detail the specific questions raised by the Commission's NPRM.  In addition, David Oxenford recently participated in a Town Hall Webinar on EAS and CAP issues, that was held on Thursday, June 16, 2011, sponsored by the National Alliance of State Broadcast Associations and the NAB.  More information about the webinar can be found here, including an archived copy of the June 16th Town Hall Webinar, which should be available shortly. 

Parties interested in filing comments with the Commission should gather their thoughts as the clock is now ticking.  Comments can be filed with the Commission in paper, or electronically via the Electronic Comment Filing System

EAS Tones in Commercial Messages - A Problem Under FCC Rules

In the "what were they thinking" category, the Society of Broadcast Engineers reports that there is a commercial for the new Skyline movie that contains an EAS tone - that can actually set off EAS receivers.  If a station is operating without an attendant, with the EAS on automatic, a receiving station could be automatically start retransmitting its primary station if it hears the tone in the ad - causing the receiving stations to start running the commercial thinking that it is an EAS alert, and it might continue running that commercial and subsequent programming from the primary station for several minutes as there was no termination code in the commercial.  This is not the first time in recent months that this issue has arisen - only a few months ago an ad by BP for its ARCO subsidiary also contained alert tones.  While this may be a mistake by commercial advertisers aiming for reality in their some marketers, as opposed to a cynical marketing ploy to take over stations that received the signal from the primary station on which the ad was run, this type of ad could be a violation of the FCC's rules - so broadcasters should be vigilant in policing these ads.

Section 11.45 of the Commission's Rules states:

No person may transmit or cause to transmit the EAS codes or Attention Signal, or a recording or simulation thereof, in any circumstance other than in an actual National, State or Local Area emergency or authorized test of the EAS. Broadcast station licensees should also refer to § 73.1217 of this chapter.

While this rule also refers broadcasters to Section 73.1217, the prohibition on broadcast hoaxes that might cause substantial harm, Section 11.45 is an absolute prohibition on the use of EAS tones for other than an emergency - whether or not harm is caused.  Stations need to police these ads - and advertisers themselves need to be aware that these ads are prohibited under FCC rules. 

FEMA Adopts Digital Message Format for EAS CAP Standard, Triggering 180-Day Clock for Compliance

This afternoon, FEMA (Federal Emergency Management Agency) adopted the new digital message format for the Common Alerting Protocol (CAP) standard.  The adoption of this message format is the next step in the implementation of Integrated Public Alert and Warning System (IPAWS), which expands the traditional Emergency Alert System used by radio and television to other communications devices, such as mobile phones and personal computers.  In the words of the FEMA news release issued today:  "This open standard will enable alert messages to be easily composed by emergency management officials for communication with citizens using a much broader set of devices to reach as many people as possible."

More importantly for broadcasters, the adoption of this digital message format triggers the clock for updating their EAS equipment to ensure that it is able to handle the new Common Alerting Protocol.  As we wrote about earlier, as part of an EAS Order adopted by the FCC back in 2007, the Commission mandated that all EAS participants -- which includes radio, television, and cable -- must accept CAP-based EAS alerts within 180 days after the date on which FEMA publishes the applicable technical standards for CAP.  Thus, with FEMA's adoption of the CAP messaging standard today it would appear that the 180-day clock has been triggered and the countdown for broadcast stations to acquire CAPS-compliant EAS equipment has begun.  I say "it would appear" because it is a bit unclear whether the 180-day clock is triggered instantaneously by the release of FEMA's notice.  Trade press this evening is reporting that the FCC has confirmed that the clock has indeed been triggered and is counting down, but no official notice has been released yet by the FCC.  Readers will recall that that the Commission is still in the midst of a proceeding to adopt revisions to its EAS rules to facilitate the CAP standard.  In addition, several parties commenting in the EAS proceeding requested an extension or tolling of the 180-day clock in order to allow broadcast stations more time to acquire the necessary equipment and to allow equipment manufacturers more lead time to meet the demand for new equipment brought about by the rule changes.  In comments today at the NAB/RAB Radio Show today, FCC staff members acknowledged that several requests for extension of time had been made and were being considered along with the comments filed in the proceeding.  We will update this post with further information if and when the FCC releases a Public Notice regarding the 180-day clock, but in the meantime broadcasters should operate under the premise that the 180-day clock is now ticking and start making plans to ensure that they have CAP-compliant EAS equipment in place within 180 days from today. 

Comments Regarding Possible Revisions to FCC's Emergency Alert System (EAS) Rules due May 17

With the recent April 15th publication of an FCC Public Notice in the Federal Register, the due date for Comments regarding possible revisions to the FCC's Emergency Alert System (EAS) rules has been set at May 17th, with Reply Comments due by June 14.  By this recent Public Notice, the Commission has requested  informal comments regarding revisions to its EAS rules in connection with the forthcoming adoption of the Common Alerting Protocol (CAP) by the Federal Emergency Management Agency (FEMA).  So what, you might ask, is “CAP”? 

CAP stands for “Common Alerting Protocol” and is the next-generation protocol for distributing emergency warnings and safety notifications.  In technical jargon it is “an open, interoperable, data interchange format for collecting and distributing all-hazard safety notifications and emergency warnings to multiple information networks, public safety alerting systems, and personal communications devices.” In layman’s terms, it will allow FEMA, the National Weather Service, a state Governor, or others authorized to initiate public alert systems to automatically format and even target a specific geographic area and simultaneously alert the public using multiple media platforms including broadcast television, radio, cable, cell phones, and electronic highway signs. CAP will also allow for alerts specifically formatted for people with disabilities and for non-English speakers.

As part of an EAS Order adopted by the FCC back in 2007, the Commission mandated that all EAS participants -- which would include radio, television, and cable -- must accept CAP-based EAS alerts within 180 days after the date on which FEMA publishes the applicable technical standards for CAP.  According to the FCC, FEMA has recently announced its intention to adopt a version of CAP as early as the third quarter of 2010, which would in turn trigger the Commission’s 180-day requirement.  Given that the Commission’s current EAS rules pre-date the concept of Common Alerting Protocol, the existing EAS rules will likely need significant revision or even replacement once CAP is adopted and implemented. 

Accordingly, in light of the short time frame following FEMA's adoption of the CAP standard, and order to get ahead of any rulemaking that may be necessary to update its rules, on March 25th the FCC’s Public Safety and Homeland Security Bureau issued a Public Notice seeking informal comments regarding what, if any, changes might be necessary to the FCC's EAS Rules in order to accommodate the introduction of CAP.  The FCC has asked that commenters specifically identify the existing rules that need to be modified or deleted, and to suggest new rules for EAS system architecture, equipment requirements, organization, operations, testing, access for people with disabilities and non-English speakers, etc.  More detailed information regarding the specific questions the Public Safety and Homeland Security Bureau has asked and the information it is hoping to gain from commenters is available in the FCC’s recent Public Notice, which is available here.

Parties interested in commenting have until May 17th to do so, and Reply Comments are due by June 14th.  Commenters should be sure to reference the subject public notice and EB Docket No. 04-296.  Comments can be filed either via ECFS, the the Federal Government’s eRulemaking Portal, or in paper with the FCC.  Given the impact on broadcasters, we'll continue to follow this issue and report on any changes to the EAS rules as the FCC and FEMA conduct their respective proceedings. 
 

FCC Proposes National Test of EAS - Emergency Alert System; Comments on Proposed Rules due March 1

The FCC has proposed amending its rules governing the Emergency Alert System (EAS) in order to test and improve the effectiveness of the system.  In particular, the Commission has proposed that all EAS participants be required to join in a nationwide test -- to be scheduled by the FCC in consultation with the Federal Emergency Management Agency (FEMA) -- to ensure that the system will function properly to inform the public in the event of a national crisis.  The FCC proposes to implement the national test on a yearly basis and seeks comment on the specific language of the proposed rule.  A copy of the Commission's Notice of Proposed Rule Making (NPRM) was recently published in the Federal Register establishing the deadline for Comments on the proposed rules as March 1, 2010, with Reply Comments due on or before March 30, 2010.

In issuing its NPRM, available here, the Commission acknowledged the shortcomings of the current rules and its belief that a national test -- and the data gathered from such a test -- is critical to ensuring consistency and reliability in a system that has actually never been used to deliver a national Presidential alert.  Under the current system, an EAS message is initiated, which is then passed via specially encoded messages to a broadcast-based transmission network, and then on to broadcast stations, cable operators, and other EAS participants in a daisy-chain distribution to the final end users, i.e., the public who is listening, watching, or reading, on radio, television, cable, or other services.  This daisy-chain structure leaves the system, in the Commission's estimation, vulnerable to a significant failure if the message distribution is severed or delayed at any one point.  By proposing an annual national test, the Commission seeks to test the system in an organized, controlled manner, gather data from the EAS participants, and apply what is learned.  Under the Commission's proposed rule, the annual test would replace one of the required monthly tests and participants would have at least two months advance notice of the nationwide test.  EAS participants would be required to log the test results of the test and provide information on the results to the Commission's Public Safety and Homeland Security Bureau within 30 days of the test.  The Commission seeks input on the proposed rule, including whether once a year is sufficient, and what the costs would be attendant to the testing and reporting.

The NPRM suggests that the following test-related diagnostic information would be provided by the EAS participants for each alert received from each message source monitored at the time of the national test:  (1) whether they received the alert message during the designated test; (2) whether they retransmitted the alert; and (3) if they were not able to receive and/or transmit the alert, their ‘best effort’ diagnostic analysis regarding the cause or causes for such failure.  In addition, the Commission would require participants to provide information regarding the station, date and time of the message and relay, information on the source of the message, and make and model number of they EAS equipment that they utilized.  The Commission proposes to make the information publicly available, but seeks input on whether it would be more appropriate to limit availability to other authorized governmental agencies. 

The final issue the NPRM raises is the fact that different encoder/decoder manufacturers may program their devices to receive and transmit emergency alert notices differently, which could impact the proper relay of an emergency message.  The Commission seeks input on the issue and what costs would be involved or options available to ensure that a legitimate emergency alert notification is passed along the network. 

The Commission has stated that it intends to "move quickly to adopt any and all necessary rule changes to ensure that the Commission and other federal, state, local, and non-governmental EAS stakeholders have the necessary diagnostic tools to evaluate EAS performance and readiness nationwide."  So interested parties should similarly act with alacrity to get comments in by March 1st (or reply comments by March 30th) to inform the Commission's rule making process.  Comments can be submitted in paper or through the FCC's Electronic Comment Filing System

An FCC About Face on a Fine for an EAS Error

The FCC last week did an about face on a fine for a violation of the EAS rules, canceling a fine issued to a broadcaster who had violated the rules and instead issuing only an admonition.  This case resulted when a local primary EAS station, KWVE, one monitored by other stations and cable systems for test messages and alerts, ran the wrong EAS test - running a required monthly test in lieu of the weekly test that was supposed to run.  The problem was compounded when the on-duty operator somehow stopped the test in the middle.  By doing so, the End of Message ("EOM") code was never sent or received, so some stations that were passing through the alert simply continued to run audio from the primary station, including the religious programming that the station featured and a commercial message from that station.  One viewer of a cable system that picked up the test complained to the FCC, and the FCC issued a fine in the amount of $5000 - the fine which was vacated last week.

The initial fine had resulted in criticism from many diverse broadcast groups and associations - including many state broadcast associations and engineering groups.  This station was volunteering to act as the primary station for the area - taking on additional EAS responsibilities to initiate tests and otherwise be responsible for potentially originating and relaying important emergency information.  Here, as a result of an inadvertent error, the station made a one-time mistake.  The protesting groups argued that the Commission's fine set a bad precedent, one which would discourage stations from volunteering for responsibilities under this and possibly under other programs which could benefit the public, if the result was that the stations were subjecting themselves to substantial liability for even the tiniest, inadvertent infractions.  And, of course, this error took place in the course of a test - and what's the purpose of a test but to discover issues with training or execution that need to be corrected in the event of a real emergency.  If everyone was already perfect, you wouldn't need to conduct tests.  The Commission decision this week, to back off the fine and just issue a warning  was seemingly a correct one - and should be applauded. 

FCC Inspections - Fines for Violations of Rules on Main Studio, EAS, and Public File

Last week, the FCC issued several fines to broadcasters for failure to observe some basic FCC rules.  As there many FCC rules to observe, broadcasters should use the misfortune of others who have suffered from these fines as a way to check their own operations to make sure that they meet all of the required Commission standards.  In the recent cases, fines were issued for a variety of violations, including the failure to have a manned main studio, the failure to have a working EAS system, incomplete public files, operations of an AM station at night with daytime power, and the failure to have a locked fence around an AM tower.  This post deals with the issues discovered at the studios of stations - a separate post will deal with the issues at the transmitter sites. 

The main studio rule violation was a case that, while seemingly obvious, also should remind broadcasters of their obligations under the requirement that a station have a manned main studio.  In this case, when the FCC inspectors arrived at the station's main studio, they found it locked and abandoned.  Once they were able to locate a station representative to let them into the studio, they found that there was some equipment in the facility, but it was not hooked up, nor was there any telephone or data line that would permit the station to be controlled from the site.  The Commission's main studio rules require that there be at least two station employees for whom the studio is their principal place of business (I like to think of it as the place where these employees have their desks with the pictures of their kids or their dog, as the case may be, and where they show up in the morning to drink their morning cup of coffee before heading out to do sales, news or whatever their job may be).  At least one of the two employees who report to the studio as their principal place of business must be a management level employee, and at least one of those employees must be present during all normal business hours.  Thus, the studio should never be devoid of human life.  The studio must be able to originate programming, and the station must be able to be controlled from that location so that the employees there could originate programming in the event of a local emergency.  In light of these violations and others, the station in this case was fined $8000.

Another problem identified identified in another case was the lack of a functioning EAS receiver.  The FCC has this week been emphasizing the importance of emergency communications, and one of the principal means of that communication (and, as we wrote here, of demonstrating service to the public in the context of all sorts of FCC proceedings) is the EAS system by which state, local or national officials can communicate with the public in the event of an emergency.  In most states, the EAS system currently works as a daisy chain, with a series of stations monitoring other stations to pass the emergency message down the chain.  All stations are supposed to monitor both a primary and secondary station, so that if they don't get the message from one station, they will get it from the other.  In one of the recent FCC cases, FCC inspectors found that the station had not logged the receipt of any emergency alert system test from either of the stations that the inspected station was supposed to be monitoring and, after being told of the problem, the station still could not receive a test when one was conducted several days later.  I have heard from some FCC inspectors, that this is not an infrequent problem, as the EAS units can be installed improperly, can be damaged by power surges or other problems, or can simply have their receive antennas knocked off the back of the unit when inadvertently jarred.  As a station's Chief Operator is supposed to be signing off on a station's "Station Log" weekly, and the principal thing that is supposed to be recorded in the log is EAS tests (as well as any other technical issue at the station), if the Chief Operator does not notice that the regular EAS test has not been logged, someone is not doing their job.  The log should make someone notice, and problems should be rectified at once.

Another issue turned up by these inspections was with the FCC public file.  In the same case where the EAS issues were discovered, the FCC inspectors discovered that there were missing Quarterly Programs Issues lists in the station's public file.  We've written before about how the failure to have these lists in a public file can lead to fines at license renewal time (probably the most frequent source of license renewal fines), but it can also lead to a fine if the FCC inspector comes knocking.  Our Davis Wright Tremaine Advisory on the Quarterly Programs Issues List (the most recent edition is here, though a new one for October reports should be out very soon), talks about how important these lists are, and provides information on how to complete them.  Check it out, and make sure that your station is in compliance.

Given the variety of issues that can arise during an FCC inspection, and the potential for fines in connection with any violation, stations should review their operations now to avoid issues later. 

FCC Schedules Summit on Status of EAS

The FCC has scheduled a Summit on the Emergency Alert System ("EAS"), to be held on May 19.  The EAS system is the alert system used by broadcasters to pass on emergency information from government officials to their listeners.  EAS replaced the Emergency Broadcast System ("EBS") and was intended to be a more reliable substitute for the system originally adopted during the Cold War to convey a Presidential message about a nuclear attack or similar emergency to the entire country.  Over the years, the system has adapted to include information about local emergencies and "amber alerts" about the kidnapping or disappearance of children.  However, especially since 9-11 and some of the hurricanes in the South, questions have been raised about the effectiveness of the system, and means to make the distribution of emergency information more reliable and efficient have been sought.  The FCC currently has a rulemaking pending to determine ways in which that system can be made more efficient - a question sure to be addressed at the Summit.

In the current proceeding on reforming the EAS system, one of the questions that has been asked is how the system should be activated for non-Federal emergencies.  Obviously, the President can still activate the system for a national emergency, but how alerts about local emergencies are initiated is one of the more controversial issues in the proceeding.  Currently, there is no uniform system.  Instead, each state's system may have different points from which an alert can be initiated.  Concerns have been raised that if the ability to initiate an alert is too broadly distributed, alerts may be initiated haphazardly, and if too many alerts are issued, the system will lose its impact and other important programming may be preempted unnecessarily.  Thus, proposals have been made that the alerts should be initiated only by a state's Governor or his or her specifically designated representative. 

Issues to be discussed at the Summit include how the state and Federal emergency communications systems should interact.  Also to be discussed is how to make the system more reliable.  One issue now is that the system relies on a "daisy-chain" of stations - one station passing on the alert to the next one down the line. Concerns exist as to how the alert will be delivered if an intermediate link in the chain somehow fails.  Satellite connections and other communications technologies are among the considerations - some states having already implemented such systems.

In addition to the broadcast alerts, the Commission has been working to expand the reach of its emergency notification systems into other media.  Quite some time ago, the Commission adopted rules for extending the alert system to satellite-delivered media.  Earlier this month, rules were also adopted to provide emergency alerts to mobile devices.  These developments should be monitored so that communications companies are current on their obligations to delver emergency alerts should the occasion arise.

FCC Releases New EAS Manuals Explaining Obligations for Broadcasters and Video Providers

The FCC's Emergency Alert System ("EAS") is the bane of many broadcasters.  Failing to have operational EAS equipment, or otherwise failing to comply with the requirements of the rules, including failures to conduct the mandatory tests of the system, are among the most common causes of a fine following an FCC field inspection.  To help ensure compliance with the EAS rules, the FCC has issued a series of booklets outlining the EAS obligations not only for broadcasters, but also for cable systems, satellite radio and wireline video providers.  These booklets can be found here.  As the FCC rules require that these booklets be maintained at the location of normal duty operator for a station or systems, all media companies that are subject to the EAS rules should download and post the appropriate booklet at their control points.

The new booklets cover new requirements imposed on broadcasters in connection with their digital operations.  These operations, along with services provided by satellite radio and telephone company video providers, were only recently made subject to the EAS rules (see our post here).  These booklets provide the first full summary by the FCC of the application of the rules to these services.  Thus, operators need to be sure to not only print out and post these booklets, but read them carefully to make sure that their operations are in full compliance.  Do it today! 

(Update - 12/11/2007 - the FCC today issued an order upholding a fine of $8000 to a cable operator who had EAS equipment that was not installed at the time of an FCC inspection.  This demonstrates how costly EAS violations can be)

Comment Dates Set in Rulemaking on Emergency Alert System

The Commission’s Further Notice of Proposed Rulemaking (“Further NPRM”) regarding the next generation Emergency Alert System (“EAS”) has been published in the Federal Register, setting the date for Comments as December 3, 2007 and the date for Reply Comments as December 17, 2007.  This summer, the Commission adopted a Report and Order extending its EAS Rules to wireless services, and adjusting the rules to better serve the needs of persons with disabilities and non-English speakers.  The Report and Order also expanded the base of EAS participants, included state-level and geographically targeted EAS alerts, and improved coordination with state and local governments.  A copy of the FCC’s Report and Order and the Further NPRM can be obtained here

The Further NPRM raises additional questions regarding how the EAS rules can be adjusted to ensure that non-English speakers and persons with disabilities are reached by EAS messages.  In addition, the Further NPRM seeks input regarding whether local, county, tribal, or other state governmental entities be allowed to initiate mandatory state and local alerts, and if so, what standards or requirements be imposed in initiating an EAS message.  Finally, the rulemaking seeks comment on options for ensuring that the EAS operates as designed in an emergency, and posits several options for measuring performance.  Comments can be filed with the Commission in paper or electronically via ECFS, and should refer to EB Docket No. 04-296. 

Fine For EAS Violation - Financial Hardship Not Enough to Merit a Reduction

As we're approaching the anniversary of September 11, it may be appropriate that the FCC issued an order on Friday upholding a fine imposed on a radio station that did not have an operating EAS system.  The station, while it had a system in place that was capable of transmitting the required EAS tones, had not received any EAS alerts for about a year, and had not entered any reasons for that failure in its station log at any time during the period.  The FCC initially issued an $8000 fine, but reduced the fine to $6400 based on a showing that the station did not have any history of past violations.  However, even though the station was operating at reduced power for a significant period of time due to towers damaged by a storm, the FCC refused to reduce the fine further based on financial hardship as the fine did not exceed 2% of the station's average gross revenue during the previous three years.

The FCC will reduce fines for a variety of reasons - the most common being the past good record of the station.  In most cases, as here, a showing that the station has not previously been fined will be sufficient to demonstrate the past compliance of the station and justify some reduction in the amount of the fine.  Stations also often plead that they cannot afford to pay a fine.  The 2% of gross revenue standard announced by the Commission in this case seems to set the threshold at which the Commission will consider that plea.  To prove that a reduction of a fine is in order, according to this case, a station needs to submit financial statements showing the past three years performance, and demonstrating that the proposed fine will exceed 2% of the station's average gross revenues.

The case also reminds stations to conduct the required tests of the EAS system, and to be sure to check their EAS equipment to make sure it has noted the receipt of the monthly EAS test that it is supposed to receive from the primary EAS stations that it is supposed to be monitoring.  If no test has been received in a month, an investigation should be conducted as to why the test was not received, and notations to that effect placed in the station log.  The FCC noted in this case that, had the station been checking for the required monthly tests, it would have noted the problems with its equipment long before the FCC inspection.  As EAS violations are consistently listed as among the most common violations by broadcast stations, the station's Chief Operator, who should be regularly reviewing the log and otherwise ensuring the station's technical compliance, should be reminded to check EAS test reception as one of his or her principal duties.  It will save the station from having to pay the FCC should one of its inspectors be the one to discover the problem.