<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Karen,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Some years ago, in the aftermath of a hurricane and massive evacuation of Houston, the forward deployment area was moved from San Antonio to Houston the day after it had left the Houston area, but Houston was unreachable other than by air. There was no PIO available, and only a relatively inexperienced PAO did the job. We were able to support that PAO from TXWG HQ, but it was uphill all the way.This PAO did not choose to be a PIO; it just fell on that one person because no one else was available. But in some cases, such as when Katrina hit New Orleans, all communications were down, and access was disrupted by floods.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>The “PIO training issue” is not really a stumbling block. For a PAO to qualify as a PIO, it is very easy. And all PAOs ought to be prepared for the day when an emergency makes that PAO the de-facto PIO.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>The converse is not easy, though. The CAP ES requirement for PIO qualification is pitifully sketchy, and a PIO who has done the required ES tasks (less than a day is all that’s needed), will be far less capable than a PAO with even a technician rating. FEMA provides PIOs with acceptable PAO training; CAP’s PAO training is far better than FEMA’s. This is the real problem, with many PIOs who are not PAOs, and when the emergency strikes, they can’t do as good a job as we can because they don’t even know how to write a good news release.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'>Arthur ~<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:windowtext'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> cap-pao-bounces@lists.sempervigilans.org [mailto:cap-pao-bounces@lists.sempervigilans.org] <b>On Behalf Of </b>Karen Copenhaver<br><b>Sent:</b> Sunday, September 08, 2013 7:44 AM<br><b>To:</b> CAP Public Affairs Officers<br><b>Subject:</b> Re: [PAO] September Disaster Preparedness Month<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Good morning Tom,<br><br>I understand how this might work, however, there are PAOs who do not wish to, or may not have the time to serve as a PIO, so why "require" him/her to do so? We do not "require" any other position to do so as part of their training (ref Mike Marek's response). One can be an effective PAO even if not serving as PIO. If we look at our entire CAP make up..... we wear two hats, one is administrative, one ES. I grouped administrative into our day-to-day missions and initiatives because of our missions in cadet programs and our aerospace education as well as our support of our community involvement, and recruiting. <br><br>One should not be "forced" to qualify as a PIO if one does not desire to do so. However, if one desires to serve as a PIO, then the background knowledge and experience gained as a PAO will definitely enhance the ability to serve in that capacity. I whole heartely agree with Alice in that we should nurture our relationships with other organizations, which I too have been pushing for years. Partnering with our fellow ES responders in training and in actual missions will make for a better team effort from all those who work in emergency services. Thanks to Alice, we also should review how current all our MOUs are, and obtain/download/print copies. <br><br>On a training note, when I first joined CAP as a PAO, I made it a point to learn about all other positions in the squadron..... and in the ES role, especially during "training" missions. During those training missions, I physically visited each section, observed their duties and asked questions and took lots of notes. That initiative provided a real perspective of what they did so I could share with the public with a better understanding and confidence. As I mentor others, this is one of my first suggestions and encouragement as it is very important to speak with knowledge.<br><br>Karen<br><br><br><br>On 9/7/2013 10:52 PM, Thomtra wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>I agree, Karen, that a PAO can NOT automatically become a PIO. I think the idea was to have a PAO EARN the PIO credentials as part of their required qualifications rather than have two separate individuals.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Tom<br><br>Sent from my iPad<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On Sep 7, 2013, at 6:03 AM, Karen Copenhaver <<a href="mailto:karenc@smyth.net">karenc@smyth.net</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><b><i><span style='font-size:13.5pt;color:#333399'><br>With respect, I do not agree..... mainly because being a PIO is more specialized and focused on emergency services. The responsibility of a PAO is different in that he/she is responsible for the image of CAP in general. When first joining CAP, usually the PAO is focused on learning more about the organization, how it works or functions within the community, impacts the future of our leaders (cadets) and just what CAP is and does as part of our congressionaly mandated missions. The PIO must be experienced and have gained the confidence to work emergency / training missions. There is a significant difference as my personal professional training taught me, and all those professional practioners will agree. Let's not forget, that all PAOs do not want to serve as PIOs. I can't imagine a new PAO automatically being considered a PIO, it's akin to telling a new CAP member is automatically certified to fly as an observer, or field operative. NO WAY. There must be a specified dedicated training program to instruct a PAO in how a mission is initiated, who initiates, learning the responsibilities of fellow mission members, what should and should not be released, how to interact with fellow mission members, the public and any members of a family involved. The list goes on... however, once the PAO gains the knowledge and training in emergency services, then.... then he/she should be evaluated before being certified to served as a PIO, but must serve as a PAO first, at least for a year...... hope this helps.<br><br><br>Karen L. Copenhaver, Lt Col, CAP<br>Deputy Director, Public Affairs<br>MER<br></span></i></b><br><br><br>On 9/6/2013 4:10 PM, Cianciolo, Lt Col, Paul wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>That makes me even more convinced that CAP should not be separating PAO and PIO responsibilities as is now. We are one organization and can't compartmentalize it so much. SAR, HLS, and DR missions are part of the whole mission. Without them, would CAP be here? At times its like being in two different organizations depending on what the activity is.<o:p></o:p></p></div><p class=MsoNormal>Paul <o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>v/r<br>--<br><b>PAUL S. CIANCIOLO, Lt Col, CAP<br>Public Affairs Officer<br>National Capital Wing</b><o:p></o:p></p><div><p class=MsoNormal>Cell: 301-751-2011<o:p></o:p></p></div><div><p class=MsoNormal>Work: 202-385-9599 (@FAA)<o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>_______________________________________________<br>CAP-PAO mailing list<br><a href="mailto:CAP-PAO@lists.sempervigilans.org">CAP-PAO@lists.sempervigilans.org</a><br><a href="http://lists.sempervigilans.org/mailman/listinfo/cap-pao">http://lists.sempervigilans.org/mailman/listinfo/cap-pao</a><o:p></o:p></p></div></blockquote><p class=MsoNormal><br><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>CAP-PAO mailing list<o:p></o:p></pre><pre><a href="mailto:CAP-PAO@lists.sempervigilans.org">CAP-PAO@lists.sempervigilans.org</a><o:p></o:p></pre><pre><a href="http://lists.sempervigilans.org/mailman/listinfo/cap-pao">http://lists.sempervigilans.org/mailman/listinfo/cap-pao</a><o:p></o:p></pre></blockquote><p class=MsoNormal><o:p> </o:p></p></div></body></html>