Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| communications [2016/01/08 11:01] – snippers | communications [2016/03/19 16:41] (current) – removed snippers | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Communications ====== | ||
| - | ===Good communication is not just relaying orders. The ability of leaders to understand what is transpiring on the battlefront is dependent on effective communication. Together this provides situational awareness and helps remove the 'fog of war'. === | ||
| - | This page will give you insight into the standard procedures & vocabulary for communications. | ||
| - | |||
| - | It is recommended you read [[platon-basics|platoon basics]] page first. | ||
| - | |||
| - | |||
| - | ====== Radio Nets and Channel Assignment ====== | ||
| - | |||
| - | This pertains to the @ACRE2 mod for Arma 3. Typically the following setup occurs: | ||
| - | * __Platoon command net__ - on the 148/ | ||
| - | * __Squad net__ - Every squad is usually issued with a unique 343 channel, At minimum the Squad leader and fireteam leaders need to have radios and be on their assigned squad channel. | ||
| - | * __Fireteam level__ - Fireteams communication is designed to be within voice range, however in some missions fireteams will use unique 343 channels. If your fireteam don't use radios it might be useful to use a pre-arranged signal such as hand signals to signal others in your fireteam to move up. | ||
| - | * __Asset nets__ - Typically if Air/ | ||
| - | |||
| - | |||
| - | |||
| - | ====== Radio Etiquette ====== | ||
| - | |||
| - | Brevity is **required** in radio comms. There are lots of people with many important things to say during a firefight, and you do not want to block that vital flow of information. Use keywords, short and clear sentences, and try to prioritize getting high priority information out first. Included is a vocabulary with many common keywords used in radio comms. \\ | ||
| - | **Think first, then talk.** | ||
| - | |||
| - | ===== Initiation ===== | ||
| - | When speaking on the radio, start by providing your unit ID and that of the unit you're attempting to contact. For example //" | ||
| - | Other units may be distracted, out of radio range or KIA, so it’s important to confirm that they are able to receive your message. The easiest way to check this is to ask for a response; //" | ||
| - | Likewise, it is important to give a counter-response to confirm that you are in a position to listen or reply to a message. Suitable responses might include //" | ||
| - | |||
| - | ===== Pause indicators ===== | ||
| - | If the message that you are relaying is particularly long, you may wish to include a ‘Break’ to take a breath or think about the next thing you’re going to say. Saying the word ‘Break’ essentially works like a comma for radio communication, | ||
| - | |||
| - | ===== Confirmation ===== | ||
| - | Once you have successfully received a message or command, remember to let the sender know that you have received the message; a simple // | ||
| - | //“Roger, Advancing”, | ||
| - | Remember that these are not absolute rules to be followed, especially when delivering an urgent message, but good radio etiquette can greatly improve communication between units and add to the immersion of the whole experience. | ||
| - | |||
| - | ===== Termination ===== | ||
| - | While “Over” terminates a turn on the back and forth of a transmission, | ||
| - | Remember: “Over” demands a response, “Out” terminates the comms. So saying “Over and out” is a conflict in its own. Don’t be THAT guy. | ||
| - | |||
| - | ====== Standardized Reports ====== | ||
| - | Standard reports are a great way to share information | ||
| - | |||
| - | ===== Contact Report ===== | ||
| - | Upon coming under contact the FTL immediately sends the Alert message to his SL. The SL will also send the alert to the Plt. CO. | ||
| - | |||
| - | Alert - “Alpha Lead this is A1 Contact wait out” | ||
| - | |||
| - | Once the FTL has got his fireteam organised and returning fire he can then send the detailed report to the SL. This will be sent up the chain of command by the squad leader. | ||
| - | Detailed Report: | ||
| - | - **Alert:** | ||
| - | - “Alpha Lead, this is A1, Contact Report” | ||
| - | - “A1, this is Alpha Lead, Send over” | ||
| - | - **What:** | ||
| - | - Infantry, Tracked Vehicle, etc | ||
| - | - **Where:** | ||
| - | - Grid/Map Marker? | ||
| - | - General Compass Bearing (N, SE, etc) plus estimated/ | ||
| - | - **What the contact is doing:** | ||
| - | - Engaging me, flanking, patrolling | ||
| - | - What you are doing about it: | ||
| - | - Engaging the enemy, observing, readying an ambush,etc | ||
| - | |||
| - | ===== SITREP ===== | ||
| - | A SITREP is a **Sit**uational **Rep**ort, which is used to provide information on the **current action** and **current location** of a unit. Alongside intel on **observed enemies**. | ||
| - | |||
| - | Example: \\ | ||
| - | // | ||
| - | **Bravo Squad Leader:** “We are heading to waypoint 3, approximately half way there from waypoint 2, no enemy contact. ”// | ||
| - | |||
| - | ===== Headcount ===== | ||
| - | The headcount is designed to to quickly gauge the effectiveness of a unit. Elements simply report how many troops are effective (alive and not injured) in their unit. The terms either effective or strong should be used. | ||
| - | |||
| - | Example: \\ | ||
| - | // | ||
| - | **Alpha squad leader:** “Command, Alpha is 10 strong.”// | ||
| - | |||
| - | ===== ACE Report ===== | ||
| - | The ACE report details **A**mmunition, | ||
| - | |||
| - | Example: \\ | ||
| - | // | ||
| - | **Alpha Squad Leader:** “Command this is Alpha, wait one” \\ | ||
| - | Alpha leader asks his men and relays. \\ | ||
| - | **Alpha Squad Leader:** “Command, this is Alpha. Ammo is good, 4 effective, No change in equipment, over”// | ||
| - | |||
| - | === Ammo Status === | ||
| - | |||
| - | This should be given in an approximate number of magazines per rifleman, and same for the AR. It can also be coupled with good or low, however, it should not be substituted for good or low. | ||
| - | |||
| - | The minimum number of magazines required by a typical soldier to pull back is 3 mags (20-30 rounds each). | ||
| - | |||
| - | //Upon giving an ACE report, if it becomes apparent there is an ammo discrepancy between subordinates, | ||
| - | === Casualty Status === | ||
| - | At the minimum the number of **effective soldiers** must be stated. It may be also be useful to go into further information e.g. //“5 up, 2 dead, 1 unconscious, | ||
| - | |||
| - | === Equipment Status === | ||
| - | Equipment covers any **asset** that provide extra capabilities such as explosives, anti-tank weapons, medical supplies, etc. It may also cover more normal assets, e.g. a lost machinegun if the gunner was killed and the weapon was not recovered. A concise list will with numbers and items is best e.g.: \\ | ||
| - | //“Used 2 AT4s, still have 1 AT4 left. We are also running low on medical supplies.”// | ||
| - | |||
| - | ====== Proactive Communications ====== | ||
| - | |||
| - | |||
| - | Leaders are not the only ones who should be talking on the squad net. Any squad member can give important contact reports or information. This would mostly concern things that are immensely useful for the squad to know immediately, | ||
| - | |||
| - | ===== Casualty ===== | ||
| - | After a firefight or engagement calms down it is wise to report back casualties. If an element leader dies it is important that someone takes over and lets the others know about it. \\ | ||
| - | ===== Task status ===== | ||
| - | Upon reaching a waypoint and/or complete a task you should inform your leader/ | ||
| - | It may also be nice to periodically check in with a status as well. | ||
| - | |||
| - | |||
| - | ====== Vocabulary ====== | ||
| - | * *-Actual - Refers to the commander of callsign *. //Example: Alpha Actual is the Alpha squad leader.// | ||
| - | * All Callsigns - Everyone on this radio net. | ||
| - | * Bail (out) - Leave/ | ||
| - | * Break - Pause in transmission. | ||
| - | * Break-Break-Break - Clear the radio net I have a priority message. | ||
| - | * Copy - I heard what you said okay. | ||
| - | * Dismount - Leave vehicle. | ||
| - | * Go firm - Stop here and prepare for engagement. | ||
| - | * How Copy - Do you hear my transmission? | ||
| - | * Incoming - Warning for artillery/ | ||
| - | * Up - how many are alive. | ||
| - | * Over - end of transmission, | ||
| - | * Out - end of transmission, | ||
| - | * Roger - Received message. | ||
| - | * Say again - Retransmit last message. | ||
| - | * Send it - Transmit your message. | ||
| - | * Set - Ready (usually used as part of maneuvers indicating to the next unit you are ready for them to make a move). | ||
| - | * Standby - More message/s coming, but wait for now. | ||
| - | * Wait One - See // | ||
| - | * Wilco - Will comply. | ||
| - | * Oscar Mike - On Mission/On the Move - This simply means we are doing the task. | ||
| - | |||
| - | ====== Appendix ====== | ||
| - | ===== Default Callsigns ===== | ||
| - | |||
| - | The default callsign to associate with the unit is placed on the left side in bold text. Infantry squads typically follow the radio alphabet, with fireteams being callsign postfixed with the fireteam number. | ||
| - | * **Command** - Platoon Command (Commander) | ||
| - | * **Alpha** - First Squad (Squad Leader) | ||
| - | * **Alpha 1** - First Squad Fireteam 1 (Team Leader) | ||
| - | * **Alpha 2** - First Squad Fireteam 2 (Team Leader) | ||
| - | * **Bravo** - Second Squad (Squad Leader) | ||
| - | * **Bravo 1** - Second Squad Fireteam 1 (Team Leader) | ||
| - | * **Bravo 2** - Second Squad Fireteam 2 (Team Leader) | ||
| - | * Other platoon assets will be assigned call signs by the mission CO/platoon commander. | ||