EAN Updates

Back Home

Assignments

Corrections and updates
for Broadcast assignments
can be made by notifying
your State EAS Broadcast Co-Chairmen:
Roger Herring rherring@ktul.com
Britt Lockhart
 BrittLockhart@clearchannel.com.

Cable Assignments should
be directed to State EAS
Cable Chairman:
Looking for a volunteer!

 

 Here's what you need to do now, prior to the test
  • Download a special EAS Handbook from the FCC, specifically and only for this EAN test.  You'll still need your current EAS Handbook after this test.
  • There are 3 forms to fill out.  The first form is to be completed PRIOR TO the Nov. 9 EAN test.
  • If you are a TV or Cable system, take action to prepare a visual TEST background.  The EAN is an actual alert.  
    • The EAN will not say test in the video unless you add a TEST background.  Examples are here.
  • Check your monitoring sources.  Confirm you hear the stations you should be monitoring.
    • My database on the web is currently not functioning.  Bad timing I know, so email me here to confirm your assignments.
  • The FCC “Handbook for November 9, 2011 Nationwide EAS Test” says on Page 4 that NN stations must participate in the test. Step 8 of the procedure on Page 16 states that NN sources must “discontinue programming” during the nationwide test. 
    • So if you are a NN, Non-participating National,  you may wish to consult your communications attorney for an interpretation of this one. 
    • NN sources that wish to change their EAS Designation to Participating National (PN) should contact the FCC.
    • If you are not sure whether you are Participating or Non-Participating, again, you may email me, or check your broadcast licnese.


EAN reports due by Broadcasters to the FCC

The first-ever initiation of a national EAS test will be held on Nov. 9, 2011, for ~three minutes.

Subsequent to the test, the Commission is requiring all participants to submit a report by Dec. 24, 2011,

which must include the following information:
  •  Whether you received the alert message during the designated test;
  •  Whether you retransmitted the alert;
  •  If you were not able to receive and/or transmit the alert, your "best effort" diagnostic analysis regarding the cause(s) for such failure; 
  •  A description of station identification and level of designation (PEP, LP-1, etc.); 
  •  The date and time of:
  • Receipt of the EAN message by all stations;
  • PEP station acknowledgement of receipt of the EAN message to FEMA;
  • Initiation of actual broadcast of the Presidential message;
  • Receipt of the EAT message by all stations
  • Who you were monitoring at the time of the test
  • Make and model number of the EAS equipment you utilized.

The Commission will not use the information against any participant in an enforcement action or other proceeding, but will be analyzing the information to determine the necessary steps to improve the process. At this point, the reports must be submitted on paper, but an electronic version of the report may be ready for use by the deadline.




SBE FAQ on EAS

Society of Broadcast Engineers FAQ


From TV TechCheck, October 4, 2010

FEMA Announces Adoption of Common Alerting Protocol (CAP)

 On Thursday September 30, the Department of Homeland Security's Federal Emergency Management Agency (FEMA) published a press release announcing its adoption of the Common Alerting Protocol (CAP) v1.2 standard as the digital message format for the Integrated Public Alert and Warning System (IPAWS). IPAWS incorporates and expands upon the traditional Emergency Alert System (EAS) supported by free over-the-air radio and TV broadcasters, and was being discussed by FEMA at their exhibit at the NAB Radio Show held this week in Washington, D.C. (see photo – shown here is Alfred Kenyon, Project Manager, IPAWS Program Office, National Continuity Programs).

CAP is a data interchange protocol developed by the emergency management community and is used to distribute all-hazard safety notifications and emergency warning information. CAP is described in a technical standard published by the Organization for the Advancement of Structured Information Standards (OASIS) and can be found at www.oasis-open.org/.

In the EAS Second Report and Order, released in July 2007 http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.pdf, the FCC mandated that all EAS participants must be able to receive CAP formatted EAS alerts no later than 180 days after FEMA publishes the technical standards and requirements for FEMA-generated alerts. Thus, by section 11.56 of the FCC’s rules (47 CFR 11.56) the 180-day clock started on Friday, October 1, 2010. However NAB, some equipment manufacturers and others have asked the FCC to extend this time frame and it is expected that they will consider doing so in the very near future.

In order to assist in evaluating new alert and warning systems, FEMA is conducting an assessment program to ensure equipment adheres to the IPAWS CAP profile. A list of pre-screened products that meet the profile will be published at the FEMA Responders Knowledge Base, to aide federal, state, territorial, tribal and local officials in purchasing emergency alert products that comply with IPAWS CAP. Vendors can apply for these assessments at www.nimssc.org/ipawsconform.

The three documents defining the FEMA IPAWS technical standards and requirements for CAP and its implementation are:
(1) OASIS CAP Standard v1.2;
(2) IPAWS Specification to the CAP Standard (CAP v1.2 IPAWS USA Profile v1.0); and,
(3) CAP-EAS Implementation Guide.

The CAP-EAS Implementation Guide can be found on the website of the EAS-CAP Industry Group. The full FEMA press release is available online at www.fema.gov/news/newsrelease.fema?id=52880.


Posted on September 30, 2010 by Brendan Holland at Broadcast Law Blog

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. 


From: Radio World:  Alerting Q&A: Harold Price, October 12, 2010With so many questions bouncing around about the implications for stations of the new CAP standard, Radio World is asking industry alerting leaders to provide their perspectives in a series of Q&As. Here we talk to Harold Price, president of equipment maker Sage Alerting Systems.
RW: Now that the EAS/CAP “shot clock” has been started, what question are you getting most from radio station engineers and managers, and what are you telling them?
Price: The most common question is pricing for our new unit. Some ask if there is a software upgrade for our legacy unit, almost all realize CAP is associated with getting data on a LAN, so they aren’t surprised to hear that new hardware is required.
RW: Is there enough information available from federal regulators for stations to know what they need to do? Or are stations hung up until the FCC puts out more specific rules?
Price: The simple answer is that the clock has started, so stations know they need equipment that is able to receive CAP messages in the next 180 days. While the FCC *may* put out new rules, they aren’t required to do so by the current rules.
As a practical matter, however, there are two groups of issues: the CAP protocol itself, and how a station will receive CAP messages.  The CAP protocol and IPAWS profile are now complete. There are two minor clarifications needed in the Implementation Guide, neither directly visible to a station.  As for delivery of messages, FEMA has not yet published specific instructions on how to get messages from its CAP server (IPAWS OPEN). Vendors will probably need to issue a software update in the future to handle this. All users, no matter which vendor they chose, should anticipate at least one software update before CAP is in regular use. While FEMA has not given specific details for IPAWS OPEN, the mechanism to be used is known, and falls under the umbrella of “web services.”
In many cases, however, CAP messages will also come from the states. Several states have already deployed, or are deploying now, state servers. Washington State and MyStateUSA is a good example of this. Other areas are using GSSNET. In those cases, the specifics are currently known. Those states can provide the information needed by stations to access state messages.
RW: What’s happening behind the scenes regarding discussion of audio encoding, and why does it matter?
Price: One of the minor clarifications mentioned above has to do with audio encoding, that is, formats, compression types, number of channels, sample rates, etc. It is important for originators of messages to know what formats are supported by CAP broadcast equipment, and for CAP broadcast equipment to know what formats it is required to handle. One area of the specifications can be interpreted in two different ways, that only two specific formats are allowed, or that any possible format is allowed, including formats yet to be developed. A change is needed to specifically state the specific formats that are allowed.
RW: Should radio stations act now to comply with CAP V1.2? Or wait? Why?
Price: Radio stations can proceed with ordering equipment from the vendor of their choice now, if that vendor has pledged to provide a free software upgrade to match the final version of CAP 1.2. Most have. If you need equipment, are building a new studio, drying out after a flood, looking at a costly repair for 15 year old equipment, make sure you buy a CAP ready device. There is no reason to wait.
Operationally, don’t expect to be able to hook up to a CAP server this week, except in some states. While the broadcasters are building up infrastructure to receive CAP alerts, others are building up infrastructure to send alerts. The goal is to all meet up near the end of the 180 day clock. FEMA has said that they will be able send national alerts before the end of the clock. States can send alerts, and you are required to be able to receive them by the end of the clock, but there is no requirement that the state be able to send CAP alerts by the end of the clock.

Stay tuned for updates. Stay in contact with your local EAS coordinating groups, and State Emergency Communications Committee as they work on the new state plans.


From: Radiomagonline.com,

EAS/CAP FAQ

Oct 8, 2010 1:00 PM, By Barry Thomas, CPBE CBNT, with Chriss Scherer, editor

Now that FEMA has adopted the CAP1.2 standard, broadcasters are asking questions about the 180-day deadline to install equipment and updates to the EAS rules. Those heavily involved with EAS note that it is not easy to give specific answers because so much is in flux. However, the questions still remain, and Radio magazine has assembled this FAQ to help you answer questions from station management.

This is a work in progress, and we will add to it and update it as needed. If you have a question to add, tell us (radio@RadioMagOnline.com) and we'll include it and find an answer.

Has the "180-day clock" specified in the FCC's Second Report and Order and Further Notice of Proposed Rulemaking (EB Docket 04-296) and included in 11.56 of the FCC Rules started?
Most experts think yes, although a number of parties are requesting further clarification. Based on the prevailing interpretation of information from FEMA, OASIS, and FCC, stations must be compliant with the NPRM on or before March 30, 2011.

If there is to be a delay of the deadline will most likely be ordered by the FCC, although a delay is not assured.

What is the minimum requirement for stations to comply?
At the very minimum:
1) Stations must be able to receive messages delivered using the CAP 1.2 data protocol.
2) Messages sent by the governor or someone he/she designates received by stations in a method specified by the State EAS Plan and put on the air immediately.

No other requirements are specified.

What is the recommended way for stations to comply?
Stations should be prepared to incorporate emergency messages delivered by the CAP protocol into their EAS systems, logging and plans. This means a station's current EAS encoder/decoder should either be capable of receiving and reacting to CAP messages, or there should be a device that can be added to a current EAS unit to inject messages delivered using CAP into it. Either way, the station's EAS unit should react appropriately.

How can a station receive and decode CAP messages with EAS equipment?
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 have the capability to incorporate the CAP messages into a station's EAS capabilities, although that integration is not part of this specific ruling.

For a station to receive CAP messages it 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 its messages can be decoded using the NWS ATOM feed http://www.weather.gov/alerts-beta/

What is CAP?
In plain English, it's simply a protocol -- a format, so to speak -- that will be used to distribute emergency messages. It's the chosen common language the emergency communications community will be using from now on.

According to this document, drafted partially by former SBE EAS Committee Member Art Botterell: (www.oasis-open.org/committees/download.php/14759/emergency-CAPv1.1.pdf)

The Common Alerting Protocol (CAP) is a simple but general format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks. CAP allows a consistent warning message to be disseminated simultaneously over many different warning systems, thus increasing warning effectiveness while simplifying the warning task. CAP also facilitates the detection of emerging patterns in local warnings of various kinds, such as might indicate an undetected hazard or hostile act. And CAP provides a template for effective warning messages based on best practices identified in academic research and real-world experience.

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

Does this mean the "duck quacks" (the EAS SAME tones stations use now) will change or go away?
Nothing changes with what stations must send. Even EAS isn't changing...yet. In fact, it is expected that the current EAS system will not be changed, but a separate, CAP-capable data distribution system will be added to EAS plans.

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

Where will stations get CAP messages?
This is one of the many decisions that has not been resolved. Experts believe that CAP messages will be delivered via a TCP/IP path, which may be the public Internet or a dedicated IP data path.

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

It is widely believed that IPAWS-OPEN will be available for testing by a limited group of originators not later than Feb. 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.

This is a good wiki on CAP developments: www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook.

What's this I heard about messages from the Governor?
FCC Rule 11.55 requires state governors or his/her designee to be able to have his/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 system as the means. Although this has never been used, that same capability is being conferred to allow governors to speak to their states.

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.

Unfortunately, there are more currently more questions than answers in this area. Read on.

What's the problem with keeping to the 180-day timetable?
That's not an easy question but put as simply as possible, the Society of Broadcast Engineers and many broadcasters are concerned that stations will be required to purchase equipment capable of CAP with no assurance that the equipment will comply with required, imminent and inevitable FCC rule changes that will make the next generation emergency communications system possible. Part 11 of the FCC Rules, covering EAS, has not been changed to incorporate CAP in any way, but this is sure to occur very soon, now that FEMA has approved the use of CAP 1.2. Unfortunately, EAS equipment available now may comply with the current rules but may NOT comply with the new FCC rules.

There are concerns that stations will, after purchasing equipment to comply with this rule will be required to spend more money and time to comply with the imminent FCC Rule changes.

Here's a sampling of what hasn't been determined yet:

  • What will stations need to do when they receive CAP messages?
  • What do my stations monitor for CAP?
  • 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?

    Wow! So what am I supposed to do now?
    The best advice is to contact EAS/CAP equipment suppliers and become familiar with the options available. Assuming your stations are in compliance with your EAS Plan, you should be planning to essentially add a new monitoring source to include CAP emergency messages to your current assignments. It is expected that the current EAS system (including the daisy chain included in many operational plans) will not change, but a separate, CAP-capable data distribution system will be added to EAS plans.

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

    While it's important to be informed and cautious, the decision and action to purchase and install CAP-capable equipment should not be put off until the very end of the FCC's specified installation clock. Doing so will result in dealing with the logistical problems of manufacturers that will be supplying new equipment to every radio and television station and cable and satellite head-end all at once. DO NOT ASSUME THE DEADLINE WILL BE EXTENDED! Although there are many groups seeking to extend the deadline until FCC Part 11 rules are changed and equipment can be certified as in compliance, it would be unwise to rely on an unknown without fully understanding the circumstance and preparing an alternate, if temporary method of complying with the current law.


    • From:  www.fema.gov

    FEMA Announces Adoption Of New Standard For Emergency Alerts 

    Common Alerting Protocol Key in Developing America's Next Emergency Alert and Warning Network

    Release Date: September 30, 2010
    Release Number: HQ-10-192

    WASHINGTON,D.C.-- The Department of Homeland Security's Federal Emergency Management Agency (FEMA) today announced the adoption of a new digital message format for the Integrated Public Alert and Warning System (IPAWS), the nation's next generation emergency alert and warning network.  The goal of IPAWS is to expand upon the traditional Emergency Alert System by allowing emergency management officials to reach as many people as possible over as many communications devices as possible, such as radio, television, mobile phones, personal computers and other communications devices.  The current Emergency Alert System relies largely on radio and television to communicate to people.

    The new digital message format being adopted by FEMA is the Organization for the Advancement of Structured Information Standards (OASIS) Common Alerting Protocol (CAP) v1.2 Standard.  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.

    "The Integrated Public Alert and Warning System will allow federal, state, territorial, tribal and local officials to get critical and timely information to the public that can protect communities and save lives," said FEMA Administrator Craig Fugate.  "People get their news and information from a wider variety of sources today than ever before, and it's important that emergency management officials are able to reach members of the public no matter what medium they may be using.  The Common Alerting Protocol gives us the opportunity to send one message over all IPAWS alert systems at the same time."

    Under Executive Order, FEMA is responsible for establishing the protocols and standards for an integrated emergency alert system that can reach Americans over a variety of media in a timely manner.  The Federal Communications Commission is the lead agency responsible for adopting and enforcing the requirements to ensure that communications service providers have the capability to receive and transmit emergency alerts to the public.

    Rear Admiral (ret.) James Arden Barnett, Jr., Chief of the Federal Communications Commission's Public Safety and Homeland Security Bureau said, "The adoption of the new CAP standard will ultimately transform America's emergency alert and warning capabilities and better enable Americans to receive these potentially life-saving alerts over  television and radio broadcast stations, via the Internet, and on their cell phones.  The ability to receive alerts over multiple platforms will dramatically increase the likelihood that Americans are receiving this critical information timely and are better informed to take actions that will help protect themselves and their families during emergencies."

    In order to assist officials in evaluating new alert and warning systems, FEMA is conducting an assessment program to ensure products adhere to the IPAWS CAP profile.  A list of pre-screened products that meet the profile will be published at the FEMA Responders Knowledge Base, to aide federal, state, territorial, tribal and local officials in purchasing emergency alert products that comply with IPAWS CAP.  Vendors can apply for these assessments at www.nimssc.org/ipawsconform.

    The three documents defining the FEMA IPAWS technical standards and requirements for CAP and its implementation are:  (1) OASIS CAP Standard v1.2; (2) IPAWS Specification to the CAP Standard (CAP v1.2 IPAWS USA Profile v1.0); and, (3) CAP to EAS Implementation Guide.  Additional information and documentation on CAP technical standards can be found on the OASIS website.  The CAP to EAS Implementation Guide can be found on the website of the EAS-CAP Industry Group (www.eas-cap.org/).

    FEMA's mission is to support our citizens and first responders to ensure that as a nation we work together to build, sustain, and improve our capability to prepare for, protect against, respond to, recover from, and mitigate all hazards.

    Last Modified: Thursday, 30-Sep-2010 13:38:12

    Below is old information for updates to various Manufacturers of Endecs and in some cases past updates.

    Harris Sage
    Sage DOS software -  Zip

    The user can enter the new Event Codes and new Location Codes using the DOS program. When using this program and entering a new Code from the keyboard, there is a max Event Code description length of 52 characters and a max Location Code description length of 40 characters. There will soon be an import file available on the Harris website which will upgrade the unit. When using the import function, up to 81 characters are available for Event Code descriptions and 41 characters for Location Code descriptions. The company reports the only way to change the County Subdivision names is with a new ROM.  The files below will keep you from having to type each individual code by hand, until the import software is available.

    Harris Instructions for Adding New Event Codes - Word Doc

    TFT
    Two-chip upgrade available for $100 + $10 s&h, 10% discount for pre-paid or credit card orders. For more information click here to go to the TFT website.

    GORMAN-REDLICH
    "The upgrade chip is now available. For units currently running firmware Version 6.4 or below, those units will need a circuit board modification in addition to the new chip. Upgrade cost including return shipping for those units is $215. Units currently running firmware higher than Version 6.4 only need the new chip, at a cost of $50."

    BURK
    Burke now states that they do not have a solution yet available for those who have purchased their unit.  They say they are working toward a solution, but do not promise anything.

    "August 2002 Update: The current project engineer has not provided a project completion date, however we will be adding project information on our website in the near future. Per, Kevin Frappier."

    Earlier from Kevin Frappier, Customer Support Manager, "We will post the EAS update on our web site available at no charge to existing customers. We expect to have this version completed this summer. I do not have an official release date I can provide at this time."

    MTS
    "We will post the System 3000D update on our website by September 1st. There will be no cost to customers who download the update. The downloaded file is run on a Windows PC to create the update diskette. We will also make the update available on diskette, for which there will be a very small shipping charge. Installing the update involves mounting the diskette in System 3000D's drive and entering a keypad sequence to start the update. The process takes about three minutes. Per Skip White, VP Software Engineering."

    HOLLYANNE CORPORATION

    HollyAnne is making the new codes available in previously manufactured units as a retrofit.

    The retrofit is currently available for HU-961's. The cost of the retrofit is $150.00 plus shipping and handling. There is also a refundable $25.00 core charge on e-proms. The retrofit is designed to be field installed. If you wish, however, HollyAnne Corporation will install the new e-prom in their facility for an additional charge of $75.00 plus shipping and handling.

    The retrofit e-prom may be ordered direct from HollyAnne Corporation by phoning (308) 428-4705. You will need to know your unit's serial number and firmware version number.

    HollyAnne Corp. 207 W. O'Connor Ave. Greeley, NE 68842 402-426-4841 Toll Free 888-4-EAS INFO (888-4-327-4636). Call Technical Support Center at (308) 428-4705 for any questions. 

     

     

    This website is the property of the EAS State Co-Chairmen.
    For problems or questions regarding this web contact easadmin@okeas.org.
    Last updated: March 31, 2003.