›› Home ›› Legislative

Emergency Alert System Issues

The U.S. government created the Emergency Alert System (EAS) to be a means for the President to communicate with the public in times of a national emergency. The EAS is also used locally by broadcasters and others to inform citizens of local or regional emergencies including those that are weather related. Many members of the SBE have responsibilities to maintain EAS equipment at their stations. Through the SBE EAS Education Committee, the SBE seeks to provide information to our members that will help them implement, maintain and operate the EAS systems they are responsible for. The SBE also serves as a resource of expertise to the broadcasting community and the FCC on EAS-related matters.

Email Scott Mason
SBE EAS Education Committee Chairman

EAS Exchange

An SBE-sponsored email discussion group about the EAS

 

FCC releases nationwide EAS test final report
An update by SBE EAS Education Committee chair, Scott Mason, CPBE, CBNT

April 18, 2013
Within the last week, the FCC released the document, "Strengthening the Emergency Alert System (EAS): Lessons Learned from the Nationwide EAS Test." This is basically the FCC's report card to the public on the results of the nationwide test, held on November 9, 2011.

The document summarizes the lessons learned from the test and the Bureau's recommendations for strengthening the EAS. While the overall tone of the document is one of praise, it does point out numerous areas that are not acceptable. The areas included:

  • Widespread poor audio quality nationwide
  • Lack of a PEP in an area to provide a direct connection to FEMA
  • Use of alternatives to PEP-based EAN distribution
  • The inability of some EAS participants to either receive or transmit the EAN
  • Short test length
  • Anomalies in EAS equipment programming and operation

The 19 page document closes with the FCC declaring the test a success, with several areas in need of improvement. It should also be noted that every station was required by the FCC to turn in the results of their test in a specified time frame. The commission did not mention any type of fine structure for those that did not turn in the results; however these fines can still be issued. If you did not submit your results, think of the old saying, "Better late, than never."

Here is a copy of the FCC report.

Scott Mason CPBE, CBNT is Director of Engineering, West Coast for CBS Radio and is a member of the national SBE Board of Directors.

Movie Trailer includes EAS Alert Tones

March 7, 2013 - This is an advisory that a new movie, Olympus Has Fallen, to be released on March 22, 2013, uses actual EAS tones in the movie trailer. If the trailer is used in radio or TV advertisements, the stations may be subject to FCC fine. 


Click on the link to see the trailer.      http://www.youtube.com/watch?v=TVZrlJQm1G4

 

EAS Device Hacked in Montana

I’m pretty sure by now you are all aware of the EAS device that was hacked in Montana.  The broadcast community has done a good job letting station management know of this event.  Many manufacturers and state broadcaster associations have already put out guidelines. Most of the suggested guidelines are simple. You may already know some of these things but we thought it a good idea to summarize them for those catching up on this.

  • Make sure you have changed all passwords, user and admin, to a strong password

  • This equipment should not be hanging out on the public Internet. It should be protected by a firewall and limit access via the Firewall

  • Regularly check your EAS units to assure your settings are where they are supposed to be

This may just be the beginning, now that nearly everything we do is digital and/or on the net. Make sure you’re transmitter and studio are protected.

Scott Mason, CPBE, CBNT, SBE EAS Education Committee Chairman

 

Sage Alerting System Releases IPAWS Support Filmware

By Scott Mason, CPBE, CBNT, SBE EAS Education Committee Chairman

June 12, 2012

Sage Alerting Systems has posted a message on their site saying:


We plan to release the IPAWS support firmware before 1:00pm EDT today. This is, as always, subject to a little drift.


• This web site is a finite resource. If everyone tries to download at 1:00pm, it won't be pretty.
• Our support lines are a finite resource as well. If you need to call us, and you get voice mail, leave a message. Don't try to call back later, assuming we'll answer the phone then. Leave a message, and we'll return your call in the order we received it. Don't try the sales or business office extensions, they can't call support either if the lines are busy.
• Please read and follow the steps in the release notes carefully. If you haven't tried to add an IPAWS server by hand, and if your ENDEC is able to sync up to a network time source, the install will go very well. If you have tried to get the ENDEC to poll IPAWS by using instructions from a source other than Sage, you will have problems. Those CAP server entries, with things like "ipaws", or "http" or "https" followed by anything, won't work, and will result in a "CAP offline" message. If you can access your ENDEC, you might want to do a little prep work, remove those servers, and upload the settings before you upload the firmware. This is especially true if you used the ENDECSetd included in release 74-2, and built a CAP server with a type of "IPAWS OPEN" and an incorrect URL. Keep any server that is currently working for you, this includes any MyState server or GSS satellite server.


The other EAS encoder manufactures also have information available.

Scott Mason, CPBE, CBNT

 

Sample SECC Plan

May 21, 2012

The Broadcast Warning Working Group (BWWG) and invited stakeholders met during the 2012 NAB Show and held a State Emergency Communications Committee (SECC) plan writing workshop. The group produced a sample state plan document (v4.0) that is posted on the EAS FORUM website. If you have any questions or suggestions about the sample plan, contact the BWWG through their website, http://eas.radiolists.net.

 

Update on EAS Developments

By Scott Mason, CPBE, CBNT, SBE EAS Education Committee Chairman

March 26, 2012

Just when you thought it was a little quiet in EAS land, you see your tickler note that the FCC’s Fifth Report and Order becomes effective in less than a month. From most broadcasters I have spoken with or interviewed, it seems like we are pretty well buttoned up.

Let’s recap the highlights, or should I say highlight, CAP.

  • You must be able to receive a CAP message at your station and convert it to comply with EAS protocol requirements.
  • You must be able to monitor CAP. You can do this direct or through an intermediate device.
  • If you’re working in TV, you must be able to use the enhanced text in the CAP message to meet the video display requirements.

Alas, you do still have a little breathing room as the requirement to install the equipment isn’t effective until June 30.

The FCC needs to let broadcast stations know what the IP address of the concentrator they want stations to monitor. Broadcasters were told this IP address would be available many weeks ago.  While most of us have had this equipment installed and working for a while now, it’s not really tested with CAP... I foresee numerous rounds of CAP testing once the concentrator IP addresses are released.

 

FCC Fifth Report & Order EB Docket 04-296

On January 10, 2012, the FCC released its Fifth Report and Order on EB Docket 04-296 regarding the Emergency Alert System. The report implements CAP into the EAS rules and revises the Part 11 Rules.

Gary Timm, an SBE member and consultant for Touchstone Consulting Group, published a list of highlights from the order in the Touchstone website newsletter, AWARE. They are reprinted here, with permission.

  • Amends section 11.55 of the Commission’s rules to eliminate the requirement that EAS Participants receive and transmit CAP-formatted messages initiated by state governors.
  • EAS Participants are permitted to use intermediary devices to meet their CAP-related obligations, provided that all intermediary devices must provide that capability of utilizing the enhanced text in a CAP message to meet the visual display requirements in section 11.51(d), (g)(3), (h)(3), and (j)(2) of the Commission’s rules, as set forth in section 3.6 of the ECIG Implementation Guide, by June 30, 2015.
  • The EAS CAP Industry Group (ECIG) Implementation Guide (I.G.) is accepted as the method to convert CAP-formatted messages into legacy EAS format, and incorporates the ECIG I.G. into the Commission’s existing certification scheme.
  • EAS Participants are required to monitor FEMA’s Integrated Public Alert and Warning System (IPAWS) for federal CAP-formatted alert messages.
  • Further on the IPAWS monitoring requirement, the R&O clarifies that it would be inappropriate to adopt any form of blanket exemption from the basic obligations of monitoring for, receiving, and processing CAP-formatted messages, but concludes that the physical unavailability of broadband Internet service offers a presumption in favor of a waiver.
  • The Non-Participating National (NN) EAS Station Designation is eliminated.
  • Action is deferred on revising the EAS Operating Handbook until after results of the November 9, 2011 Nationwide EAS Test are analyzed.
  • Revises section 11.32(a)(9)(iv) of the Commission’s rules to limit the duration of the Attention Signal to no more than eight seconds.

Click here for the complete EB 04-296 R&O.

 

SBE Statement Following the National EAS Test

November 10, 2011

Following the Nov. 9, 2011 national EAS test, it's obvious there were some problems. While some stations passed a complete test message, other stations did not. Though it appeared most broadcast station EAS equipment worked as expected, portions of the audio had problems nationwide.

 

Damon Penn, assistant administrator of National Continuity Programs at FEMA wrote the following on the FEMA Blog at 6:30 p.m. ET, four and a half hours after the test. "This nationwide test served the purpose for which it was intended - 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."

The SBE has noted the high volume of messages on its SBE Exchange - EAS discussion list, regarding the test. SBE EAS Education Chair, Scott Mason, CPBE, CBNT said, "The SBE will continue to provide educational support on EAS to our members and technical guidance to the FCC and FEMA, to provide a higher success rate for the future." 

FCC Extends CAP Deadline

September 16, 2011

The FCC announced today that they have extended the deadline for broadcast stations to have their Emergency Alert System equipment be CAP compliant to June 30, 2012. The deadline had been set for September 30, 2011.

The FCC said, “In this Fourth Report and Order, we have revised the rules to extend the date by which EAS Participants must be able to receive CAP-formatted EAS alert to June 30, 2012.”

The FCC explained that more time is needed to revise Part 11 of the FCC Rules so that it cannot impose a deadline by which EAS participants must receive CAP-formatted alerts.

View the full text of the Fourth Report and Order.

 

EAS UPDATE:

July 31, 2011

FCC Rule changes are under way and many questions are being addressed through normal FCC processes.  The FCC Released a Third Further Notice of Proposed Rulemaking on May 26, 2011 under EB Docket 04-296 which outlines ways that new requirements will be addressed and requests comment on the important issues surrounding the new EAS requirements.  The SBE recommends station ownership and EAS stakeholders participate in this process.  The SBE is working closely with FEMA and others to provide accurate and reliable EAS education and information for members and the industry to help foster compliance with the deadline whenever it occurs.

Comments on the NPRM were due to the FCC July 20, 2011, however reply comments can be filed until August 4, 2011.  Submit comments using the FCC ECFS system.  View previously filed comments on this docket here and enter proceeding number 04-296.

Please see the list of FAQs about the EAS below.

 

FCC Third FNPRM on EAS Published in Federal Register; Comments Due July 20

June 22, 2011

The FCC Third Further Notice of Proposed Rulemaking was published in the Federal Register June 20, starting the clock for the Comment and Reply Comment Periods.  Comments must be submitted by July 20, 2011 and Reply Comments are due by August 4, 2011.

 

Notes and Best Practices from June 9 FEMA Virtual Roundtable

June 9, 2011

PDF of notes from the roundtable provided by FEMA.

 

National EAS Test Set for November 9

June 9, 2011

Rear Admiral James Barnett, Jr., Chief, Public Safety and Homeland Security Bureau, Federal Communications Commission, today announced that the National Emergency Alert System (EAS) Test will take place November 9, 2011 at 2pm EST. The announcement was made during today's regularly scheduled FCC Meeting.  

"With the date of the National EAS Test now set, broadcast stations will now be able to make their plans to participate. SBE will continue to provide information to our members to assist in their preparation," said SBE President, Vinny Lopez, CEV, CBNT.

 

FCC releases Third Report and Order on national EAS test

February 4, 2011

The FCC released on February 3, a Third Report and Order amending FCC Part 11 rules governing the Emergency Alert System (EAS), to provide for national testing and the collection of data from those tests.

Elements of the FCC national test requirements include:

· Require all EAS Participants to participate in national EAS tests as scheduled by the Federal Communications Commission (Commission) in consultation with the Federal Emergency Management Agency (FEMA);

· Require that the first national EAS test use the Emergency Alert Notification (EAN), the live event code for nationwide Presidential alerts;

· Require that the national test replace the monthly and weekly EAS tests in the month and week in which it is held;

· Require the Public Safety and Homeland Security Bureau (Bureau) to provide at least two months’ public notice prior to any national test of the EAS;

· Require EAS Participants to submit test-related data to the Bureau within 45 days following a national EAS test;

· Require that test data received from EAS Participants be treated as presumptively confidential, but allow test data to be shared on a confidential basis with other Federal agencies and state governmental emergency management agencies that have confidentiality protection at least equal to that provided by the Freedom of Information Act (FOIA); and

· Delegate authority to the Public Safety and Homeland Security Bureau to determine, in

consultation with FEMA and with other EAS stakeholders, as appropriate, various administrative procedures for national tests, including location codes to be used and pre-test outreach.

Damon Penn, Assistant Administrator of the National Continuity Programs (NCP) Directorate, Federal Emergency Management Agency, when asked when he expected the first national test to take place, said, “this fall.” Penn was a panelist on a live EAS webinar sponsored by the National Alliance of State Broadcasters Associations and the NAB, held on February 3.

 

The complete Third Report and Order is available here.

 

FCC Extends EAS compliance deadline to Sept. 30, 2011

November 24, 2010  

The FCC has agreed with the SBE, NAB, MSTV and almost all state broadcaster associations that the 180-day EAS deadline should be extended.  On November 28, 2010, the FCC announced that the deadline will be extended from 180 days to 360 days, effectively making the new deadline, September 30, 2011.  The FCC action was officially taken on November 18.

SBE President, Vinny Lopez, CEV, CBNT, upon hearing the announcement said, "The FCC took an important step toward establishing an effective and orderly improvement of the US' public warning strategy.  The SBE and its EAS-experienced members intend to work to support our industry and the FCC to improve the EAS.  As the system changes, the SBE will be publishing information and education to help our members and the industry incorporate the changes in a cost-efficient and effective way."

The FCC considered multiple factors cited in industry filings in approving the extension, including the need for more time for the development, testing and potential certification of the new equipment and the costs associated with purchasing the CAP-compliant equipments by EAS participants.

 

FAQ on EAS

July 31, 2011

On September 30, 2010, the Federal Emergency Management Agency (FEMA) announced the adoption of major changes to the Emergency Alert System (EAS), incorporating a new digital messaging format, the Common Alerting Protocol (CAP). Broadcasters would have 180 days from the date of the announcement to comply with the new requirements, however, the FCC extended this another 180 days, for a new deadline of compliance of September 30, 2011.

The announcement has prompted many questions from our members.  Some of the more frequently asked questions are addressed below.

Q1. What does this mean to me?

A. You have until September 30, 2011 to comply with these new standards.  This will mean purchasing new equipment.

Q2. Why didn’t the SBE join the joint July 29, 2011 Industry filing with NAB, state broadcasters and others, asking for another extension of the CAP compliance deadline?

A. The SBE Board of Directors established a policy in October 2010 regarding its role in the Emergency Alert System that, going forward, the organization would refine its focus on educating our members about the changes to EAS and the implementation of those changes.  The question of further extending the CAP compliance deadline is an important one; one that we feel is best led by those stakeholders who represent station ownership and management. The SBE will continue to communicate and provide educational opportunities to members about changes to EAS, directly and through our strategic alliances.

Q3. Has the compliance deadline "clock" started?

A. Yes.  According to FEMA and the FCC, stations must be compliant with the NPRM on or before 9/30/2011. 

 

Q4. What is THE MINUMUM required for stations to comply?

A. At the very minimum, stations must be able to receive and decode messages delivered using the CAP data protocol. 

Q5. What is the RECOMMENDED way for stations to comply?

A. Stations should be prepared to incorporate emergency messages delivered by the CAP protocol into their EAS systems, logging and plans.  Meaning that your EAS Box should either be capable of receiving and reacting to CAP messages, or there should be some device that can be added to your current EAS boxes to inject messages delivered using CAP into it; and the EAS Box should react appropriately.

Q6. How will that be done?

A. Stations will need to have a device or system capable of receiving messages using the CAP protocol.  At this time most EAS equipment manufacturers can either provide or are in the process of developing devices to decode CAP; some even with the capability to incorporate the CAP messages into a station's EAS capabilities, although that integration is not part of this specific ruling.

Receiving CAP messages in your plant may simply be a matter of having a computer that can receive and decode the message.  For example, The National Weather Service is currently using CAP and their messages can be decoded using the NWS' ATOM feed: http://www.weather.gov/alerts-beta/#cap

Q7. How is CAP different?

A. CAP messages can contain not just data, like the SAME protocol broadcasters are familiar with, but also audio, video, text...all sorts of information.

Q8. How will the changes affect the "duck quacks" (meaning the EAS SAME tones) stations are using now?

A. Nothing changes with what stations must send or even EAS....yet.  In fact, we expect the current EAS system; the "daisy chain", will not be changed, but a separate, CAP-capable data distribution system will likely be added to your EAS plan.

There will need to be an approved "translation" of messages carried using extensive CAP protocol into the EAS SAME protocol "language".  A digital Rosetta Stone, if you will. This is referred to as the CAP/EAS "profile" and has not been officially agreed upon.

Q9. From Where will stations get CAP messages?

A. This is one of the questions that have not been resolved.  CAP messages will be delivered over a data path of some sort.  Current indications are that the delivery method will use the public Internet in some way.    This is actually one of the many unresolved issues and potential problems stations and state emergency officials will need to solve.

Current plans indicate that transmission from FEMA to broadcasters will be by means of the existing IPAWS (Integrated Public Alert and Warning System, http://www.fema.gov/emergency/ipaws/ ) SOAP interface using the IPAWS-OPEN (Open Platform for Emergency Networks, http://www.fema.gov/emergency/ipaws/projects.shtm#6) as an aggregator.

We understand that "IPAWS-OPEN" will be available for testing by a limited group of originators not later than February 28, 2011.  There will be no accountability for IPAWS alerts to EAS.  Originator credentials will be issued to organizations and shared among their staff.  FEMA will be the issuer, but the procedure for issuing credentials is undefined at this time

Q10. What information is available about CAP?

A. Here's a really good wiki on CAP developments:

http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook

Q11. What about messages from the Governor?

A. The FCC Part 11 rules require state governors, or someone he or she designates, to be able to have his or her message aired on all participating stations. Most broadcasters understand that the purpose of EAS is, ultimately, to provide a means for the President to speak to the entire United States at once using the EAS as the means of delivery.  Although the EAS has never been used for this purpose, that same capability is now required to allow governors to speak to the citizens of their states.

Q12. We can do that now, right?

A. Not exactly.  Where this relates to the current change is that CAP provides the means where such a message can be sent.  Remember CAP can carry audio and video messages as well as the text of a message.  The rule confers a similar access to the airwaves to Governors, that was held only by the President.  There are a whole host of issues that state emergency officials will need to address like security, authentication, distribution methods, etc.   

Q13. What hasn't been determined yet?

A. An almost innumerable list of issues.  Such as:

  • What will stations need to do when they receive CAP messages?
  • What sources do my stations monitor for CAP messages?
  • How will CAP messages be logged?
  • What will be the approved mapping of codes from a CAP-delivered emergency message to an EAS message (will the EAN code mean the same thing in CAP as EAS?)?
  • How will stations actually receive their CAP messages?
  • If the cap messages will be sent using the public Internet, what about stations that cannot get an Internet connection?
  • What security measures will be used so that hackers won't be able to take control of broadcast stations and emergency networks?
  • How can governors send their messages to stations?
  • How will state plans be changed?
  • What data codes will be used so that EAS boxes know that a message is coming from a governor AND that it is a "must air" message like an EAN?

Q14. What do you suggest we do?

A. We recommend that you contact your equipment suppliers and familiarize yourself with the options available.  Assuming your stations are in compliance with your state's EAS Plan, you should be planning to essentially add a new monitoring source... one that will include CAP emergency messages, to your current assignments.  We expect the current EAS system - the "daisy chain", will not be changed, but a separate CAP-capable data distribution system will be added to your EAS plan.

If you decide to purchase equipment now, we advise that the equipment be field-upgradable by software, flash, or other means to comply with the many upcoming rule changes.

While we suggest you educate yourself and be cautious, we also suggest you avoid waiting until the last minute, or you will likely be facing the logistical problems caused by manufacturers that will be trying to supply new equipment to thousands of radio and television stations, cable and satellite head-ends, all at once. DO NOT ASSUME THE DEADLINE WILL BE EXTENDED AGAIN!  Although there are groups seeking to extend the deadline until FCC Part 11 rules are changed and equipment can be certified to be in compliance, we feel it would be unwise to rely that an extension will be granted without fully understanding the circumstances and preparing an alternate, if temporary, method of complying with the current law.

Q15. When will the National EAS Test take place?

A. The National EAS Test will be held on November 9, 2011, at 2 p.m.

*** A FREE SBE webinar, originally presented on August 19, 2010 is available online. Click here for more details.  A second SBE webinar about EAS developments will be held when more information is available. 

If you have questions you'd like to see included in this FAQ and in upcoming webinars, please send your questions to: Ralph Beaver, SBE EAS Education Committee Chairman.

The SBE operates an ongoing conversation about EAS.  Members and guests are invited to join the SBE EAS Exchange email discussion list.  Also, EAS is one of many topics discussed on the SBE Roundtable.  Information on joining either of these discussion groups is at www.sbe.org

 

Recap - SBE EAS Meeting

April 20, 2010

The meeting was held at the 2010 NAB Show in Las Vegas, N.V. on Monday, April 12, 2010 at the Las Vegas Hilton Hotel

The Society of Broadcast Engineers hosted an interesting slate of technical presenters this year for its annual SBE EAS Meeting. SBE EAS Committee Chairman, Ralph Beaver opened the meeting and introduced SBE EAS Committee member, Gary Timm, who moderated the program. Gary's Meeting Outline and EAS/CAP Update.

The first session was titled: “Recent Developments in Alert Aggregation and Dissemination Technologies: How We Think it’s Really Going to Work(may take 30 seconds or more to download). The session was presented by two engineers and a systems architect working with the FEMA IPAWS Program; Al Kenyon, Senior Technical Analyst, Rod Cash, Systems Engineer and Gary Ham, Eye Street Software Corporation. IPAWS, the Integrated Public Alert and Warning System, will be the vehicle for aggregating and disseminating messages for the new EAS CAP alerting system.  This was an interesting insight into how that work is progressing. More information is available about the speakers, Al Kenyon, Rod Cash and Gary Ham.

The second session was presented by ECIG, the EAS-CAP Industry Group.  ECIG is a broad coalition of equipment, software and service providers to the Emergency Alert System.  This is an organization made up of most of the EAS/CAP equipment manufacturers.  Members of the ECIG Board of Directors told us about their organization and its progress on drafting a CAP-to-EAS Implementation Guide as a recommendation to the FEMA IPAWS Program.

The closing session was an open discussion among the meeting attendees and all of the presenters. 

 

FEMA Estimates CAP adoption date

April 14, 2010

According to a statement by DHS Assistant Administrator Damon Penn on April 14, 2010, FEMA estimates that its CAP adoption date, which would start the 180-day clock for broadcasters to buy CAP equipment, will be, "September of 2010”.

 

What is the Integrated Public Alert and Warning System (IPAWS)?

April 13, 2010

Click here to link to the FEMA website page that explains IPAWS.

 

NAB Report from March 30, 2009 EAS Summit - FM radio in cell phones

April 1, 2009

This report is not endorsed nor the policy of the SBE. Provided for informational purposes only.

 

The evolution of the SBE EAS - CAP Roadmap

By Clay Freinwald November 24, 2008

In conjunction with an FCC EAS Summit in Washington, DC, in May of 2008, the Society of Broadcast Engineers (SBE) released a document titled, "A Strategy for Implementing CAP EAS".  It outlined the steps that the SBE saw as needing to be accomplished in order to implement Common Alerting Protocol (CAP) for EAS.  The SBE document divided the tasks among six proposed Working Groups (WG): EAS CAP Profile WG, EAS CAP Distribution Network WG, EAS CAP On-Air Presentation WG, EAS CAP Training WG, EAS CAP Equipment WG, and EAS CAP FCC Rules/FEMA Directives Study WG.

Shortly thereafter, this SBE document was adopted by a newly-formed group called the EAS CAP Roadmap Coordinating Committee, of which the SBE is a member.  This group further refined the SBE document, now known as "The EAS CAP Roadmap", and is now moving forward with staffing the Working Groups and addressing the identified tasks.  The following is current version of The EAS CAP Roadmap.  

 

Strategy for Implementing CAP EAS

November 2008

The SBE's suggestions to aid implementation of CAP technology for a revised Emergency Alert System

 

SBE's Interpretation of New EAS Rules

August 2007

 

Common Alerting Protocol information

July 2007

Now available are four podcast files that make up the SBE EAS Meeting held on Monday, April 16, 2007 in Las Vegas during the 2007NAB Show. Each file is large in size, and may take signifigant time to download. Additional information about the Common Alerting Protocol is available here.

Click here to listen to Part 1

Click here to listen to Part 2

Click here to listen to Part 3

Click here to listen to Part 4

Click this link to hear an archived recording of the SBE EAS Meeting. Our thanks to Broadcast.net, Tieline and Trilithic for their support which made the live streaming and archive of the meeting possible.

 

FCC Acts on EAS Issues

November 2005

 

Emergency Alert System, EAS WA State Info

Self-Inspection Checklist for Broadcasters and Cable System Operators - Procedures (November 2000)

Emergency Alert System Self-Inspection Checklist for Broadcasters and Cable Systems- EAS Sample Log (November 2000)