Making SET and Field Day count: designing exercises that expose real communication gaps
- Replies 2
- Views 30
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Mike 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Most of us agree that exercises matter. The harder question is whether the ones we run test anything difficult. A Simulated Emergency Test where everyone checks in on the primary repeater, passes two tidy messages, and logs off after ninety minutes proves the repeater works on a good day. It tells us little about what happens when the repeater site loses power, the served agency's liaison is pulled away, or half the volunteers can't reach the staging location.
Here is a framework for building more useful exercises, and I'd like to see where people disagree with it.
1. Pick one failure per scenario and make it the point. Different disasters stress different parts of the system. A hurricane is mostly about duration: shift rotation, fuel and battery logistics, and traffic that changes from pre-landfall coordination to welfare inquiries and resource requests. A wildfire is about moving targets, with evacuation zones shifting, repeater coverage changing, and agencies needing situational information. An earthquake is about the sudden loss of infrastructure and the flood of unscheduled check-ins. A tornado or severe-weather event is short-fuse, so activation speed and clear reporting matter more than endurance. Flooding often brings road closures that decide who can physically get to a shelter or EOC. A grid failure is a good scenario for testing your own preparedness, because every station and every repeater is on battery or generator from the first minute. Choosing a single dominant problem makes the after-action review much clearer than throwing everything in at once.
2. Treat Field Day as practice, but add the missing pieces. Field Day is excellent for setting up antennas quickly, running on alternative power, operating in poor conditions, and working with people you don't operate with every week. It does not, by default, practice message handling, net control discipline, or interaction with an agency. If your group is already on site, consider a side activity: a small group formally originating and relaying a few messages while the contest-style operating continues. Even a short exercise shows who knows the format and who is guessing.
3. Use realistic, boring messages. The messages that matter in real events are rarely dramatic. They look like: request for 200 cots at a shelter, a road closure report, a generator fuel status, a change in shelter occupancy, a request for a medical resupply. Write exercise messages like that, with names, numbers, and locations that are easy to garble. Include at least one message that is long enough to tempt someone to paraphrase it, and one where the addressee can't be found.
4. Test the handoff between the agency form and the radio form. Served agencies often use their own forms, such as the ICS-213 General Message. Amateur traffic systems use the radiogram format, which has a message number, precedence, handling instructions, station of origin, check (word count), place of origin, time and date, addressee, text, and signature. Decide beforehand which format you'll use at the point of origin and which at the point of delivery, and who is responsible for the conversion. Practice sending the text exactly as written. A volunteer who "cleans up" the wording can accidentally change the meaning.
5. Write a net script, then see where it breaks. A good script is short enough to read under stress and covers: net identification and purpose, who is net control, how to check in (priority or emergency traffic first), what is being asked of stations, and how to ask for a repeat. Leave out unnecessary detail. The exercise should show whether net control can keep the channel moving when five stations call at once, and whether stations know to stand by instead of keying up with a long explanation.
6. Write the after-action report while it's fresh, and keep it structured. A simple format works: what we intended to test, what happened, what worked, what didn't, why, and what we'll change, with a named owner and a time frame for each change. The most useful reports separate observation from opinion. "Net control took eleven minutes to find a station able to relay to the shelter" is better than "coordination was weak."
Questions for the group: What failure do you think local exercises most often leave out? And has anyone found a good way to bring a served-agency counterpart into the exercise without turning it into a scripted show?
Link to comment
https://www.hamradiobase.com/forums/topic/11482-making-set-and-field-day-count-designing-exercises-that-expose-real-communication-gaps/Share on other sites