Turning SET and Field Day into real disaster comms practice: what should we be testing, and how do we write it up?
- Replies 2
- Views 56
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Mike 1 post
Every year, many emergency communications groups run a Simulated Emergency Test (SET) and a Field Day, then file a short summary and go back to normal. The risk is that both turn into "we made contacts and the radios worked" without telling us whether we could actually support a served agency during a hurricane, wildfire, flood, earthquake, tornado or long grid outage.
I'd like to start a discussion on how to make these events more useful as practice, and how to capture lessons in an after-action report (AAR) that someone will read. Some starting points:
1. Pick a scenario that forces different problems. A hurricane exercise usually stresses long-duration operations, shelter traffic, and a possible loss of commercial power and internet. A wildfire stresses mobility, evacuation information, and repeater coverage in rough terrain. Floods tend to isolate areas and damage roads. An earthquake raises questions about damaged infrastructure and a sudden surge of welfare traffic. Tornadoes bring short-notice activation and spotter-style reporting. A grid failure tests battery plans, generator fuel, and how long your own repeaters can stay up. If every drill is "generic disaster," you only practice generic problems.
2. Treat message handling as the main skill, not a side activity. Field Day is excellent for setting up stations quickly, operating on generator or battery power, and working under less-than-ideal conditions. But a contact exchange is not the same as handling formal traffic. Consider adding practice messages: a shelter supply request, a status report from a hospital, a welfare inquiry. Check for the basics: Is the message complete? Does it have a clear originator and recipient? Was it copied exactly? Was it read back when needed? Was it delivered, and did anyone record the time?
3. Write net scripts that people can follow under stress. A good script is short, plain, and easy to read aloud. It should cover who the net control station is, the purpose of the net, how to check in (emergency or priority traffic first, then others), how to request relays, and when the net will close or change frequency. It helps to have a printed version at each station, plus a few variations: a directed net, an informal net, and a net where net control must be handed off partway through.
4. Practice working with the served agency, not just with each other. Whether it's emergency management, a Red Cross chapter, a hospital, or a shelter manager, the agency's needs drive the exercise. Ask them what information they actually need, in what format, and how quickly. Have them write some of the messages. Agree beforehand on who may authorize a message to be sent, and on what is confidential. Operators should be ready to say "I'm here to move your message, not to decide your response."
5. Capture lessons while they're fresh. A useful AAR is simple: what was planned, what happened, what went well, what didn't, and what specific actions will be taken, by whom, and by when. Avoid vague items like "improve communication." Instead: "Replace the shelter-station antenna feedline," or "Add a second trained operator to each shelter shift."
So, a few questions for the group: What do you include in your SET to make it more than a contact count? How do you adapt Field Day to practice emergency skills without spoiling the fun? And what has been the most useful change you've made to a net script or AAR template?
Link to comment
https://www.hamradiobase.com/forums/topic/10768-turning-set-and-field-day-into-real-disaster-comms-practice-what-should-we-be-testing-and-how-do-we-write-it-up/Share on other sites