Making Field Day and SET Count: Scenarios, Message Handling, and After-Action Reports That Get Used
- Replies 2
- Views 15
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Lee 1 post
-
Mod_Chrissy 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Field Day and the Simulated Emergency Test (SET) are both useful, but they test different things. Field Day shows whether you can get stations, power, and antennas working in a hurry. SET, or any local drill, should test whether the communication works: whether traffic gets from a shelter or EOC to its destination, accurately and in a form the receiving party can use. If both events get treated as the same thing, you can come away with a good score and no better prepared.
Here are some ways to use each one, and I'd like to hear what others have tried.
1. Treat Field Day as an equipment and setup rehearsal, then add one deliberate constraint. Run on generator, battery, or solar only. Power up a station from a cold start with no one who normally runs it. Deploy an antenna from a written checklist rather than memory. Handle a few formal messages in between contacts. The contest exchange is easy to do on autopilot, so the constraint is what makes it practice.
2. Build SET scenarios around a specific loss, not just a hazard name. "Hurricane" is a theme. "Commercial power is out across the county, the primary repeater is on a generator with limited fuel, and the hospital needs a supply status relayed to the EOC" is a scenario. Some starting points:
3. Practice message handling as a skill with its own failure modes. A standard ARRL radiogram has a number, precedence, handling instructions, station of origin, check (word count), place of origin, time and date filed, addressee, text, and signature. Precedences run Emergency, Priority, Welfare, and Routine. The ICS-213 General Message form is also common with served agencies. The usual problems are not exotic: illegible handwriting, a wrong word count, a message that is really three requests, a missing callback number, and operators who paraphrase instead of copying exactly. A good drill includes at least a few messages designed to expose those problems, such as an ambiguous address or a text full of numbers that must be copied verbatim.
4. Write the net script for tired people. A script should help a new net control station who has been up for hours. Include the opening statement, how to call for emergency or priority traffic first, how to take check-ins (and whether to ask for capabilities), a short way to assign traffic, a repeating reminder about stand-by procedures, and closing language. Keep it to one or two pages. Add a pre-printed log sheet so the operator is not inventing a format under stress.
5. Do an after-action report even for a small drill. A simple structure works: what was planned, what happened, what went well, what needs improvement, and who will do what by when. The homeland-security exercise tradition (HSEEP) frames this around strengths, areas for improvement, and corrective actions. The corrective actions are the part groups skip. "Improve comms" is not an action. "Rewrite the shelter report form so the occupant count is the first field, and review it at the next meeting" is.
Questions for discussion:
Link to comment
https://www.hamradiobase.com/forums/topic/11681-making-field-day-and-set-count-scenarios-message-handling-and-after-action-reports-that-get-used/Share on other sites