[SBE] [sbe-ecc] CAP for ND warning system

[Richard Rudman]

Hello, Richard:

Permit me to offer a few comments to add to what Clay offered.

Many states , including my own, have had good luck getting support  
from their state's broadcasters association. Nationally, the  
organization that represents all state broadcasters organizations is  
called NASBA, the National Alliance of State Broadcaster Associations.  
NASBA is a key player along with SBE and NAB as we work with the feds.

As far as lighting a fire under government, here in California,  
despite many years of good progress, State OES was not moving as fast  
as the SECC wanted. Fortunately, the State legislature came to the  
rescue and passed legislation mandating that OES set up working groups  
to improve all state public warning systems, including EAS.

If you can get backing in your legislature, this approach might be  
helpful. It would also let you propose working groups roughly based on  
the outline Clay forwarded to you. I also hope others on the remailer  
who are facing similar situations (I know you are out there) consider  
doing the same thing. A big part of state coming on board will be  
major rewrites of state EAS plans. Creating local and state relay  
networks should in my opinion be a hallmark of new state plans for  
enhanced EAS.

Regards,

Richard Rudman
Vice Chair, California SECC
Member, SBE EAS Committee




On May 21, 2008, at 8:08 PM, k7cr wrote:


> Hello Richard -

>

> My responses are below -

>

> Clay

>

> ----- Original Message -----

> From: Robinson, Richard N.

> To: k7cr at blarg.net

> Sent: Wednesday, May 21, 2008 2:27 PM

> Subject: CAP for ND warning system

>

> Good Afternoon Mr. Feinwald,

>

>         I have talked to you on a couple of occasions at the 2006  

> and 2007 EAS Summit meetings regarding North Dakota’s need to  

> improve warning systems.   I watched the May 19 discussions over the  

> web and, as usual, appreciated your contributions to the interchange  

> among the panel representative.

>

> Apparently a number of folks watched the web coverage of this  

> event.   Believe me, I could have said a great deal more, I just  

> hope that what I did contribute was helpful to the discussion.

>

>         North Dakota (“I”) continues to struggle with progression of  

> further development of our EAS system.  Most of this is due to,  

> well, not a lack of interest, but ambivalence.  As was stated in the  

> meeting LECCs and SECCs have been on autopilot for about the last 5  

> years.

>

> This is a very common problem, believe me.   As was mentioned at the  

> recent FCC EAS Summit, I have, in the past, traveled around the  

> country teaching others how to create a more effective EAS system.    

> Believe me, you are not alone.   This was the basis of the  

> 'patchwork' comments that were made by Dale Gehman and others.

>

>  I need to push the N.D. Department of Emergency Services, Division  

> of Homeland Security to take an active role in initiating the  

> development of LECCs within the state (we have none) and I would  

> like to present an outline of how to move forward in the development  

> of a CAP system.

>

> You have mentioned two items here -  First, developing LECC's within  

> the state is a matter of teaching organization.   This calls for  

> leadership and, as you heard on Monday, there were repeated calls  

> for the Feds to do just that.   What will come of this is anyones  

> guess.   There are those that do consulting in this area, Dale  

> Gehman from Pa (on the first panel) is an example of where you can  

> turn for answers. - Second, development of a CAP system...I assume  

> that you are talking about a method to distribute CAP messages  

> throughout your state.   There are a number of systems out there  

> doing just that.  A couple were mentioned on Monday.   Dale has been  

> working with a system call EM-Net.  Pa. and a number of other states  

> are using this system.   Here in Washington State we are using an  

> Internet based system supported by My State USA.   The bottom line  

> is that there are options for you to choose from and people who can  

> help.

>

>   I am really tired of getting calls from broadcasters throughout  

> the state relating their frustrations with our antiquated daisychain  

> system andLP1s failing to forward on warnings they have received.

>

> Referencing my comment about the Daisy Chain at the FCC Summit,  

> there is not requirement that you use this method for EAS Message  

> Distribution.   This is a hold-over from the days of EBS.  Several  

> states do not use this method knowing the limitations that it  

> presents.

>

>  At minimum we need to assign someone in the state to inspect  

> station equipment, PSAPs as well as broadcast stations, to ensure  

> their equipment is programmed properly.

>

> The first place you have to go is your States EAS Plan.  Does it  

> specify specific programming for each EAS Endec in the state?   It's  

> best that the Plan provides the instructions to those that own this  

> equipment.  One of the jobs for the SECC is to educate broadcasters  

> in the state as to how the EAS plan functions and what their role is  

> in the process.  Then there is the matter of FCC rule enforcement.  

> I  suggest that you contact your State Broadcasters Association and  

> see if someone in your state is involved with what's call ABIP.    

> This is a voluntary broadcast station inspection program.   If they  

> are, it's a matter of getting this person and/or firm up to speed as  

> to your state EAS Plan etc.

>

>  I am willing to accept this responsibility but my superiors are not  

> willing to commit my services to those tasks.

>

> As I stated on Monday, the success of your EAS system rests with you  

> and to some degree those that are called upon to support and fund  

> it.   EAS can be a great public warning tool, but ONLY if the effort  

> is put into it.  As you said, it was on Auto Pilot.   This is a  

> receipe for a failure.   Probably one of the most important items on  

> the must-have list is a strong leader that has the passion for the  

> mission and who can modivate others.   This person heads up your  

> SECC.   The SECC is not a singular person, but rather a group of  

> folks that are the major steakholders in the process.  And one more  

> thing.  This person need not be an Engineer.  Look for a leader first.

>

>         I am sending you this e-mail because you had in your  

> possession at the meeting an outline of where to start in the  

> development of a CAPorganization for state warning systems.   I have  

> accessed the SBE.org website but was unable to locate the document.

>

> The outline that I referenced in my comments is attached, however  

> this is likely not what you are looking for.  This is a suggested  

> roadmap for getting EAS, in general, from where we are today to one  

> that operates with CAP.   This will have to be a national level  

> discussion.    Per my previous comments, your best bet will be to  

> contact states that are doing what you wish and seek advice as to  

> how to get from where you are to where you wish to go.

>

>  Can you provide me with some direction on how to obtain a copy of  

> the document, and perhaps some support to convince my agency to get  

> active and start development of a reliable warning system.   Thanks  

> in advance for any help in this matter….Rick

>

> Rick,  I sincerely hope that the above information will give you a  

> head start.     Feel free to contact me directly If I can be of  

> further help.   If a telephone call would help, my cell number is  

> 206-947-6115.

>

> By the way, my Brother in Law works with the Red River and Western  

> RR and lives in Wapeton

>

> Clay

>

>

>

>

>

>

> Richard N. Robinson

>

> Planning Specialist

>

> N.D. Department of Emergency Services

>

> Division of Homeland Security

>

> 701-328-8136

>

> rnrobinson at nd.gov

>

>

>

> <Final - Working Groups Document May 16  

> 2008.pdf>_______________________________________________

> sbe-ecc mailing list

> sbe-ecc at sbe.org

> http://seven.pairlist.net/mailman/listinfo/sbe-ecc