|
Here is what we covered: First
half of our 2-hour meeting:
- Area 10 meeting at end of month, March 29.
Time and location to be announced soon on dnc-ares site and announced
via the yahoogroups list and other venues.
- website: Please give input on our
site, any corrections, additional content, or suggestions welcome.
Link for submitting by email is on this site. Dave WA4NID and Joe
K4SAR are working to make the site useful, but need your help!
- Arrangements with served agencies. We
reviewed these and found we are in sore need of updating our
communications with some of the served agencies. We identified some
key "point people" and need to encourage and empower these
people to push forward to strengthen the ties with our served
agencies. Note especially Don at Duke, Randy at Durham Reg,
David at RC, etc.
- Methods for callout / notification
/alert. We discussed the limitations of various methods for
notification of members when we activate. The need for multiple
methods of alert was stressed, and the following points were made
about specific alert mechanisms:
- Email is useful but there are key limitations.
First, it is subject to delays in transport from the nature of
the medium. Also it can be affected by power outages. Finally,
not everyone checks their email very often.
- Getting additional pagers may not
be useful as some people already feel over-burdened with alert
devices and other comm devices and will not carry additional
units. Instead, we should think about using existing
systems.
- Can we use special tones on a
repeater, and have people monitor that freq? Well, it may be
possible with certain repeaters but this will be limited as not
many members will tune in constantly. Many monitor at certain
times, and don't monitor at other times when they do other
things in their lives. This doesn't mean that a repeater-based
alert system is not needed, but it points out the limitations to
any single method. Again, multiple methods should be used. N4UBH
discussed some of the specific capabilities of local repeaters
regarding tone access management, and only certain systems can
do selective alerts. Seems this should be considered
more.
- Alpha-message capable pages was
discussed as a possible method for alerts of a number in our
group. Sure, not everyone has advanced pagers, but several do,
and this may be a way for alerting a number of the members
efficiently, and using devices they carry with them at all
times. Joe K4SAR asked if we can poll the members for their
capabilities in this regard, and he will follow up with
gathering data. Please everyone watch for notices on how to
submit your data on current capabilities with pagers, so we can
use this method to advantage. Thanks Joe, maybe this can be a
good tool in our arsenal of alert methods!
- Dave N4UBH mentioned that KAM 9600
supports POCSAG paging that can be implemented on repeaters.
Dave WA4NID remembers something about this, with a unit he has
in his station, and will check the documentation. There sure are
lots of signaling methods that can be used on VHF or any freq
that may help us with selective alerts!
- We should encourage all members to
GET ON THE REPEATERS whenever there is a severe weather event.
Let's put this into our SOP and any other formal and informal
mechanism to encourage members to GET ON and help. We need to
formalize our request to participate and "informalize"
by just encouraging other hams to simply help out as they are
able, by getting on the repeaters. Follow the suggested freq
plan, monitor those freqs when you see approaching trouble
weather. We don't always have the luxury of advanced warning,
but we should at least do all we can to encourage participation
when we are privileged to see trouble approaching. One way to
set this up is to have a NET on the DAY BEFORE bad weather will
hit, when we are getting the advance reports from the
forecasters. Let's DO THIS, it's a great suggestion, we must run
the net AHEAD of the trouble so we start to get prepared. This
is guaranteed to help increase participation if done right.
Think about it, we will have some events where we meet and plan
and talk on the net, but are not needed, but even this activity
will be useful to encourage participation and readiness.
- Recruitment. We need to encourage
more involvement with ham radio and ARES in our area. Instead of
twisting arms, let's foster enthusiasm, as this breeds more
enthusiasm. Getting more people into ham radio may be the best
long-term strategy, and from the marketing viewpoint we should
think about the best angle. Dave N4UBH shared a strategy that
involves getting people interested first in readiness and
emergency communications.
- People see the need for disaster
readiness and we could target the renewed interest in security
and emergency preparedness, while introducing people to all the
facets of ham radio in classes.
- Let's get people hooked on the
idea of emergency comms, community service, and disaster
preparedness.
- Then when they come into the ham radio class they
can be "wowed" with all the other fun stuff.
- After
all, our primary mandate is service! Forget targeting existing
hams, they've already made up their minds whether they want to
be involved with community service and ARES. If we go after
newcomers with this angle FIRST, we will get new people who are committed
to this ideal. Think about it.
Randy brought up some important points about the CERT program
that are related to recruitment and also community service. He
is involved with CERT, Citizens Emergency Response Teams. We
need to coordinate with CERT, for serving communities and also
for access to pools of excellent candidates for ARES. Think
about this. These are people proven to have an interest in
emergency preparedness. Surely some of them would be interested
in emergency comms and ham radio! One of the things Randy
discussed with Jeff Batten is the opportunity for ARES to help
coordinate a comm plan, including FRS, GMRS, and ham radio, with
CERT. Let's do it! Randy brought up the need for locating ham
radio capability in the Police Mobile Command Unit, the
Sheriff's Mobile Command Unit, and Parkwood Fire Dept.
- Inventory of Equipment at all
Locations:
- We don't have a lot of
equipment but we should be good stewards of what we have.
Let's make a current list soon. Here is a start. We've got
TMV7a and other equipment at EOC. There is some equipment at
Duke, and an antenna (vertical dipole) at Durham Regional.
There are vests with some members (WA4NID, N4UBH, etc.) and
N4UBH has some gear like headsets.
Also I'm including some here from Joe K4SAR that was posted (Mar 4,
2003) to the yahoogroups list, as he tells even more about the
important suggestions that were made about callout methods:
********
At Saturday's meeting we discussed the need for a multimode approach to
activation notification. These days many people have alphanumeric pagers,
and in my experience this works very well for emergency callouts (it's what
the NC Search and Rescue Dog Association uses for search callouts). Not
everyone has alpha pagers, and paging systems are subject to breakdowns as
well, so I'd suggest a primary protocol of paging, a secondary protocol of a
telephone-tree process, and an underlying protocol of "monitor 145.45
whenever possible, especially if there's trouble afoot."
It was said Saturday that we have access to around four old voice pagers (I
believe it was stated that these are crystalled for 145.45, but if they're
not they probably could be) that could possibly be loaned to ARES members
who don't have their own alpha pagers.
Also, many ARES members have HTs with CTCSS and/or DTMF decoding capability;
though they might not be willing to monitor 145.45 traffic all the time,
they might be more willing to have an HT around the office or house with
tone or DTMF squelch on. (Does 145.45 have a CTCSS tone on output? If not,
perhaps a macro to enable one for ARES activation could be programmed into
the controller. If so, and if it passes subaudible tones, perhaps someone
initiating an ARES callout could encode a special ARES callout tone and make
an announcement. Unless harmonics from two subaudible tones would cause
problems? I've never tried it).
A scenario might go something like this:
The EC or an AEC is notified by a served agency that ARES activation is
needed (or the EC or an on-call AEC determines that ARES needs to be
notified to stand by for possible activation).
A paging callout is initiated by an email message from EC or an AEC to the
list of email-capable pagers, and modem calls to appropriate paging
computers for those which are not e-mail accessible (we have access to
software to do this). A text callout message is sent to the
dnc-ares@yahoogroups.com <mailto:dnc-ares@yahoogroups.com> mailing list.
The messages all include notification of which repeater to use - assume
145.45 for this example).
EC or AEC announces an ARES activation on 145.45, and issues the command to
sound paging tones on the repeater to activate voice pagers, and issues a
command to sound special CTCSS and/or DTMF tones to open squelches. (S)he
then starts the ARES net.
Some of the first checkins to the net are assigned the task of initiating
the telephone calling tree for those members who do not have pagers and who
have not already checked into the net. After attempt has been made to
contact those members, telephone calling continues to any pager-capable
members who have not yet checked into the net.
If 145.45 is down, a backup repeater is used for the net, and the voice
pager step is skipped.
Any comments/suggestions on this approach?
It was also suggested that the repeater be programmed to have selectable
"standby" and "active" courtesy tones similar to those on 146.88. This
seems like a good idea too if it can be done. If the repeater doesn't
currenty have CTCSS on output, the same macros that enable the courtesy
tones could be include the commands to enable the CTCSS tone.
To guage the prevalence of alpha pager ownership among ARES members, I will
set up a poll on the Yahoo group later today.
-joe
73 de K4SAR
********
The entire last hour of our 2-hour
meeting covered our duties to served agencies, and in particular,
things Dave KD4WQU saw were being done at variance with Red Cross (RC)
rules. This was an excellent discussion because it revealed problems
with inadequate understanding of RC rules on the part of our group, and
ongoing troubles between RC and Emergency Management (EM). We had a consensus
that there is a strong need for two things here:
1. RC procedures need to be spelled out clearly for ARES, so that
we can better serve this agency. Dave KD4WQU generously offered to
prepare documentation for this, to be distributed to our members and
to EM.
2. RC and EM must get some things ironed out so that we can all
work together for the common goal of serving the public.
As I (WA4NID) understand it, RC rules state that RC shelters must
report data to RC headquarters, and then RC headquarters reports any
needed data to EM. The problem arose when data flowed from an RC
shelter directly to EM (EOC). A valid point was made by several in our
group that we, as ARES members, are serving the public. EM has
statutory authority to serve the public safety, and when we as ARES
members are serving in any capacity involving EM, we must respond to
their requests as best we can. If this conflicts with RC rules, RC and
EM need to work this out. ARES members do not want to be caught in the
middle of political squabbles. We all want to serve the public, so
let's see what can be done to solve this.
We discussed having an EM rep visit with us in the April meeting. This
may be one good step toward achieving a better understanding of needs
and procedures for all involved.
Submitted March 1, 2003,
Dave WA4NID
|