<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">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:<br>
</div>
<blockquote cite="mid:550A7DD0-B9B2-4F64-858E-8C1F77BEBFE3@aol.com"
type="cite">
<div>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.</div>
<div><br>
</div>
<div>Tom<br>
<br>
Sent from my iPad</div>
<div><br>
On Sep 7, 2013, at 6:03 AM, Karen Copenhaver <<a
moz-do-not-send="true" href="mailto:karenc@smyth.net">karenc@smyth.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div class="moz-cite-prefix"><big><i><b><font 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>
</font></b></i></big><br>
<br>
<br>
On 9/6/2013 4:10 PM, Cianciolo, Lt Col, Paul wrote:<br>
</div>
<blockquote
cite="mid:CAGhD5NVwywyeuJ2QzvHy9WBPv-XwYGAUZw6zT3qFq-OrDZAp1Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>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.<br>
<br>
</div>
Paul <br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr"><br>
v/r<br>
--<br>
<b>PAUL S. CIANCIOLO, Lt Col, CAP<br>
Public Affairs Officer<br>
National Capital Wing</b><br>
<br>
<div>Cell: 301-751-2011<b><br>
</b></div>
<div>Work: 202-385-9599 (@FAA)<b><br>
</b></div>
<div> </div>
</div>
</div>
<br>
<br>
</div>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>CAP-PAO mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:CAP-PAO@lists.sempervigilans.org">CAP-PAO@lists.sempervigilans.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://lists.sempervigilans.org/mailman/listinfo/cap-pao">http://lists.sempervigilans.org/mailman/listinfo/cap-pao</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CAP-PAO mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CAP-PAO@lists.sempervigilans.org">CAP-PAO@lists.sempervigilans.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sempervigilans.org/mailman/listinfo/cap-pao">http://lists.sempervigilans.org/mailman/listinfo/cap-pao</a>
</pre>
</blockquote>
<br>
</body>
</html>