Preventing Failure to Communicate- Part 2, by JMD

We’re continuing to evaluate how to prevent a failure to communicate in the event that our normal, electronic communications equipment are not available to us. Yesterday, we looked as some definitions and began defining our own communications requirements. With that in mind, let’s move forward.

Options

Now that you’ve (hopefully) thought a little bit about what your communications requirements might be, let’s take a look at some possible options for the various elements.

Sender/Recipient

As I mentioned earlier, the best starting point for figuring out a communications strategy is by making a list of everyone it will need to support. For a smaller group, like a family, this may simply involve a list of all of the people in the family. However, what if an emergency arises that requires you to call for help from your neighbors? Make the list as complete as possible, and allow for potential future additions. When the group starts getting larger, like a compound or a small town, you’re better off defining communications in terms of roles. For example, anyone involved with security should probably learn how to use tactical hand signals.Someone who never leaves the vicinity of the compound probably doesn’t need to know how to use a long-distance signal lamp.

Content

Most communications that we’re familiar with tend to be a logically connected series of sounds or images that convey an idea. The range and flexibility of modern language and media allows us to convey a lot of information quickly and concisely. Technologies like the Internet allow us to exchange huge volumes of data quickly. However, in a grid-down situation where we can’t use radios, we’ll be forced to fall back on low-bandwidth technologies like signal lamps and whistles. That means that the more concisely we can structure our communications content, the better we’ll be able to communicate low-bandwidth technologies. One way we can cut down on the volume of information we actually need to transmit is by substituting simple codes for commonly used content (encoding). For example, instead of having to transmit “Emergency – send the medic.

We have someone injured by the old grain mill” using Morse code, we can create a code where the number of flashes represents the most commonly used items we need to communicate. This might look something like “flash-flash-flash, pause, flash-flash, pause, flash-flash-flash-flash” being sent by a flashlight. The first group of three flashes is the internationally-recognized code for an emergency (three signals of any type). The second group of two flashes is a code your group has defined to mean “medical emergency”. The last group of four flashes represents the code defined for the old grain mill. However, in order for this scheme to work, we need to first define lists of the most common content items we may need to communicate.

Common Content Items

A list of common content items could include items such as:

  • Types of communication
    • Information request
    • Assistance request
    • Emergency
    • Status update
    • Message relay request
    • Morse code to follow
  • Events/Activities
    • Medical emergency
    • Enemy spotted
    • Enemy engaged
    • Being pursued
    • Prepare ambush
    • Fire
    • Load carrying assistance
    • Making camp
    • Broken equipment
    • Returning to base
    • Expected arrival
    • Moving out
    • Arrived at checkpoint
    • Walking
    • Driving
    • Horseback
    • Bicycle
    • Delayed
    • Weather
  • Common locations
  • Entities
    • People
    • Patrols
    • Groups
    • Compounds
    • Towns
  • Count (numbers)
  • Distance
    • Numbers (number of digits)
    • Units (e.g. yards, miles, et cetera.)
  • Direction (North, South, East, West, et cetera.)
  • Duration
    • Number (number of digits)
    • Units (minutes, hours, days, et cetera.)
    • Time
    • Number (number of digits)
    • AM/PM
    • Early/late
    • Morning, afternoon, evening, et cetera.

The more types of standard content you can pre-define, the more you can send using simple codes; however, the tradeoff is that memorizing the content and its associated code will become more complicated as it expands.

No matter how much content you pre-define, there will always be situations that require communicating information that you haven’t thought of. In those situations, your people should be trained to communicate in simple, clear, and concise language that provide complete information and can be easily encoded. That’s why the military defines reporting mechanisms like SALUTE (Size, Activity, Location, Unit identification, Time, and Equipment), which provides an operator with a mnemonic checklist of what they need to provide when reporting an enemy sighting. You should develop your own checklists that are relevant to your situation and location.

Encoding

Encoding defines how the content is actually represented in the communication. In the previous example, the number of flashes represented (or encoded) specific items. Three flashes for an emergency, two flashes for the type of emergency (medical), and four flashes for the location (old grain mill), so the medic knows where to go. By pre-defining your content as previously discussed, you can use simple codes to represent to represent each message element, significantly simplifying your communications.

The encoding format should also define how the parts of a message fit together. For example, a message that starts with the code for “Emergency” is always immediately followed by a code indicating what type of emergency. A status report for “Returning to base” is always followed by a time unit indicator (“days”, “hours”, or “minutes”). That is followed by the number of those time units.

Numbers can be difficult to encode, particularly large numbers, since you need a scheme to handle any possible number, and you don’t want someone to have to have to send 100 flashes to indicate the enemy is 100 yards away. This is a situation where mixing encoding formats may be useful. You can use your simple number=content code for the core message, then use something like Morse code for sending the numbers, assuming your communications channel can handle both short (dot) and long (dash) sending pulses.

Encoding- Hand Signals

Another example of encoding are tactical hand signals. These are standard hand signs that police and military teams use to communicate silently when any noise, even a whisper, could get you killed. Sign language is another good form of encoding, as it can provide a comprehensive range of content quickly and silently (but it can be difficult to learn).

Encoding- Fixed Visual Signal

For persistent communications that don’t need to exchange a large volume of information, and where you have a good line of sight between the sender and receiver, a fixed visual signal is a good choice for encoding information. This can be something as simple as a splash of a certain color of paint on a tree, or something as complex as signal flags. One of the most commonly known forms of persistent flag-based communication is flying the American flag upside-down to indicate help is needed.

Encoding- Reducing Risk of Intercept with Codes and Ciphers

One other advantage of encoding is that it minimizes the risk of someone outside of the group understanding any communications they may intercept. Your own substitution code will probably be unique to your group, and there aren’t that many people out there that know Morse code (but there are some). If communications security is a significant concern for you, especially with written communications, you may want to look into using some form of code or cipher. A good choice is a book cipher. In a book cipher, the message consists of a series of numbers, representing the page number, the paragraph/verse/sentence, and the word in that section, in a book that both the sender and receiver have a copy of.

Using common books, such as a Bible or dictionary, allows a wide range of messages to be encoded/decoded across a group of people. Another option is a one-time pad or rotating cipher, where standard letters and numbers are substituted with other letters or numbers, with the substitution code changing every time a message is sent, or on a regular basis. A simple header code is frequently used to inform the receiver which version of the cipher was used to encode the message.

Handshake

Before any communication can be effectively exchanged, both the sender and the recipient have to agree upon a number of items. First, the recipient has to be ready and able to receive the communication. For normal verbal communications, this is usually as simple as saying the intended recipient’s name and waiting for them to acknowledge you. For long-distance signal lamp communications, this may involve sending a continuous signal in the direction of the recipient until you get a “ready to receive” signal back.

Details regarding the format of the message in the subsequent communication may also need to be provided by the sender. In the previous example, the receiver knew that three flashes meant an emergency; but what if the sender actually intended to send a more detailed message in Morse code, and the three flashes were an initial “S”? Your communications should always start with something (frequently referred to as a “header”) that lets the receiver know if the message is encoded and, if so, how it’s encoded. In the previous flashes example, the agreed format may be that starting with a single 3-second long “flash” means the following message will be in Morse code; otherwise it uses your standard content encoding.

Tomorrow, we’ll continue discussing “options”. There is much more on this subject.

See Also:

SurvivalBlog Writing Contest

This has been part two of a five part entry for Round 72 of the SurvivalBlog non-fiction writing contest. The nearly $11,000 worth of prizes for this round include:

First Prize:

  1. A $3000 gift certificate towards a Sol-Ark Solar Generator from Veteran owned Portable Solar LLC. The only EMP Hardened Solar Generator System available to the public.
  2. A Gunsite Academy Three Day Course Certificate. This can be used for any one, two, or three day course (a $1,195 value),
  3. A course certificate from onPoint Tactical for the prize winner’s choice of three-day civilian courses, excluding those restricted for military or government teams. Three day onPoint courses normally cost $795,
  4. DRD Tactical is providing a 5.56 NATO QD Billet upper. These have hammer forged, chrome-lined barrels and a hard case, to go with your own AR lower. It will allow any standard AR-type rifle to have a quick change barrel. This can be assembled in less than one minute without the use of any tools. It also provides a compact carry capability in a hard case or in 3-day pack (an $1,100 value),
  5. An infrared sensor/imaging camouflage shelter from Snakebite Tactical in Eureka, Montana (A $350+ value),
  6. Two cases of Mountain House freeze-dried assorted entrees in #10 cans, courtesy of Ready Made Resources (a $350 value),
  7. A $250 gift certificate good for any product from Sunflower Ammo,
  8. Two cases of meals, Ready to Eat (MREs), courtesy of CampingSurvival.com (a $180 value).

Second Prize:

  1. A Model 175 Series Solar Generator provided by Quantum Harvest LLC (a $439 value),
  2. A Glock form factor SIRT laser training pistol and a SIRT AR-15/M4 Laser Training Bolt, courtesy of Next Level Training, which have a combined retail value of $589,
  3. A gift certificate for any two or three-day class from Max Velocity Tactical (a $600 value),
  4. A transferable certificate for a two-day Ultimate Bug Out Course from Florida Firearms Training (a $400 value),
  5. A Trekker IV™ Four-Person Emergency Kit from Emergency Essentials (a $250 value),
  6. A $200 gift certificate good towards any books published by PrepperPress.com,
  7. A pre-selected assortment of military surplus gear from CJL Enterprize (a $300 value),
  8. RepackBox is providing a $300 gift certificate to their site, and
  9. American Gunsmithing Institute (AGI) is providing a $300 certificate good towards any of their DVD training courses.

Third Prize:

  1. A Royal Berkey water filter, courtesy of Directive 21 (a $275 value),
  2. A custom made Sage Grouse model utility/field knife from custom knife-maker Jon Kelly Designs, of Eureka, Montana,
  3. A large handmade clothes drying rack, a washboard, and a Homesteading for Beginners DVD, all courtesy of The Homestead Store, with a combined value of $206,
  4. Expanded sets of both washable feminine pads and liners, donated by Naturally Cozy (a $185 retail value),
  5. Two Super Survival Pack seed collections, a $150 value, courtesy of Seed for Security, LLC,
  6. Mayflower Trading is donating a $200 gift certificate for homesteading appliances,
  7. Montie Gear is donating a Y-Shot Slingshot and a $125 Montie gear Gift certificate.,
  8. Two 1,000-foot spools of full mil-spec U.S.-made 750 paracord (in-stock colors only) from www.TOUGHGRID.com (a $240 value), and

Round 72 ends on September 31st, so get busy writing and e-mail us your entry. Remember that there is a 1,500-word minimum, and that articles on practical “how to” skills for survival have an advantage in the judging.

Bookmark the permalink.



Leave a Reply

Your email address will not be published.
Anonymous comments are allowed, but will be moderated.
Note: Please read our discussion guidlelines before commenting.