Skip to main content

Integrating with Served Agencies

Operational Note: This page provides guidance for ARES operators and mesh advocates working with served agencies including Red Cross, hospitals, EOCs, and fire/EMS. Establish relationships before an emergency - these conversations are far harder during an active event.

Understanding Served Agency Communication Requirements

Served agencies have specific, often rigid communication requirements driven by their own SOPs, legal obligations, and incident command structures. Understanding these requirements is essential before proposing mesh integration.

Red Cross / American Red Cross

  • Needs: shelter population counts, resource requests (cots, meals, water), staff check-ins
  • Message traffic: typically short, structured (ICS-213 equivalent), not conversational
  • Key concern: reliability and accountability - messages must be logged
  • Staffing: mix of trained volunteers and paid staff; not all are technically sophisticated
  • Integration point: mesh node at each shelter feeding position/status to EOC

Hospitals

  • Needs: patient counts by severity (START triage), resource status (available beds, O2, blood), evacuation coordination
  • Message traffic: HIPAA-sensitive - do not transmit identifying patient information over mesh
  • Key concern: HIPAA compliance; any mesh content must be aggregate, not individual patient data
  • Integration point: hospital HAM radio operator or communications officer; mesh for non-PHI status only

Emergency Operations Center (EOC)

  • Needs: comprehensive situational awareness; resource tracking; inter-agency coordination
  • Message traffic: high volume, multi-agency, documented
  • Key concern: integration with existing systems (WebEOC, ICS forms, CAD)
  • Integration point: MQTT bridge connecting mesh to EOC dashboard; mesh coordinator assigned at EOC

Fire and EMS

  • Needs: incident position, resource status, casualty counts, scene perimeter
  • Message traffic: tactical and time-critical; concise
  • Key concern: interoperability with CAD and dispatch; not adding cognitive load to incident commanders
  • Integration point: mesh as supplemental position tracking, not primary tactical comms

Mesh in the ICS Communications Hierarchy

The Incident Command System (ICS) defines a strict communications structure. Mesh fits into this structure as a supplemental tactical channel, not a command channel.

ICS Traffic Type Primary Channel Mesh Role
Command (incident command decisions) Voice (P25, VHF/UHF) NOT appropriate for mesh - use designated voice channels
Tactical (field team coordination) Voice (simplex or repeater) Supplemental: short status messages, position updates
Logistics (resource requests, supply) Voice or Winlink email Supplemental: structured request messages via mesh
Situation Awareness (mapping, tracking) Manual boards, GIS Primary supplement: GPS position sharing is a natural mesh strength
Public Information Designated PIOs only NOT appropriate - no public-facing mesh traffic
Warning: Never use mesh as a primary command channel during active incidents. Mesh has variable latency (seconds to minutes), no guaranteed delivery, and no acknowledgment in basic operation. Life-safety commands must use primary voice channels with confirmed receipt.

What Served Agencies Actually Need

When pitching mesh to served agency coordinators, focus on what they actually want - not the technology:

  • Reliable short messages: "Is the shelter at Lincoln School open and how many people are there?" Mesh can deliver a 230-character answer without consuming repeater air time.
  • Position data: "Where are my teams right now?" Meshtastic's automatic GPS position broadcast answers this continuously without any operator action.
  • No additional training burden: Served agency staff should be able to use mesh with minimal training. A Meshtastic node with a preconfigured channel and a simple phone app meets this bar.
  • Works when infrastructure fails: The core value proposition: mesh works when cell towers, internet, and repeaters are down.

How to Pitch Mesh to an OES or EOC Coordinator

The Three-Minute Pitch

  1. Open with their problem: "During the [local event] last year, your shelter coordinators couldn't reach EOC for 4 hours because the repeater was down. LoRa mesh works without repeaters or cell service."
  2. Show one capability: Hand them a Meshtastic device. Send a message from across the room. Show the position on the map. "This works on battery for 3 days."
  3. Make the ask small: "I'm not asking you to replace anything. I'm asking to run this in parallel at your next exercise so you can see how it works."

Common Objections and Responses

Objection Response
"We already have radios." "Absolutely - and mesh doesn't replace them. It adds a text and position data layer so your voice channels stay clear for important calls."
"What if it breaks?" "Mesh is decentralized - there's no single point of failure. If one node fails, traffic routes around it. And your existing radio systems remain the primary comms."
"Our staff can't learn new technology during a disaster." "The basic interface is a phone app most people can learn in 5 minutes. We train before the disaster, not during it. We can include it in your next tabletop exercise."
"Is it secure/encrypted?" "Meshtastic supports AES-128 encryption. For served agency use over Part 15, we recommend a private channel with a strong key shared only with authorized nodes."
"Who maintains it?" "The ARES group maintains the infrastructure nodes. Each served agency location just needs a single low-cost device that runs unattended on solar power."
"We don't have budget." "A complete node costs $30 - 80. The ARES group can provide and maintain pre-positioned nodes at your facilities at no cost to you."

Training and Exercise Requirements

Before a served agency relies on mesh in an actual emergency, the following training milestones should be met:

  1. Initial orientation (30 - 60 min): Demonstrate mesh hardware, install Meshtastic app on agency-designated device, configure pre-set channel, send and receive test messages.
  2. Tabletop exercise integration: Include mesh message traffic in a tabletop exercise scenario. Evaluate whether served agency staff can successfully send and receive mesh messages during a simulated event.
  3. Field exercise: Deploy mesh nodes at served agency locations during a full field exercise. Test coverage, message delivery, and integration with EOC display systems.
  4. SOP integration: Served agency communications SOP should reference mesh as a supplemental channel, identify who is responsible for the node at each location, and document how to initiate mesh use during an activation.
  5. Annual verification: Test each served agency node annually. Replace batteries, update firmware, verify channel configuration is current.

Served Agency Integration Checklist

  • ☐ Met with served agency communications officer or OES coordinator
  • ☐ Demonstrated mesh capability during non-emergency visit
  • ☐ Identified served agency mesh liaison (person responsible for the node)
  • ☐ Installed and configured mesh node at served agency location
  • ☐ Trained served agency liaison on basic operation (send/receive messages, check battery)
  • ☐ Conducted tabletop or field exercise with mesh integration
  • ☐ Documented served agency location in ARES mesh node inventory
  • ☐ Integrated mesh into served agency communication SOP
  • ☐ Annual maintenance schedule established
  • ☐ Backup/spare node available if primary fails

No comments to display

Back to top