Fair warning

Standards, coordination at heart of alert-system debate

President Bush's recent executive order to upgrade the nation's emergency warning system lays out an ambitious plan to coordinate a patchwork of federal, state and local alert systems.

But is it ambitious enough? Emergency warning experts said the June 26 order stops short of resolving a conflict involving an emergency-warning data standard used by both the Commerce and Homeland Security departments. It also doesn't designate an official to be in charge of emergency warning.

The order also fails to clarify whether an upgraded national public warning system will be based on open standards or proprietary technology.

Despite those gaps, the executive order is viewed as a positive development.
"It is long overdue, and there is a great need for it," said Kenneth Allen, former executive director of the Partnership for Public Warning advocacy group.

The order designates DHS as the lead agency for public warning, and directs the Commerce Department to make its technology available to DHS in order to establish an integrated warning system, among other provisions.

Even so, whether the executive order will have broad reach is uncertain.

Talk about Weather

Some of those involved in standards writing have raised concerns about the National Weather Service's alleged modifications to a major emergency warning standard, the Common Alerting Protocol. CAP is an Extensible Markup Language-based, national open standard for universal alert messaging.

Industry and emergency managers developed the protocol, and the Organization for the Advancement of Structured Information Standards adopted it in 2003. The Federal Emergency Management Agency endorsed it in 2004, and a number of government agencies are using it.

Art Botterell, original CAP architect and a California emergency management official, recently protested the weather service's development of a "dumbed down" version of the protocol for use in its new HazCollect, a national, all-hazards, emergency public warning system that National Oceanic and Atmospheric Administration is developing.

"Regrettably, what the National Oceanic and Atmospheric Administration is proposing to roll out nationwide in the next few months is a crippled and incomplete version of the Common Alerting Protocol data format," Botterell wrote May 31 on a public message board.

The HazCollect program, which is intended to convey warning messages to federal, state and local emergency management offices and agencies as well as the public, does not include an important feature of the protocol, according to Botterell and others. Two major data fields of the protocol identify the hazard and provide instructions to the public on what actions to take. In the weather service's version, those two fields are combined, with the effect that urgent and critical instructions may be missed, Botterell said.

"CAP tells you what to do," said David Aylward, executive director of the ComCare Alliance, a national, non-profit advocacy group for improved emergency communications. "The specific issue with HazCollect is that it was not able to pass on that information."

Weather service officials have defended the HazCollect program, saying they fully intend for it to comply with CAP.

"NOAA is not rewriting the CAP specification and, as stated, needs to conform to CAP," Herb White, dissemination services manager for the National Weather Service, wrote on the incident.com message board June 2. White did not respond to several requests for further comment, and a weather service spokesman declined a request for a comment.

Aylward said he believes the weather service will correct the problems and comply with CAP before debuting the program nationally.

"The good news is that the Commerce Department has committed to fixing this quickly," he said.

"Since we made a flap about this, [weather service officials] are saying some positive things," CAP architect Botterell told Washington Technology.

The stakes are high, Botterell said, because the National Weather Service is a high-profile agency with a broad reach into the emergency management community. If it eliminates the instruction field in emergency messages, it is likely that many state and local agencies will follow suit, and it would harm the effectiveness of the messages, he said.

Open standards question
The other chief issue is whether the federal government truly supports open standards such as CAP for a national warning system. The executive order calls for development of "common alerting and warning protocols, standards, terminology and operating procedures ? to enable interoperability," but does not specifically mention CAP.

"The order is very unclear with regard to the Common Alerting Protocol," Aylward said.

Under the order, DHS within 120 days will issue guidance on how to carry it out. Botterell said he hopes to find out whether DHS will then officially adopt CAP governmentwide.

One of CAP's characteristics is that it is an openly published standard, which lets many vendors develop software to meet it. By contrast, several emergency warning-related programs in the federal government use proprietary technologies. The order does not specify a preference for open standards.

"It is not clear whether [the national warning system] will be a proprietary technology or an open standard," Aylward said.

The order designates DHS as the lead agency for public warning, but it identifies neither an individual to be in charge nor a specific leadership position, which some observers see as a possible shortcoming.

"One of the things the Partnership for Public Warning has always said is there needs to be clear leadership at the federal level designating who is sitting at the federal table," said Allen, the group's former director. "Also, there needs to be a collaborative environment with state and local governments and the private sector."

Staff Writer Alice Lipowicz can be reached at alipowicz@postnewsweektech.com.

About the Author

Alice Lipowicz is a staff writer covering government 2.0, homeland security and other IT policies for Federal Computer Week.

Reader Comments

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above.

What is your e-mail address?

My e-mail address is:

Do you have a password?

Forgot your password? Click here

Washington Technology Daily

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.


contracts DB